We usually apply highlight groups in the statusline or tabline with the %#...# construct.
Since a condition cannot be used (I think) to choose the highlight group, plugin authors often resort to complex autocommand listings to keep these elements up-to-date.
A construct like %#{...}# where the "..." is an expression returning a string naming a highlight group would greatly simplify a number of beautiful plugins.
Is there something I'm missing? Would this feature be too complex to be worth it?
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Friday, April 28, 2017
Re: Syntax highlighting problem when foldmethod=syntax is set
Marcin Szewczyk wrote:
> I have noticed a problem with syntax highlighting when using the
> following .vimrc (minimal to reproduce the thing):
> #v+
> syntax on
> set nocompatible
> set foldmethod=syntax
> set nofoldenable
> #v-
>
> I am not sure if it is a bug or a feature because I rarely use folding
> but I suspect the former.
>
> With foldmethod=syntax making a comment (in C in this example) has the
> following effect:
> - /* makes many lines below to be colored as a comment,
> - the comment body follows,
> - after closing the comment with */ only the next line regains proper
> colors but other lines below remain being colored like a comment.
>
> Without setting foldmethod=syntax highlighting works properly.
>
> I have made some screenshots to visualize the problem:
> http://wodny.org/download/vim-bug/
>
> Should I fix something in my mindset or should I file a bug? Write on
> vim_dev?
I can reproduce the problem. With "set foldenable" and opening the
folds it doesn't happen. Not sure if I have time to look into fixing
this.
--
Q: How do you tell the difference between a female cat and a male cat?
A: You ask it a question and if HE answers, it's a male but, if SHE
answers, it's a female.
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> I have noticed a problem with syntax highlighting when using the
> following .vimrc (minimal to reproduce the thing):
> #v+
> syntax on
> set nocompatible
> set foldmethod=syntax
> set nofoldenable
> #v-
>
> I am not sure if it is a bug or a feature because I rarely use folding
> but I suspect the former.
>
> With foldmethod=syntax making a comment (in C in this example) has the
> following effect:
> - /* makes many lines below to be colored as a comment,
> - the comment body follows,
> - after closing the comment with */ only the next line regains proper
> colors but other lines below remain being colored like a comment.
>
> Without setting foldmethod=syntax highlighting works properly.
>
> I have made some screenshots to visualize the problem:
> http://wodny.org/download/vim-bug/
>
> Should I fix something in my mindset or should I file a bug? Write on
> vim_dev?
I can reproduce the problem. With "set foldenable" and opening the
folds it doesn't happen. Not sure if I have time to look into fixing
this.
--
Q: How do you tell the difference between a female cat and a male cat?
A: You ask it a question and if HE answers, it's a male but, if SHE
answers, it's a female.
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] minpac v1.0: a minimal package manager for Vim 8
> About this? Well it's fixed.
Not the original author but I ran into similar problems with optional plugins that didn't load files in the after directory properly. Thi soccurred with vim 8.0 since I didn't use the pack feature before. Anyway, I cannot reconstruct the problem exactly because ...
Shameless plug: I wrote autopack[1] to facilitate the loading of optional "pack plugins" which also provides IMHO better support for configuring plugins in packs via before and after scripts (actually packrc/before/PLUGIN.vim and packrc/after/PLUGIN.vim).
Regards
[1] http://www.vim.org/scripts/script.php?script_id=5526
https://github.com/tomtom/autopack_vim
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Not the original author but I ran into similar problems with optional plugins that didn't load files in the after directory properly. Thi soccurred with vim 8.0 since I didn't use the pack feature before. Anyway, I cannot reconstruct the problem exactly because ...
Shameless plug: I wrote autopack[1] to facilitate the loading of optional "pack plugins" which also provides IMHO better support for configuring plugins in packs via before and after scripts (actually packrc/before/PLUGIN.vim and packrc/after/PLUGIN.vim).
Regards
[1] http://www.vim.org/scripts/script.php?script_id=5526
https://github.com/tomtom/autopack_vim
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: where is my file under c:\windows\
Hi,
I'm using vim on Windows 7 and found a very odd problem.
For example, under DOS prompt, I can use command:
vim c:\windows\abc.txt
to edit the file abc.txt. However,
dir c:\windows\abc.txt
show me file not found !!!
and I run
vim c:\windows\abc.txt
again, everything I put in abc.txt is still there !!!???
Does vim use some cache directory ?? What's the problem here ??
Are you running a 32-bit Vim.exe under 64-bit Windows?
This is probably WoW64 File System Redirection.
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thursday, April 27, 2017
where is my file under c:\windows\
Hi,
I'm using vim on Windows 7 and found a very odd problem.
For example, under DOS prompt, I can use command:
vim c:\windows\abc.txt
to edit the file abc.txt. However,
dir c:\windows\abc.txt
show me file not found !!!
and I run
vim c:\windows\abc.txt
again, everything I put in abc.txt is still there !!!???
Does vim use some cache directory ?? What's the problem here ??
Best Regards,
KC
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm using vim on Windows 7 and found a very odd problem.
For example, under DOS prompt, I can use command:
vim c:\windows\abc.txt
to edit the file abc.txt. However,
dir c:\windows\abc.txt
show me file not found !!!
and I run
vim c:\windows\abc.txt
again, everything I put in abc.txt is still there !!!???
Does vim use some cache directory ?? What's the problem here ??
Best Regards,
KC
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] minpac v1.0: a minimal package manager for Vim 8
Hi Yutao,
2017-4-27(Thu) 19:23:12 UTC+9 Yutao Yuan:
> On Fri, Apr 21, 2017 at 10:06:44PM -0700, Ken Takata wrote:
> > Hi all,
> >
> > I announce release of minpac ver 1.0.
> > It is a minimal package manager for Vim 8 (and Neovim).
> >
> > https://github.com/k-takata/minpac
> >
> > Minpac utilizes the packages feature of Vim 8, and uses the jobs feature for
> > parallel install/update. So, it is simple and fast.
> >
> > Have fun!
> >
> > Regards,
> > Ken Takata
>
> A few months ago I tried to use vim packages to manage plugins, but it
> wasn't adding the "after" directories in the correct order, and breaks
> several plugins. Is this still the case now?
About this? Well it's fixed.
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Aug 6 19:01:55 2016 +0200
patch 7.4.2164
Problem: It is not possible to use plugins in an "after" directory to tune
the behavior of a package.
Solution: First load plugins from non-after directories, then packages and
finally plugins in after directories.
Reset 'loadplugins' before executing --cmd arguments.
--
Best regards,
Hirohito Higashi (h_east)
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
2017-4-27(Thu) 19:23:12 UTC+9 Yutao Yuan:
> On Fri, Apr 21, 2017 at 10:06:44PM -0700, Ken Takata wrote:
> > Hi all,
> >
> > I announce release of minpac ver 1.0.
> > It is a minimal package manager for Vim 8 (and Neovim).
> >
> > https://github.com/k-takata/minpac
> >
> > Minpac utilizes the packages feature of Vim 8, and uses the jobs feature for
> > parallel install/update. So, it is simple and fast.
> >
> > Have fun!
> >
> > Regards,
> > Ken Takata
>
> A few months ago I tried to use vim packages to manage plugins, but it
> wasn't adding the "after" directories in the correct order, and breaks
> several plugins. Is this still the case now?
About this? Well it's fixed.
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Aug 6 19:01:55 2016 +0200
patch 7.4.2164
Problem: It is not possible to use plugins in an "after" directory to tune
the behavior of a package.
Solution: First load plugins from non-after directories, then packages and
finally plugins in after directories.
Reset 'loadplugins' before executing --cmd arguments.
--
Best regards,
Hirohito Higashi (h_east)
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] minpac v1.0: a minimal package manager for Vim 8
On Fri, Apr 21, 2017 at 10:06:44PM -0700, Ken Takata wrote:
> Hi all,
>
> I announce release of minpac ver 1.0.
> It is a minimal package manager for Vim 8 (and Neovim).
>
> https://github.com/k-takata/minpac
>
> Minpac utilizes the packages feature of Vim 8, and uses the jobs feature for
> parallel install/update. So, it is simple and fast.
>
> Have fun!
>
> Regards,
> Ken Takata
A few months ago I tried to use vim packages to manage plugins, but it
wasn't adding the "after" directories in the correct order, and breaks
several plugins. Is this still the case now?
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Hi all,
>
> I announce release of minpac ver 1.0.
> It is a minimal package manager for Vim 8 (and Neovim).
>
> https://github.com/k-takata/minpac
>
> Minpac utilizes the packages feature of Vim 8, and uses the jobs feature for
> parallel install/update. So, it is simple and fast.
>
> Have fun!
>
> Regards,
> Ken Takata
A few months ago I tried to use vim packages to manage plugins, but it
wasn't adding the "after" directories in the correct order, and breaks
several plugins. Is this still the case now?
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wednesday, April 26, 2017
Re: Bullet list and "showbreak"
On Wednesday, April 26, 2017 at 8:36:19 AM UTC-5, Yann wrote:
> Hello,
>
> I use "showbreak" in my text, I'd like to know if somebody could help me with a "showbreak conditional", please:
>
> if "text begins with [_]"
> set showbreak=\ \ \ \
> else if "text begins with -"
> set showbreak=\ \
> else
> endif
>
> In fact, I want a "showbreak" According to the beginning of the paragraph. Does someone have ideas, please?
>
> thX
Impossible, because showbreak takes a string and not a function; also showbreak is a global option that affects all of Vim, not just a single buffer, and *definitely* not just a single paragraph.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Hello,
>
> I use "showbreak" in my text, I'd like to know if somebody could help me with a "showbreak conditional", please:
>
> if "text begins with [_]"
> set showbreak=\ \ \ \
> else if "text begins with -"
> set showbreak=\ \
> else
> endif
>
> In fact, I want a "showbreak" According to the beginning of the paragraph. Does someone have ideas, please?
>
> thX
Impossible, because showbreak takes a string and not a function; also showbreak is a global option that affects all of Vim, not just a single buffer, and *definitely* not just a single paragraph.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Syntax highlighting problem when foldmethod=syntax is set
Hi,
I have noticed a problem with syntax highlighting when using the
following .vimrc (minimal to reproduce the thing):
#v+
syntax on
set nocompatible
set foldmethod=syntax
set nofoldenable
#v-
I am not sure if it is a bug or a feature because I rarely use folding
but I suspect the former.
With foldmethod=syntax making a comment (in C in this example) has the
following effect:
- /* makes many lines below to be colored as a comment,
- the comment body follows,
- after closing the comment with */ only the next line regains proper
colors but other lines below remain being colored like a comment.
Without setting foldmethod=syntax highlighting works properly.
I have made some screenshots to visualize the problem:
http://wodny.org/download/vim-bug/
Should I fix something in my mindset or should I file a bug? Write on
vim_dev?
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 13 2017 01:36:41)
Included patches: 1-488, 576
Extra patches: 8.0.0322, 8.0.0056
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by jamessan@debian.org
Huge version with GTK2 GUI. Features included (+) or not (-):
+acl +farsi +mouse_netterm +syntax
+arabic +file_in_path +mouse_sgr +tag_binary
+autocmd +find_in_path -mouse_sysmouse +tag_old_static
+balloon_eval +float +mouse_urxvt -tag_any_white
+browse +folding +mouse_xterm +tcl
++builtin_terms -footer +multi_byte +terminfo
+byte_offset +fork() +multi_lang +termresponse
+cindent +gettext -mzscheme +textobjects
+clientserver -hangul_input +netbeans_intg +title
+clipboard +iconv +path_extra +toolbar
+cmdline_compl +insert_expand +perl +user_commands
+cmdline_hist +jumplist +persistent_undo +vertsplit
+cmdline_info +keymap +postscript +virtualedit
+comments +langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds +quickfix +wildignore
+cursorshape +localmap +reltime +wildmenu
+dialog_con_gui +lua +rightleft +windows
+diff +menu +ruby +writebackup
+digraphs +mksession +scrollbind +X11
+dnd +modify_fname +signs -xfontset
-ebcdic +mouse +smartindent +xim
+emacs_tags +mouseshape -sniff +xsmp_interact
+eval +mouse_dec +startuptime +xterm_clipboard
+ex_extra +mouse_gpm +statusline -xterm_save
+extra_search -mouse_jsbterm -sun_workshop +xpm
--
Marcin Szewczyk
http://wodny.org
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I have noticed a problem with syntax highlighting when using the
following .vimrc (minimal to reproduce the thing):
#v+
syntax on
set nocompatible
set foldmethod=syntax
set nofoldenable
#v-
I am not sure if it is a bug or a feature because I rarely use folding
but I suspect the former.
With foldmethod=syntax making a comment (in C in this example) has the
following effect:
- /* makes many lines below to be colored as a comment,
- the comment body follows,
- after closing the comment with */ only the next line regains proper
colors but other lines below remain being colored like a comment.
Without setting foldmethod=syntax highlighting works properly.
I have made some screenshots to visualize the problem:
http://wodny.org/download/vim-bug/
Should I fix something in my mindset or should I file a bug? Write on
vim_dev?
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 13 2017 01:36:41)
Included patches: 1-488, 576
Extra patches: 8.0.0322, 8.0.0056
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by jamessan@debian.org
Huge version with GTK2 GUI. Features included (+) or not (-):
+acl +farsi +mouse_netterm +syntax
+arabic +file_in_path +mouse_sgr +tag_binary
+autocmd +find_in_path -mouse_sysmouse +tag_old_static
+balloon_eval +float +mouse_urxvt -tag_any_white
+browse +folding +mouse_xterm +tcl
++builtin_terms -footer +multi_byte +terminfo
+byte_offset +fork() +multi_lang +termresponse
+cindent +gettext -mzscheme +textobjects
+clientserver -hangul_input +netbeans_intg +title
+clipboard +iconv +path_extra +toolbar
+cmdline_compl +insert_expand +perl +user_commands
+cmdline_hist +jumplist +persistent_undo +vertsplit
+cmdline_info +keymap +postscript +virtualedit
+comments +langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds +quickfix +wildignore
+cursorshape +localmap +reltime +wildmenu
+dialog_con_gui +lua +rightleft +windows
+diff +menu +ruby +writebackup
+digraphs +mksession +scrollbind +X11
+dnd +modify_fname +signs -xfontset
-ebcdic +mouse +smartindent +xim
+emacs_tags +mouseshape -sniff +xsmp_interact
+eval +mouse_dec +startuptime +xterm_clipboard
+ex_extra +mouse_gpm +statusline -xterm_save
+extra_search -mouse_jsbterm -sun_workshop +xpm
--
Marcin Szewczyk
http://wodny.org
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Bullet list and "showbreak"
Hello,
I use "showbreak" in my text, I'd like to know if somebody could help me with a "showbreak conditional", please:
if "text begins with [_]"
set showbreak=\ \ \ \
else if "text begins with -"
set showbreak=\ \
else
endif
In fact, I want a "showbreak" According to the beginning of the paragraph. Does someone have ideas, please?
thX
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I use "showbreak" in my text, I'd like to know if somebody could help me with a "showbreak conditional", please:
if "text begins with [_]"
set showbreak=\ \ \ \
else if "text begins with -"
set showbreak=\ \
else
endif
In fact, I want a "showbreak" According to the beginning of the paragraph. Does someone have ideas, please?
thX
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tuesday, April 25, 2017
Re: an old "hack" of mine, shared for amusement
On Tue, Apr 25, 2017 at 04:23:12PM -0400, Eli the Bearded wrote:
> Christian Brabandt wrote:
> > Are you saying, original Vi could be tricked to execute various commands
> > via modelines? That sounds pretty scary actually.
>
> Still can, if you have real vi somewhere. (You can also embed arbitrary
> ex commands in tag files for real vi.)
I will say in my defense that the clue about the Vim 4.2 swap file was
a bit of a red herring, especially since Vim honors ex and vi's
modelines.
Anyhow, it's now time to test this with Traditional Vi
http://ex-vi.sourceforge.net/
--
Erik Falor
Registered Linux User #445632 http://unnovative.net
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Christian Brabandt wrote:
> > Are you saying, original Vi could be tricked to execute various commands
> > via modelines? That sounds pretty scary actually.
>
> Still can, if you have real vi somewhere. (You can also embed arbitrary
> ex commands in tag files for real vi.)
I will say in my defense that the clue about the Vim 4.2 swap file was
a bit of a red herring, especially since Vim honors ex and vi's
modelines.
Anyhow, it's now time to test this with Traditional Vi
http://ex-vi.sourceforge.net/
--
Erik Falor
Registered Linux User #445632 http://unnovative.net
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: an old "hack" of mine, shared for amusement
Christian Brabandt wrote:
> Are you saying, original Vi could be tricked to execute various commands
> via modelines? That sounds pretty scary actually.
Still can, if you have real vi somewhere. (You can also embed arbitrary
ex commands in tag files for real vi.)
Elijah
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Are you saying, original Vi could be tricked to execute various commands
> via modelines? That sounds pretty scary actually.
Still can, if you have real vi somewhere. (You can also embed arbitrary
ex commands in tag files for real vi.)
Elijah
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: an old "hack" of mine, shared for amusement
Hi Eli!
On Di, 25 Apr 2017, Eli the Bearded wrote:
> Everyone seems to be missing it. rot13 solution for those interested.
>
> This *hack* was designed to *not* work in vim.
>
> It works in vi. It makes vi reopen the file with vim.
>
> (And by-the-by, I have Vim 3.0 for Mac System 7. I found it for download
> last year when I was playing with the Basilisk II emulator. Vim 3: back
> when 'q' did the thing 'gq' does now. And 'Q' was unimplemented.)
Are you saying, original Vi could be tricked to execute various commands
via modelines? That sounds pretty scary actually.
Best,
Christian
--
Ein kluger Mann widerspricht nie einer Frau. Er wartet, bis sie es
selbst tut.
-- Humphrey Bogart
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Di, 25 Apr 2017, Eli the Bearded wrote:
> Everyone seems to be missing it. rot13 solution for those interested.
>
> This *hack* was designed to *not* work in vim.
>
> It works in vi. It makes vi reopen the file with vim.
>
> (And by-the-by, I have Vim 3.0 for Mac System 7. I found it for download
> last year when I was playing with the Basilisk II emulator. Vim 3: back
> when 'q' did the thing 'gq' does now. And 'Q' was unimplemented.)
Are you saying, original Vi could be tricked to execute various commands
via modelines? That sounds pretty scary actually.
Best,
Christian
--
Ein kluger Mann widerspricht nie einer Frau. Er wartet, bis sie es
selbst tut.
-- Humphrey Bogart
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: an old "hack" of mine, shared for amusement
Erik Falor wrote:
> I can report that this "hack" doesn't do anything interesting as of Vim 5.5.
> It doesn't complain about the pipe characters in the modelines, though.
Everyone seems to be missing it. rot13 solution for those interested.
Guvf *unpx* jnf qrfvtarq gb *abg* jbex va ivz.
Vg jbexf va iv. Vg znxrf iv erbcra gur svyr jvgu ivz.
(And by-the-by, I have Vim 3.0 for Mac System 7. I found it for download
last year when I was playing with the Basilisk II emulator. Vim 3: back
when 'q' did the thing 'gq' does now. And 'Q' was unimplemented.)
Elijah
------
http://wayback.archive.org/web/19990422231919/http://www.qz.to/~eli/src/modeline.html
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> I can report that this "hack" doesn't do anything interesting as of Vim 5.5.
> It doesn't complain about the pipe characters in the modelines, though.
Everyone seems to be missing it. rot13 solution for those interested.
Guvf *unpx* jnf qrfvtarq gb *abg* jbex va ivz.
Vg jbexf va iv. Vg znxrf iv erbcra gur svyr jvgu ivz.
(And by-the-by, I have Vim 3.0 for Mac System 7. I found it for download
last year when I was playing with the Basilisk II emulator. Vim 3: back
when 'q' did the thing 'gq' does now. And 'Q' was unimplemented.)
Elijah
------
http://wayback.archive.org/web/19990422231919/http://www.qz.to/~eli/src/modeline.html
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: an old "hack" of mine, shared for amusement
On Tue, Apr 25, 2017 at 09:16:54AM +0200, Christian Brabandt wrote:
>
> A while ago, I converted the old Vim CVS Repository to git and I made it
> available here:
> https://bitbucket.org/vim-mirror/vim-ancient
>
> #v+
> ~/vim-ancient$ git log --reverse |head -15
> commit 686757e4d2a46c8ab55c08c7a0ccd9d83d2465fb
> Author: Bram Moolenaar <bram@vim.org>
> Date: Sun Dec 19 03:43:45 1999 +0000
>
> Initial revision
I can report that this "hack" doesn't do anything interesting as of Vim 5.5.
It doesn't complain about the pipe characters in the modelines, though.
:version
VIM - Vi IMproved 5.5 (1999 Sep 19)
Compiled by fadein@viking2, with (+) or without (-):
+autocmd -browse ++builtin_terms +byte_offset +cindent +cmdline_compl +cmdline_info +comments +cryptv +cscope
+dialog_con +digraphs +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path -osfiletype +find_in_path +fork()
-GUI -hangul_input +insert_expand +langmap +linebreak +lispindent +menu +mksession +modify_fname +mouse +mouse_dec
-mouse_gpm +mouse_netterm +mouse_xterm +multi_byte -perl +quickfix -python +rightleft +scrollbind +smartindent -sniff
+statusline +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +textobjects +title +user_commands
+visualextra +viminfo +wildignore +wildmenu +writebackup -X11 -xfontset -xim -xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -Wall
Linking: gcc -o vim -lncurses
--
Erik Falor
Registered Linux User #445632 http://unnovative.net
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>
> A while ago, I converted the old Vim CVS Repository to git and I made it
> available here:
> https://bitbucket.org/vim-mirror/vim-ancient
>
> #v+
> ~/vim-ancient$ git log --reverse |head -15
> commit 686757e4d2a46c8ab55c08c7a0ccd9d83d2465fb
> Author: Bram Moolenaar <bram@vim.org>
> Date: Sun Dec 19 03:43:45 1999 +0000
>
> Initial revision
I can report that this "hack" doesn't do anything interesting as of Vim 5.5.
It doesn't complain about the pipe characters in the modelines, though.
:version
VIM - Vi IMproved 5.5 (1999 Sep 19)
Compiled by fadein@viking2, with (+) or without (-):
+autocmd -browse ++builtin_terms +byte_offset +cindent +cmdline_compl +cmdline_info +comments +cryptv +cscope
+dialog_con +digraphs +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path -osfiletype +find_in_path +fork()
-GUI -hangul_input +insert_expand +langmap +linebreak +lispindent +menu +mksession +modify_fname +mouse +mouse_dec
-mouse_gpm +mouse_netterm +mouse_xterm +multi_byte -perl +quickfix -python +rightleft +scrollbind +smartindent -sniff
+statusline +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +textobjects +title +user_commands
+visualextra +viminfo +wildignore +wildmenu +writebackup -X11 -xfontset -xim -xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -Wall
Linking: gcc -o vim -lncurses
--
Erik Falor
Registered Linux User #445632 http://unnovative.net
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: already at oldest change - how to suppress this message
On Tue, Apr 25, 2017 at 10:18 AM, Christian Brabandt <cblists@256bit.org> wrote:
> Hi Jim!
>
> On Mo, 24 Apr 2017, Jim Wilmore wrote:
>
>> I recently got a new laptop, so I decided I would install gvim80 after using gvim73 for many years.
>> As an old Unix user from the 70s onward, I have quite a lot of customization, and when I discovered Gvim, my customization quadrupled.
>> I finally have my new machine running gvim about the same as before. I had to set the guifont, but most everything else worked out. However, I keep getting the message "Already at oldest change" when I open a file. I am guessing this is related either to version control (which I handle independently when I need it) or some sort of temporary backup file (which I have turned off, at least in previous customizations).
>> How do I turn off this message?!? I have browsed through the possible settings, and have found nothing yet. Help, please...
>
> Looks like some configuration is issuing an undo command when it
> shouldn't. Check your autocommands or your plugins. Also see the faq:
> https://vimhelp.appspot.com/vim_faq.txt.html#faq-2.5
>
>
> Best,
> Christian
Yes, "Already at oldest change" is a message from the Normal-mode u
(undo) command or the :u[ndo] Ex-command when they can't do anything
because there is no earlier stored history for them to go to. I find
that message extremely useful when I try to (manually) go back in
history and nothing happens.
See also the 'history' and 'viminfo' options.
Best regards,
Tony.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Hi Jim!
>
> On Mo, 24 Apr 2017, Jim Wilmore wrote:
>
>> I recently got a new laptop, so I decided I would install gvim80 after using gvim73 for many years.
>> As an old Unix user from the 70s onward, I have quite a lot of customization, and when I discovered Gvim, my customization quadrupled.
>> I finally have my new machine running gvim about the same as before. I had to set the guifont, but most everything else worked out. However, I keep getting the message "Already at oldest change" when I open a file. I am guessing this is related either to version control (which I handle independently when I need it) or some sort of temporary backup file (which I have turned off, at least in previous customizations).
>> How do I turn off this message?!? I have browsed through the possible settings, and have found nothing yet. Help, please...
>
> Looks like some configuration is issuing an undo command when it
> shouldn't. Check your autocommands or your plugins. Also see the faq:
> https://vimhelp.appspot.com/vim_faq.txt.html#faq-2.5
>
>
> Best,
> Christian
Yes, "Already at oldest change" is a message from the Normal-mode u
(undo) command or the :u[ndo] Ex-command when they can't do anything
because there is no earlier stored history for them to go to. I find
that message extremely useful when I try to (manually) go back in
history and nothing happens.
See also the 'history' and 'viminfo' options.
Best regards,
Tony.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim Improvement suggester
On Tue, 25 Apr 2017 04:12:46 -0700 (PDT)
Patrik Iselind <patrik.mrx@gmail.com> wrote:
> Even if they lack context you can still figure out things like "You
> use j and k to move around a lot. A faster and less error prone way
> would be using seaching for example.". This could be one example of
> that the feature would bring to the table.
I use / (search) to move around a lot. It is the fastest way I found (so
far). ☺
The second fastest is to use an after/ftplugin to preset marks.
--
Don't stop where the ink does.
Shawn H Corey
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Patrik Iselind <patrik.mrx@gmail.com> wrote:
> Even if they lack context you can still figure out things like "You
> use j and k to move around a lot. A faster and less error prone way
> would be using seaching for example.". This could be one example of
> that the feature would bring to the table.
I use / (search) to move around a lot. It is the fastest way I found (so
far). ☺
The second fastest is to use an after/ftplugin to preset marks.
--
Don't stop where the ink does.
Shawn H Corey
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim Improvement suggester
Den onsdag 19 april 2017 kl. 10:22:25 UTC+2 skrev ZyX:
>
> 1. Parsing &verbosefile, see :h 'verbose' and :h 'verbosefile'. Should
> only work for Ex commands, but not for normal-mode commands.
> 2. Recording your input in `-w {scriptout}` and parsing to guess where
> are commands there and where is regular input.
>
> Though I am not thinking this would be a good idea: based on my
> experience Vim commands are normally not a bottleneck, designing what
> and how to write is.
>
The bottle neck for me is usually how i change my text. When i learn a new feature/command in Vim i usually think something along the lines of "I would have gained so much if someone had told me about this earlier". So abstracting the someone into something might be a good enough approximation.
Vim fluency would be attained faster with a bit of help. As we all know, the learning curve of Vim is not flat...
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>
> 1. Parsing &verbosefile, see :h 'verbose' and :h 'verbosefile'. Should
> only work for Ex commands, but not for normal-mode commands.
> 2. Recording your input in `-w {scriptout}` and parsing to guess where
> are commands there and where is regular input.
>
> Though I am not thinking this would be a good idea: based on my
> experience Vim commands are normally not a bottleneck, designing what
> and how to write is.
>
The bottle neck for me is usually how i change my text. When i learn a new feature/command in Vim i usually think something along the lines of "I would have gained so much if someone had told me about this earlier". So abstracting the someone into something might be a good enough approximation.
Vim fluency would be attained faster with a bit of help. As we all know, the learning curve of Vim is not flat...
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim Improvement suggester
Den onsdag 19 april 2017 kl. 11:25:38 UTC+2 skrev MarcWeber:
> Brams advice was
> 1) watch yourself
> 2) look at what takes most of you time
> 3) use mailinglist or chat to ask how to do things faster.
>
> I've put some ideas here:
> https://github.com/MarcWeber/vim-addon-manager/blob/master/autoload/sample_vimrc_for_new_users.vim
>
> "The commands" you wan to record lack context, so no human/ai would be
> able to suggest "how to do things better" without knowing your task.
>
> MfG
> Marc Weber
Even if they lack context you can still figure out things like "You use j and k to move around a lot. A faster and less error prone way would be using seaching for example.". This could be one example of that the feature would bring to the table.
I'm not saying it needs a 100% coverage, just enough to get over the biggest hurdles.
// Patrik
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Brams advice was
> 1) watch yourself
> 2) look at what takes most of you time
> 3) use mailinglist or chat to ask how to do things faster.
>
> I've put some ideas here:
> https://github.com/MarcWeber/vim-addon-manager/blob/master/autoload/sample_vimrc_for_new_users.vim
>
> "The commands" you wan to record lack context, so no human/ai would be
> able to suggest "how to do things better" without knowing your task.
>
> MfG
> Marc Weber
Even if they lack context you can still figure out things like "You use j and k to move around a lot. A faster and less error prone way would be using seaching for example.". This could be one example of that the feature would bring to the table.
I'm not saying it needs a 100% coverage, just enough to get over the biggest hurdles.
// Patrik
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: already at oldest change - how to suppress this message
Hi Jim!
On Mo, 24 Apr 2017, Jim Wilmore wrote:
> I recently got a new laptop, so I decided I would install gvim80 after using gvim73 for many years.
> As an old Unix user from the 70s onward, I have quite a lot of customization, and when I discovered Gvim, my customization quadrupled.
> I finally have my new machine running gvim about the same as before. I had to set the guifont, but most everything else worked out. However, I keep getting the message "Already at oldest change" when I open a file. I am guessing this is related either to version control (which I handle independently when I need it) or some sort of temporary backup file (which I have turned off, at least in previous customizations).
> How do I turn off this message?!? I have browsed through the possible settings, and have found nothing yet. Help, please...
Looks like some configuration is issuing an undo command when it
shouldn't. Check your autocommands or your plugins. Also see the faq:
https://vimhelp.appspot.com/vim_faq.txt.html#faq-2.5
Best,
Christian
--
Ich bin bereit überall hinzugehen, wenn es nur vorwärts ist.
-- David Livingstone
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Mo, 24 Apr 2017, Jim Wilmore wrote:
> I recently got a new laptop, so I decided I would install gvim80 after using gvim73 for many years.
> As an old Unix user from the 70s onward, I have quite a lot of customization, and when I discovered Gvim, my customization quadrupled.
> I finally have my new machine running gvim about the same as before. I had to set the guifont, but most everything else worked out. However, I keep getting the message "Already at oldest change" when I open a file. I am guessing this is related either to version control (which I handle independently when I need it) or some sort of temporary backup file (which I have turned off, at least in previous customizations).
> How do I turn off this message?!? I have browsed through the possible settings, and have found nothing yet. Help, please...
Looks like some configuration is issuing an undo command when it
shouldn't. Check your autocommands or your plugins. Also see the faq:
https://vimhelp.appspot.com/vim_faq.txt.html#faq-2.5
Best,
Christian
--
Ich bin bereit überall hinzugehen, wenn es nur vorwärts ist.
-- David Livingstone
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: an old "hack" of mine, shared for amusement
On Mo, 24 Apr 2017, Erik Falor wrote:
> Eli did mention that he had been running Vim version 4.2. Perhaps
> modelines worked differently back then?
>
> The oldest Vim source code I could find in a brief search is version
> 6.4. Does anybody know of a way to find a version that's even older
> than that?
A while ago, I converted the old Vim CVS Repository to git and I made it
available here:
https://bitbucket.org/vim-mirror/vim-ancient
#v+
~/vim-ancient$ git log --reverse |head -15
commit 686757e4d2a46c8ab55c08c7a0ccd9d83d2465fb
Author: Bram Moolenaar <bram@vim.org>
Date: Sun Dec 19 03:43:45 1999 +0000
Initial revision
commit d8a836d4df71284a494011056263b98972ae6823
Author: Bram Moolenaar <bram@vim.org>
Date: Sun Dec 19 03:50:09 1999 +0000
Patch 5.5.001
Problem: Configure in the top directory did not pass on an argument with a
space correctly. For example "./configure --previs="/My home".
(Stephane Chazelas)
Solution: Use '"$@"' instead of '$*' to pass on the arguments.
#v-
Best,
Christian
--
Es gibt zwei Arten von Menschen: Solche die Glück haben und solche wie mich.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Eli did mention that he had been running Vim version 4.2. Perhaps
> modelines worked differently back then?
>
> The oldest Vim source code I could find in a brief search is version
> 6.4. Does anybody know of a way to find a version that's even older
> than that?
A while ago, I converted the old Vim CVS Repository to git and I made it
available here:
https://bitbucket.org/vim-mirror/vim-ancient
#v+
~/vim-ancient$ git log --reverse |head -15
commit 686757e4d2a46c8ab55c08c7a0ccd9d83d2465fb
Author: Bram Moolenaar <bram@vim.org>
Date: Sun Dec 19 03:43:45 1999 +0000
Initial revision
commit d8a836d4df71284a494011056263b98972ae6823
Author: Bram Moolenaar <bram@vim.org>
Date: Sun Dec 19 03:50:09 1999 +0000
Patch 5.5.001
Problem: Configure in the top directory did not pass on an argument with a
space correctly. For example "./configure --previs="/My home".
(Stephane Chazelas)
Solution: Use '"$@"' instead of '$*' to pass on the arguments.
#v-
Best,
Christian
--
Es gibt zwei Arten von Menschen: Solche die Glück haben und solche wie mich.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Monday, April 24, 2017
Re: an old "hack" of mine, shared for amusement
On Tue, Apr 25, 2017 at 01:40:52PM +1000, Erik Christiansen wrote:
> On 24.04.17 19:50, Eli the Bearded wrote:
> > What this does is left as an exercise for the reader.
>
> That is most interesting, as ":h modeline" describes that they comprise only
> "set" directives, not arbitrary commands. I.e.:
>
> {options} a list of option settings, separated with white space
> or ':', where each part between ':' is the argument
> for a ":set" command (can be empty)
>
> after the:
>
> {vi:|vim:|ex:} the string "vi:", "vim:" or "ex:"
>
> It doesn't even allow the '|'.
>
> How turning off modelines might help to execute commands in modelines is
> a guessing game, without documentation of supported behaviour.
>
> Admittedly, on the few occasions that an arbitrary command seemed to be
> needed, I've found another way to achieve the result.
Eli did mention that he had been running Vim version 4.2. Perhaps
modelines worked differently back then?
The oldest Vim source code I could find in a brief search is version
6.4. Does anybody know of a way to find a version that's even older
than that?
--
Erik Falor
Registered Linux User #445632 http://unnovative.net
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On 24.04.17 19:50, Eli the Bearded wrote:
> > What this does is left as an exercise for the reader.
>
> That is most interesting, as ":h modeline" describes that they comprise only
> "set" directives, not arbitrary commands. I.e.:
>
> {options} a list of option settings, separated with white space
> or ':', where each part between ':' is the argument
> for a ":set" command (can be empty)
>
> after the:
>
> {vi:|vim:|ex:} the string "vi:", "vim:" or "ex:"
>
> It doesn't even allow the '|'.
>
> How turning off modelines might help to execute commands in modelines is
> a guessing game, without documentation of supported behaviour.
>
> Admittedly, on the few occasions that an arbitrary command seemed to be
> needed, I've found another way to achieve the result.
Eli did mention that he had been running Vim version 4.2. Perhaps
modelines worked differently back then?
The oldest Vim source code I could find in a brief search is version
6.4. Does anybody know of a way to find a version that's even older
than that?
--
Erik Falor
Registered Linux User #445632 http://unnovative.net
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: an old "hack" of mine, shared for amusement
On 24.04.17 19:50, Eli the Bearded wrote:
> $ cat my-src/hacks/vi/fork
> vi: set noml | w! | ! vim % :
> vi: e! % | w! | q :
>
> foobar
> $
>
> I don't remember writing that, but I can fully believe I did. (There's
> other stuff there, I'm sure I have written.
>
> What this does is left as an exercise for the reader.
That is most interesting, as ":h modeline" describes that they comprise only
"set" directives, not arbitrary commands. I.e.:
{options} a list of option settings, separated with white space
or ':', where each part between ':' is the argument
for a ":set" command (can be empty)
after the:
{vi:|vim:|ex:} the string "vi:", "vim:" or "ex:"
It doesn't even allow the '|'.
How turning off modelines might help to execute commands in modelines is
a guessing game, without documentation of supported behaviour.
Admittedly, on the few occasions that an arbitrary command seemed to be
needed, I've found another way to achieve the result.
Erik
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> $ cat my-src/hacks/vi/fork
> vi: set noml | w! | ! vim % :
> vi: e! % | w! | q :
>
> foobar
> $
>
> I don't remember writing that, but I can fully believe I did. (There's
> other stuff there, I'm sure I have written.
>
> What this does is left as an exercise for the reader.
That is most interesting, as ":h modeline" describes that they comprise only
"set" directives, not arbitrary commands. I.e.:
{options} a list of option settings, separated with white space
or ':', where each part between ':' is the argument
for a ":set" command (can be empty)
after the:
{vi:|vim:|ex:} the string "vi:", "vim:" or "ex:"
It doesn't even allow the '|'.
How turning off modelines might help to execute commands in modelines is
a guessing game, without documentation of supported behaviour.
Admittedly, on the few occasions that an arbitrary command seemed to be
needed, I've found another way to achieve the result.
Erik
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
already at oldest change - how to suppress this message
I recently got a new laptop, so I decided I would install gvim80 after using gvim73 for many years.
As an old Unix user from the 70s onward, I have quite a lot of customization, and when I discovered Gvim, my customization quadrupled.
I finally have my new machine running gvim about the same as before. I had to set the guifont, but most everything else worked out. However, I keep getting the message "Already at oldest change" when I open a file. I am guessing this is related either to version control (which I handle independently when I need it) or some sort of temporary backup file (which I have turned off, at least in previous customizations).
How do I turn off this message?!? I have browsed through the possible settings, and have found nothing yet. Help, please...
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
As an old Unix user from the 70s onward, I have quite a lot of customization, and when I discovered Gvim, my customization quadrupled.
I finally have my new machine running gvim about the same as before. I had to set the guifont, but most everything else worked out. However, I keep getting the message "Already at oldest change" when I open a file. I am guessing this is related either to version control (which I handle independently when I need it) or some sort of temporary backup file (which I have turned off, at least in previous customizations).
How do I turn off this message?!? I have browsed through the possible settings, and have found nothing yet. Help, please...
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
an old "hack" of mine, shared for amusement
I found this today, while looking for abandoned swap files on my
computer. The file was dated 2006, but the swap file is for vim 4.2,
and the hostname is one I last used ~ 1998. I guess I copied the
file, and the swap file, from a backup or something in 2006.
$ ls -l my-src/hacks/vi/fork my-src/hacks/vi/fork.swp
-rw-r--r-- 1 elijah users 58 Jun 6 2006 my-src/hacks/vi/fork
-rw-r--r-- 1 elijah users 24576 Jun 6 2006 my-src/hacks/vi/fork.swp
$ cat my-src/hacks/vi/fork
vi: set noml | w! | ! vim % :
vi: e! % | w! | q :
foobar
$
I don't remember writing that, but I can fully believe I did. (There's
other stuff there, I'm sure I have written.
What this does is left as an exercise for the reader.
I suspect I tested it on Solaris vi of that era. Testing in Solaris vi
(Version SVR4.0, Solaris 2.5.0) today[*], I need to hit <esc> to
unstick-it at a certain point, and I think the second line would be
better as just:
vi: q :
Elijah
------
[*] only has one, rather old, Solaris system left to test with
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
computer. The file was dated 2006, but the swap file is for vim 4.2,
and the hostname is one I last used ~ 1998. I guess I copied the
file, and the swap file, from a backup or something in 2006.
$ ls -l my-src/hacks/vi/fork my-src/hacks/vi/fork.swp
-rw-r--r-- 1 elijah users 58 Jun 6 2006 my-src/hacks/vi/fork
-rw-r--r-- 1 elijah users 24576 Jun 6 2006 my-src/hacks/vi/fork.swp
$ cat my-src/hacks/vi/fork
vi: set noml | w! | ! vim % :
vi: e! % | w! | q :
foobar
$
I don't remember writing that, but I can fully believe I did. (There's
other stuff there, I'm sure I have written.
What this does is left as an exercise for the reader.
I suspect I tested it on Solaris vi of that era. Testing in Solaris vi
(Version SVR4.0, Solaris 2.5.0) today[*], I need to hit <esc> to
unstick-it at a certain point, and I think the second line would be
better as just:
vi: q :
Elijah
------
[*] only has one, rather old, Solaris system left to test with
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sunday, April 23, 2017
Updated Vim 8.0 available with 586 patches
Hello Vim users!
I have built a version of Vim 8.0 with all the latest patches. This is
mainly interesting for MS-Windows users who download the binary.
Upgrading to this version is recommended, since it fixes many
problems.
I have renamed the original Vim 8.0 files to include the patchlevel.
The new files are both available as "80" and "80-586". Note that
caching may cause the "80" file to still be the old one.
Since patch 8.0.0029 removed support for older MS-Windows systems, only
MS-Windows XP and later are supported.
Most MS-Windows users will want to get this one:
ftp://ftp.vim.org/pub/vim/pc/gvim80-586.exe
These files available for download:
UNIX:
sources + runtime files, bzip2 compressed:
ftp://ftp.vim.org/pub/vim/unix/vim-8.0.tar.bz2
ftp://ftp.vim.org/pub/vim/unix/vim-8.0.586.tar.bz2
VARIOUS:
help files converted to HTML:
ftp://ftp.vim.org/pub/vim/doc/vim80html.zip
ftp://ftp.vim.org/pub/vim/doc/vim80-586html.zip
MS-WINDOWS one-size-fits-all:
Self-installing, includes all runtime files, loads libraries dynamically:
ftp://ftp.vim.org/pub/vim/pc/gvim80.exe
ftp://ftp.vim.org/pub/vim/pc/gvim80-586.exe
MS-WINDOWS separate files:
Runtime files:
ftp://ftp.vim.org/pub/vim/pc/vim80rt.zip
ftp://ftp.vim.org/pub/vim/pc/vim80-586rt.zip
GUI binary for Windows XP and later:
ftp://ftp.vim.org/pub/vim/pc/gvim80.zip
ftp://ftp.vim.org/pub/vim/pc/gvim80-586.zip
GUI binary with OLE support:
ftp://ftp.vim.org/pub/vim/pc/gvim80ole.zip
ftp://ftp.vim.org/pub/vim/pc/gvim80-586ole.zip
Console version for Windows NT/2000/XP/7:
ftp://ftp.vim.org/pub/vim/pc/vim80w32.zip
ftp://ftp.vim.org/pub/vim/pc/vim80-586w32.zip
Sources for PC (with CR-LF):
ftp://ftp.vim.org/pub/vim/pc/vim80src.zip
ftp://ftp.vim.org/pub/vim/pc/vim80-586src.zip
For debugging:
ftp://ftp.vim.org/pub/vim/pc/gvim80.pdb
ftp://ftp.vim.org/pub/vim/pc/gvim80-586.pdb
ftp://ftp.vim.org/pub/vim/pc/gvim80ole.pdb
ftp://ftp.vim.org/pub/vim/pc/gvim80-586ole.pdb
ftp://ftp.vim.org/pub/vim/pc/vim80w32.pdb
ftp://ftp.vim.org/pub/vim/pc/vim80-586w32.pdb
Omitted in this version are:
- The 16-bit DOS, OS/2 and Amiga versions, these are obsolete.
- The MS-Windows versions for Windows older than XP
Happy Vimming!
--
There can't be a crisis today, my schedule is already full.
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I have built a version of Vim 8.0 with all the latest patches. This is
mainly interesting for MS-Windows users who download the binary.
Upgrading to this version is recommended, since it fixes many
problems.
I have renamed the original Vim 8.0 files to include the patchlevel.
The new files are both available as "80" and "80-586". Note that
caching may cause the "80" file to still be the old one.
Since patch 8.0.0029 removed support for older MS-Windows systems, only
MS-Windows XP and later are supported.
Most MS-Windows users will want to get this one:
ftp://ftp.vim.org/pub/vim/pc/gvim80-586.exe
These files available for download:
UNIX:
sources + runtime files, bzip2 compressed:
ftp://ftp.vim.org/pub/vim/unix/vim-8.0.tar.bz2
ftp://ftp.vim.org/pub/vim/unix/vim-8.0.586.tar.bz2
VARIOUS:
help files converted to HTML:
ftp://ftp.vim.org/pub/vim/doc/vim80html.zip
ftp://ftp.vim.org/pub/vim/doc/vim80-586html.zip
MS-WINDOWS one-size-fits-all:
Self-installing, includes all runtime files, loads libraries dynamically:
ftp://ftp.vim.org/pub/vim/pc/gvim80.exe
ftp://ftp.vim.org/pub/vim/pc/gvim80-586.exe
MS-WINDOWS separate files:
Runtime files:
ftp://ftp.vim.org/pub/vim/pc/vim80rt.zip
ftp://ftp.vim.org/pub/vim/pc/vim80-586rt.zip
GUI binary for Windows XP and later:
ftp://ftp.vim.org/pub/vim/pc/gvim80.zip
ftp://ftp.vim.org/pub/vim/pc/gvim80-586.zip
GUI binary with OLE support:
ftp://ftp.vim.org/pub/vim/pc/gvim80ole.zip
ftp://ftp.vim.org/pub/vim/pc/gvim80-586ole.zip
Console version for Windows NT/2000/XP/7:
ftp://ftp.vim.org/pub/vim/pc/vim80w32.zip
ftp://ftp.vim.org/pub/vim/pc/vim80-586w32.zip
Sources for PC (with CR-LF):
ftp://ftp.vim.org/pub/vim/pc/vim80src.zip
ftp://ftp.vim.org/pub/vim/pc/vim80-586src.zip
For debugging:
ftp://ftp.vim.org/pub/vim/pc/gvim80.pdb
ftp://ftp.vim.org/pub/vim/pc/gvim80-586.pdb
ftp://ftp.vim.org/pub/vim/pc/gvim80ole.pdb
ftp://ftp.vim.org/pub/vim/pc/gvim80-586ole.pdb
ftp://ftp.vim.org/pub/vim/pc/vim80w32.pdb
ftp://ftp.vim.org/pub/vim/pc/vim80-586w32.pdb
Omitted in this version are:
- The 16-bit DOS, OS/2 and Amiga versions, these are obsolete.
- The MS-Windows versions for Windows older than XP
Happy Vimming!
--
There can't be a crisis today, my schedule is already full.
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
On 23 Apr 2017, acampbell wrote:
I've now resubscribed to the list and have also added my normal domain
name address as an alternative in gmail, so let's see if I can now post
again to the list.
--
Anthony Campbell http://www.acampbell.uk
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I've now resubscribed to the list and have also added my normal domain
name address as an alternative in gmail, so let's see if I can now post
again to the list.
--
Anthony Campbell http://www.acampbell.uk
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: command-t plugin need wrong ruby version
Hi,
2017/4/21 Fri 1:48:01 UTC+9 Sand Glass wrote:
> I want to install command-t plugin.(gvim 7.4; windows)
> https://github.com/wincent/command-t
> It needs ruby 1.9.2. I download the right ruby version.
> http://rubyinstaller.org/downloads/archives
> But when I run ':ruby 1' to test ruby. It shows Error "E370 msvcrt-ruby192.dll
> lost", then I goto the ruby diretory to search the 192.dll, but only msvcrt-ruby191.dll, I tried all 192 ruby verion in above page. All of them 191.dll, I tried to change msvcrt-ruby191.dll to msvcrt-ruby192.dll, not work.
>
> question:
> Is there anyone istall command-t plugin, how do you do it?
I think that ruby support of the official Vim 7.4 installer is broken.
Ruby's dll has the API version in its name. Ruby 1.9.2's API version is 1.9.1.
So the dll name should include 191. However, strangely Vim 7.4 requires 192.
I think the easiest way to enable ruby support is using Vim 8.0.
(I don't know about command-t.)
Regards,
Ken Takata
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
2017/4/21 Fri 1:48:01 UTC+9 Sand Glass wrote:
> I want to install command-t plugin.(gvim 7.4; windows)
> https://github.com/wincent/command-t
> It needs ruby 1.9.2. I download the right ruby version.
> http://rubyinstaller.org/downloads/archives
> But when I run ':ruby 1' to test ruby. It shows Error "E370 msvcrt-ruby192.dll
> lost", then I goto the ruby diretory to search the 192.dll, but only msvcrt-ruby191.dll, I tried all 192 ruby verion in above page. All of them 191.dll, I tried to change msvcrt-ruby191.dll to msvcrt-ruby192.dll, not work.
>
> question:
> Is there anyone istall command-t plugin, how do you do it?
I think that ruby support of the official Vim 7.4 installer is broken.
Ruby's dll has the API version in its name. Ruby 1.9.2's API version is 1.9.1.
So the dll name should include 191. However, strangely Vim 7.4 requires 192.
I think the easiest way to enable ruby support is using Vim 8.0.
(I don't know about command-t.)
Regards,
Ken Takata
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
On Sunday, 23 April 2017 09:14:27 UTC+1, George Dinwiddie wrote:
> Anthony,
>
> I think I see the problem. See below...
>
> On 4/23/17 3:50 AM, acampbell wrote:
> > On Saturday, 22 April 2017 20:22:07 UTC+1, Bram Moolenaar wrote:
> >> Anthony Campbell wrote:
> >>
> >>> On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
> >>>> On Sat, 22 Apr 2017 15:17:54 +0200
> >>>> Bram Moolenaar <Bram@moolenaar.net> wrote:
> >>>>
> >>>>>
> >>>>> Anthony Campbell wrote:
> >>>>>
> >>>>>> I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> >>>>>> mail from the list. And when I tried to email the list myself it
> >>>>>> bounced. Is there a problem I'm not aware of?
> >>>>>
> >>>>> Well, this message arrived. I don't see anything special about your
> >>>>> membership. Perhaps check the spam folder?
> >>>>>
> >>>>
> >>>> Yes but he mostly likely use the Google Group web page rather than an
> >>>> email client to post it.
> >>>>
> >>>> https://groups.google.com/forum/#!forum/vim_use
> >>>>
> >>>>
> >>>> --
> >>>> Don't stop where the ink does.
> >>>>
> >>>> Shawn H Corey
> >>>
> >>> Yes, that's right. I posted a message by email to vim_user@gmail.com
> >>> but it bounced. So I came here to post the same thing.
> >>
> >> That's the wrong address, use vim_use@googlegroups.com. And make sure
> >> you send it from the same account you subscribed with.
> >>
> >>> I've been subscribed to the list via email for many months and never
> >>> had any problem either receiving messages or sending them. Perhaps I
> >>> should unsubscribe and resubscribe.
> >>
> >> --
> >> The early bird gets the worm. The second mouse gets the cheese.
> >>
> >> /// Bram Moolenaar -- Bram@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 ///
> >
> > Sorry, got my brain wires crossed; that was a typo; I was emailing the correct addrress. Here is the bounce message:
> >
> >
> > We're writing to let you know that the group you tried to contact (vim_use) may not exist, or you may not have
> > permission to post messages to the group. A few more details on why you weren't able to post:
> >
> > * You might have spelled or formatted the group name incorrectly.
> > * The owner of the group may have removed this group.
> > * You may need to join the group before receiving permission to post.
> > * This group may not be open to posting.
> >
> > If you have questions related to this or any other Google Group, visit the Help Center at
> > https://groups.google.com/support/.
> >
> > [cut]
> >
> > Received: from [88.97.55.211] (port=41111 helo=localhost)
> > by shcp05.hosting.zen.net.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
> > (Exim 4.87)
> > (envelope-from <ac@mydomain>)
>
> Try sending from <camanthony@gmail.com> instead.
>
> - George
>
> > id 1d1r61-002HtJ-Ny
> > for vim_use@googlegroups.com; Sat, 22 Apr 2017 10:12:58 +0100
> >
> > [cut]
> >
>
> --
> ----------------------------------------------------------------------
> * George Dinwiddie * http://blog.gdinwiddie.com
> Software Development http://www.idiacomputing.com
> Consultant and Coach http://www.agilemaryland.org
> ----------------------------------------------------------------------
Yes, I expect you are right. I don't know how it has begun to set my gmail account as sender, but I don't want to use that (don't like gmail) so I will resubscribe to try to fix that.
As regards the non-arrival of mail from the list, I found the problem there; my fault, I'd created an error in my procmailrc.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Anthony,
>
> I think I see the problem. See below...
>
> On 4/23/17 3:50 AM, acampbell wrote:
> > On Saturday, 22 April 2017 20:22:07 UTC+1, Bram Moolenaar wrote:
> >> Anthony Campbell wrote:
> >>
> >>> On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
> >>>> On Sat, 22 Apr 2017 15:17:54 +0200
> >>>> Bram Moolenaar <Bram@moolenaar.net> wrote:
> >>>>
> >>>>>
> >>>>> Anthony Campbell wrote:
> >>>>>
> >>>>>> I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> >>>>>> mail from the list. And when I tried to email the list myself it
> >>>>>> bounced. Is there a problem I'm not aware of?
> >>>>>
> >>>>> Well, this message arrived. I don't see anything special about your
> >>>>> membership. Perhaps check the spam folder?
> >>>>>
> >>>>
> >>>> Yes but he mostly likely use the Google Group web page rather than an
> >>>> email client to post it.
> >>>>
> >>>> https://groups.google.com/forum/#!forum/vim_use
> >>>>
> >>>>
> >>>> --
> >>>> Don't stop where the ink does.
> >>>>
> >>>> Shawn H Corey
> >>>
> >>> Yes, that's right. I posted a message by email to vim_user@gmail.com
> >>> but it bounced. So I came here to post the same thing.
> >>
> >> That's the wrong address, use vim_use@googlegroups.com. And make sure
> >> you send it from the same account you subscribed with.
> >>
> >>> I've been subscribed to the list via email for many months and never
> >>> had any problem either receiving messages or sending them. Perhaps I
> >>> should unsubscribe and resubscribe.
> >>
> >> --
> >> The early bird gets the worm. The second mouse gets the cheese.
> >>
> >> /// Bram Moolenaar -- Bram@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 ///
> >
> > Sorry, got my brain wires crossed; that was a typo; I was emailing the correct addrress. Here is the bounce message:
> >
> >
> > We're writing to let you know that the group you tried to contact (vim_use) may not exist, or you may not have
> > permission to post messages to the group. A few more details on why you weren't able to post:
> >
> > * You might have spelled or formatted the group name incorrectly.
> > * The owner of the group may have removed this group.
> > * You may need to join the group before receiving permission to post.
> > * This group may not be open to posting.
> >
> > If you have questions related to this or any other Google Group, visit the Help Center at
> > https://groups.google.com/support/.
> >
> > [cut]
> >
> > Received: from [88.97.55.211] (port=41111 helo=localhost)
> > by shcp05.hosting.zen.net.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
> > (Exim 4.87)
> > (envelope-from <ac@mydomain>)
>
> Try sending from <camanthony@gmail.com> instead.
>
> - George
>
> > id 1d1r61-002HtJ-Ny
> > for vim_use@googlegroups.com; Sat, 22 Apr 2017 10:12:58 +0100
> >
> > [cut]
> >
>
> --
> ----------------------------------------------------------------------
> * George Dinwiddie * http://blog.gdinwiddie.com
> Software Development http://www.idiacomputing.com
> Consultant and Coach http://www.agilemaryland.org
> ----------------------------------------------------------------------
Yes, I expect you are right. I don't know how it has begun to set my gmail account as sender, but I don't want to use that (don't like gmail) so I will resubscribe to try to fix that.
As regards the non-arrival of mail from the list, I found the problem there; my fault, I'd created an error in my procmailrc.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
Anthony,
I think I see the problem. See below...
On 4/23/17 3:50 AM, acampbell wrote:
> On Saturday, 22 April 2017 20:22:07 UTC+1, Bram Moolenaar wrote:
>> Anthony Campbell wrote:
>>
>>> On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
>>>> On Sat, 22 Apr 2017 15:17:54 +0200
>>>> Bram Moolenaar <Bram@moolenaar.net> wrote:
>>>>
>>>>>
>>>>> Anthony Campbell wrote:
>>>>>
>>>>>> I'm subscribe to vim_use@ but for the last 2 weeks I've received no
>>>>>> mail from the list. And when I tried to email the list myself it
>>>>>> bounced. Is there a problem I'm not aware of?
>>>>>
>>>>> Well, this message arrived. I don't see anything special about your
>>>>> membership. Perhaps check the spam folder?
>>>>>
>>>>
>>>> Yes but he mostly likely use the Google Group web page rather than an
>>>> email client to post it.
>>>>
>>>> https://groups.google.com/forum/#!forum/vim_use
>>>>
>>>>
>>>> --
>>>> Don't stop where the ink does.
>>>>
>>>> Shawn H Corey
>>>
>>> Yes, that's right. I posted a message by email to vim_user@gmail.com
>>> but it bounced. So I came here to post the same thing.
>>
>> That's the wrong address, use vim_use@googlegroups.com. And make sure
>> you send it from the same account you subscribed with.
>>
>>> I've been subscribed to the list via email for many months and never
>>> had any problem either receiving messages or sending them. Perhaps I
>>> should unsubscribe and resubscribe.
>>
>> --
>> The early bird gets the worm. The second mouse gets the cheese.
>>
>> /// Bram Moolenaar -- Bram@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 ///
>
> Sorry, got my brain wires crossed; that was a typo; I was emailing the correct addrress. Here is the bounce message:
>
>
> We're writing to let you know that the group you tried to contact (vim_use) may not exist, or you may not have
> permission to post messages to the group. A few more details on why you weren't able to post:
>
> * You might have spelled or formatted the group name incorrectly.
> * The owner of the group may have removed this group.
> * You may need to join the group before receiving permission to post.
> * This group may not be open to posting.
>
> If you have questions related to this or any other Google Group, visit the Help Center at
> https://groups.google.com/support/.
>
> [cut]
>
> Received: from [88.97.55.211] (port=41111 helo=localhost)
> by shcp05.hosting.zen.net.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
> (Exim 4.87)
> (envelope-from <ac@mydomain>)
Try sending from <camanthony@gmail.com> instead.
- George
> id 1d1r61-002HtJ-Ny
> for vim_use@googlegroups.com; Sat, 22 Apr 2017 10:12:58 +0100
>
> [cut]
>
--
----------------------------------------------------------------------
* George Dinwiddie * http://blog.gdinwiddie.com
Software Development http://www.idiacomputing.com
Consultant and Coach http://www.agilemaryland.org
----------------------------------------------------------------------
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I think I see the problem. See below...
On 4/23/17 3:50 AM, acampbell wrote:
> On Saturday, 22 April 2017 20:22:07 UTC+1, Bram Moolenaar wrote:
>> Anthony Campbell wrote:
>>
>>> On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
>>>> On Sat, 22 Apr 2017 15:17:54 +0200
>>>> Bram Moolenaar <Bram@moolenaar.net> wrote:
>>>>
>>>>>
>>>>> Anthony Campbell wrote:
>>>>>
>>>>>> I'm subscribe to vim_use@ but for the last 2 weeks I've received no
>>>>>> mail from the list. And when I tried to email the list myself it
>>>>>> bounced. Is there a problem I'm not aware of?
>>>>>
>>>>> Well, this message arrived. I don't see anything special about your
>>>>> membership. Perhaps check the spam folder?
>>>>>
>>>>
>>>> Yes but he mostly likely use the Google Group web page rather than an
>>>> email client to post it.
>>>>
>>>> https://groups.google.com/forum/#!forum/vim_use
>>>>
>>>>
>>>> --
>>>> Don't stop where the ink does.
>>>>
>>>> Shawn H Corey
>>>
>>> Yes, that's right. I posted a message by email to vim_user@gmail.com
>>> but it bounced. So I came here to post the same thing.
>>
>> That's the wrong address, use vim_use@googlegroups.com. And make sure
>> you send it from the same account you subscribed with.
>>
>>> I've been subscribed to the list via email for many months and never
>>> had any problem either receiving messages or sending them. Perhaps I
>>> should unsubscribe and resubscribe.
>>
>> --
>> The early bird gets the worm. The second mouse gets the cheese.
>>
>> /// Bram Moolenaar -- Bram@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 ///
>
> Sorry, got my brain wires crossed; that was a typo; I was emailing the correct addrress. Here is the bounce message:
>
>
> We're writing to let you know that the group you tried to contact (vim_use) may not exist, or you may not have
> permission to post messages to the group. A few more details on why you weren't able to post:
>
> * You might have spelled or formatted the group name incorrectly.
> * The owner of the group may have removed this group.
> * You may need to join the group before receiving permission to post.
> * This group may not be open to posting.
>
> If you have questions related to this or any other Google Group, visit the Help Center at
> https://groups.google.com/support/.
>
> [cut]
>
> Received: from [88.97.55.211] (port=41111 helo=localhost)
> by shcp05.hosting.zen.net.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
> (Exim 4.87)
> (envelope-from <ac@mydomain>)
Try sending from <camanthony@gmail.com> instead.
- George
> id 1d1r61-002HtJ-Ny
> for vim_use@googlegroups.com; Sat, 22 Apr 2017 10:12:58 +0100
>
> [cut]
>
--
----------------------------------------------------------------------
* George Dinwiddie * http://blog.gdinwiddie.com
Software Development http://www.idiacomputing.com
Consultant and Coach http://www.agilemaryland.org
----------------------------------------------------------------------
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
On Saturday, 22 April 2017 20:22:07 UTC+1, Bram Moolenaar wrote:
> Anthony Campbell wrote:
>
> > On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
> > > On Sat, 22 Apr 2017 15:17:54 +0200
> > > Bram Moolenaar <Bram@moolenaar.net> wrote:
> > >
> > > >
> > > > Anthony Campbell wrote:
> > > >
> > > > > I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> > > > > mail from the list. And when I tried to email the list myself it
> > > > > bounced. Is there a problem I'm not aware of?
> > > >
> > > > Well, this message arrived. I don't see anything special about your
> > > > membership. Perhaps check the spam folder?
> > > >
> > >
> > > Yes but he mostly likely use the Google Group web page rather than an
> > > email client to post it.
> > >
> > > https://groups.google.com/forum/#!forum/vim_use
> > >
> > >
> > > --
> > > Don't stop where the ink does.
> > >
> > > Shawn H Corey
> >
> > Yes, that's right. I posted a message by email to vim_user@gmail.com
> > but it bounced. So I came here to post the same thing.
>
> That's the wrong address, use vim_use@googlegroups.com. And make sure
> you send it from the same account you subscribed with.
>
> > I've been subscribed to the list via email for many months and never
> > had any problem either receiving messages or sending them. Perhaps I
> > should unsubscribe and resubscribe.
>
> --
> The early bird gets the worm. The second mouse gets the cheese.
>
> /// Bram Moolenaar -- Bram@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 ///
Sorry, got my brain wires crossed; that was a typo; I was emailing the correct addrress. Here is the bounce message:
We're writing to let you know that the group you tried to contact (vim_use) may not exist, or you may not have
permission to post messages to the group. A few more details on why you weren't able to post:
* You might have spelled or formatted the group name incorrectly.
* The owner of the group may have removed this group.
* You may need to join the group before receiving permission to post.
* This group may not be open to posting.
If you have questions related to this or any other Google Group, visit the Help Center at
https://groups.google.com/support/.
[cut]
Received: from [88.97.55.211] (port=41111 helo=localhost)
by shcp05.hosting.zen.net.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.87)
(envelope-from <ac@mydomain>)
id 1d1r61-002HtJ-Ny
for vim_use@googlegroups.com; Sat, 22 Apr 2017 10:12:58 +0100
[cut]
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Anthony Campbell wrote:
>
> > On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
> > > On Sat, 22 Apr 2017 15:17:54 +0200
> > > Bram Moolenaar <Bram@moolenaar.net> wrote:
> > >
> > > >
> > > > Anthony Campbell wrote:
> > > >
> > > > > I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> > > > > mail from the list. And when I tried to email the list myself it
> > > > > bounced. Is there a problem I'm not aware of?
> > > >
> > > > Well, this message arrived. I don't see anything special about your
> > > > membership. Perhaps check the spam folder?
> > > >
> > >
> > > Yes but he mostly likely use the Google Group web page rather than an
> > > email client to post it.
> > >
> > > https://groups.google.com/forum/#!forum/vim_use
> > >
> > >
> > > --
> > > Don't stop where the ink does.
> > >
> > > Shawn H Corey
> >
> > Yes, that's right. I posted a message by email to vim_user@gmail.com
> > but it bounced. So I came here to post the same thing.
>
> That's the wrong address, use vim_use@googlegroups.com. And make sure
> you send it from the same account you subscribed with.
>
> > I've been subscribed to the list via email for many months and never
> > had any problem either receiving messages or sending them. Perhaps I
> > should unsubscribe and resubscribe.
>
> --
> The early bird gets the worm. The second mouse gets the cheese.
>
> /// Bram Moolenaar -- Bram@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 ///
Sorry, got my brain wires crossed; that was a typo; I was emailing the correct addrress. Here is the bounce message:
We're writing to let you know that the group you tried to contact (vim_use) may not exist, or you may not have
permission to post messages to the group. A few more details on why you weren't able to post:
* You might have spelled or formatted the group name incorrectly.
* The owner of the group may have removed this group.
* You may need to join the group before receiving permission to post.
* This group may not be open to posting.
If you have questions related to this or any other Google Group, visit the Help Center at
https://groups.google.com/support/.
[cut]
Received: from [88.97.55.211] (port=41111 helo=localhost)
by shcp05.hosting.zen.net.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.87)
(envelope-from <ac@mydomain>)
id 1d1r61-002HtJ-Ny
for vim_use@googlegroups.com; Sat, 22 Apr 2017 10:12:58 +0100
[cut]
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Saturday, April 22, 2017
Re: A million Euro raised for Uganda
On Fri, Apr 21, 2017, at 20:28, Bram Moolenaar wrote:
> > It looks like that as of 2017, about a million Euro in total has been
> > raised for Uganda. See my answer here for details:
> > https://vi.stackexchange.com/q/572/51
> >
> > Of course, we don't know if it was all Vimmers that raised the million,
> > but the majority probably is.
>
> Wow, that's impressive!
>
> The estimate for the German donations are a bit too high though. Last
> year was about 16,000 euro.
Ow... I just scaled them with the same number as the regular donations.
If you happen to have more accurate numbers at hand for the rest of the
years then that would be nice (if you don't, then don't bother).
> If you wonder what the children get for the money: We recently had two
> students finish their university studies that we are proud of. One of
> them is now a Doctor (still has to finish his practical year) and one a
> registered lawyer.
That's good to hear. Sounds like the "teach a person to fish"-sort of
aid!
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> > It looks like that as of 2017, about a million Euro in total has been
> > raised for Uganda. See my answer here for details:
> > https://vi.stackexchange.com/q/572/51
> >
> > Of course, we don't know if it was all Vimmers that raised the million,
> > but the majority probably is.
>
> Wow, that's impressive!
>
> The estimate for the German donations are a bit too high though. Last
> year was about 16,000 euro.
Ow... I just scaled them with the same number as the regular donations.
If you happen to have more accurate numbers at hand for the rest of the
years then that would be nice (if you don't, then don't bother).
> If you wonder what the children get for the money: We recently had two
> students finish their university studies that we are proud of. One of
> them is now a Doctor (still has to finish his practical year) and one a
> registered lawyer.
That's good to hear. Sounds like the "teach a person to fish"-sort of
aid!
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim documentation index.txt using word "buffer" for the word "register"
René wrote:
> I'm preparing a presentation of Vim's essentials hence I'm extensively
> browsing through Vim's documentation. Unless I'm mistaken it seems
> that in the index.txt file the word 'buffer' is quite often used in
> lieu of 'register'. I found this by chance while I was looking for the
> word 'buffer' (:help index :set hls /buffer).
>
> For instance:
>
> |C| ["x]C 2 change from the cursor position to the end
> of the line, and N-1 more lines [into
> buffer x]; synonym for "c$"
>
> Now if I follow the tag |C| (positioning my cursor on it, then typing CTRL-]) I read in change.txt:
>
> *C*
> ["x]C Delete from the cursor position to the end of the
> line and [count]-1 more lines [into register x], and
> start insert. Synonym for c$ (not |linewise|).
>
> The notation '"x' unambiguously refers to 'register x'. So in the
> index.txt file I think that one should read 'register' in lieu of
> 'buffer' while the text in change.txt uses the word 'register'
> correctly.
>
> This is mostly the case in section 2 (Normal mode) and once in section
> 2.4 (gp command). In other places (section 5 EX commands) the word
> 'buffer' seems to be always used appropriately.
>
> These small discrepancies might confuse new users. Indeed clear
> vocabulary and precise definitions are important in the learning
> process.
>
> I'm too new to Vim and far from an expert but I'd be very happy to
> contribute by reviewing the index.txt file and proposing an update
> with the word changes. It seems not too difficult: everywhere one
> reads '["x]' one should also read '[into register x]'. However I'd
> prefer to pass my updates to someone with expertise and authority to
> review my proposed changes.
>
> Note: I found it in Vim version 7.4 and 8.0
You are right, these "buffer x" should be "register x". There are a few
of them. I'll fix it.
--
LAUNCELOT: I am, sir. I am a Knight of King Arthur.
FATHER: 'Mm ... very nice castle, Camelot ... very good pig country....
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> I'm preparing a presentation of Vim's essentials hence I'm extensively
> browsing through Vim's documentation. Unless I'm mistaken it seems
> that in the index.txt file the word 'buffer' is quite often used in
> lieu of 'register'. I found this by chance while I was looking for the
> word 'buffer' (:help index :set hls /buffer).
>
> For instance:
>
> |C| ["x]C 2 change from the cursor position to the end
> of the line, and N-1 more lines [into
> buffer x]; synonym for "c$"
>
> Now if I follow the tag |C| (positioning my cursor on it, then typing CTRL-]) I read in change.txt:
>
> *C*
> ["x]C Delete from the cursor position to the end of the
> line and [count]-1 more lines [into register x], and
> start insert. Synonym for c$ (not |linewise|).
>
> The notation '"x' unambiguously refers to 'register x'. So in the
> index.txt file I think that one should read 'register' in lieu of
> 'buffer' while the text in change.txt uses the word 'register'
> correctly.
>
> This is mostly the case in section 2 (Normal mode) and once in section
> 2.4 (gp command). In other places (section 5 EX commands) the word
> 'buffer' seems to be always used appropriately.
>
> These small discrepancies might confuse new users. Indeed clear
> vocabulary and precise definitions are important in the learning
> process.
>
> I'm too new to Vim and far from an expert but I'd be very happy to
> contribute by reviewing the index.txt file and proposing an update
> with the word changes. It seems not too difficult: everywhere one
> reads '["x]' one should also read '[into register x]'. However I'd
> prefer to pass my updates to someone with expertise and authority to
> review my proposed changes.
>
> Note: I found it in Vim version 7.4 and 8.0
You are right, these "buffer x" should be "register x". There are a few
of them. I'll fix it.
--
LAUNCELOT: I am, sir. I am a Knight of King Arthur.
FATHER: 'Mm ... very nice castle, Camelot ... very good pig country....
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
Anthony Campbell wrote:
> On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
> > On Sat, 22 Apr 2017 15:17:54 +0200
> > Bram Moolenaar <Bram@moolenaar.net> wrote:
> >
> > >
> > > Anthony Campbell wrote:
> > >
> > > > I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> > > > mail from the list. And when I tried to email the list myself it
> > > > bounced. Is there a problem I'm not aware of?
> > >
> > > Well, this message arrived. I don't see anything special about your
> > > membership. Perhaps check the spam folder?
> > >
> >
> > Yes but he mostly likely use the Google Group web page rather than an
> > email client to post it.
> >
> > https://groups.google.com/forum/#!forum/vim_use
> >
> >
> > --
> > Don't stop where the ink does.
> >
> > Shawn H Corey
>
> Yes, that's right. I posted a message by email to vim_user@gmail.com
> but it bounced. So I came here to post the same thing.
That's the wrong address, use vim_use@googlegroups.com. And make sure
you send it from the same account you subscribed with.
> I've been subscribed to the list via email for many months and never
> had any problem either receiving messages or sending them. Perhaps I
> should unsubscribe and resubscribe.
--
The early bird gets the worm. The second mouse gets the cheese.
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
> > On Sat, 22 Apr 2017 15:17:54 +0200
> > Bram Moolenaar <Bram@moolenaar.net> wrote:
> >
> > >
> > > Anthony Campbell wrote:
> > >
> > > > I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> > > > mail from the list. And when I tried to email the list myself it
> > > > bounced. Is there a problem I'm not aware of?
> > >
> > > Well, this message arrived. I don't see anything special about your
> > > membership. Perhaps check the spam folder?
> > >
> >
> > Yes but he mostly likely use the Google Group web page rather than an
> > email client to post it.
> >
> > https://groups.google.com/forum/#!forum/vim_use
> >
> >
> > --
> > Don't stop where the ink does.
> >
> > Shawn H Corey
>
> Yes, that's right. I posted a message by email to vim_user@gmail.com
> but it bounced. So I came here to post the same thing.
That's the wrong address, use vim_use@googlegroups.com. And make sure
you send it from the same account you subscribed with.
> I've been subscribed to the list via email for many months and never
> had any problem either receiving messages or sending them. Perhaps I
> should unsubscribe and resubscribe.
--
The early bird gets the worm. The second mouse gets the cheese.
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
Anthony,
On 4/22/17 11:36 AM, acampbell wrote:
> On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
>> On Sat, 22 Apr 2017 15:17:54 +0200
>> Bram Moolenaar <Bram@moolenaar.net> wrote:
>>
>>>
>>> Anthony Campbell wrote:
>>>
>>>> I'm subscribe to vim_use@ but for the last 2 weeks I've received no
>>>> mail from the list. And when I tried to email the list myself it
>>>> bounced. Is there a problem I'm not aware of?
>>>
>>> Well, this message arrived. I don't see anything special about your
>>> membership. Perhaps check the spam folder?
>>>
>>
>> Yes but he mostly likely use the Google Group web page rather than an
>> email client to post it.
>>
>> https://groups.google.com/forum/#!forum/vim_use
>>
>>
>> --
>> Don't stop where the ink does.
>>
>> Shawn H Corey
>
> Yes, that's right. I posted a message by email to vim_user@gmail.com
> but it bounced. So I came here to post the same thing.
>
> I've been subscribed to the list via email for many months and never
> had any problem either receiving messages or sending them. Perhaps I
> should unsubscribe and resubscribe.
I doubt it's a subscription problem, since these messages come through.
What is the content of the bounce message? That should shed some light.
- George
--
----------------------------------------------------------------------
* George Dinwiddie * http://blog.gdinwiddie.com
Software Development http://www.idiacomputing.com
Consultant and Coach http://www.agilemaryland.org
----------------------------------------------------------------------
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On 4/22/17 11:36 AM, acampbell wrote:
> On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
>> On Sat, 22 Apr 2017 15:17:54 +0200
>> Bram Moolenaar <Bram@moolenaar.net> wrote:
>>
>>>
>>> Anthony Campbell wrote:
>>>
>>>> I'm subscribe to vim_use@ but for the last 2 weeks I've received no
>>>> mail from the list. And when I tried to email the list myself it
>>>> bounced. Is there a problem I'm not aware of?
>>>
>>> Well, this message arrived. I don't see anything special about your
>>> membership. Perhaps check the spam folder?
>>>
>>
>> Yes but he mostly likely use the Google Group web page rather than an
>> email client to post it.
>>
>> https://groups.google.com/forum/#!forum/vim_use
>>
>>
>> --
>> Don't stop where the ink does.
>>
>> Shawn H Corey
>
> Yes, that's right. I posted a message by email to vim_user@gmail.com
> but it bounced. So I came here to post the same thing.
>
> I've been subscribed to the list via email for many months and never
> had any problem either receiving messages or sending them. Perhaps I
> should unsubscribe and resubscribe.
I doubt it's a subscription problem, since these messages come through.
What is the content of the bounce message? That should shed some light.
- George
--
----------------------------------------------------------------------
* George Dinwiddie * http://blog.gdinwiddie.com
Software Development http://www.idiacomputing.com
Consultant and Coach http://www.agilemaryland.org
----------------------------------------------------------------------
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
On Sat, 22 Apr 2017 08:36:45 -0700 (PDT)
acampbell <camanthony@gmail.com> wrote:
> Yes, that's right. I posted a message by email to vim_user@gmail.com
> but it bounced. So I came here to post the same thing.
>
> I've been subscribed to the list via email for many months and never
> had any problem either receiving messages or sending them. Perhaps I
> should unsubscribe and resubscribe.
Have you checked your spam filter? Do it thru your browser. Sometimes
Gmail is very aggressive about spam.
--
Don't stop where the ink does.
Shawn H Corey
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
acampbell <camanthony@gmail.com> wrote:
> Yes, that's right. I posted a message by email to vim_user@gmail.com
> but it bounced. So I came here to post the same thing.
>
> I've been subscribed to the list via email for many months and never
> had any problem either receiving messages or sending them. Perhaps I
> should unsubscribe and resubscribe.
Have you checked your spam filter? Do it thru your browser. Sometimes
Gmail is very aggressive about spam.
--
Don't stop where the ink does.
Shawn H Corey
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
On Saturday, 22 April 2017 14:21:24 UTC+1, Shawn H Corey wrote:
> On Sat, 22 Apr 2017 15:17:54 +0200
> Bram Moolenaar <Bram@moolenaar.net> wrote:
>
> >
> > Anthony Campbell wrote:
> >
> > > I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> > > mail from the list. And when I tried to email the list myself it
> > > bounced. Is there a problem I'm not aware of?
> >
> > Well, this message arrived. I don't see anything special about your
> > membership. Perhaps check the spam folder?
> >
>
> Yes but he mostly likely use the Google Group web page rather than an
> email client to post it.
>
> https://groups.google.com/forum/#!forum/vim_use
>
>
> --
> Don't stop where the ink does.
>
> Shawn H Corey
Yes, that's right. I posted a message by email to vim_user@gmail.com but it bounced. So I came here to post the same thing.
I've been subscribed to the list via email for many months and never had any problem either receiving messages or sending them. Perhaps I should unsubscribe and resubscribe.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Sat, 22 Apr 2017 15:17:54 +0200
> Bram Moolenaar <Bram@moolenaar.net> wrote:
>
> >
> > Anthony Campbell wrote:
> >
> > > I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> > > mail from the list. And when I tried to email the list myself it
> > > bounced. Is there a problem I'm not aware of?
> >
> > Well, this message arrived. I don't see anything special about your
> > membership. Perhaps check the spam folder?
> >
>
> Yes but he mostly likely use the Google Group web page rather than an
> email client to post it.
>
> https://groups.google.com/forum/#!forum/vim_use
>
>
> --
> Don't stop where the ink does.
>
> Shawn H Corey
Yes, that's right. I posted a message by email to vim_user@gmail.com but it bounced. So I came here to post the same thing.
I've been subscribed to the list via email for many months and never had any problem either receiving messages or sending them. Perhaps I should unsubscribe and resubscribe.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
On Saturday, 22 April 2017 11:25:31 UTC+1, acampbell wrote:
> I'm subscribe to vim_use@ but for the last 2 weeks I've received no mail from the list. And when I tried to email the list myself it bounced. Is there a problem I'm not aware of?
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> I'm subscribe to vim_use@ but for the last 2 weeks I've received no mail from the list. And when I tried to email the list myself it bounced. Is there a problem I'm not aware of?
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] minpac v1.0: a minimal package manager for Vim 8
Hi Bram,
At first, I have to say one thing: minpac is actually a plugin manager using
the packages feature, not a package manager. It cannot download packages and
install them.
(Maybe it's better to fix the document.)
2017/4/22 Sat 22:18:04 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > I announce release of minpac ver 1.0.
> > It is a minimal package manager for Vim 8 (and Neovim).
> >
> > https://github.com/k-takata/minpac
> >
> > Minpac utilizes the packages feature of Vim 8, and uses the jobs feature for
> > parallel install/update. So, it is simple and fast.
> >
> > Have fun!
>
> Thanks for making this.
>
> Some questions pop up when reading the first page:
> - Does this only work with git repositories?
Yes, minpac supports only git repositories. Nowadays most Vim plugins have
each git repository.
I don't have a plan to support other types of plugins.
I want to keep minpac simple.
> - Does it automatically update, or does the user need to execute a
> command to update the packages?
It doesn't automatically update. If a user want to update plugins,
he need to execute:
call minpac#update()
Minpac doesn't define a command for this, but the user define a command for
this by himself if he want.
> - It mentions "start" plugins and "opt" plugins, who makes that choice?
The user should specify this as an argument of `minpac#add()`.
For "start" plugins:
call minpac#add('account/plugin')
or
call minpac#add('account/plugin', {'type': 'start'})
For "opt" plugins:
call minpac#add('account/plugin', {'type': 'opt'})
> - Is there a list of packages and how to add them?
As I wrote above, minpac actually doesn't manage packages. It only handles
one package, `~/.vim/pack/minpac` by default.
About a list of plugins, the user should register the plugins by `minpac#add()`.
Normally he will write a list in his .vimrc like this:
call minpac#add('account1/plugin1')
call minpac#add('account1/plugin2')
call minpac#add('account2/plugin3')
call minpac#add('https://example.com/account3/plugin4.git')
This is similar to other plugin managers: Vundle, vim-plug, dein.vim, etc.
Regards,
Ken Takata
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
At first, I have to say one thing: minpac is actually a plugin manager using
the packages feature, not a package manager. It cannot download packages and
install them.
(Maybe it's better to fix the document.)
2017/4/22 Sat 22:18:04 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > I announce release of minpac ver 1.0.
> > It is a minimal package manager for Vim 8 (and Neovim).
> >
> > https://github.com/k-takata/minpac
> >
> > Minpac utilizes the packages feature of Vim 8, and uses the jobs feature for
> > parallel install/update. So, it is simple and fast.
> >
> > Have fun!
>
> Thanks for making this.
>
> Some questions pop up when reading the first page:
> - Does this only work with git repositories?
Yes, minpac supports only git repositories. Nowadays most Vim plugins have
each git repository.
I don't have a plan to support other types of plugins.
I want to keep minpac simple.
> - Does it automatically update, or does the user need to execute a
> command to update the packages?
It doesn't automatically update. If a user want to update plugins,
he need to execute:
call minpac#update()
Minpac doesn't define a command for this, but the user define a command for
this by himself if he want.
> - It mentions "start" plugins and "opt" plugins, who makes that choice?
The user should specify this as an argument of `minpac#add()`.
For "start" plugins:
call minpac#add('account/plugin')
or
call minpac#add('account/plugin', {'type': 'start'})
For "opt" plugins:
call minpac#add('account/plugin', {'type': 'opt'})
> - Is there a list of packages and how to add them?
As I wrote above, minpac actually doesn't manage packages. It only handles
one package, `~/.vim/pack/minpac` by default.
About a list of plugins, the user should register the plugins by `minpac#add()`.
Normally he will write a list in his .vimrc like this:
call minpac#add('account1/plugin1')
call minpac#add('account1/plugin2')
call minpac#add('account2/plugin3')
call minpac#add('https://example.com/account3/plugin4.git')
This is similar to other plugin managers: Vundle, vim-plug, dein.vim, etc.
Regards,
Ken Takata
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
On Sat, 22 Apr 2017 15:17:54 +0200
Bram Moolenaar <Bram@moolenaar.net> wrote:
>
> Anthony Campbell wrote:
>
> > I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> > mail from the list. And when I tried to email the list myself it
> > bounced. Is there a problem I'm not aware of?
>
> Well, this message arrived. I don't see anything special about your
> membership. Perhaps check the spam folder?
>
Yes but he mostly likely use the Google Group web page rather than an
email client to post it.
https://groups.google.com/forum/#!forum/vim_use
--
Don't stop where the ink does.
Shawn H Corey
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Bram Moolenaar <Bram@moolenaar.net> wrote:
>
> Anthony Campbell wrote:
>
> > I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> > mail from the list. And when I tried to email the list myself it
> > bounced. Is there a problem I'm not aware of?
>
> Well, this message arrived. I don't see anything special about your
> membership. Perhaps check the spam folder?
>
Yes but he mostly likely use the Google Group web page rather than an
email client to post it.
https://groups.google.com/forum/#!forum/vim_use
--
Don't stop where the ink does.
Shawn H Corey
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] minpac v1.0: a minimal package manager for Vim 8
Ken Takata wrote:
> I announce release of minpac ver 1.0.
> It is a minimal package manager for Vim 8 (and Neovim).
>
> https://github.com/k-takata/minpac
>
> Minpac utilizes the packages feature of Vim 8, and uses the jobs feature for
> parallel install/update. So, it is simple and fast.
>
> Have fun!
Thanks for making this.
Some questions pop up when reading the first page:
- Does this only work with git repositories?
- Does it automatically update, or does the user need to execute a
command to update the packages?
- It mentions "start" plugins and "opt" plugins, who makes that choice?
- Is there a list of packages and how to add them?
--
No letters of the alphabet were harmed in the creation of this message.
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> I announce release of minpac ver 1.0.
> It is a minimal package manager for Vim 8 (and Neovim).
>
> https://github.com/k-takata/minpac
>
> Minpac utilizes the packages feature of Vim 8, and uses the jobs feature for
> parallel install/update. So, it is simple and fast.
>
> Have fun!
Thanks for making this.
Some questions pop up when reading the first page:
- Does this only work with git repositories?
- Does it automatically update, or does the user need to execute a
command to update the packages?
- It mentions "start" plugins and "opt" plugins, who makes that choice?
- Is there a list of packages and how to add them?
--
No letters of the alphabet were harmed in the creation of this message.
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: List not working for me any more
Anthony Campbell wrote:
> I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> mail from the list. And when I tried to email the list myself it
> bounced. Is there a problem I'm not aware of?
Well, this message arrived. I don't see anything special about your
membership. Perhaps check the spam folder?
--
"It's so simple to be wise. Just think of something stupid to say
and then don't say it." -- Sam Levenson
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> I'm subscribe to vim_use@ but for the last 2 weeks I've received no
> mail from the list. And when I tried to email the list myself it
> bounced. Is there a problem I'm not aware of?
Well, this message arrived. I don't see anything special about your
membership. Perhaps check the spam folder?
--
"It's so simple to be wise. Just think of something stupid to say
and then don't say it." -- Sam Levenson
/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
List not working for me any more
I'm subscribe to vim_use@ but for the last 2 weeks I've received no mail from the list. And when I tried to email the list myself it bounced. Is there a problem I'm not aware of?
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Swap directory changes when opening files under /media [Fedora]
2017-04-21 13:16 GMT+03:00 Ian <ian.cross@gmail.com>:
> Perfect, thanks. Here's what I get:
>
> --- Auto-Commands ---
> fedora BufReadPre
> /media/* set directory=~/tmp,/var/tmp,/tmp
> Last set from /etc/vimrc
> /run/media/*
> set directory=~/tmp,/var/tmp,/tmp
> Last set from /etc/vimrc
> /mnt/* set directory=~/tmp,/var/tmp,/tmp
> Last set from /etc/vimrc
> ...
>
> This lead me to /etc/vimrc which has a line:
>
> " don't write swapfile on most commonly used directories for NFS mounts or USB sticks
> autocmd BufNewFile,BufReadPre /media/*,/run/media/*,/mnt/* set directory=~/tmp,/var/tmp,/tmp
>
> Which confuses me. The aim appears to be to NOT write swap files but all it does is change the location of swap files. And I do want swap files for my mounts in case of recovery.
>
> I am tempted to remove this line though it feels a bit hacky to change this in /etc/vimrc. I will see if I can work out how to override this autocmd in my own profile perhaps.
Files in /etc are editable, it is OK to modify them if you are system
administrator, correct package manager must not overwrite edited files
in /etc. I would suggest to file a bug report to fedora Vim package
maintainers: these autocommands serve no purpose if &directory option
contains no `.`. Additionally they change a global option so if you
open file in /media and another file you will find out that swap files
for that another file are also put into ~/tmp, or /var/tmp, or /tmp.
>
> --
> --
> 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 http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Perfect, thanks. Here's what I get:
>
> --- Auto-Commands ---
> fedora BufReadPre
> /media/* set directory=~/tmp,/var/tmp,/tmp
> Last set from /etc/vimrc
> /run/media/*
> set directory=~/tmp,/var/tmp,/tmp
> Last set from /etc/vimrc
> /mnt/* set directory=~/tmp,/var/tmp,/tmp
> Last set from /etc/vimrc
> ...
>
> This lead me to /etc/vimrc which has a line:
>
> " don't write swapfile on most commonly used directories for NFS mounts or USB sticks
> autocmd BufNewFile,BufReadPre /media/*,/run/media/*,/mnt/* set directory=~/tmp,/var/tmp,/tmp
>
> Which confuses me. The aim appears to be to NOT write swap files but all it does is change the location of swap files. And I do want swap files for my mounts in case of recovery.
>
> I am tempted to remove this line though it feels a bit hacky to change this in /etc/vimrc. I will see if I can work out how to override this autocmd in my own profile perhaps.
Files in /etc are editable, it is OK to modify them if you are system
administrator, correct package manager must not overwrite edited files
in /etc. I would suggest to file a bug report to fedora Vim package
maintainers: these autocommands serve no purpose if &directory option
contains no `.`. Additionally they change a global option so if you
open file in /media and another file you will find out that swap files
for that another file are also put into ~/tmp, or /var/tmp, or /tmp.
>
> --
> --
> 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 http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Posts (Atom)