On 6/18/06, Suresh Govindachar <[EMAIL PROTECTED]> wrote:
Hello,
Since svn sources haven't been updated,
The content in subversion repository is the same with the CVS
repository, at most 1 day later. It doesn't update only because Bram
had been out for holiday since last month.
and sinc
On Sat, 17 Jun 2006, K.S.Sreeram wrote:
[EMAIL PROTECTED] wrote:
:he netrw-problems
In particular, look at P6.
Thanks for the pointer, but unfortunately doing
let g:netrw_keepdir = 0
in _vimrc file does not seem to have any effect at all!
Here's what happens:
1) run gvim.exe
2) :pwd (outpu
Gerald Lai wrote:
On Sat, 17 Jun 2006, A.J.Mechelynck wrote:
Gerald Lai wrote:
On Sat, 17 Jun 2006, Bram Moolenaar wrote:
Gerald Lai wrote:
For Vim 7, it seems that filename completion in the :cmdline ignores
case when searching for matches. For example,
:e F
matches both
foo.txt
On Sat, 17 Jun 2006, K.S.Sreeram wrote:
[EMAIL PROTECTED] wrote:
:he netrw-problems
In particular, look at P6.
Thanks for the pointer, but unfortunately doing
let g:netrw_keepdir = 0
in _vimrc file does not seem to have any effect at all!
Here's what happens:
1) run gvim.exe
2) :pwd (outpu
On Sat, 17 Jun 2006, A.J.Mechelynck wrote:
Gerald Lai wrote:
On Sat, 17 Jun 2006, Bram Moolenaar wrote:
Gerald Lai wrote:
For Vim 7, it seems that filename completion in the :cmdline ignores
case when searching for matches. For example,
:e F
matches both
foo.txt
Foo.txt
This i
Max Dyckhoff wrote:
> I have some issues with the working directory in vim that I really
> cannot get to the bottom of. I have tried looking through the help, and
> I've searched the Interweb too, to no avail, so I thought I would turn
> to this trusty mailing list!
>
> I operate a single vim in
Dan Clarke wrote:
> In my workplace, our coding standard states that we have to declare our
> variables on the next line from the variable type. The intellisense in
> vim7 doesn't work when it's like this.
>
> For example ...
>
>
> typedef struct
> {
> int
> i;
> }my_str
[EMAIL PROTECTED] wrote:
> :he netrw-problems
>
> In particular, look at P6.
Thanks for the pointer, but unfortunately doing
let g:netrw_keepdir = 0
in _vimrc file does not seem to have any effect at all!
Here's what happens:
1) run gvim.exe
2) :pwd (output: c:\Vim\vim70)
3) :e c:\Projects\Test
Quoting "K.S.Sreeram" <[EMAIL PROTECTED]>:
> Chris Sutcliffe wrote:
> > if exists('+autochdir')
> >set autochdir
> > else
> >autocmd BufEnter * silent! lcd %:p:h:gs/ /\\ /
> > endif
> >
> > In my _vimrc and it's worked beautifully in both vim 6 and vim 7.
>
> I just tried 'autochdir', and
Hari Krishna Dara wrote:
> I am observing what might be inconsistency in the order in which vim
> fires autocommands. First, ovserving the order of buffer and window events,
>
> - Using :new:
>
> WinLeave
> WinEnter
> BufLeave
> BufEnter
>
> - Using :wincmd w
>
> BufLeave
> WinLeave
> WinEnte
Marc Weber wrote:
> Hi. I don't know much about errorformats in vim yet,
> I didn't manage to match these errors
> but I get a crash ;)
> It doesn't crash when removing the none error marker lines.
> Can you help me with finding a errorformat string ?
> Or should I write another parser to remove
Gerald Lai wrote:
On Sat, 17 Jun 2006, Bram Moolenaar wrote:
Gerald Lai wrote:
For Vim 7, it seems that filename completion in the :cmdline ignores
case when searching for matches. For example,
:e F
matches both
foo.txt
Foo.txt
This is different from Vim 6 where it only matches
Chris Sutcliffe wrote:
> if exists('+autochdir')
>set autochdir
> else
>autocmd BufEnter * silent! lcd %:p:h:gs/ /\\ /
> endif
>
> In my _vimrc and it's worked beautifully in both vim 6 and vim 7.
I just tried 'autochdir', and when i'm browsing a directory, it seems to
set the current wor
Tony Mechelynck wrote:
> Gerald Lai wrote:
> > Hi all,
> >
> > [On Windows Vim 7.0, binary at ftp://ftp.vim.org/pub/vim/pc/gvim70.exe]
> > I'm having trouble getting the example in
> >
> > :help complete()
> >
> > to work. When I hit in Insert mode, I get this:
> >
> > Error detected while proce
Hi All
I'm using the CD.vim script from:
http://vim.sourceforge.net/scripts/script.php?script_id=65
to synchronize the current working directory with the current buffer.
au BufEnter * execute ":lcd " . expand("%:p:h")
On Vim7, when I browse directories (e.g :e c:\Projects)... the current
wo
Hi,
Am Freitag, 16. Jun 2006, 18:47:32 +0200 schrieb Christian Ebert:
> * Bram Moolenaar on Friday, June 16, 2006 at 17:24:20 +0200:
> > I'll leave it up to language specialists to decide whether making straße
> > uppercase should result in STRAßE or STRASSE. I thought it was STRASSE.
>
> Histor
On Sat, 17 Jun 2006, Bram Moolenaar wrote:
Gerald Lai wrote:
For Vim 7, it seems that filename completion in the :cmdline ignores
case when searching for matches. For example,
:e F
matches both
foo.txt
Foo.txt
This is different from Vim 6 where it only matches
Foo.txt
Is the
Gerald Lai wrote:
> For Vim 7, it seems that filename completion in the :cmdline ignores
> case when searching for matches. For example,
>
>:e F
>
> matches both
>
>foo.txt
>Foo.txt
>
> This is different from Vim 6 where it only matches
>
>Foo.txt
>
> Is there any way to rev
try :noic
On Sat, Jun 17, 2006 at 02:32:46AM -0700, Gerald Lai wrote:
> Hi all,
>
> For Vim 7, it seems that filename completion in the :cmdline ignores
> case when searching for matches. For example,
>
> :e F
>
> matches both
>
> foo.txt
> Foo.txt
>
> This is different from Vim 6 where
Hi all,
For Vim 7, it seems that filename completion in the :cmdline ignores
case when searching for matches. For example,
:e F
matches both
foo.txt
Foo.txt
This is different from Vim 6 where it only matches
Foo.txt
Is there any way to revert back to the old behavior?
--
Gerald
20 matches
Mail list logo
