Re: Syntax file contains/containedin not respected.

2011-08-25 Thread Christophe Eymard
On Thu, Aug 25, 2011 at 05:34, Benjamin Fritz fritzophre...@gmail.comwrote: On Wed, Aug 24, 2011 at 10:27 PM, Ben Fritz fritzophre...@gmail.com wrote: I cannot reproduce on Windows Vista gvim 7.3.2,06 with the syntax rules you sent earlier on the snippet you send here. I also cannot

Re: Syntax file contains/containedin not respected.

2011-08-25 Thread Christophe Eymard
On Thu, Aug 25, 2011 at 11:27, Christophe Eymard christophe.eym...@ravelsoft.com wrote: On Thu, Aug 25, 2011 at 05:34, Benjamin Fritz fritzophre...@gmail.comwrote: On Wed, Aug 24, 2011 at 10:27 PM, Ben Fritz fritzophre...@gmail.com wrote: I cannot reproduce on Windows Vista gvim 7.3.2,06

Can a function tell if % range was explicitly passed?

2011-08-25 Thread lessthanideal
function RangeTest() range echo a:firstline . . a:lastline endfunction command -range=% CallRT line1,line2call RangeTest() These two commands give the same output :CallRT :%CallRt Could the function distinguish between the two? thanks, Geoff (Background: I've tweaked the :Sort command in

Enabling/disabling keyboard layout on the fly (qwerty vs colemak)

2011-08-25 Thread Dotan Cohen
I'm just getting into Colemak and this is the VIM layout that I'm using: http://colemak.com/pub/vim/colemak.vim However, I still want to be able to switch to Qwerty on the fly. Is there a way to quickly enable/disable the Colemak mapping when I switch to Qwerty? Thanks! -- Dotan Cohen

Re: Enabling/disabling keyboard layout on the fly (qwerty vs colemak)

2011-08-25 Thread Dotan Cohen
On Thu, Aug 25, 2011 at 13:38, Dotan Cohen dotanco...@gmail.com wrote: I'm just getting into Colemak and this is the VIM layout that I'm using: http://colemak.com/pub/vim/colemak.vim However, I still want to be able to switch to Qwerty on the fly. Is there a way to quickly enable/disable the

RE: Can a function tell if % range was explicitly passed?

2011-08-25 Thread John Beckett
lessthanideal wrote: function RangeTest() range echo a:firstline . . a:lastline endfunction command -range=% CallRT line1,line2call RangeTest() These two commands give the same output :CallRT :%CallRt Could the function distinguish between the two? I noticed your change at

Re: Can a function tell if % range was explicitly passed?

2011-08-25 Thread Tim Chase
On 08/25/2011 06:17 AM, John Beckett wrote: lessthanideal wrote: function RangeTest() range echo a:firstline . . a:lastline endfunction command -range=% CallRTline1,line2call RangeTest() These two commands give the same output :CallRT :%CallRt Could the function distinguish between the

Re: how to rename a vim tab?

2011-08-25 Thread ping
thanks. but looks no luck. set tabline=abc only generate an extra line marked with abc over the entire tab line and make them invisible. at least this is in my case. I use vim inside gnome-terminal b.t.w regards ping On Aug 24, 5:07 pm, Ben Fritz fritzophre...@gmail.com wrote: On Aug 24, 9:10 

Re: Autocommand event for new buffers including startup buffer

2011-08-25 Thread Taylor Hedberg
All I'm trying to do is prevent a particular plugin (delimitMate) from automatically turning on. The plugin just auto-closes matching delimiters, like parentheses, brackets, etc. However, the auto-closing behavior turns on by default in every buffer, whereas I would prefer it to be off by default,

Re: Can a function tell if % range was explicitly passed?

2011-08-25 Thread lessthanideal
On Aug 25, 12:54 pm, Tim Chase v...@tim.thechases.com wrote: On 08/25/2011 06:17 AM, John Beckett wrote: lessthanideal wrote: function RangeTest() range    echo a:firstline . . a:lastline endfunction command -range=% CallRTline1,line2call RangeTest() These two commands give the

Re: Can a function tell if % range was explicitly passed?

2011-08-25 Thread thinca
How about this? function RangeTest(range_given, line1, line2) if a:range_given echo printf('range was given: %s - %s', a:line1, a:line2) else echo 'range was not given.' endif endfunction command -range=0 RangeTest call RangeTest(count, line1, line2) -- thinca thi...@gmail.com --

Re: path completion after 'export PATH=/tmp' (C-X C-F)

2011-08-25 Thread Benjamin R. Haskell
On Wed, 24 Aug 2011, Peng Yu wrote: On Wed, Aug 24, 2011 at 8:52 AM, Benjamin R. Haskell wrote: On Wed, 24 Aug 2011, Peng  Yu wrote: Hi, Path completion (C-X C-F) does not recognize /tmp as a path, rather it recognize PATH=/tmp as a path. I'm wondering if there is a way to change this

Re: Autocommand event for new buffers including startup buffer

2011-08-25 Thread Ben Fritz
On Aug 25, 10:28 am, Taylor Hedberg tmhedb...@gmail.com wrote: All I'm trying to do is prevent a particular plugin (delimitMate) from automatically turning on. The plugin just auto-closes matching delimiters, like parentheses, brackets, etc. However, the auto-closing behavior turns on by

Re: how to rename a vim tab?

2011-08-25 Thread Ben Fritz
On Aug 25, 8:45 am, ping songpingem...@gmail.com wrote: thanks. but looks no luck. set tabline=abc only generate an extra line marked with abc over the entire tab line and make them invisible. at least this is in my case. I use vim inside gnome-terminal b.t.w That's because 'tabline'

Re: Autocommand event for new buffers including startup buffer

2011-08-25 Thread Taylor Hedberg
Ben Fritz, Thu 2011-08-25 @ 12:30:28-0700: Just set b:loaded_delimitMate in your .vimrc. It will apply to the first buffer. Good call, but it still won't apply to other no name buffers besides the first one though. I ended up just making a small modification to the plugin, to add an option to

Re: Autocommand event for new buffers including startup buffer

2011-08-25 Thread Ben Fritz
On Aug 25, 2:43 pm, Taylor Hedberg tmhedb...@gmail.com wrote: Ben Fritz, Thu 2011-08-25 @ 12:30:28-0700: Just set b:loaded_delimitMate in your .vimrc. It will apply to the first buffer. Good call, but it still won't apply to other no name buffers besides the first one though. Does

Re: Autocommand event for new buffers including startup buffer

2011-08-25 Thread Taylor Hedberg
Ben Fritz, Thu 2011-08-25 @ 13:41:20-0700: Does BufEnter work? autocmd BufEnter * if !exists('b:created') | let b:created = 1 | let b:loaded_delimitMate = 1 | endif Yeah, in retrospect, that would probably do it. But I've fixed it another way now, so I'm not going to bother. On the other

Syntax errors in shell scripts

2011-08-25 Thread Bastien Dejean
Hi, Any idea why, in the following expression: ${UZBL_URI#*://} the '#*://' part gets highlighted as shDerefWordError? Cheers, -- Bastien -- You received this message from the vim_use maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit

Writing only the selected characters

2011-08-25 Thread Bastien Dejean
Hi, How can I write only the selected characters of a line? Suppose I'm selecting the word 'foo' from the line 'foo bar', if I issue :','w ! xclip, the output of xclip -o is going to be 'foo bar' and not 'foo'... Thanks, -- Bastien -- You received this message from the vim_use maillist. Do

Re: Syntax errors in shell scripts

2011-08-25 Thread Javier Rojas
On Thu, Aug 25, 2011 at 10:18:13AM +0200, Bastien Dejean wrote: Hi, Any idea why, in the following expression: ${UZBL_URI#*://} the '#*://' part gets highlighted as shDerefWordError? Because, by default, vim uses the sh syntax file. To use the bash syntax file by default, add the

Re: Syntax errors in shell scripts

2011-08-25 Thread ZyX
Reply to message «Re: Syntax errors in shell scripts», sent 07:06:29 26 August 2011, Friday by Javier Rojas: Because, by default, vim uses the sh syntax file. To use the bash syntax file by default, add the following line to your .vimrc file: let g:is_bash=1 Check also :help

Re: Vim writing to disk with every single keypress...why?

2011-08-25 Thread John Magolske
* Benjamin R. Haskell v...@benizi.com [110819 22:49]: On Thu, 18 Aug 2011, John Magolske wrote: When using Vim, I observe a write to disk upon every single keypress. Every single time I press a key the HD light blinks. When I start Vim like so: vim --noplugin ...I notice this is not