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
On 3/11/09, Ben Schmidt wrote:
>
> > recover use of some terminal keys for vim
> >
> > The terminal apps I use:
> >MacOS 10.4.11 -- Terminal.app
> >Linux -- rxvt
> > intercept some control keys, such as:
>
> I never had any problems except with ^Q and ^S and fixed it by just
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
On Wed, 11 Mar 2009, Harry Putnam wrote:
> vim .bashrc
> :so ~/.vimrc
>
> 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 globa
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
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
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.
> recover use of some terminal keys for vim
>
> The terminal apps I use:
>MacOS 10.4.11 -- Terminal.app
>Linux -- rxvt
> intercept some control keys, such as:
>
> 0x03 ^C intr
> 0x0F ^O discard ("flush" on Linux)
> 0x11 ^Q start
> 0x13 ^S stop
> 0x1A ^Z susp(%% to r
recover use of some terminal keys for vim
The terminal apps I use:
MacOS 10.4.11 -- Terminal.app
Linux -- rxvt
intercept some control keys, such as:
0x03 ^C intr
0x0F ^O discard ("flush" on Linux)
0x11 ^Q start
0x13 ^S stop
0x1A ^Z susp(%% to resume)
0x1C ^\ quit
T
Is there a way to make my "statusline" into "statuslines"
I have a lot of information I am putting into it that I would like to
view over at least 2 lines.
Or, possibly, is there something static that I could use to print
messages to the screen? For example I am using vim+nerdtree as a front
On Thu, Mar 12, 2009 at 12:00:38AM +0100, Dominique Pelle wrote:
>
> kba wrote:
>
> >
> > 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.
kba wrote:
> On Wed, Mar 11, 2009 at 03:47:28PM -0500, Harry Putnam wrote:
>>
>> 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 t
On Wed, Mar 11, 2009 at 03:47:28PM -0500, Harry Putnam wrote:
>
> 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 does
On Mar 11, 4:17 pm, Tim Chase wrote:
> > Small problem. How can I quickly strip of a leading space from a
> > string?
>
> > let foo = " C" [leading space]
> > Then what is a quick way to get a new variable "bar" in the script
> > such that:
>
> > bar="C" [no leading space]
>
> There are
> Small problem. How can I quickly strip of a leading space from a
> string?
>
> let foo = " C" [leading space]
> Then what is a quick way to get a new variable "bar" in the script
> such that:
>
> bar="C"[no leading space]
There are several ways...the shortest for your particular case
On Mar 11, 1:00 pm, _sc_ wrote:
> On Wednesday 11 March 2009 12:33 pm, Rahul wrote:
> i think you're looking for signs -- there's a whole help section on
> them so if you execute :h sign.txt you can start at the beginning
Vim is Amazing! I could already get this working fairly
satisfactorily.
S
On Wed, Mar 11, 2009 at 01:29:01PM -0700, fossist wrote:
>
> I read the documentation. CTRL-O behavior seemed to be pretty clear.
> But, I am unable to understand the CTRL-O behavior. Here is what I did
> after launching vim.
Be sure to also read the documentation on tags:
:he tags
> :help
> /b
On Mar 11, 11:16 am, "Gene Kwiecinski" wrote:
>
> Ooh.. Quick example: Why bother with a rather ghastly
>
>
>
>
> Caution
>
>
>
>
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
On Mar 11, 3:03 pm, Harry Putnam wrote:
> When I start vim on a file it does not source the ~/.vimrc file.
> If I souce ~/.vimrc manually after opening a file it works fine:
>
> vim .bashrc
> :so ~/.vimrc
>
> Then all the setting I have in ~/.vimrc show up. Obvious because
> syntax highlign
I read the documentation. CTRL-O behavior seemed to be pretty clear.
But, I am unable to understand the CTRL-O behavior. Here is what I did
after launching vim.
:help
/bars
CTRL-]
5k
CTRL-]
/Vim (takes the cursor to VimEnter)
CTRL-]
/dying
CTRL-]
Now I start going back but notice I mix CTRL-O an
I read the documentation. CTRL-O behavior seemed to be pretty clear.
But, I am unable to understand the CTRL-O behavior. Here is what I did
after launching vim.
:help
/bars
CTRL-]
5k
CTRL-]
/Vim (takes the cursor to VimEnter)
CTRL-]
/dying
CTRL-]
Now I start going back but notice I mix CTRL-O an
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
On Mar 11, 1:00 pm, _sc_ wrote:
> i think you're looking for signs -- there's a whole help section on
> them so if you execute :h sign.txt you can start at the beginning
>
> probably a good example of their use is by charles' relative number
> plugin
Thanks! That was exactly what I was lookin
On Wednesday 11 March 2009 12:33 pm, Rahul wrote:
>
> Is there a way in vim to somehow display metadata next to a line. Just
> the way, say, set nu displays line-numbers next to a line? This is
> useful info. but not a part of the file contents.
>
> Goal: My files have blocks of atom positions l
Is there a way in vim to somehow display metadata next to a line. Just
the way, say, set nu displays line-numbers next to a line? This is
useful info. but not a part of the file contents.
Goal: My files have blocks of atom positions like so:
DynamicAtomPositions =
0.9931842, -0.0086573, 0.173
On Mar 10, 2:09 pm, Charles Campbell
wrote:
> Try the following:
>
> au InsertEnter * if exists("syntax_on")| syn off | endif
> au InsertLeave * syn on
> au CursorMoved * if &modified && exists("syntax_on") | syn off | endif
> au BufWritePost * if !exists("syntax_on") | syn on | endif
>
> As yo
On Mar 11, 5:13 am, Matt Wozniski wrote:
> On Tue, Mar 10, 2009 at 6:32 PM, RPN wrote:
> for l in range(s+1,e)
>let atom = matchstr(getline(l),'\w\+')
>exec 'hi link L'.(l-s).' '.atom
> endfor
> endfun
> call Update()
>
> It's exactly the same issue - your syntax highlighting script mo
>>His indentation of opening braces is inconsistent.
>Yes, but it's clearer (to me) than
>for (;;)
>{CallFunction();}
Might be academic at this point, but for a single *statement* (not line)
following a for(), if(), while(), etc., enclosing braces are *not*
required. So
for(;;)
Hey matt, i missed it, and i kicked myself :)
Fact is, i read it, but since i got completion for string, i thought
the problem was elsewhere, but it wasn't !
after replacing the __STL_BEGIN_ and such, and rebuilding my ctags, my
omnicppcomplete is finally working perfectly , AFAIK
Thanks for th
On Mar 11, 1:47 am, Gary Johnson wrote:
>
> I don't think there's any way to use those options to do what he
> wants to do, though. His indentation of opening braces is
> inconsistent.
>
Yeah, I guess not.
Looks like it is time to write your own function for use in an
indentexpr. You can ha
On Wed, 2009-03-11 at 08:46 +0100, Anton Sharonov wrote:
> I have decided to move the conversation to it's own thread, since
> it is unrelated to "Best command key for use with GNU screen".
>
> > > > bill lam wrote:
> > > > > ...
> > > > >
> > > > > For the bash shell I use the vi key binding. Ty
Thank you very much you all. This is very useful.
Leandro.
--~--~-~--~~~---~--~~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Pan wrote:
> Bram Moolenaar 写道:
> > It's not like when you use "cterm=bg" that the color follows what the
> > Normal color is set to. It just uses the current value. And if there
> > is none at the moment it doesn't work.
> > If you don't care about the error, you could do this:
> > try
>
On Wed, Mar 11, 2009 at 4:22 AM, pansz wrote:
>
> Bram Moolenaar 写道:
>> It's not like when you use "cterm=bg" that the color follows what the
>> Normal color is set to. It just uses the current value. And if there
>> is none at the moment it doesn't work.
>> If you don't care about the error, yo
On Tue, Mar 10, 2009 at 6:32 PM, RPN wrote:
> But then I tried "syn off" and "syn on" manually and the bizarre
> behavior still remains. So my "syn on" seems to be having this strange
> side effect of putting the cursor at the bottom of the file. How can I
> change this? Relevant two lines from m
On Tue, Mar 10, 2009 at 8:23 PM, Notfonk wrote:
>
> Hello there, i finally resolved myself to post there because i gave
> this quite a bit of search and didn't found no solution to my problem.
Heh, you'll kick yourself if you managed to miss this, but have you seen
:help omnicpp-faq
The first e
2009/3/11 Gary Johnson :
>
> On 2009-03-10, Ben Fritz wrote:
>> On Mar 10, 10:02 am, "A. S. Budden" wrote:
>>
>>
>> > I was wondering whether it is possible to make a (minor) change to the
>> > indent style used for C code. Generally I like the style and I don't
>> > want to change much. The on
On 09/03/09 16:27, ivan budiselic wrote:
> Hi, I've searched around a bit for a solution to this problem, but
> didn't really come up with anything that works, and since it seems to be
> a pretty simple problem, I hope you won't mind too much that I'm posting
> the question here.
>
> Basically, th
Bram Moolenaar 写道:
> It's not like when you use "cterm=bg" that the color follows what the
> Normal color is set to. It just uses the current value. And if there
> is none at the moment it doesn't work.
> If you don't care about the error, you could do this:
> try
> hi Something ct
> > > sash...@gmail.com schrieb:
> > > > Hi
> > > >
> > > > As a long time VStudio user I've found it hard to figure
> > > > out the best way to switch from the current buffer to a
> > > > previously worked on buffer. VStudio keeps a history list
> > > > of the most recently used buffers and hitti
I have decided to move the conversation to it's own thread, since
it is unrelated to "Best command key for use with GNU screen".
> > > bill lam wrote:
> > > > ...
> > > >
> > > > For the bash shell I use the vi key binding. Type "esc 0" will
> > > > move to the beginning just the same as vim. In
On 2009-03-11, robert song wrote:
> hello,everyone.
> Is there any shortcut key that can quickly jump from endif to the
> corresponding ifeq in Makefile ?
If you source the matchit.vim plugin, e.g., by putting
runtime macros/matchit.vim
in your .vimrc, you can use the % key to cycle through
43 matches
Mail list logo
