Hirohito Higashi wrote:
> Hi Bram and Vim developers,
>
> How to reproduce:
> 1. Prepare test_vimrc
> $ cat test_vimrc
> augroup vimrc
> autocmd!
> augroup END
> autocmd vimrc WinEnter * :execute ( (winnr('$') == 1) && (&filetype ==#
> 'qf') ? 'bwipeout!' : '')
>
> 2. Start vim
>
Shougo Matsu wrote:
> Sorry, I get it. I fixed the description.
Thanks!
--
hundred-and-one symptoms of being an internet addict:
117. You are more comfortable typing in html.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features
Gary Johnson wrote:
> The :tjump command displays the character constant '\n' incorrectly
> as '\\n'.
>
> To demonstrate this, create two files, foo.h and bar.h, each
> containing this one line:
>
> char newline = '\n';
>
> Execute:
>
> $ ctags foo.h bar.h
> $ vim -N -u NONE
>
On 2014-01-06, Gary Johnson wrote:
> The :tjump command displays the character constant '\n' incorrectly
> as '\\n'.
[Description skipped]
Assuming that this behavior is considered a defect and not a
feature, I have attached a proposed patch. It discards each
backslash in the tagaddress that is
> There is. The very good probability of such bugs is one of the reasons why I
> did not even consider adding similar global in extended funcref patch when I
> encountered similar problems (and removed no_autoload from there once it got
> my attention).
This patch replaces global with arguments
> Thank you for finding it out. I didn't notice it.
>
> Perhaps there is another problem that exists('x[y#z()]') doesn't trigger
> autoload.
There is. The very good probability of such bugs is one of the reasons why I
did not even consider adding similar global in extended funcref patch when I
On Tue, Jan 7, 2014 at 5:33 AM, ZyX wrote:
> > Yes, I am.
>
> You should not be.
>
> let d={}
> echo exists('*d[extend(g:, {"Foo#x": function("tr")})]')
>
> . f_exists() sets no_autoload to TRUE, dict_extend() runs
> var_check_func_name() which you have modified setting it back to FALSE
>
The :tjump command displays the character constant '\n' incorrectly
as '\\n'.
To demonstrate this, create two files, foo.h and bar.h, each
containing this one line:
char newline = '\n';
Execute:
$ ctags foo.h bar.h
$ vim -N -u NONE
:tjump newline
The output is:
# pri kin
2014年1月6日月曜日 22時52分34秒 UTC+9 Bram Moolenaar:
> Shougo wrote:
>
>
>
> > Thank you for the reply.
>
> > I improved the documentation in the patch.
>
>
>
> [...]
>
>
>
> > is found.
>
> > I don't give the intro message when starting Vim |:intro|.
>
> > + c don
> Yes, I am.
You should not be.
let d={}
echo exists('*d[extend(g:, {"Foo#x": function("tr")})]')
. f_exists() sets no_autoload to TRUE, dict_extend() runs var_check_func_name()
which you have modified setting it back to FALSE before f_exists ends. f_exists
should by the way save no_au
Yasuhiro Matsumoto wrote:
> $ vim
> :echo v:oldfiles
> ['/path/to/oldfile.txt', snip]
>
> $ vim -u NONE
> $ echo v:oldfiles
>
> This return empty because VV_OLDFILES isn't initialized with allocated list.
Thanks I'll add it in the todo list.
--
Amnesia is one of my favorite words, bu
On 06-Jan-2014 Bram Moolenaar wrote:
>
> Lech Lorens wrote:
>
> > Yesterday while remotely debugging some Vim scripts I discovered
> > (actually it is mentioned in the documentation) that remote_expr()
> > imposes a limitation on the type of expressions handled: the expression
> > must be a s
Hi Bram and Vim developers,
How to reproduce:
1. Prepare test_vimrc
$ cat test_vimrc
augroup vimrc
autocmd!
augroup END
autocmd vimrc WinEnter * :execute ( (winnr('$') == 1) && (&filetype ==# 'qf')
? 'bwipeout!' : '')
2. Start vim
$ vim -N -u test_vimrc
3. Open quickfix window
:
Patch 7.4.135
Problem:Missing dot in MingW test Makefile.
Solution: Add the dot. (Michael Soyka)
Files: src/testdir/Make_ming.mak
*** ../vim-7.4.134/src/testdir/Make_ming.mak2013-11-21 14:21:25.0
+0100
--- src/testdir/Make_ming.mak 2014-01-06 15:41:27.0 +0100
**
Patch 7.4.134
Problem:Spurious space in MingW Makefile.
Solution: Remove the space. (Michael Soyka)
Files: src/Make_ming.mak
*** ../vim-7.4.133/src/Make_ming.mak2013-12-11 15:06:36.0 +0100
--- src/Make_ming.mak 2014-01-06 15:37:57.0 +0100
***
*** 598,
@Bram
I often just open GVim (Windows 7, 64 bit) w/o any file name. As I always use
the OLE version of GVim, and only want/need one incarnation of GVim - so I have
to start GVim with '--remote-silent ""', resulting in the above mentioned error
message; omitting the '""' ('--remote-silent') prod
Shougo wrote:
> Thank you for the reply.
> I improved the documentation in the patch.
[...]
> is found.
> I don't give the intro message when starting Vim |:intro|.
> + c don't give the |ins-completion-menu| message. It clears the
> + previous co
What is the user case for "--remote-silent" without a file name?
Start editing an empty buffer?
> A simple solution might be the one attached below. Don't know however,
> if there are any side effects. Works for me.
It has side effects. You probably want to use ":enew" or ":new" instead
of ":dr
Ken Takata wrote:
> 2014/1/1 Wed 1:36:51 UTC+9 Bram Moolenaar wrote:
> > Ken Takata wrote:
> >
> > > Hi,
> > >
> > > I wrote a patch to fix an issue from the todo.txt:
> > >
> > > > 8 non-ASCII font names don't work. Need to convert from 'encoding'
> > > > and use
> > > > the wide func
Hi,
2014/1/1 Wed 1:36:51 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > Hi,
> >
> > I wrote a patch to fix an issue from the todo.txt:
> >
> > > 8 non-ASCII font names don't work. Need to convert from 'encoding' and
> > > use
> > > the wide functions.
> >
> > How to reproduce:
>
2014年1月6日月曜日 14時19分44秒 UTC+9 Bram Moolenaar:
> Shougo wrote:
>
>
>
> > I created the patch for adding option to disable insert completion message
> > in
>
> > shortmess.
>
> > Because, the completion message is not useful for powered users.
>
> > But it clears previous command line messages
On Sun, Jan 5, 2014 at 11:44 PM, Nikolay Pavlov wrote:
>
> On Jan 1, 2014 9:47 AM, "Yukihiro Nakadaira"
> wrote:
> >
> > Steps to reproduce:
> > $ cat ~/.vim/autoload/Foo.vim
> > let Foo#x = 0
> > $ vim -u NONE -N
> > :let Foo#x = function('tr')
> > E685: Internal error: hash_add()
> >
The autocommands TextChanged and TextChangedI are still missing in the Viml
syntax file. My patch adds it.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.ph
-
-#if SIZEOF_INT <= 3 /* use long if int is smaller than 32 bits */
-typedef long varnumber_T;
-#else
-typedef int varnumber_T;
-#endif
+typedef int64_t varnumber_T;
In my opinion, this type of change is not acceptable.
If VIM is to be targetted for 32-bit platforms, it should have the option
24 matches
Mail list logo
