On 02/11/12 01:07, Axel wrote:
Steps:
1) md c#
2) cd c#
3) gvim --remote-silent test.cs
GVim starts up and displays "E194: No alternate filename to substitute for '#'".
GVim 7.3.712 on Windows 7 (64-bit).
The error doesn't show up if --remote-silent is omitted.
When using the |clientserver|
Steps:
1) md c#
2) cd c#
3) gvim --remote-silent test.cs
GVim starts up and displays "E194: No alternate filename to substitute for '#'".
GVim 7.3.712 on Windows 7 (64-bit).
The error doesn't show up if --remote-silent is omitted.
--
You received this message from the "vim_dev" maillist.
Do n
Hi Bram!
On Sa, 20 Okt 2012, Bram Moolenaar wrote:
>
> Michael Henry wrote:
>
> > The :sandbox command seems to disallow the use of :setlocal,
> > even though it permits changing buffer-local options via :set.
> > For example, this works fine:
> >
> > vim -u NONE '+set nocp | sandbox set ts=
Hi Bram!
On So, 28 Okt 2012, Bram Moolenaar wrote:
>
> Marcin Szamotulski wrote:
>
> > Here is a way to crash vim (vim -u NONE --noplugin).
> >
> > Set an autocommand:
> >
> > au BufUnload * :call setloclist(0, [{'bufnr':1, 'lnum':1, 'col':1, 'text':
> > 'tango down'}])
> >
> > Now run:
> >
On Mo, 29 Okt 2012, Jürgen Krämer wrote:
> I can confirm this behavior on Vim 7.3.1-712 on Windows 7, compiled with
> MS-C 16.0.40219.1 (i.e., Visual Studio 2008), although it only seems to
> happen of every other input of "^".
>
> The caret is a dead-letter key and is ignored although a space is
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 89 by mazem...@gmail.com: [patch] to fix some typos in usr_21.txt
http://code.google.com/p/vim/issues/detail?id=89
Typos in usr_21.txt :
Line 285
Suppose you store you session files in the directory "~/.vim". You are
should
Help for g& states:
g& Synonym for `:%s//~/&` (repeat last substitute on all
lines with the same flags).
Mnemonic: global substitute. {not in Vi}
The part
(repeat last substitute on all lines with the same flags)
should say something like
(repeat last substitute with
On 01/11/12 09:19, Kartik Agaram wrote:
Thanks, Tony. It seems to be because of a call to mb_string2cells in
if_py_both.h:VimStrWidth. Since python isn't a feature in feature.h
I'm not sure what to check for to enable FEAT_MBYTE..
A little searching in the source gives:
FEAT_PYTHON
Pyt
Thanks, Tony. It seems to be because of a call to mb_string2cells in
if_py_both.h:VimStrWidth. Since python isn't a feature in feature.h
I'm not sure what to check for to enable FEAT_MBYTE..
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text
> You're likely looking at the "automatically generated keyword lists";
> vimCommands are generated automatically. The keywords are sorted in the
> usual ascending alphabetical order with 100 keywords per line.
Yeah I see the comments now that these lines are auto-generated:
syn keyword vimComma
On 01/11/12 01:09, Kartik Agaram wrote:
I was building vim with python support today, and I noticed that it
gives a linker error if multibyte support isn't also enabled. Is that
unexpected, or is the usual model to include features and all their
dependencies?
I don't know. Python requiring mul
On 01/11/12 01:19, Kartik Agaram wrote:
I notice many keywords in runtime/syntax/vim.vim are split across
multiple lines. For example, I assume all the lines beginning with
"syn keyword vimCommand" could logically be assumed to be a single
(very long) command. Is that accurate?
If this is correc
12 matches
Mail list logo