Setup:
OS=Opensolaris 2008.11
vim=See full `:version output at the end
When I start vim on a file it does not source the ~/.vimrc file.
That file is actually a symlink to the hard file elsewhere.
Permissions are on both slink and hard copy:
ls -l ~/.vimrc:
lrwxrwxrwx 1 reader staff 35 [...] /ex
Shawn Walker writes:
>> What might cause ~/.vimrc to be ignored on vim start
>
> It works fine on my system, but the file is owned by me, and it's not
> a symlink.
It worked for me for a while too. But now it doesn't. To test, I
moved the actual actual file into ~/ and as I showed in OP it bel
Shawn Walker writes:
>> But still it does not get sourced when I start vim on a file.
>
> What build are you on? I'm using 106.
I´m on 108
--~--~-~--~~~---~--~~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.
kba writes:
>> But still it does not get sourced when I start vim on a file.
>
> Maybe you are using a shell alias/wrapper script and not aware of it?
> Check `which vim` and make sure that 'vim' is not an alias for 'vim -u
> /non/exsistant/vimrc' or 'vim -C' or something like that. If 'vim' is
Dominique Pelle writes:
>>> But still it does not get sourced when I start vim on a file.
>>
>> Maybe you are using a shell alias/wrapper script and not aware of it?
>> Check `which vim` and make sure that 'vim' is not an alias for 'vim -u
>> /non/exsistant/vimrc' or 'vim -C' or something like t
Ben Fritz writes:
>> Then all the setting I have in ~/.vimrc show up. Obvious because
>> syntax highlignting suddenly comes on.
>
> Are you certain that your .vimrc is not being sourced?
>
> What is the output of the :scriptnames command?
No I wasn´t I was going by the fact that when I run :s
bill lam writes:
>> Then all the setting I have in ~/.vimrc show up. Obvious because
>> syntax highlignting suddenly comes on.
>
> I would rather suspect the syntax coloring was altered during boot up.
> What if you specifically set a testing global variable inside .vimrc
> and echo that variab
Tony Mechelynck writes:
>>> As a brute-force way to determine which of the scripts sourced after
>>> your vimrc is disabling highlighting, you could move them all out of the
>>> plugins directory temporarily, verify that syntax highlighting remains
>>> enabled after your vimrc is sourced at star
Harry Putnam writes:
> Setup:
> OS=Opensolaris 2008.11
> vim=See full `:version output at the end
I think parts of this thread stayed on gmane.editors.vim or at least I
thought I saw a post here somewhere that asked me to post my vimrc.
In case anyone is still willing to help figure
Shawn Walker writes:
> The problem is that you're setting syntax on *before* you set the
> value of t_Co. Move this:
>
> " Switch syntax highlighting on, when the terminal has colors
> " Also switch on highlighting the last used search pattern.
> if &t_Co > 2 || has("gui_running")
> syntax on
Here I'm talking about the perl-support plugin available at:
http://www.vim.org/scripts/script.php?script_id=556
It seems well enough documented to quickly see how to alter the
templates to suit but how about altering a basic behavior?
After loading the above plugin, when you open a (non exist
sc writes:
> On Thursday 24 September 2009, Harry Putnam wrote:
>
>> Can anyone tell me how to do that... or maybe just write a
>> separate setting that causes the file to be chmod to 755 on
>> save.
>
> with the following in your .vimrc:
sc writes:
> On Thursday 24 September 2009, Harry Putnam wrote:
>
>> I'm guessing the part of getting dumped into a blank buffer
>> in cmd mode is not supposed to happen?
>
> ok try this:
>
> remove all checktime and FileChangedShell lines, remove the
> de
Running 7.2.238 since since late June.
I'm seeing something I haven't noticed for quite a while.
Stair stepping when I paste something into vim.
I can stop it by setting paste but then none of my insert abbrevs
(`iab') work.
I have done a fairly major update recently on my entire OS.
(Gentoo L
I wondered if anyone can show me how to write something for commenting
better than what I was able to do:
:.,$s/^## //
Replaces ^ with '## ' from current position to end of file
How can I write something that will do that same thing but for limited
area?
The Dollar sign needs to
Tim Chase writes:
> But yes, this is the "big gun" for commenting. To answer your
> original question, you can use visual mode:
>
>:vnoremap :s/^##//
>:nnoremap :.,$s/^##//
>
>:vnoremap :s/^/##/
>:nnoremap :.,$s/^/##/
Thanks... I haven looked into Luc's suggestion as yet b
Any body here using the perl-support tools available at:
http://www.vim.org/scripts/script.php?script_id=556
that can help me get a better start using them?
The readme advises you to (after installation):
Restart gVim/Vim generate the help tags
:helptags ~/.vim/doc
and look a
sc writes:
> personally i like simple solutions to things -- less to learn,
> less to maintain and debug -- i'd go with something like
>
> map :s/^/## /j
>
> then you just hold F9 down longer for bigger areas
>
Now that is very nice... thanks.
--~--~-~--~~~--
Harry Putnam writes:
> I'm pretty sure perl-support can do all kinds of wonderful things like
> that. But where are the details of how?
Err sorry... nevermind that question... I googled up some pretty good
clues.
--~--~-~--~~~---~--~~
You re
Tim Chase writes:
[...]
> Hope this helps know more about vim, mappings, and allows you to
> modify them with greater understanding.
Yes it does, and thanks for taking the time to explain in some detail.
--~--~-~--~~~---~--~~
You received this message from th
Sorry about the longwindedness It may be a bit much to ask you to
read through to the question at the end. But if you have the time
it will be appreciated on this end to hear any comments you may have.
I'm going to describe a technique I've used extensively in another
editor.
No religious wa
Ben Fritz writes:
> Demo: http://vimeo.com/4449258
> Plugin: http://www.vim.org/scripts/script.php?script_id=2611
>
> It looks like what you want, offering very powerful "skeleton" text
> insertion with just a few keystrokes, and just a few more to fill in
> the unique bits.
That does look nift
I'm a bit confused about how to go about putting plugins into vims
path.
After reading most of :h plugin. It just says to put a plugin in ~.vim
But on the two plugin tools I've downloaded to add:
xpt and perl-support
its not clear what is supposed to happen. The READMEs just say to
unpack in
Having trouble trying to use a single init (.vimrc) file for both vim
and gvim. I'd actually prefer just forget about gvim but some plugins
seem to need it... at least one that I want to learn to use. (xpt).
I pulled up lots of balderdash on google, and the 1 that actuall gave
a code example of
Robert H writes:
[...]
> I am not sure what you are describing. I have
[...]
Turned out Jason say the problem
Jason Axelson writes:
[...]
> I think it's just a simple typo. It should be gui_running with an
> underscore rather than gui-running with a hyphen.
Thanks Jason... you've got a s
Harry Putnam writes:
Typo alert
> Turned out Jason say the problem
^ saw
--~--~-~--~~~---~--~~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
John Little writes:
> On Sep 27, 3:42 am, MK wrote:
>
>> I use the XFCE Terminal (because it is better than all the others!)
>
> Slightly OT, sorry, but I'm always on the lookout for a better
> terminal.
>
> Does it allow you to control the blink rate of the cursor? I use
> gnome-terminal in K
pansz writes:
>
> To be bug-free you must use the autocmd GUI Enter to do all .gvimrc
> related stuffs.
What does that mean... in terms of what goes in .vimrc?
--~--~-~--~~~---~--~~
You received this message from the "vim_use" maillist.
For more information, v
pansz writes:
> reason:
> 1. you can switch from console vim to gvim with the command :gui
> 2. some options and settings are reset when starting the gui.
>
> in this case:
> a. .vimrc are source *without* "gui_running" defined
> b. some of the options are reset
> c. GUIEnter event and .gvimrc a
meino.cra...@gmx.de writes:
> Hi,
>
> (I am using vim (console) on Linux.)
>
> When debugging vim setting it is possible to get informations
> what code part has changed a setting/option at last as far as
> I know.
>
> Is it possible to get informations about what code has changed
> a sett
Luc Hermitte writes:
> There exist a lot of template/skeleton expander plugins. Each has
> its own format. Most of them are listed there :
> http://vim.wikia.com/wiki/Category:Automated_Text_Insertion
>
> I'm maintaining the fork of mutemplate. The expansion in
> insert-mode is done with by de
Ben Fritz writes:
[...]
> I disagree about the quality of the demo. I think that if this were a
> tutorial about how to use the plugin, I would think it poor, but I
> viewed it instead as a "hey, look at this neat plugin, download it and
> check out the docs if you're interested". With a tutori
Torsten Andre writes:
> Hello,
>
> I have a problem setting my tags path to a specific file. The tags file
> is stored within a directory I need to search for different other
> settings. Since I already know, where the tags file is to located, I'd
> like to set the tags path to the file when loa
Something has happened that is causing the ruler not to diplay the
normal line number and column number.
I'm not sure when it happened but had to be recent. I tried going
back a couple mnths in the revisions of .vimrc but sourcing that and
I still don't see the ruler... all I see is a percent
Harry Putnam writes:
> My .vimrc is posted below... is there something there that is blocking
> the ruler from being displayed.
Never mind... I found the culprit.
laststatus=2
I must have had that commented out at some time.. Setting it to 0
gives me what I'm used to. I'm
dr-dr xp writes:
> Move everything inside .vim/xpt/ to .vim/
>
> Or set 'runtimepath' to include .vim/xpt/
Thank... just the ticket.
--~--~-~--~~~---~--~~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/mai
> Move everything inside .vim/xpt/ to .vim/
>
> Or set 'runtimepath' to include .vim/xpt/
How can I make vim show me its runtimepath?
I know about $VIMRUNTIME
But that isn't the same as the runtimepath... is it?
: echo $runtimepath
:h runtimepath (Shows the default for various OS but not t
I've been going round and round with the status line and ruler
setting.
I have these in .vimrc
set ruler
set laststatus=0
If I start vim I see a
nice: 36,1 6%
Or what ever percentage I'm at.
However I do nothing more than put the xpt plugin into my path, when I
sta
Matt Wozniski writes:
>> I'm pretty sure its xpt causing the trouble.
>>
>> My test is to start vim without xpt in ~/.vim
>>
>> Then start vim after unpacking xpt into ~/.vim ... and the status line
>> is changed. And I can repeat it every time.
>
> :verbose set statusline?
>
> should confirm t
sc writes:
>> Good... but I don't understand why resourcing .vimrc or
>> manually calling: :set statusline& with vim running
>> doesn't repair whatever xpt is doing.
>
> harry -- take a deep breath, pause, and think
>
> the VimEnter autocommands are triggered when you start vim,
> not when you
Richard Pöttler writes:
> Hi,
>
> I like to try out vimscripts, to test, whether they help me with my
> editing. After a while I lost oversight of all my installed scripts and
> their current status. Trying to track them with git, which didn't help
> much, so I hacked together a perl script t
Richard Pöttler writes:
> Harry Putnam schrieb:
>> Richard Pöttler writes:
>>> I like to try out vimscripts, to test, whether they help me with my
>>> editing. After a while I lost oversight of all my installed scripts and
>>> their current status. Trying
Richard Pöttler writes:
> Harry Putnam schrieb:
>> Richard Pöttler writes:
>>> Harry Putnam schrieb:
>>>> Richard Pöttler writes:
>>> Imho the "use feature..." stuff was introduced in 5.10, and removing it
>>> shouldn't be too mu
My setup: Linux (gentoo) 2.6.33-gentoo
vim VIM - Vi IMproved 7.2
compile info inlined at the end of this post
For some time now I've been noticing when I paste scripting code
into vim I'm getting the stair stepping effect.
It didn't used to a few mnts back..
I know about p
Tony Mechelynck writes:
> According to ":help 'paste'", setting paste is not necessary in gvim,
I'm not using gvim. I should have made it clearer
> nor in a terminal where Vim handles the mouse clicks itself. So: are
> you sure you're using the same terminal as a few months ago? Are the
> mous
Gary Johnson writes:
>> Not some gnome terminal, KDE terminal or some other jive.. just a
>> regular xterm.
>
> That's how I use Vim, too. My pasting works fine, like yours used
> to. I compared by version information with yours and I didn't see
> any X- or mouse-related differences that I thou
"Benjamin R. Haskell" writes:
[...]
>> Not some gnome terminal, KDE terminal or some other jive.. just a
>> regular xterm.
>
> I also use Gentoo.
>
> xterm-256 wasn't in portage a couple months ago, so your terminal has
> certainly changed in the last few months. Using all combinations of
>
Tony Mechelynck writes:
>> Typing in an xterm:
>>xterm -version
>>XTerm(256)
>
> Hm. Here (on openSUSE Linux 11.2) the answer is:
>
> X.Org 6.8.99.903(242)
Its starting to look like that might be the culprit... my later
version of xterm I haven't installed an older version to test
ye
"Benjamin R. Haskell" writes:
> My line may have been too specific. In the bug report my previous post
> referenced[1], the line causing problems was the more general:
>
> *allowWindowOps: false
>
> I used UXTerm in mine, because... well... I use uxterm. So, maybe try
> without the class name
Harry Putnam writes:
> Looks like the fartherest back I could downgrade on current portage
> would be xterm 250.
I did try it... downgrade to 250... no help
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are reply
John Little writes:
> This is caused by the same thing as causes your "stair stepping": the
> middle mouse click is being seen and acted on by the terminal
> emulator, instead of passing it to vim. If vim gets the click it can
> act appropriately whatever mode it's in. (Vim gets an escape seque
Can anyone show an example of how to do this:
I want to wrap this:
# [HP 101202_15:55:07
# ]
Around the selected text... that is, select some text and press a key
combo ... voila... its no surrounded by:
# [HP 101202_15:55:07
# ]
Over the yrs I've acquired a fairly lengthy
If this is too off topic please if you know, send me to the
appropriate group/list/forum.
I want to use one of the perl-plugins... not really particularly
wedded to the one in vim-plugins-master. Its just what I'm currently
trying to figure out.
One big stumbling block, in the case of starting a
Probably at risk of starting a vim/emacs tug of war. I hope not.
I have small bit of code using elisp that inserts a 'Keyword' entry
around a selected region. Now I want to replicate that ability using
vim.
Example (assumes the lines are something I need to be able to
find, maybe years later):
Paul Isambert writes:
[...]
>> It will look like this when done and I've removed the one comment
>> to let the new rule work
>>
>> # Keywords: Replace old rule with new experimental rule
>> #[Keydate:130922_214226 0 - Sun Sep 22, 2013
>> # This is the default setting because bla
Paul Isambert writes:
> For any further fun, try “:help [range]”.
Oh no... you're not getting off that easy... hehe.
Honestly, you'll probably wish you never started, but I'm not getting
enough out of this bit of code to see how to make it do what I want.
Quest 1) How is the code determining
Paul Isambert writes:
> The code relies on an analysis of the “comments” option, which is
> normally set by filetype. For .conf files, I can see that the option
> is ambiguous (for our purpose), as it contains several characters for
> one-line comments, and the code picked up the wrong one (the f
Paul Isambert writes:
> I say goodbye here, the code follows. I’ll hope you’ll be satisfied
> this time (there might be glitches, I did not test the command much,
> just basic tries).
Oh boy, yup this baby works now.
Man, you went so far beyond the call of duty, and let me tell you that
it was
Any one here familiar with emacs cperl mode, that can tell me how to
get something similar when using vim?
If not familiar, `cperl-mode' trys to offer a host of short cuts that insert
quite a bit of standard code for you... a simple example is; if you
type `if' `cperl-mode' inserts:
if (_) {
59 matches
Mail list logo
