Update ftplugin/ocaml.vim
Hi, I have updated ftplugin/ocaml.vim. 1) use buffer-local mapping instead of global one 2) provide 3) remove iabbrev (I think this is user specific setting.) Please check this patch. Regards. -- Hirotaka Hamada -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. fix-ocaml.diff Description: Binary data
Extraneous BufUnload event triggered
I run vim with no file on the command-line, so that it shows the scratch
buffer. When I then run
:e foo
to edit file 'foo', there is a BufUnload event triggered for file 'foo'. Here
is a test vim command that I use to demonstrate the issue:
autocmd BufUnload * echom "Unloaded " . expand("")
I posted this issue to stackoverflow, where user Ingo Karkat responded:
I can reproduce this with the latest Vim 7.4a.39. I guess this has to do with
the fact that Vim reuses the initial scratch buffer number (1) for the first
:edited file. Please report this problem to the vim_dev mailing list.
--
--
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.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Use of uninitialized variable
In the following code, n and p can be used without initialization.
diff -r 3f65dc9c8840 src/os_win32.c
--- a/src/os_win32.cSun Jul 21 18:59:24 2013 +0200
+++ b/src/os_win32.cMon Jul 22 22:32:43 2013 +0900
@@ -2728,21 +2728,26 @@
{
longn;
#ifdef FEAT_MBYTE
-WCHAR *p;
if (enc_codepage >= 0 && (int)GetACP() != enc_codepage)
{
-p = enc_to_utf16(name, NULL);
+WCHAR *p = enc_to_utf16(name, NULL);
if (p != NULL)
{
n = _wchmod(p, perm);
vim_free(p);
-if (n == -1 && GetLastError() != ERROR_CALL_NOT_IMPLEMENTED)
-return FAIL;
-/* Retry with non-wide function (for Windows 98). */
+if (n == -1)
+{
+if (GetLastError() != ERROR_CALL_NOT_IMPLEMENTED)
+return FAIL;
+/* Retry with non-wide function (for Windows 98). */
+n = _chmod(name, perm);
+}
}
+else
+n = _chmod(name, perm);
}
-if (p == NULL)
+else
#endif
n = _chmod(name, perm);
if (n == -1)
--
Yukihiro Nakadaira - yukihiro.nakada...@gmail.com
--
--
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.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
default value of variable VIM changed?
Was it changed the default value for the variable VIM? I used to have VIM=C:\Vim and by updating from 7.4a.35 to 7.4a.39 I get VIM=C:\Vim\vim73 Many thanks in advance, -- Cesar -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Vim 7.4a ready for beta testing (test96 FAILED)
On Mon, Jul 8, 2013 at 9:51 AM, wrote: > Bram Moolenaar wrote: > > > Announcing: Vim (Vi IMproved) version 7.4a BETA > > > > This is the first BETA release of Vim 7.4. > > > > Please check that the distribution is OK. I haven't done one for a long > > time. Report anything that isn't right. That includes a crash but also > > a typo in the documentation or a missing file. > > mid-2010 macbookpro > macosx-10.6.8 > gcc-4.2.1 > > obtained vim-7.4a.002 via hg (same result via ftp). > > configure \ > --disable-darwin \ > --with-x \ > --enable-gui=motif \ > --enable-multibyte \ > --with-mac-arch=current \ > --with-features=huge \ > --disable-acl > > Test results: > test96 FAILED > TEST FAILURE > > diff -u test96.ok test96.failed > --- test96.ok 2013-07-08 10:12:36.0 +1000 > +++ test96.failed 2013-07-08 10:15:31.0 +1000 > @@ -4,6 +4,8 @@ >- quickfix claims that the file name displayed is: test://bar.txt > Test B: >- number of window open: 2 > +Test B: > + - number of window open: 2 > Test C: >- 'buftype' of the location list window: quickfix >- buffer displayed in the 2nd window: test://quux.txt > > i.e. the "Test B" section of the file is repeated. > test96 failed on Windows Vista, too. Maybe I found the cause of this problem. test96 depends on cursor position after switching buffer. But it is not stable. Try the following script: call setline(1, range(10)) for i in range(5) new buffer 1 let &l:foldminlines = i call cursor(i, 1) endfor for i in range(5) quit endfor for i in range(5) new buffer 1 endfor Now, each window have different cursor position and different window-local option value (&l:foldminlines in this case). I guess: win_free() doesn't clear buf->b_wininfo. After freeing memory, win_alloc() can return same address. Then, buf->b_wininfo is re-used for newly allocated window in spite of diffrent window. -- Yukihiro Nakadaira - yukihiro.nakada...@gmail.com -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Extraneous BufUnload event triggered
On 17:51 Mon 22 Jul , Bram Moolenaar wrote:
>
> Pokey Rule wrote:
>
> > I run vim with no file on the command-line, so that it shows the
> > scratch buffer. When I then run
> >
> > :e foo
> >
> > to edit file 'foo', there is a BufUnload event triggered for file
> > 'foo'. Here is a test vim command that I use to demonstrate the issue:
> >
> > autocmd BufUnload * echom "Unloaded " . expand("")
> >
> > I posted this issue to stackoverflow, where user Ingo Karkat responded:
> >
> > I can reproduce this with the latest Vim 7.4a.39. I guess this has to
> > do with the fact that Vim reuses the initial scratch buffer number (1)
> > for the first :edited file. Please report this problem to the vim_dev
> > mailing list.
>
> Thanks, I'll add a note to the todo list.
>
> --
> hundred-and-one symptoms of being an internet addict:
> 8. You spend half of the plane trip with your laptop on your lap...and your
>child in the overhead compartment.
>
> /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\ an exciting new programming language -- http://www.Zimbu.org///
> \\\help me help AIDS victims -- http://ICCF-Holland.org///
>
Hello,
Here is a patch. I tested that it works with :cclose, and :lclose
commands, i.e. does not block BufUnload on them.
Are there any other commands that should be checked?
Regards,
Marcin Szamotulski
--
--
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.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
diff -r 3f65dc9c8840 src/buffer.c
--- a/src/buffer.c Sun Jul 21 18:59:24 2013 +0200
+++ b/src/buffer.c Mon Jul 22 17:48:13 2013 +0100
@@ -566,7 +566,8 @@
int is_curbuf = (buf == curbuf);
buf->b_closing = TRUE;
-apply_autocmds(EVENT_BUFUNLOAD, buf->b_fname, buf->b_fname, FALSE, buf);
+if (!(buf->b_fname == NULL && buf->b_ffname != NULL))
+ apply_autocmds(EVENT_BUFUNLOAD, buf->b_fname, buf->b_fname, FALSE, buf);
if (!buf_valid(buf)) /* autocommands may delete the buffer */
return;
if ((flags & BFA_DEL) && buf->b_p_bl)
Issue 154 in vim: gVim 7.4a beta crashes from time to time
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 154 by dief...@gmail.com: gVim 7.4a beta crashes from time to time http://code.google.com/p/vim/issues/detail?id=154 What steps will reproduce the problem? 1. use awesome wm 2. try to save a file in gvim gvim crashes sometimes after saving a file and I cannot reproduce this by intent. [xcb] Unknown request in queue while dequeuing gvim: Fatal IO error 11 (Resource temporarily unavailable) on X server unix/:0. [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. gvim: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed. Vim: Caught deadly signal ABRT Vim: Finished. " My Bundles Bundle 'gmarik/vundle' Bundle 'Lokaltog/powerline' Bundle 'git://repo.or.cz/vcscommand.git' Bundle 'tpope/vim-fugitive' Bundle 'tpope/vim-markdown' Bundle 'vim-diekeys' Bundle 'tpope/vim-obsession' Bundle 'tpope/vim-repeat.git' Bundle 'tpope/vim-abolish.git' Bundle 'tpope/vim-surround.git' Bundle 'Raimondi/delimitMate' Bundle 'rstacruz/sparkup' Bundle 'kien/ctrlp.vim' Bundle 'majutsushi/tagbar' Bundle 'techlivezheng/vim-plugin-tagbar-phpctags' Bundle 'jeetsukumaran/vim-buffergator' Bundle 'chrisbra/NrrwRgn' Bundle 'chin4ski/Mark--Karkat' Bundle 'scrooloose/nerdtree' Bundle 'scrooloose/nerdcommenter' Bundle 'scrooloose/syntastic' Bundle 'Lokaltog/vim-easymotion' Bundle 'mileszs/ack.vim' Bundle 'jelera/vim-javascript-syntax' Bundle 'vim-scripts/vim-javascript' Bundle 'hynek/vim-python-pep8-indent' Bundle 'michaeljsmith/vim-indent-object' Bundle 'klen/python-mode' Bundle 'hdima/python-syntax' Bundle 'Valloric/YouCompleteMe' Bundle 'evidens/vim-twig.git' Bundle 'Glench/Vim-Jinja2-Syntax' Bundle 'lepture/vim-jinja' Bundle 'sophacles/vim-bundle-mako' Bundle 'groenewege/vim-less' Bundle 'miripiruni/vim-better-css-indent' Bundle 'hail2u/vim-css3-syntax' Bundle 'gregsexton/MatchTag' Bundle 'khorser/vim-rst-ftplugin' Bundle 'vim-scripts/genshi.vim' Bundle 'lukaszb/vim-web-indent' Bundle 'danro/rename.vim' Bundle 'L9' Bundle 'FuzzyFinder' -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Issue 153 in vim: adding changelog entries to spec files using \c doesn't work properly
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 153 by martin.g...@gmail.com: adding changelog entries to spec files using \c doesn't work properly http://code.google.com/p/vim/issues/detail?id=153 What steps will reproduce the problem? 1. open an (rpm) spec file 2. go to the %changelog section 3. type \c in command mode What is the expected output? What do you see instead? A new changelog entry with date, name + email address, and version-release number pair is supposed to be inserted. Currently, the version and release numbers are missing. Also, the date contains translated day of week and month abbreviations based on the current locale instead of the international ones. What version of the product are you using? On what operating system? Vim 7.4 BETA patchlevel 39 (Linux and Windows, x86-64) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: default value of variable VIM changed?
Cesar Romani wrote: > Was it changed the default value for the variable VIM? > I used to have VIM=C:\Vim and by updating from 7.4a.35 to 7.4a.39 I get > VIM=C:\Vim\vim73 > > Many thanks in advance, I don't think anything changed. Vim tries to remove "vim74a" from the path, thus if it's actually "vim73" then that will fail. Did you install Vim in the wrong directory? -- hundred-and-one symptoms of being an internet addict: 7. You finally do take that vacation, but only after buying a cellular modem and a laptop. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 154 in vim: gVim 7.4a beta crashes from time to time
On Jul 22, 2013 9:06 PM, wrote: > > Status: New > Owner: > Labels: Type-Defect Priority-Medium > > New issue 154 by dief...@gmail.com: gVim 7.4a beta crashes from time to time > http://code.google.com/p/vim/issues/detail?id=154 > > What steps will reproduce the problem? > 1. use awesome wm > 2. try to save a file in gvim > > gvim crashes sometimes after saving a file and I cannot reproduce this by intent. > > [xcb] Unknown request in queue while dequeuing > gvim: Fatal IO error 11 (Resource temporarily unavailable) on X server unix/:0. > [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called > [xcb] Aborting, sorry about that. > gvim: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed. > Vim: Caught deadly signal ABRT > Vim: Finished. > > > " My Bundles > Bundle 'gmarik/vundle' > Bundle 'Lokaltog/powerline' This one uses threads in some segments. GVim does not initialize threads and thus there may be weird problems. > Bundle 'git://repo.or.cz/vcscommand.git' > Bundle 'tpope/vim-fugitive' > Bundle 'tpope/vim-markdown' > Bundle 'vim-diekeys' > Bundle 'tpope/vim-obsession' > Bundle 'tpope/vim-repeat.git' > Bundle 'tpope/vim-abolish.git' > Bundle 'tpope/vim-surround.git' > Bundle 'Raimondi/delimitMate' > Bundle 'rstacruz/sparkup' > Bundle 'kien/ctrlp.vim' > Bundle 'majutsushi/tagbar' > Bundle 'techlivezheng/vim-plugin-tagbar-phpctags' > Bundle 'jeetsukumaran/vim-buffergator' > Bundle 'chrisbra/NrrwRgn' > Bundle 'chin4ski/Mark--Karkat' > Bundle 'scrooloose/nerdtree' > Bundle 'scrooloose/nerdcommenter' > Bundle 'scrooloose/syntastic' > Bundle 'Lokaltog/vim-easymotion' > Bundle 'mileszs/ack.vim' > Bundle 'jelera/vim-javascript-syntax' > Bundle 'vim-scripts/vim-javascript' > Bundle 'hynek/vim-python-pep8-indent' > Bundle 'michaeljsmith/vim-indent-object' > Bundle 'klen/python-mode' > Bundle 'hdima/python-syntax' > Bundle 'Valloric/YouCompleteMe' > Bundle 'evidens/vim-twig.git' > Bundle 'Glench/Vim-Jinja2-Syntax' > Bundle 'lepture/vim-jinja' > Bundle 'sophacles/vim-bundle-mako' > Bundle 'groenewege/vim-less' > Bundle 'miripiruni/vim-better-css-indent' > Bundle 'hail2u/vim-css3-syntax' > Bundle 'gregsexton/MatchTag' > Bundle 'khorser/vim-rst-ftplugin' > Bundle 'vim-scripts/genshi.vim' > Bundle 'lukaszb/vim-web-indent' > Bundle 'danro/rename.vim' > Bundle 'L9' > Bundle 'FuzzyFinder' > > -- > You received this message because this project is configured to send all issue notifications to this address. > You may adjust your notification preferences at: > https://code.google.com/hosting/settings > > -- > -- > 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.php > > ---You received this message because you are subscribed to the Google Groups "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Issue 155 in vim: feature request: Option for keeping cursor position while scrolling by mouse
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 155 by gade...@gmail.com: feature request: Option for keeping cursor position while scrolling by mouse http://code.google.com/p/vim/issues/detail?id=155 Right now, vim always shows cursor in viewable part of window by changing its position as viewport changes, even when user is scrolling by mouse wheel. Personally, I hate this. I understand that vim's philosophy is that you should never use a mouse, but mouse wheel is perfect for looking around document and no keyboard key can replace this functionality properly: users use mouse wheel to see what is out of the visible part of screen and no key replaces this properly. I don't think anybody use mouse wheel scrolling in vim for positioning cursor on exact line as they want as this method is highly inaccurate or slow for this - user have to scroll very slow to not overscroll desired line - if he does and still want to do this by mouse, he will need to scroll back by all of the height of buffer + missed lines because cursor stays on position if it does not reach border of viewport. Because of this, if user want to go to new position below viewport, he instead use mouse scrolling only to position viewport to part of document where approximately is located line which user want to edit and then he will most probably use mouse click (they are still holding mouse right?) or use gg instead (or similar movement commands) as he now see line number. I understand that some users maybe prefer it the way it is now - e.g. people using relative line numbering thanks to this feature don't have to type 1350gg to move to desired line, but instead 15+ as cursor is closer to desired line. That's why I'm asking for option for us. If this is implemented, people can use mouse wheel in vim not only for changing cursor position to new unknown location (outside of view) but they can use it too in a way that they can scroll down/up to see what is below/above viewport, but when they want to continue in editing line they were editing, they just do it and viewport automatically changes to cursor position. If user want do this now without this proposed option, he has to use mark - and if he is in other mode, he have to exit this mode and then enter to this mode again (or use in insert mode or key binding, doesn't matter still a lot more unergonomic than doing nothing). Because jumplist changes as cursor changes its position line by line when scrolling out of viewport, it can't be used comfortably either - because user doesn't know position of item in jumplist as it changed multiple times since then. Also, it wouldn't manipulate with selection if user is in visual mode as it is now. As another added benefits, scrolling with this options would be faster and more neat - without flickering cursor which position constantly changes. It would be faster because vim won't have to: - calculate new location of cursor (start/end of line, start/end of words or similar behaviour which vim has now) - move and display cursor to new position - change active line background if option cursorline is set - highlight current line number - expand current visual selection -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Issue 156 in vim: Vim exits with error "ICE default IO error handler doing an exit(), pid = 6769, errno = 32"
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 156 by dominiqu...@gmail.com: Vim exits with error "ICE default IO error handler doing an exit(), pid = 6769, errno = 32" http://code.google.com/p/vim/issues/detail?id=156 Summary: Vim exits with the error: ICE default IO error handler doing an exit(), pid = 6769, errno = 32 What steps will reproduce the problem? 1. In a terminal, run: $ for i in $(seq 1 60); do echo foo; sleep 1; done | vim - 2. Wait for about a minute and vim will exit with this error message: "-stdin-" 60L, 240CICE default IO error handler doing an exit(), pid = 6769, errno = 32 What is the expected output? What do you see instead? Vim should not exit with such an error. It should display instead 60 lines containing "foo". What version of the product are you using? On what operating system? I'm using vim-7.4a.39 BETA on Linux x86_64 (xubuntu-12.10). In case it matters, Vim was configured with: ./configure --enable-gui=gtk2 --with-features=huge --enable-pythoninterp=dynamic --enable-python3interp=dynamic --enable-tclinterp=yes --enable-rubyinterp=dynamic --enable-mzschemeinterp --enable-luainterp=dynamic Please provide any additional information below. Interestingly, reducing 60 to 55 in the above command does trigger the error anymore. In other words, the following command works all the time: $ for i in $(seq 1 55); do echo foo; sleep 1 ; done | vim - I also see that the default vim with xubuntu-12.10 (that vim-7.3.547 in /usr/bin/vim) does not have this bug. So either it's a regression introduced recently, or a different compilation option triggers the bug or not. I happen to find this bug because I ran something like this in a slow svn repository: $ svn log | vim - This caused vim to exit with the "ICE default IO error handler doing an exit()" error. After trial and error, I found that I could reproduce this bug using a more reproducible command: $ for i in $(seq 1 60); do echo foo; sleep 1; done | vim - -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Extraneous BufUnload event triggered
Pokey Rule wrote:
> I run vim with no file on the command-line, so that it shows the
> scratch buffer. When I then run
>
> :e foo
>
> to edit file 'foo', there is a BufUnload event triggered for file
> 'foo'. Here is a test vim command that I use to demonstrate the issue:
>
> autocmd BufUnload * echom "Unloaded " . expand("")
>
> I posted this issue to stackoverflow, where user Ingo Karkat responded:
>
> I can reproduce this with the latest Vim 7.4a.39. I guess this has to
> do with the fact that Vim reuses the initial scratch buffer number (1)
> for the first :edited file. Please report this problem to the vim_dev
> mailing list.
Thanks, I'll add a note to the todo list.
--
hundred-and-one symptoms of being an internet addict:
8. You spend half of the plane trip with your laptop on your lap...and your
child in the overhead compartment.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 156 in vim: Vim exits with error "ICE default IO error handler doing an exit(), pid = 6769, errno = 32"
Comment #1 on issue 156 by dominiqu...@gmail.com: Vim exits with error "ICE default IO error handler doing an exit(), pid = 6769, errno = 32" http://code.google.com/p/vim/issues/detail?id=156 The bug does not happen when starting vim with the -X option. So this works: $ for i in $(seq 1 60); do echo foo; sleep 1; done | vim -X - vim-7.3.547 in /usr/bin/vim (xubuntu-12.10) is not affected by this bug because it is built without X11 feature. But the same version recompiled with +X11 feature has the bug. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Vim slow after big count insert
Dimitar DIMITROV wrote: > > There is no use case > If you do something stupid by accident most vim operations can be > aborted by ctrl-c (exception: python, rbuy, .. scripts) Try to abort it you will see the success you have. > So there is still nothing to fix or talk about unless there is a use > case. > > Marc Weber I tried this problem with both 100iHello 100iHello In both cases ctrl-c worked just fine to break the operation. I used vim 7.4a.35 on a linux system when trying this. Regards, C Campbell -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [patch] fixed typos in help files
Dominique wrote: > Attached patch fixes a few typos in help files. Thanks! -- hundred-and-one symptoms of being an internet addict: 9. All your daydreaming is preoccupied with getting a faster connection to the net: 28.8...ISDN...cable modem...T1...T3. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Update ftplugin/ocaml.vim
Markus Mottl wrote: > Hi Hirotaka, > > thanks for the patches, I have applied them to my files. > > What is actually the best way to contribute updates to the Vim > maintainers these days? I see you have switched to Mercurial, which > is great, because I'm also an avid user. Is there a way to submit > pull requests? I don't know much about the workflow on Google Code. > I have moved all my repositories to Bitbucket a long time ago, because > it made project management with Mercurial shockingly easy. Just email the update file to me. Then it's easy for me to check for any differences (and sometimes catch changes already in the distribution that didn't flow back to the maintainer). I also run a script to check for mistakes before submitting the updated files. -- hundred-and-one symptoms of being an internet addict: 10. And even your night dreams are in HTML. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch for built in javascript.vim and css.vim
Amadeus Demarzi wrote:
> This patch fixes javascript.vim and css.vim from clobbering plugin syntaxes
> when sourced via html.vim.
>
> Would it be possible to get this in for 7.4?
>
> More details here:
> https://groups.google.com/forum/#!topic/vim_dev/4Idz6Em2ZuU
>
> It's a long explanation, so this would be the TL;DR for it
Makes sense. It can be reduced to one elseif:
elseif exists("b:current_syntax") && b:current_syntax == 'css'
finish
endif
--
"How is your new girlfriend?"
"90-60-90 man!"
"What, pale purple?"
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch for built in javascript.vim and css.vim
On Monday, July 22, 2013 1:50:39 PM UTC-7, Bram Moolenaar wrote:
> Amadeus Demarzi wrote:
>
>
>
> > This patch fixes javascript.vim and css.vim from clobbering plugin syntaxes
> > when sourced via html.vim.
>
> >
>
> > Would it be possible to get this in for 7.4?
>
> >
>
> > More details here:
>
> > https://groups.google.com/forum/#!topic/vim_dev/4Idz6Em2ZuU
>
> >
>
> > It's a long explanation, so this would be the TL;DR for it
>
>
>
> Makes sense. It can be reduced to one elseif:
>
>
>
> elseif exists("b:current_syntax") && b:current_syntax == 'css'
>
> finish
>
> endif
>
>
>
>
>
> --
>
> "How is your new girlfriend?"
>
> "90-60-90 man!"
>
> "What, pale purple?"
>
>
>
> /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
>
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
>
> \\\ an exciting new programming language -- http://www.Zimbu.org///
>
> \\\help me help AIDS victims -- http://ICCF-Holland.org///
This is true, I can amend the patch and resubmit if you'd like?
Thanks for the response!
--
--
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.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Update ftplugin/ocaml.vim
Hirotaka, I had to undo part of the patch. There seems to be a strange performance problem with the version of OCamlSwitch. Switching becomes really slow with it. Please refer to my Bitbucket repository (not a clone of the Vim-repository) for the latest files, which do seem to work as usual. Maybe you can find out what's going on: https://bitbucket.org/mmottl/vim-files Regards, Markus On Sun, Jul 21, 2013 at 12:27 PM, Hirotaka Hamada wrote: > Hi, > > I have updated ftplugin/ocaml.vim. > > 1) use buffer-local mapping instead of global one > 2) provide > 3) remove iabbrev (I think this is user specific setting.) > > Please check this patch. > > Regards. > > -- > Hirotaka Hamada -- Markus Mottlhttp://www.ocaml.infomarkus.mo...@gmail.com -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
gvim handling Ctrl+NonLatinKeys
Hi group. I'm running vim/gvim on Linux with ru_RU.UTF-8 locale and have a problem for which I can't find an answer. Basically, gvim doesn't handle Ctrl-key if key is a cyrillic key. For example, I have W and Ц sharing same key on my keyboard. In Insert mode, C-W deletes a word as usual, but C-Ц just displays Ц as if no Ctrl was pressed. I've checked X event with xev. It detects W as W, Ц as Ц, C-W as С-W and С-Ц as C-W as it should. Xterm (and console vim under xterm) works correctly too. Please help! Sergey Also, looks like StackOverflow question describes similar situation for Esperanto: http://stackoverflow.com/questions/16013290/shortcut-with-ctrl-doest-work-in-gvim -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: default value of variable VIM changed?
On 22/07/2013 10:51 a.m., Bram Moolenaar wrote: > > Cesar Romani wrote: > >> Was it changed the default value for the variable VIM? >> I used to have VIM=C:\Vim and by updating from 7.4a.35 to 7.4a.39 I get >> VIM=C:\Vim\vim73 >> >> Many thanks in advance, > > I don't think anything changed. Vim tries to remove "vim74a" from the > path, thus if it's actually "vim73" then that will fail. > Did you install Vim in the wrong directory? > Yes, that was it. I installed Vim on vim73 directory. Then I installed it on vim74a directory and everything is working OK. Sorry for the noise. Regards, -- Cesar -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Use of uninitialized variable
Yukihiro Nakadaira wrote: > In the following code, n and p can be used without initialization. Thanks. I'll put it at the top of the todo list. -- The Feynman problem solving Algorithm: 1) Write down the problem 2) Think real hard 3) Write down the answer /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Update ftplugin/ocaml.vim
Ok, I'll send you the latest files once some minor issues have been worked out. I'll use your Mercurial repository in the future to make sure that I'm working with the latest version of all files. Would it improve your workflow if I cloned the Vim-repository on Bitbucket and sent you an email with the appropriate pull command whenever new files should be released? That way you could use Mercurial right off the bat to deal with my incoming patches. Regards, Markus On Mon, Jul 22, 2013 at 4:50 PM, Bram Moolenaar wrote: > > > Markus Mottl wrote: > >> Hi Hirotaka, >> >> thanks for the patches, I have applied them to my files. >> >> What is actually the best way to contribute updates to the Vim >> maintainers these days? I see you have switched to Mercurial, which >> is great, because I'm also an avid user. Is there a way to submit >> pull requests? I don't know much about the workflow on Google Code. >> I have moved all my repositories to Bitbucket a long time ago, because >> it made project management with Mercurial shockingly easy. > > Just email the update file to me. Then it's easy for me to check for > any differences (and sometimes catch changes already in the distribution > that didn't flow back to the maintainer). I also run a script to check > for mistakes before submitting the updated files. > > -- > hundred-and-one symptoms of being an internet addict: > 10. And even your night dreams are in HTML. > > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > \\\ an exciting new programming language -- http://www.Zimbu.org/// > \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- Markus Mottlhttp://www.ocaml.infomarkus.mo...@gmail.com -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 154 in vim: gVim 7.4a beta crashes from time to time
give a try for vim-airline. 在 2013-7-23 上午2:01，"Nikolay Pavlov" 写道： > > On Jul 22, 2013 9:06 PM, wrote: > > > > Status: New > > Owner: > > Labels: Type-Defect Priority-Medium > > > > New issue 154 by dief...@gmail.com: gVim 7.4a beta crashes from time to > time > > http://code.google.com/p/vim/issues/detail?id=154 > > > > What steps will reproduce the problem? > > 1. use awesome wm > > 2. try to save a file in gvim > > > > gvim crashes sometimes after saving a file and I cannot reproduce this > by intent. > > > > [xcb] Unknown request in queue while dequeuing > > gvim: Fatal IO error 11 (Resource temporarily unavailable) on X server > unix/:0. > > [xcb] Most likely this is a multi-threaded client and XInitThreads has > not been called > > [xcb] Aborting, sorry about that. > > gvim: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion > `!xcb_xlib_unknown_req_in_deq' failed. > > Vim: Caught deadly signal ABRT > > Vim: Finished. > > > > > > " My Bundles > > Bundle 'gmarik/vundle' > > Bundle 'Lokaltog/powerline' > > This one uses threads in some segments. GVim does not initialize threads > and thus there may be weird problems. > > > Bundle 'git://repo.or.cz/vcscommand.git' > > Bundle 'tpope/vim-fugitive' > > Bundle 'tpope/vim-markdown' > > Bundle 'vim-diekeys' > > Bundle 'tpope/vim-obsession' > > Bundle 'tpope/vim-repeat.git' > > Bundle 'tpope/vim-abolish.git' > > Bundle 'tpope/vim-surround.git' > > Bundle 'Raimondi/delimitMate' > > Bundle 'rstacruz/sparkup' > > Bundle 'kien/ctrlp.vim' > > Bundle 'majutsushi/tagbar' > > Bundle 'techlivezheng/vim-plugin-tagbar-phpctags' > > Bundle 'jeetsukumaran/vim-buffergator' > > Bundle 'chrisbra/NrrwRgn' > > Bundle 'chin4ski/Mark--Karkat' > > Bundle 'scrooloose/nerdtree' > > Bundle 'scrooloose/nerdcommenter' > > Bundle 'scrooloose/syntastic' > > Bundle 'Lokaltog/vim-easymotion' > > Bundle 'mileszs/ack.vim' > > Bundle 'jelera/vim-javascript-syntax' > > Bundle 'vim-scripts/vim-javascript' > > Bundle 'hynek/vim-python-pep8-indent' > > Bundle 'michaeljsmith/vim-indent-object' > > Bundle 'klen/python-mode' > > Bundle 'hdima/python-syntax' > > Bundle 'Valloric/YouCompleteMe' > > Bundle 'evidens/vim-twig.git' > > Bundle 'Glench/Vim-Jinja2-Syntax' > > Bundle 'lepture/vim-jinja' > > Bundle 'sophacles/vim-bundle-mako' > > Bundle 'groenewege/vim-less' > > Bundle 'miripiruni/vim-better-css-indent' > > Bundle 'hail2u/vim-css3-syntax' > > Bundle 'gregsexton/MatchTag' > > Bundle 'khorser/vim-rst-ftplugin' > > Bundle 'vim-scripts/genshi.vim' > > Bundle 'lukaszb/vim-web-indent' > > Bundle 'danro/rename.vim' > > Bundle 'L9' > > Bundle 'FuzzyFinder' > > > > -- > > You received this message because this project is configured to send all > issue notifications to this address. > > You may adjust your notification preferences at: > > https://code.google.com/hosting/settings > > > > -- > > -- > > 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.php > > > > ---You received this message because you are subscribed to the Google > Groups "vim_dev" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to vim_dev+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > -- > 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.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vim_dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Vim slow after big count insert
On Jul 20, 2013 2:28 AM, "Gary Johnson" wrote: > > On 2013-07-19, Dimitar DIMITROV wrote: > > Hi Dimitar, > > It would be a big help to those of us with threading mail readers if > you would be sure that your replies include "Re: " at the start of > the Subject. This has nothing to do with threads. There is a special field added to messages when you reply that contains unique ID of the message being replied to and *this* field makes mail readers able to arrange messages correctly. > Thanks, > Gary > > -- > -- > 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.php > > --- > You received this message because you are subscribed to the Google Groups "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[OT] Mail threading (Was: Re: Vim slow after big count insert)
On Tue, Jul 23, 2013 at 07:39:12AM +0400, Nikolay Pavlov wrote: > On Jul 20, 2013 2:28 AM, "Gary Johnson" wrote: > > > > On 2013-07-19, Dimitar DIMITROV wrote: > > > > Hi Dimitar, > > > > It would be a big help to those of us with threading mail readers if > > you would be sure that your replies include "Re: " at the start of > > the Subject. > > This has nothing to do with threads. There is a special field added to > messages when you reply that contains unique ID of the message being > replied to and *this* field makes mail readers able to arrange messages > correctly. That depends on the mail reader. Even with MUAs that follow the Message-ID/In-Reply-To chains, it's not uncommon to treat a topic change as a new thread. For ones that don't honor the IDs, the subject is usually used instead. Regardless, Dimitar's emails don't even have the In-Reply-To header set. The X-Mailer header claims to be YahooMailWebService, so I doubt there's much that he can do to fix it short of deciding to use a more standard, standalone MUA instead of (I assume) their web interface. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Vim slow after big count insert
On 2013-07-23, Nikolay Pavlov wrote: > > On Jul 20, 2013 2:28 AM, "Gary Johnson" wrote: > > > > On 2013-07-19, Dimitar DIMITROV wrote: > > > > Hi Dimitar, > > > > It would be a big help to those of us with threading mail readers if > > you would be sure that your replies include "Re: " at the start of > > the Subject. > > This has nothing to do with threads. There is a special field added to > messages > when you reply that contains unique ID of the message being replied to and > *this* field makes mail readers able to arrange messages correctly. I'm well aware of those fields, and my mail reader (mutt) handles them quite well. It is also capable of threading messages that lack those fields and have only "Re: " in front of the original subject to go by. Dimitar's messages did not contain those headers, though, and since his Subject lines didn't even include the "Re: ", I assumed it would be a stretch for his mail client to do any more than allow him to add the "Re: ". Regards, Gary -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 155 in vim: feature request: Option for keeping cursor position while scrolling by mouse
On Tuesday, July 23, 2013 5:49:23 AM UTC+12, v...@googlecode.com wrote: > New issue 155 by gade...@gmail.com: feature request: Option for keeping > cursor position while scrolling by mouse > http://code.google.com/p/vim/issues/detail?id=155 > > Right now, vim always shows cursor in viewable part of window by changing > its position as viewport changes, even when user is scrolling by mouse > wheel. Personally, I hate this. I understand that vim's philosophy is that > you should never use a mouse... This issue is not about the mouse, and if vim's philosophy was that you should never use the mouse, there'd be no mouse support! Rather, it's that vim always shows the current cursor position in a window, so if you scroll the window, however, the current cursor position is moved to keep it in the window. That's the way vim works presently, and I imagine it would be difficult to add this feature, but IMO it has some merit. There'd have to be a clear specification of what happens if the current position isn't displayed, and a text changing command occurred. Vim has many ways to move the cursor, perhaps setting a mark before scrolling would get you back to where you want. I'd expect there's a plugin that meets your need. Regards, John -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 156 in vim: Vim exits with error "ICE default IO error handler doing an exit(), pid = 6769, errno = 32"
Comment #2 on issue 156 by john.b.l...@gmail.com: Vim exits with error "ICE default IO error handler doing an exit(), pid = 6769, errno = 32" http://code.google.com/p/vim/issues/detail?id=156 FWIW, my vim 7.4a.35, huge with GTK2 (and so with +X11) on Kubuntu 13.04 does not give this trouble; I've tried with 60, 65 and 125. Regards, John Little -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: svn syntax with localization?
On Friday, July 19, 2013 6:14:18 PM UTC-4, Dmitry Vasiliev wrote: > On 07/18/2013 08:15 PM, studog wrote: > > I'd like to update the regex so it's accurate, > Why exactly do you want to change the regexp? It's not accurate. > If I recall correctly it > was simplified precisely because the delimiter text was changed. > Probably it can be changed to something like ^--[^-]\+--$ but I really > don't think that all the possible delimiter texts that SVN have ever had > should be added. I think that's exactly what should happen. I saw in passing just now that the diff syntax file is doing the same thing. ...Stu -- -- 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.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch for built in javascript.vim and css.vim
On Monday, July 22, 2013 1:57:34 PM UTC-7, Amadeus Demarzi wrote:
> On Monday, July 22, 2013 1:50:39 PM UTC-7, Bram Moolenaar wrote:
> > Amadeus Demarzi wrote:
> >
> >
> >
> > > This patch fixes javascript.vim and css.vim from clobbering plugin
> > > syntaxes when sourced via html.vim.
> >
> > >
> >
> > > Would it be possible to get this in for 7.4?
> >
> > >
> >
> > > More details here:
> >
> > > https://groups.google.com/forum/#!topic/vim_dev/4Idz6Em2ZuU
> >
> > >
> >
> > > It's a long explanation, so this would be the TL;DR for it
> >
> >
> >
> > Makes sense. It can be reduced to one elseif:
> >
> >
> >
> > elseif exists("b:current_syntax") && b:current_syntax == 'css'
> >
> > finish
> >
> > endif
> >
> >
> >
> >
> >
> > --
> >
> > "How is your new girlfriend?"
> >
> > "90-60-90 man!"
> >
> > "What, pale purple?"
> >
> >
> >
> > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
> >
> > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> >
> > \\\ an exciting new programming language -- http://www.Zimbu.org///
> >
> > \\\help me help AIDS victims -- http://ICCF-Holland.org///
>
> This is true, I can amend the patch and resubmit if you'd like?
>
> Thanks for the response!
Just in case, I've attached an updated patch with the single line if
statements. Also, I noticed on my older patch a mixed the use of single and
double quotes, that should be rectified to only double quotes here as well.
--
--
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.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
# HG changeset patch
# User amadeus
# Date 1374560593 25200
# Mon Jul 22 23:23:13 2013 -0700
# Node ID bf48ba5d9e36e58f75f80d77e8b0d77f78ad1fe9
# Parent 3f65dc9c8840c376ae38e5b5d48688cb5d7a4846
Improve built in javascript.vim and css.vim in html files
This commit prevents the built in javascript.vim and css.vim
runtime files from clobbering a plugin that may have already
setup syntax rules.
diff -r 3f65dc9c8840 -r bf48ba5d9e36 runtime/syntax/css.vim
--- a/runtime/syntax/css.vim Sun Jul 21 18:59:24 2013 +0200
+++ b/runtime/syntax/css.vim Mon Jul 22 23:23:13 2013 -0700
@@ -17,6 +17,8 @@
finish
endif
let main_syntax = 'css'
+elseif exists("b:current_syntax") && b:current_syntax == "css"
+ finish
endif
let s:cpo_save = &cpo
diff -r 3f65dc9c8840 -r bf48ba5d9e36 runtime/syntax/javascript.vim
--- a/runtime/syntax/javascript.vim Sun Jul 21 18:59:24 2013 +0200
+++ b/runtime/syntax/javascript.vim Mon Jul 22 23:23:13 2013 -0700
@@ -22,6 +22,8 @@
finish
endif
let main_syntax = 'javascript'
+elseif exists("b:current_syntax") && b:current_syntax == "javascript"
+ finish
endif
let s:cpo_save = &cpo
@@ -58,9 +60,9 @@
syn keyword javaScriptException try catch finally throw
syn keyword javaScriptMessage alert confirm prompt status
syn keyword javaScriptGlobal self window top parent
-syn keyword javaScriptMember document event location
+syn keyword javaScriptMember document event location
syn keyword javaScriptDeprecated escape unescape
-syn keyword javaScriptReserved abstract boolean byte char class const debugger double enum export extends final float goto implements import int interface long native package private protected public short static super synchronized throws transient volatile
+syn keyword javaScriptReserved abstract boolean byte char class const debugger double enum export extends final float goto implements import int interface long native package private protected public short static super synchronized throws transient volatile
if exists("javaScript_fold")
syn match javaScriptFunction "\"
@@ -123,7 +125,7 @@
HiLink javaScriptMessage Keyword
HiLink javaScriptGlobal Keyword
HiLink javaScriptMember Keyword
- HiLink javaScriptDeprecated Exception
+ HiLink javaScriptDeprecated Exception
HiLink javaScriptReserved Keyword
HiLink javaScriptDebug Debug
HiLink javaScriptConstant Label
Re: Patch for built in javascript.vim and css.vim
On Monday, July 22, 2013 11:25:40 PM UTC-7, Amadeus Demarzi wrote:
> On Monday, July 22, 2013 1:57:34 PM UTC-7, Amadeus Demarzi wrote:
> > On Monday, July 22, 2013 1:50:39 PM UTC-7, Bram Moolenaar wrote:
> > > Amadeus Demarzi wrote:
> > >
> > >
> > >
> > > > This patch fixes javascript.vim and css.vim from clobbering plugin
> > > > syntaxes when sourced via html.vim.
> > >
> > > >
> > >
> > > > Would it be possible to get this in for 7.4?
> > >
> > > >
> > >
> > > > More details here:
> > >
> > > > https://groups.google.com/forum/#!topic/vim_dev/4Idz6Em2ZuU
> > >
> > > >
> > >
> > > > It's a long explanation, so this would be the TL;DR for it
> > >
> > >
> > >
> > > Makes sense. It can be reduced to one elseif:
> > >
> > >
> > >
> > > elseif exists("b:current_syntax") && b:current_syntax == 'css'
> > >
> > > finish
> > >
> > > endif
> > >
> > >
> > >
> > >
> > >
> > > --
> > >
> > > "How is your new girlfriend?"
> > >
> > > "90-60-90 man!"
> > >
> > > "What, pale purple?"
> > >
> > >
> > >
> > > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
> > > \\\
> > >
> > > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> > > \\\
> > >
> > > \\\ an exciting new programming language -- http://www.Zimbu.org
> > > ///
> > >
> > > \\\help me help AIDS victims -- http://ICCF-Holland.org
> > > ///
> >
> > This is true, I can amend the patch and resubmit if you'd like?
> >
> > Thanks for the response!
>
> Just in case, I've attached an updated patch with the single line if
> statements. Also, I noticed on my older patch a mixed the use of single and
> double quotes, that should be rectified to only double quotes here as well.
Actually scratch that last one, I inadvertently removed extraneous whitespace,
making it a less clean patch. Here's a better one.
--
--
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.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
# HG changeset patch
# User amadeus
# Date 1374560906 25200
# Mon Jul 22 23:28:26 2013 -0700
# Node ID 2f8858d9b3a13f5b9dc2d0399a973962a96ecc7d
# Parent 3f65dc9c8840c376ae38e5b5d48688cb5d7a4846
Improve built in javascript.vim and css.vim in html files
This commit prevents the built in javascript.vim and css.vim
runtime files from clobbering a plugin that may have already
setup syntax rules.
diff -r 3f65dc9c8840 -r 2f8858d9b3a1 runtime/syntax/css.vim
--- a/runtime/syntax/css.vim Sun Jul 21 18:59:24 2013 +0200
+++ b/runtime/syntax/css.vim Mon Jul 22 23:28:26 2013 -0700
@@ -17,6 +17,8 @@
finish
endif
let main_syntax = 'css'
+elseif exists("b:current_syntax") && b:current_syntax == "css"
+ finish
endif
let s:cpo_save = &cpo
diff -r 3f65dc9c8840 -r 2f8858d9b3a1 runtime/syntax/javascript.vim
--- a/runtime/syntax/javascript.vim Sun Jul 21 18:59:24 2013 +0200
+++ b/runtime/syntax/javascript.vim Mon Jul 22 23:28:26 2013 -0700
@@ -22,6 +22,8 @@
finish
endif
let main_syntax = 'javascript'
+elseif exists("b:current_syntax") && b:current_syntax == 'javascript'
+ finish
endif
let s:cpo_save = &cpo
