On Thursday, November 30, 2017 at 1:09:02 PM UTC+5:30, Florian Rehnisch wrote:
> On Thu, Nov 30, 2017 at 08:32:17AM +0100, Florian Rehnisch wrote:
> > On Wed, Nov 29, 2017 at 11:06:19PM -0800, sinbad wrote:
> > > I'm trying to map <space>x in normal mode to do send a command to a pane in tmux.
> > >
> > > sudo tmux send-keys -t "1" C-z "test"
> > >
> > > I tried the following. wrote the above command in a test.sh file and made a mapping as below.
> > >
> > > :nnoremap <Space>x 'silent :!./test.sh<C-m>'
> > >
> > > I'm getting the following error.
> > >
> > > E20: Mark not set
> > >
> > > i think it's due to the following mapping.
> > >
> > > n ' & :call Showmarks() <CR>
> > >
> > > Isn't nnoremap disable recursive mapping ?
> >
> here..
> > AFAICS recursive mapping /is/ disabled head. You're getting the error message
> > because Vim tries to jump to a mark s when hitting the first tick (') in the
> > right-hand side of your mapping. Furthermore, silent is AFAIK a command line
> > command, so your colon is misplaced. Untested:
> >
> > :nnoremap <space>x :silent\ !./test.sh<c-m>
> >
> > The backslash is for escaping the space.
>
> Ah, the backslash gives another error (E10).
>
> :nnoremap <space>x :silent !./test.sh<c-m>
>
> Should do the trick.
>
> Gruß,
> fm-r
Thanks Florian. It worked.
--
--
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, November 30, 2017
Wednesday, November 29, 2017
Re: mapping error.
On Thu, Nov 30, 2017 at 08:32:17AM +0100, Florian Rehnisch wrote:
> On Wed, Nov 29, 2017 at 11:06:19PM -0800, sinbad wrote:
> > I'm trying to map <space>x in normal mode to do send a command to a pane in tmux.
> >
> > sudo tmux send-keys -t "1" C-z "test"
> >
> > I tried the following. wrote the above command in a test.sh file and made a mapping as below.
> >
> > :nnoremap <Space>x 'silent :!./test.sh<C-m>'
> >
> > I'm getting the following error.
> >
> > E20: Mark not set
> >
> > i think it's due to the following mapping.
> >
> > n ' & :call Showmarks() <CR>
> >
> > Isn't nnoremap disable recursive mapping ?
>
here..
> AFAICS recursive mapping /is/ disabled head. You're getting the error message
> because Vim tries to jump to a mark s when hitting the first tick (') in the
> right-hand side of your mapping. Furthermore, silent is AFAIK a command line
> command, so your colon is misplaced. Untested:
>
> :nnoremap <space>x :silent\ !./test.sh<c-m>
>
> The backslash is for escaping the space.
Ah, the backslash gives another error (E10).
:nnoremap <space>x :silent !./test.sh<c-m>
Should do the trick.
Gruß,
fm-r
--
--
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 Wed, Nov 29, 2017 at 11:06:19PM -0800, sinbad wrote:
> > I'm trying to map <space>x in normal mode to do send a command to a pane in tmux.
> >
> > sudo tmux send-keys -t "1" C-z "test"
> >
> > I tried the following. wrote the above command in a test.sh file and made a mapping as below.
> >
> > :nnoremap <Space>x 'silent :!./test.sh<C-m>'
> >
> > I'm getting the following error.
> >
> > E20: Mark not set
> >
> > i think it's due to the following mapping.
> >
> > n ' & :call Showmarks() <CR>
> >
> > Isn't nnoremap disable recursive mapping ?
>
here..
> AFAICS recursive mapping /is/ disabled head. You're getting the error message
> because Vim tries to jump to a mark s when hitting the first tick (') in the
> right-hand side of your mapping. Furthermore, silent is AFAIK a command line
> command, so your colon is misplaced. Untested:
>
> :nnoremap <space>x :silent\ !./test.sh<c-m>
>
> The backslash is for escaping the space.
Ah, the backslash gives another error (E10).
:nnoremap <space>x :silent !./test.sh<c-m>
Should do the trick.
Gruß,
fm-r
--
--
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: mapping error.
On Wed, Nov 29, 2017 at 11:06:19PM -0800, sinbad wrote:
> I'm trying to map <space>x in normal mode to do send a command to a pane in tmux.
>
> sudo tmux send-keys -t "1" C-z "test"
>
> I tried the following. wrote the above command in a test.sh file and made a mapping as below.
>
> :nnoremap <Space>x 'silent :!./test.sh<C-m>'
>
> I'm getting the following error.
>
> E20: Mark not set
>
> i think it's due to the following mapping.
>
> n ' & :call Showmarks() <CR>
>
> Isn't nnoremap disable recursive mapping ?
AFAICS recursive mapping /is/ disabled head. You're getting the error message
because Vim tries to jump to a mark s when hitting the first tick (') in the
right-hand side of your mapping. Furthermore, silent is AFAIK a command line
command, so your colon is misplaced. Untested:
:nnoremap <space>x :silent\ !./test.sh<c-m>
The backslash is for escaping the space.
Gruß,
fm-r
--
--
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 trying to map <space>x in normal mode to do send a command to a pane in tmux.
>
> sudo tmux send-keys -t "1" C-z "test"
>
> I tried the following. wrote the above command in a test.sh file and made a mapping as below.
>
> :nnoremap <Space>x 'silent :!./test.sh<C-m>'
>
> I'm getting the following error.
>
> E20: Mark not set
>
> i think it's due to the following mapping.
>
> n ' & :call Showmarks() <CR>
>
> Isn't nnoremap disable recursive mapping ?
AFAICS recursive mapping /is/ disabled head. You're getting the error message
because Vim tries to jump to a mark s when hitting the first tick (') in the
right-hand side of your mapping. Furthermore, silent is AFAIK a command line
command, so your colon is misplaced. Untested:
:nnoremap <space>x :silent\ !./test.sh<c-m>
The backslash is for escaping the space.
Gruß,
fm-r
--
--
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.
mapping error.
Hi,
I'm trying to map <space>x in normal mode to do send a command to a pane in tmux.
sudo tmux send-keys -t "1" C-z "test"
I tried the following. wrote the above command in a test.sh file and made a mapping as below.
:nnoremap <Space>x 'silent :!./test.sh<C-m>'
I'm getting the following error.
E20: Mark not set
i think it's due to the following mapping.
n ' & :call Showmarks() <CR>
Isn't nnoremap disable recursive mapping ?
thanks
--
--
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 trying to map <space>x in normal mode to do send a command to a pane in tmux.
sudo tmux send-keys -t "1" C-z "test"
I tried the following. wrote the above command in a test.sh file and made a mapping as below.
:nnoremap <Space>x 'silent :!./test.sh<C-m>'
I'm getting the following error.
E20: Mark not set
i think it's due to the following mapping.
n ' & :call Showmarks() <CR>
Isn't nnoremap disable recursive mapping ?
thanks
--
--
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.
Deleting non-empty directories in netrw in Vim 8+
When using `D` on top of a non-empty directory in netrw I get an error: `**error** (netrw) unable to delete directory {path}`. `D` works as expected on an empty directory.
I've tried setting `let g:netrw_localrmdir='rm -rf'` (https://gist.github.com/KevinSjoberg/5068370) with the same result. Looking at the man page for `:help netrw_localrmdir` it says "This variable is only used if your vim is earlier than 7.4"
How can I use `D` to delete non-empty directories in Vim 8+?
--
--
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 tried setting `let g:netrw_localrmdir='rm -rf'` (https://gist.github.com/KevinSjoberg/5068370) with the same result. Looking at the man page for `:help netrw_localrmdir` it says "This variable is only used if your vim is earlier than 7.4"
How can I use `D` to delete non-empty directories in Vim 8+?
--
--
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.
netrw bug with :edit
I use `:edit **/*` to fuzzy find files. I like to use the default working directory settings (based on the project root, the directory I started vim in). This works great until I open netrw, then any subsequent searches no longer respect my wildignore. This seems to be a bug in netrw.
Here is a gif showing me removing everything from my .vimrc except wildignore and wildmenu, then using `:edit **/*` both before and after opening netrw:
https://media.giphy.com/media/3ohs827FcZgRHzGbcI/giphy.gif
As you can see, after opening netrw, the wildignore is no longer respected and the matches are different than before netrw was opened.
I'm on latest Vim installed via Homebrew on macOS. I haven't manually changed any files or plugins from the default `brew install vim` installation.
--
--
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.
Here is a gif showing me removing everything from my .vimrc except wildignore and wildmenu, then using `:edit **/*` both before and after opening netrw:
https://media.giphy.com/media/3ohs827FcZgRHzGbcI/giphy.gif
As you can see, after opening netrw, the wildignore is no longer respected and the matches are different than before netrw was opened.
I'm on latest Vim installed via Homebrew on macOS. I haven't manually changed any files or plugins from the default `brew install vim` installation.
--
--
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.
netrw bug found with :edit wildignore glob completion
I use `:edit **/*` to fuzzy find files. I like to use the default working directory settings (based on the project root, the directory I started vim in). This works great until I open netrw, then any subsequent searches no longer respect my wildignore. This seems to be a bug in netrw.
Here is a gif showing me removing everything from my .vimrc except wildignore and wildmenu, then using `:edit **/*` both before and after opening netrw:
https://media.giphy.com/media/3ohs827FcZgRHzGbcI/giphy.gif
As you can see, after opening netrw, the wildignore is no longer respected and the matches are different than before netrw was opened.
I'm on latest Vim installed via Homebrew on macOS. I haven't manually changed any files or plugins from the default `brew install vim` installation.
--
--
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.
Here is a gif showing me removing everything from my .vimrc except wildignore and wildmenu, then using `:edit **/*` both before and after opening netrw:
https://media.giphy.com/media/3ohs827FcZgRHzGbcI/giphy.gif
As you can see, after opening netrw, the wildignore is no longer respected and the matches are different than before netrw was opened.
I'm on latest Vim installed via Homebrew on macOS. I haven't manually changed any files or plugins from the default `brew install vim` installation.
--
--
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, November 28, 2017
Can Vim be configured so it considers files with no-op edits as unmodified?
I'm looking for a plugin or even a Vim patch that makes it so files are
not considered unmodified if the "changes" that were effectively no-op.
For example, if I execute "gq}" to reflow a paragraph, Vim considers the
file modified even if the command didn't actually change anything. I
thought I could at least disabled "No write since last change for
buffer..." by writing a function that gets executed when Vim is
quitting, but the autocommands "VimLeave" and "VimLeavePre" don't seem
to be executed before the error is shown.
Eric
--
--
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 considered unmodified if the "changes" that were effectively no-op.
For example, if I execute "gq}" to reflow a paragraph, Vim considers the
file modified even if the command didn't actually change anything. I
thought I could at least disabled "No write since last change for
buffer..." by writing a function that gets executed when Vim is
quitting, but the autocommands "VimLeave" and "VimLeavePre" don't seem
to be executed before the error is shown.
Eric
--
--
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: Pasting with Shift-Insert in Windows console Vim
On Monday, November 27, 2017 at 4:55:59 PM UTC+9, Matjaz Rihtar wrote:
> Hi!
> I was trying to fix this using advices from similar issues from Google/Stack Overflow, but I couldn't.
> I am using Vim on Windows only in consoles (cmd, tcc; not gvim) and with the latest versions of Vim I am having problems with behavior of Shift-Insert/Paste functionality.
>
> If I take a clean installation of Windows 7 on a virtual machine and install vim 7.3.46, Shift-Insert key does normal Paste as expected. If I install any later version of Vim (7.4, 7.4-1024, 8.0-002, 8.0-069, 8.0-586) on the same virtual machine (previously reset to the same state), Shift-Insert key inserts character 0xCE in goes out of INSERT mode. The same happens on any of my other Windows machines.
>
> I tried remapping Shift-Insert and/or 0xCE to other values, but to no avail. Regardless of mapping (n,v,..., noremap, ...) Shift-Insert continues to insert 0xCE. If I disable or enable loading of various *.vim scripts like mswin.vim, Shift-Insert continues to insert 0xCE.
>
> What has changed regarding the Windows console keyboard processing between Vim 7.3 and later versions?
> What am I missing regarding mapping/initialization of Vim in newer versions so that Shift-Insert key would do the Paste as in 7.3?
>
> Matjaz
Hi, Could you please try this fix?
https://github.com/vim/vim/pull/2381
--
--
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!
> I was trying to fix this using advices from similar issues from Google/Stack Overflow, but I couldn't.
> I am using Vim on Windows only in consoles (cmd, tcc; not gvim) and with the latest versions of Vim I am having problems with behavior of Shift-Insert/Paste functionality.
>
> If I take a clean installation of Windows 7 on a virtual machine and install vim 7.3.46, Shift-Insert key does normal Paste as expected. If I install any later version of Vim (7.4, 7.4-1024, 8.0-002, 8.0-069, 8.0-586) on the same virtual machine (previously reset to the same state), Shift-Insert key inserts character 0xCE in goes out of INSERT mode. The same happens on any of my other Windows machines.
>
> I tried remapping Shift-Insert and/or 0xCE to other values, but to no avail. Regardless of mapping (n,v,..., noremap, ...) Shift-Insert continues to insert 0xCE. If I disable or enable loading of various *.vim scripts like mswin.vim, Shift-Insert continues to insert 0xCE.
>
> What has changed regarding the Windows console keyboard processing between Vim 7.3 and later versions?
> What am I missing regarding mapping/initialization of Vim in newer versions so that Shift-Insert key would do the Paste as in 7.3?
>
> Matjaz
Hi, Could you please try this fix?
https://github.com/vim/vim/pull/2381
--
--
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/vim] netrw 162m closes and deletes current window/buffer when opening directory (#2141)
chdir(c:\Users\pbugala\Downloads)
Szukanie "bitmaps/vim.ico" w "C:\Users\pbugala/vimfiles,c:\software\vim/vimfiles,c:\software\vim\vim80,c:\software\vim/vimfiles/after,C:\Users\pbugala/vimfiles/after"
Szukanie "C:\Users\pbugala/vimfiles\bitmaps/vim.ico"
Szukanie "c:\software\vim/vimfiles\bitmaps/vim.ico"
Szukanie "c:\software\vim\vim80\bitmaps/vim.ico"
Szukanie "c:\software\vim/vimfiles/after\bitmaps/vim.ico"
Szukanie "C:\Users\pbugala/vimfiles/after\bitmaps/vim.ico"
not found in 'runtimepath': "bitmaps/vim.ico"
wczytywanie "netrw.vimrc"
Szukanie "plugin/netrwPlugin.vim" w "C:\Users\pbugala/vimfiles,c:\software\vim/vimfiles,c:\software\vim\vim80,c:\software\vim/vimfiles/after,C:\Users\pbugala/vimfiles/after"
Szukanie "C:\Users\pbugala/vimfiles\plugin/netrwPlugin.vim"
Szukanie "c:\software\vim/vimfiles\plugin/netrwPlugin.vim"
Szukanie "c:\software\vim\vim80\plugin/netrwPlugin.vim"
wiersz 3: wczytywanie "c:\software\vim\vim80\plugin\netrwPlugin.vim"
skończono wczytywanie c:\software\vim\vim80\plugin\netrwPlugin.vim
kontynuacja w c:\Users\pbugala\Downloads\netrw.vimrc
finished sourcing netrw.vimrc
"netrw.vimrc"
"netrw.vimrc" [unix] 4L, 102C
Executing BufEnter Auto commands for "*"
autocommand sil call s:LocalBrowse(expand("<amatch>"))
Executing VimEnter Auto commands for "*"
autocommand sil call s:VimEnter(expand("<amatch>"))
Searching for "autoload/netrw.vim" in "C:\Users\pbugala/vimfiles,c:\software\vim/vimfiles,c:\software\vim\vim80,c:\software\vim/vimfiles/after,C:\Users\pbugala/vimfiles/after"
Searching for "C:\Users\pbugala/vimfiles\autoload/netrw.vim"
Searching for "c:\software\vim/vimfiles\autoload/netrw.vim"
Searching for "c:\software\vim\vim80\autoload/netrw.vim"
sourcing "c:\software\vim\vim80\autoload\netrw.vim"
finished sourcing c:\software\vim\vim80\autoload\netrw.vim
Executing WinEnter Auto commands for "*"
autocommand if &ft == "netrw"|call s:NetrwInsureWinVars()|endif
line 18: sourcing "c:\software\vim\vim80/.netrwhist"
finished sourcing c:\software\vim\vim80/.netrwhist
continuing in function netrw#Explore[220]..netrw#LocalBrowseCheck[23]..<SNR>3_NetrwBrowse[16]..<SNR>3_NetrwBookHistRead
chdir(c:/Users/pbugala/Downloads)
c:\Users\pbugala\Downloads
Searching for "filetype.vim" in "C:\Users\pbugala/vimfiles,c:\software\vim/vimfiles,c:\software\vim\vim80,c:\software\vim/vimfiles/after,C:\Users\pbugala/vimfiles/after"
Searching for "C:\Users\pbugala/vimfiles\filetype.vim"
Searching for "c:\software\vim/vimfiles\filetype.vim"
Searching for "c:\software\vim\vim80\filetype.vim"
line 101: sourcing "c:\software\vim\vim80\filetype.vim"
Searching for "ftdetect/*.vim" in "C:\Users\pbugala/vimfiles,c:\software\vim/vimfiles,c:\software\vim\vim80,c:\software\vim/vimfiles/after,C:\Users\pbugala/vimfiles/after"
Searching for "C:\Users\pbugala/vimfiles\ftdetect/*.vim"
Searching for "c:\software\vim/vimfiles\ftdetect/*.vim"
Searching for "c:\software\vim\vim80\ftdetect/*.vim"
Searching for "c:\software\vim/vimfiles/after\ftdetect/*.vim"
Searching for "C:\Users\pbugala/vimfiles/after\ftdetect/*.vim"
not found in 'runtimepath': "ftdetect/*.vim"
finished sourcing c:\software\vim\vim80\filetype.vim
continuing in function netrw#Explore[220]..netrw#LocalBrowseCheck[23]..<SNR>3_NetrwBrowse[141]..<SNR>3_NetrwGetBuffer[54]..<SNR>3_NetrwEnew[23]..<SNR>3_NetrwOptionRestore
Searching for "c:\software\vim/vimfiles/after\filetype.vim"
Searching for "C:\Users\pbugala/vimfiles/after\filetype.vim"
Executing BufRead Auto commands for "*"
autocommand if !did_filetype() && expand("<amatch>") !~ g:ft_ignore_pat | runtime! scripts.vim | endif
Searching for "scripts.vim" in "C:\Users\pbugala/vimfiles,c:\software\vim/vimfiles,c:\software\vim\vim80,c:\software\vim/vimfiles/after,C:\Users\pbugala/vimfiles/after"
Searching for "C:\Users\pbugala/vimfiles\scripts.vim"
Searching for "c:\software\vim/vimfiles\scripts.vim"
Searching for "c:\software\vim\vim80\scripts.vim"
line 0: sourcing "c:\software\vim\vim80\scripts.vim"
finished sourcing c:\software\vim\vim80\scripts.vim
continuing in BufRead Auto commands for "*"
Searching for "c:\software\vim/vimfiles/after\scripts.vim"
Searching for "C:\Users\pbugala/vimfiles/after\scripts.vim"
Executing BufRead Auto commands for "*vimrc*"
autocommand call s:StarSetf('vim')
Executing BufRead Auto commands for "*"
autocommand if !did_filetype() && expand("<amatch>") !~ g:ft_ignore_pat && (getline(1) =~ '^#' || getline(2) =~ '^#' || getline(3) =~ '^#'^I|| getline(4) =~ '^#' || getline(5) =~ '^#') | setf FALLBACK conf | endif
Executing BufLeave Auto commands for "*"
autocommand if &ft != "netrw"|let w:netrw_prvfile= expand("%:p")|endif
Executing BufEnter Auto commands for "*"
autocommand sil call s:LocalBrowse(expand("<amatch>"))
"~\Downloads\" [Not edited] --No lines in buffer--
No matching autocommands
Pattern not found: ^$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.h$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.c$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.cpp$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.o$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.obj$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.info$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.bak$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \~$
Pattern not found: ^\d\{3}˙\d\{3}\/
Error detected while processing function netrw#Explore[220]..netrw#LocalBrowseCheck[23]..<SNR>3_NetrwBrowse[252]..<SNR>3_PerformListing[231]..<SNR>3_NetrwWideListing:
line 67:
E31: No such mapping
Error detected while processing function netrw#Explore[220]..netrw#LocalBrowseCheck[23]..<SNR>3_NetrwBrowse[252]..<SNR>3_PerformListing[231]..<SNR>3_NetrwWideListing:
line 70:
E31: No such mapping
Pattern not found: @$
chdir(c:/Users/pbugala/Downloads)
c:\Users\pbugala\Downloads
No matching autocommands
chdir(c:/Users/pbugala/Downloads)
c:\Users\pbugala\Downloads
chdir(c:/Users/pbugala/Downloads)
c:\Users\pbugala\Downloads
Executing BufLeave Auto commands for "*"
autocommand if &ft != "netrw"|let w:netrw_prvfile= expand("%:p")|endif
Executing BufEnter Auto commands for "*"
autocommand sil call s:LocalBrowse(expand("<amatch>"))
"~\Downloads\MaintenancePage\" [Not edited] --No lines in buffer--
"~\Downloads\MaintenancePage\" [Not edited] --No lines in buffer--
Executing BufLeave Auto commands for "*"
autocommand if &ft != "netrw"|let w:netrw_prvfile= expand("%:p")|endif
chdir(c:\Users\pbugala\Downloads)
Executing WinEnter Auto commands for "*"
autocommand if &ft == "netrw"|call s:NetrwInsureWinVars()|endif
Executing BufEnter Auto commands for "*"
autocommand sil call s:LocalBrowse(expand("<amatch>"))
No matching autocommands
Pattern not found: ^$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.h$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.c$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.cpp$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.o$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.obj$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.info$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.swp$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \.bak$
Pattern not found: ^\d\{3}˙\d\{3}\/
Pattern not found: \~$
Pattern not found: ^\d\{3}˙\d\{3}\/
Error detected while processing function netrw#LocalBrowseCheck[23]..<SNR>3_NetrwBrowse[252]..<SNR>3_PerformListing[231]..<SNR>3_NetrwWideListing:
line 67:
E31: No such mapping
Error detected while processing function netrw#LocalBrowseCheck[23]..<SNR>3_NetrwBrowse[252]..<SNR>3_PerformListing[231]..<SNR>3_NetrwWideListing:
line 70:
E31: No such mapping
Pattern not found: @$
Executing VimLeave Auto commands for "*"
autocommand call s:NetrwBookHistSave()
".netrwhist" [Not edited] --No lines in buffer--
"c:\software\vim\vim80/.netrwhist" 2L, 57C writtenW dniu poniedziałek, 13 listopada 2017 16:08:18 UTC+1 użytkownik DrChip napisał:
> jim jammer wrote:
> >
> > How to replicate:
> > Open a file in vim, either command
> > |vim filename.ext|
> > or from vim
> > |:e filename.ext|
> > Open netrw explorer in vertical split
> > |:Vex|
> > Choose a directory and open it by pressing |<enter>|
> >
> > your buffer containing filename.ext is automatically deleted and the
> > window is closed. 99% sure this is a bug with netrw but I don't know
> > where their issues are tracked.
> >
> > OS: windows, both vim and gvim behave the same
> > Vim Version: Various versions of 8, lately using nightly builds,
> > present in 8.0.1130
> >
> >
> I am unable to duplicate this problem; I'm using Scientific Linux, vim
> 8.0.1257.
>
> So, please refer to the directions in :help netrw-debug, generate a
> trace, and send it on to me.
>
> * run it with: vim -u netrw.vimrc (see attached)
> * please use :Dsep after each command that you type (it helps me
> delineate what netrw did after each command)
>
> Thank you!
> Chip Campbell
I was not able to reproduce this in provided way too. But I noticed that with vim it happens all the time using below commands:
$ vim test.file
:Vexp
Enter any directory
Chip,
I tried to follow netrw-debug but somehow it just saved window output only which is no much of a use. I'm attaching some debug from vim.
I run vim with
vim -u netrw.vimrc --noplugins -i NONE
netrw.vimrc attached too.
--
--
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, November 27, 2017
Re: python 3
On 26/11/2017 04:45 p.m., Ni Va wrote:
[...]
>>
>> Sorry but vim's own build is compild with PYTHON_VER=37, DYNAMIC etc..
>> So it should works. It fails.
>
> Uninstalling python 3.7 and after pyhton 3.5 installed it works.
> Thank you.
It also works with python 3.6.3
--
Cesar
--
--
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.
[...]
>>
>> Sorry but vim's own build is compild with PYTHON_VER=37, DYNAMIC etc..
>> So it should works. It fails.
>
> Uninstalling python 3.7 and after pyhton 3.5 installed it works.
> Thank you.
It also works with python 3.6.3
--
Cesar
--
--
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: Apples distributed Vim version
On Mo, 27 Nov 2017, romainlafourcade@gmail.com wrote:
> Apple publishes their open source code over there : https://opensource.apple.com/
>
> That 8056 patch appeared in this version: https://opensource.apple.com/source/vim/vim-62.41.2/
>
> The differences seem to be limited to src/option.c and src/version.c.
Yeah, patch 8056 does fix CVE-2016-1248
https://www.cvedetails.com/cve/CVE-2016-1248/ so that is probably the
reason they included it.
Let's see if the next version released version will then be 7.4.81300 :)
Christian
--
Die meisten Adeligen erinnern an ihre Vorfahren wie ein italienischer
Cicerone an Cicero.
-- Nicolas Sébastien de Chamfort
--
--
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.
> Apple publishes their open source code over there : https://opensource.apple.com/
>
> That 8056 patch appeared in this version: https://opensource.apple.com/source/vim/vim-62.41.2/
>
> The differences seem to be limited to src/option.c and src/version.c.
Yeah, patch 8056 does fix CVE-2016-1248
https://www.cvedetails.com/cve/CVE-2016-1248/ so that is probably the
reason they included it.
Let's see if the next version released version will then be 7.4.81300 :)
Christian
--
Die meisten Adeligen erinnern an ihre Vorfahren wie ein italienischer
Cicerone an Cicero.
-- Nicolas Sébastien de Chamfort
--
--
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: Apples distributed Vim version
Apple publishes their open source code over there : https://opensource.apple.com/
That 8056 patch appeared in this version: https://opensource.apple.com/source/vim/vim-62.41.2/
The differences seem to be limited to src/option.c and src/version.c.
--
--
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.
That 8056 patch appeared in this version: https://opensource.apple.com/source/vim/vim-62.41.2/
The differences seem to be limited to src/option.c and src/version.c.
--
--
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, November 26, 2017
Re: python 3
Le dimanche 26 novembre 2017 22:14:56 UTC+1, Ni Va a écrit :
> Le samedi 25 novembre 2017 12:55:32 UTC+1, ZyX a écrit :
> > 2017-11-25 3:09 GMT+03:00 Shidong Wang <wsdjeg@outlook.com>:
> > > no need to install python3.5 ， just set the value of pythonthreedll.
> >
> > It is not going to work properly if Vim was compiled with python 3.5.
> > Python version Vim was compiled with and Python version actually used
> > must match, Python's n.i and n.j are generally not ABI-compatible.
> >
> > >
> > > 发自我的华为手机
> > >
> > > -------- 原始邮件 --------
> > > 主题：Re: python 3
> > > 发件人：Ni Va
> > > 收件人：vim_use
> > > 抄送：
> > >
> > > Le vendredi 24 novembre 2017 14:58:17 UTC+1, andalou a écrit :
> > >> On 24/11/2017 03:46 a.m., rameo wrote:
> > >> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
> > >> >> Hi,
> > >> >>
> > >> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
> > >> v3.7.0a2) fails and exit vim.
> > >> >>
> > >> >>
> > >> >> May I miss some things to do?
> > >> >> Thank you
> > >> >
> > >> > You're using Python 3.7.
> > >> > Vim is made for Python 3.5.
> > >> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
> > >> > Vim version))
> > >> >
> > >>
> > >> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
> > >>
> > >> --
> > >> Cesar
> > >
> > > Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are
> > > installed.
> > > Problem always here.
> > >
> > > --
> > > --
> > > 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.
>
> Sorry but vim's own build is compild with PYTHON_VER=37, DYNAMIC etc..
> So it should works. It fails.
Uninstalling python 3.7 and after pyhton 3.5 installed it works.
Thank you.
--
--
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.
> Le samedi 25 novembre 2017 12:55:32 UTC+1, ZyX a écrit :
> > 2017-11-25 3:09 GMT+03:00 Shidong Wang <wsdjeg@outlook.com>:
> > > no need to install python3.5 ， just set the value of pythonthreedll.
> >
> > It is not going to work properly if Vim was compiled with python 3.5.
> > Python version Vim was compiled with and Python version actually used
> > must match, Python's n.i and n.j are generally not ABI-compatible.
> >
> > >
> > > 发自我的华为手机
> > >
> > > -------- 原始邮件 --------
> > > 主题：Re: python 3
> > > 发件人：Ni Va
> > > 收件人：vim_use
> > > 抄送：
> > >
> > > Le vendredi 24 novembre 2017 14:58:17 UTC+1, andalou a écrit :
> > >> On 24/11/2017 03:46 a.m., rameo wrote:
> > >> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
> > >> >> Hi,
> > >> >>
> > >> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
> > >> v3.7.0a2) fails and exit vim.
> > >> >>
> > >> >>
> > >> >> May I miss some things to do?
> > >> >> Thank you
> > >> >
> > >> > You're using Python 3.7.
> > >> > Vim is made for Python 3.5.
> > >> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
> > >> > Vim version))
> > >> >
> > >>
> > >> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
> > >>
> > >> --
> > >> Cesar
> > >
> > > Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are
> > > installed.
> > > Problem always here.
> > >
> > > --
> > > --
> > > 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.
>
> Sorry but vim's own build is compild with PYTHON_VER=37, DYNAMIC etc..
> So it should works. It fails.
Uninstalling python 3.7 and after pyhton 3.5 installed it works.
Thank you.
--
--
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: python 3
Le samedi 25 novembre 2017 12:55:32 UTC+1, ZyX a écrit :
> 2017-11-25 3:09 GMT+03:00 Shidong Wang <wsdjeg@outlook.com>:
> > no need to install python3.5 ， just set the value of pythonthreedll.
>
> It is not going to work properly if Vim was compiled with python 3.5.
> Python version Vim was compiled with and Python version actually used
> must match, Python's n.i and n.j are generally not ABI-compatible.
>
> >
> > 发自我的华为手机
> >
> > -------- 原始邮件 --------
> > 主题：Re: python 3
> > 发件人：Ni Va
> > 收件人：vim_use
> > 抄送：
> >
> > Le vendredi 24 novembre 2017 14:58:17 UTC+1, andalou a écrit :
> >> On 24/11/2017 03:46 a.m., rameo wrote:
> >> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
> >> >> Hi,
> >> >>
> >> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
> >> v3.7.0a2) fails and exit vim.
> >> >>
> >> >>
> >> >> May I miss some things to do?
> >> >> Thank you
> >> >
> >> > You're using Python 3.7.
> >> > Vim is made for Python 3.5.
> >> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
> >> > Vim version))
> >> >
> >>
> >> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
> >>
> >> --
> >> Cesar
> >
> > Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are
> > installed.
> > Problem always here.
> >
> > --
> > --
> > 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.
Sorry but vim's own build is compild with PYTHON_VER=37, DYNAMIC etc..
So it should works. It fails.
--
--
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-11-25 3:09 GMT+03:00 Shidong Wang <wsdjeg@outlook.com>:
> > no need to install python3.5 ， just set the value of pythonthreedll.
>
> It is not going to work properly if Vim was compiled with python 3.5.
> Python version Vim was compiled with and Python version actually used
> must match, Python's n.i and n.j are generally not ABI-compatible.
>
> >
> > 发自我的华为手机
> >
> > -------- 原始邮件 --------
> > 主题：Re: python 3
> > 发件人：Ni Va
> > 收件人：vim_use
> > 抄送：
> >
> > Le vendredi 24 novembre 2017 14:58:17 UTC+1, andalou a écrit :
> >> On 24/11/2017 03:46 a.m., rameo wrote:
> >> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
> >> >> Hi,
> >> >>
> >> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
> >> v3.7.0a2) fails and exit vim.
> >> >>
> >> >>
> >> >> May I miss some things to do?
> >> >> Thank you
> >> >
> >> > You're using Python 3.7.
> >> > Vim is made for Python 3.5.
> >> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
> >> > Vim version))
> >> >
> >>
> >> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
> >>
> >> --
> >> Cesar
> >
> > Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are
> > installed.
> > Problem always here.
> >
> > --
> > --
> > 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.
Sorry but vim's own build is compild with PYTHON_VER=37, DYNAMIC etc..
So it should works. It fails.
--
--
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: using vim to add <a href= ...> links to an epub index file
On Saturday, November 25, 2017 at 10:25:32 AM UTC-8, Chris Jones wrote:
> On Fri, Nov 24, 2017 at 12:43:46PM EST, porphyry5 wrote:
> > On Thursday, November 23, 2017 at 3:53:58 PM UTC-8, Chris Jones wrote:
>
> [..]
> >
> > Substitute (:h :s) will do all you need. In the case of links and
> > anchors, I modify this model to the specific situation in each case:
> >
> > :%s/ \(_\(\w\+\)\)/ <a href="#\1">\2<\/a>/g|:%s/^_\w\+$/<a > name="&"><\/a>/
>
> Do you mean using submatch(0) to retrieve what /\d\+< actually matched
> in the current iteration?
>
> So far this seems to be the only way to retrieve the string that a regex
> actually matches... alas, as per the :help submatch vim manual...
> submatch() can only be used in the context of the replacement part of
> a :substitute command - which is not what I had in mind.
>
> Just curious. I gave up on the idea of using vim in this instance and
> wrote a ~10 lines python script that rewrites the file... adding the
> links where relevant.
>
> > Being simple minded, I just ensure that anchors always occur at the
> > start of lines, and that links never do.
>
> Always try to eat off of a clean plate when you can. The index file as
> tidied up by yours truly was nice and clean to start with... My little
> script only created ~10 faulty <a href= > links out of the 6,000+...
> which took c. 10 minutes to edit.
>
> All the same & just for the hell of it... doing it in vim would have
> been more satisfying.
>
> So if you could afford the time... could you explain the vim solution
> you had in mind? I'm still interested.
>
> Thanks,
>
> CJ
I was referring to the :substitute command, which can use submatch() if need be, but usually is not necessary.
Entering :h :s<Enter> at the command line invokes the help for :substitute. :s is usually employed, being the shortest abbreviation of :substitute vim recognizes
There is an associated function substitute(), which works almost identically to :substitute
You really need to read the help chapters usr_27.txt and pattern.txt (:h usr_27 and :h pattern), I cannot possibly give a brief overview of vim's pattern matching and manipulating ability.
Largely I correct ocr-ed texts and convert them to .txt, .html and .epub. The 2 :s command string I supplied is literally all I ever need to produce the Page No. anchors and within Index links (occasionally I may need to use a minor modification of the pattern). But I do this early in the conversion process, when it is simple to differentiate links from anchors. You have left yours until much later, so your pattern will be more complex, but the general principles still apply.
--
--
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 Fri, Nov 24, 2017 at 12:43:46PM EST, porphyry5 wrote:
> > On Thursday, November 23, 2017 at 3:53:58 PM UTC-8, Chris Jones wrote:
>
> [..]
> >
> > Substitute (:h :s) will do all you need. In the case of links and
> > anchors, I modify this model to the specific situation in each case:
> >
> > :%s/ \(_\(\w\+\)\)/ <a href="#\1">\2<\/a>/g|:%s/^_\w\+$/<a > name="&"><\/a>/
>
> Do you mean using submatch(0) to retrieve what /\d\+< actually matched
> in the current iteration?
>
> So far this seems to be the only way to retrieve the string that a regex
> actually matches... alas, as per the :help submatch vim manual...
> submatch() can only be used in the context of the replacement part of
> a :substitute command - which is not what I had in mind.
>
> Just curious. I gave up on the idea of using vim in this instance and
> wrote a ~10 lines python script that rewrites the file... adding the
> links where relevant.
>
> > Being simple minded, I just ensure that anchors always occur at the
> > start of lines, and that links never do.
>
> Always try to eat off of a clean plate when you can. The index file as
> tidied up by yours truly was nice and clean to start with... My little
> script only created ~10 faulty <a href= > links out of the 6,000+...
> which took c. 10 minutes to edit.
>
> All the same & just for the hell of it... doing it in vim would have
> been more satisfying.
>
> So if you could afford the time... could you explain the vim solution
> you had in mind? I'm still interested.
>
> Thanks,
>
> CJ
I was referring to the :substitute command, which can use submatch() if need be, but usually is not necessary.
Entering :h :s<Enter> at the command line invokes the help for :substitute. :s is usually employed, being the shortest abbreviation of :substitute vim recognizes
There is an associated function substitute(), which works almost identically to :substitute
You really need to read the help chapters usr_27.txt and pattern.txt (:h usr_27 and :h pattern), I cannot possibly give a brief overview of vim's pattern matching and manipulating ability.
Largely I correct ocr-ed texts and convert them to .txt, .html and .epub. The 2 :s command string I supplied is literally all I ever need to produce the Page No. anchors and within Index links (occasionally I may need to use a minor modification of the pattern). But I do this early in the conversion process, when it is simple to differentiate links from anchors. You have left yours until much later, so your pattern will be more complex, but the general principles still apply.
--
--
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.
Pasting with Shift-Insert in Windows console Vim
Hi!
I was trying to fix this using advices from similar issues from Google/Stack Overflow, but I couldn't.
I am using Vim on Windows only in consoles (cmd, tcc; not gvim) and with the latest versions of Vim I am having problems with behavior of Shift-Insert/Paste functionality.
If I take a clean installation of Windows 7 on a virtual machine and install vim 7.3.46, Shift-Insert key does normal Paste as expected. If I install any later version of Vim (7.4, 7.4-1024, 8.0-002, 8.0-069, 8.0-586) on the same virtual machine (previously reset to the same state), Shift-Insert key inserts character 0xCE in goes out of INSERT mode. The same happens on any of my other Windows machines.
I tried remapping Shift-Insert and/or 0xCE to other values, but to no avail. Regardless of mapping (n,v,..., noremap, ...) Shift-Insert continues to insert 0xCE. If I disable or enable loading of various *.vim scripts like mswin.vim, Shift-Insert continues to insert 0xCE.
What has changed regarding the Windows console keyboard processing between Vim 7.3 and later versions?
What am I missing regarding mapping/initialization of Vim in newer versions so that Shift-Insert key would do the Paste as in 7.3?
Matjaz
--
--
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 was trying to fix this using advices from similar issues from Google/Stack Overflow, but I couldn't.
I am using Vim on Windows only in consoles (cmd, tcc; not gvim) and with the latest versions of Vim I am having problems with behavior of Shift-Insert/Paste functionality.
If I take a clean installation of Windows 7 on a virtual machine and install vim 7.3.46, Shift-Insert key does normal Paste as expected. If I install any later version of Vim (7.4, 7.4-1024, 8.0-002, 8.0-069, 8.0-586) on the same virtual machine (previously reset to the same state), Shift-Insert key inserts character 0xCE in goes out of INSERT mode. The same happens on any of my other Windows machines.
I tried remapping Shift-Insert and/or 0xCE to other values, but to no avail. Regardless of mapping (n,v,..., noremap, ...) Shift-Insert continues to insert 0xCE. If I disable or enable loading of various *.vim scripts like mswin.vim, Shift-Insert continues to insert 0xCE.
What has changed regarding the Windows console keyboard processing between Vim 7.3 and later versions?
What am I missing regarding mapping/initialization of Vim in newer versions so that Shift-Insert key would do the Paste as in 7.3?
Matjaz
--
--
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, November 25, 2017
Re: QuickFixCmdPost autocmd not always invoked
Copying vim_use to get additional comments.
On Sat, Nov 25, 2017 at 10:44 AM, Yegappan Lakshmanan
<yegappanl@gmail.com> wrote:
> Hi,
>
> The QuickFixCmdPost autocmd is not invoked for some quickfix commands
> that fail to add/modify the quickfix list.
>
> For the cfile, cgetfile, caddfile, make, grep, grepadd, vimgrep, vimgrepadd and
> helpgrep commands, the QuickFixCmdPost autocmd is always invoked irrespective
> of whether command succeeded or not.
>
> For the cexpr, caddexpr, cgetexpr, cbuffer, caddbuffer and cgetbuffer commands,
> the QuickFixCmdPost autocmd is invoked only when the command succeeds. Otherwise
> the autocmd is not invoked.
>
> If this behavior is changed to always invoke the autocmd for the cexpr,
> caddexpr, cgetexpr, cbuffer, caddbuffer and cgetbuffer commands, does anyone
> see a problem?
>
> The above proposed change will make it consistent that whenever the
> QuickFixCmdPre autocmd is invoked, the corresponding QuickFixCmdPost
> autocmd will also be invoked.
>
> Thanks,
> Yegappan
--
--
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, Nov 25, 2017 at 10:44 AM, Yegappan Lakshmanan
<yegappanl@gmail.com> wrote:
> Hi,
>
> The QuickFixCmdPost autocmd is not invoked for some quickfix commands
> that fail to add/modify the quickfix list.
>
> For the cfile, cgetfile, caddfile, make, grep, grepadd, vimgrep, vimgrepadd and
> helpgrep commands, the QuickFixCmdPost autocmd is always invoked irrespective
> of whether command succeeded or not.
>
> For the cexpr, caddexpr, cgetexpr, cbuffer, caddbuffer and cgetbuffer commands,
> the QuickFixCmdPost autocmd is invoked only when the command succeeds. Otherwise
> the autocmd is not invoked.
>
> If this behavior is changed to always invoke the autocmd for the cexpr,
> caddexpr, cgetexpr, cbuffer, caddbuffer and cgetbuffer commands, does anyone
> see a problem?
>
> The above proposed change will make it consistent that whenever the
> QuickFixCmdPre autocmd is invoked, the corresponding QuickFixCmdPost
> autocmd will also be invoked.
>
> Thanks,
> Yegappan
--
--
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: location of vim rc files and directories. Making them relocatable.
On Sat, Nov 25, 2017 at 07:38:10PM +0300, Nikolay Aleksandrovich Pavlov wrote:
> 2017-11-25 19:17 GMT+03:00 Jose Caballero <jcaballero.hep@gmail.com>:
> > Hi,
> >
> > this is a quick question about how to modify my .vimrc and all my
> > plugins so I can copy all of them to different hosts (under different
> > usernames) and still work.
> >
> > I have all of them (vimrc and all plugin directories) in a github account.
> > So my intention is, when I login to a remote host -either root or any
> > other user account-, I would like to clone that account, and being
> > able to keep using them.
> > I don't want to place them under the usual locations (~/.vimrc and
> > ~/.vim) because, as mentioned, sometimes I log as root, on a shared
> > host, so I cannot interfere with others.
> >
> > So basically I want to place the files under /tmp/, for example.
> > However, I have things hardcoded in the files. Things like this:
> >
> > autocmd BufNewFile *.py :-1read ~/.vim/templates/emptypython
> >
> > So I would like to know if there is a mechanism, like an env var or
> > similar, to avoid using hardcoded absolute paths, and make everything
> > relative.
> >
> > googling, I got that I can use -u to point to .vimrc. That solves part
> > of the problem.
> > But I still need a way to make the rest of them relative.
> > Which key word should I search for?
>
> :h <sfile>
>
You can also pair GNU stow and Git to manage configuration files.
http://davebucklin.com/play/2017/03/24/backing-up-dotfiles-with-stow-and-git.html
> >
> >
> > Thanks a lot in advance,
> > Jose
> >
> > --
> > --
> > 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.
--
--
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-11-25 19:17 GMT+03:00 Jose Caballero <jcaballero.hep@gmail.com>:
> > Hi,
> >
> > this is a quick question about how to modify my .vimrc and all my
> > plugins so I can copy all of them to different hosts (under different
> > usernames) and still work.
> >
> > I have all of them (vimrc and all plugin directories) in a github account.
> > So my intention is, when I login to a remote host -either root or any
> > other user account-, I would like to clone that account, and being
> > able to keep using them.
> > I don't want to place them under the usual locations (~/.vimrc and
> > ~/.vim) because, as mentioned, sometimes I log as root, on a shared
> > host, so I cannot interfere with others.
> >
> > So basically I want to place the files under /tmp/, for example.
> > However, I have things hardcoded in the files. Things like this:
> >
> > autocmd BufNewFile *.py :-1read ~/.vim/templates/emptypython
> >
> > So I would like to know if there is a mechanism, like an env var or
> > similar, to avoid using hardcoded absolute paths, and make everything
> > relative.
> >
> > googling, I got that I can use -u to point to .vimrc. That solves part
> > of the problem.
> > But I still need a way to make the rest of them relative.
> > Which key word should I search for?
>
> :h <sfile>
>
You can also pair GNU stow and Git to manage configuration files.
http://davebucklin.com/play/2017/03/24/backing-up-dotfiles-with-stow-and-git.html
> >
> >
> > Thanks a lot in advance,
> > Jose
> >
> > --
> > --
> > 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.
--
--
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: using vim to add <a href= ...> links to an epub index file
On Fri, Nov 24, 2017 at 12:43:46PM EST, porphyry5 wrote:
> On Thursday, November 23, 2017 at 3:53:58 PM UTC-8, Chris Jones wrote:
[..]
>
> Substitute (:h :s) will do all you need. In the case of links and
> anchors, I modify this model to the specific situation in each case:
>
> :%s/ \(_\(\w\+\)\)/ <a href="#\1">\2<\/a>/g|:%s/^_\w\+$/<a > name="&"><\/a>/
Do you mean using submatch(0) to retrieve what /\d\+< actually matched
in the current iteration?
So far this seems to be the only way to retrieve the string that a regex
actually matches... alas, as per the :help submatch vim manual...
submatch() can only be used in the context of the replacement part of
a :substitute command - which is not what I had in mind.
Just curious. I gave up on the idea of using vim in this instance and
wrote a ~10 lines python script that rewrites the file... adding the
links where relevant.
> Being simple minded, I just ensure that anchors always occur at the
> start of lines, and that links never do.
Always try to eat off of a clean plate when you can. The index file as
tidied up by yours truly was nice and clean to start with... My little
script only created ~10 faulty <a href= > links out of the 6,000+...
which took c. 10 minutes to edit.
All the same & just for the hell of it... doing it in vim would have
been more satisfying.
So if you could afford the time... could you explain the vim solution
you had in mind? I'm still interested.
Thanks,
CJ
--
--
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 Thursday, November 23, 2017 at 3:53:58 PM UTC-8, Chris Jones wrote:
[..]
>
> Substitute (:h :s) will do all you need. In the case of links and
> anchors, I modify this model to the specific situation in each case:
>
> :%s/ \(_\(\w\+\)\)/ <a href="#\1">\2<\/a>/g|:%s/^_\w\+$/<a > name="&"><\/a>/
Do you mean using submatch(0) to retrieve what /\d\+< actually matched
in the current iteration?
So far this seems to be the only way to retrieve the string that a regex
actually matches... alas, as per the :help submatch vim manual...
submatch() can only be used in the context of the replacement part of
a :substitute command - which is not what I had in mind.
Just curious. I gave up on the idea of using vim in this instance and
wrote a ~10 lines python script that rewrites the file... adding the
links where relevant.
> Being simple minded, I just ensure that anchors always occur at the
> start of lines, and that links never do.
Always try to eat off of a clean plate when you can. The index file as
tidied up by yours truly was nice and clean to start with... My little
script only created ~10 faulty <a href= > links out of the 6,000+...
which took c. 10 minutes to edit.
All the same & just for the hell of it... doing it in vim would have
been more satisfying.
So if you could afford the time... could you explain the vim solution
you had in mind? I'm still interested.
Thanks,
CJ
--
--
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: location of vim rc files and directories. Making them relocatable.
2017-11-25 19:17 GMT+03:00 Jose Caballero <jcaballero.hep@gmail.com>:
> Hi,
>
> this is a quick question about how to modify my .vimrc and all my
> plugins so I can copy all of them to different hosts (under different
> usernames) and still work.
>
> I have all of them (vimrc and all plugin directories) in a github account.
> So my intention is, when I login to a remote host -either root or any
> other user account-, I would like to clone that account, and being
> able to keep using them.
> I don't want to place them under the usual locations (~/.vimrc and
> ~/.vim) because, as mentioned, sometimes I log as root, on a shared
> host, so I cannot interfere with others.
>
> So basically I want to place the files under /tmp/, for example.
> However, I have things hardcoded in the files. Things like this:
>
> autocmd BufNewFile *.py :-1read ~/.vim/templates/emptypython
>
> So I would like to know if there is a mechanism, like an env var or
> similar, to avoid using hardcoded absolute paths, and make everything
> relative.
>
> googling, I got that I can use -u to point to .vimrc. That solves part
> of the problem.
> But I still need a way to make the rest of them relative.
> Which key word should I search for?
:h <sfile>
>
>
> Thanks a lot in advance,
> Jose
>
> --
> --
> 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.
> Hi,
>
> this is a quick question about how to modify my .vimrc and all my
> plugins so I can copy all of them to different hosts (under different
> usernames) and still work.
>
> I have all of them (vimrc and all plugin directories) in a github account.
> So my intention is, when I login to a remote host -either root or any
> other user account-, I would like to clone that account, and being
> able to keep using them.
> I don't want to place them under the usual locations (~/.vimrc and
> ~/.vim) because, as mentioned, sometimes I log as root, on a shared
> host, so I cannot interfere with others.
>
> So basically I want to place the files under /tmp/, for example.
> However, I have things hardcoded in the files. Things like this:
>
> autocmd BufNewFile *.py :-1read ~/.vim/templates/emptypython
>
> So I would like to know if there is a mechanism, like an env var or
> similar, to avoid using hardcoded absolute paths, and make everything
> relative.
>
> googling, I got that I can use -u to point to .vimrc. That solves part
> of the problem.
> But I still need a way to make the rest of them relative.
> Which key word should I search for?
:h <sfile>
>
>
> Thanks a lot in advance,
> Jose
>
> --
> --
> 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.
location of vim rc files and directories. Making them relocatable.
Hi,
this is a quick question about how to modify my .vimrc and all my
plugins so I can copy all of them to different hosts (under different
usernames) and still work.
I have all of them (vimrc and all plugin directories) in a github account.
So my intention is, when I login to a remote host -either root or any
other user account-, I would like to clone that account, and being
able to keep using them.
I don't want to place them under the usual locations (~/.vimrc and
~/.vim) because, as mentioned, sometimes I log as root, on a shared
host, so I cannot interfere with others.
So basically I want to place the files under /tmp/, for example.
However, I have things hardcoded in the files. Things like this:
autocmd BufNewFile *.py :-1read ~/.vim/templates/emptypython
So I would like to know if there is a mechanism, like an env var or
similar, to avoid using hardcoded absolute paths, and make everything
relative.
googling, I got that I can use -u to point to .vimrc. That solves part
of the problem.
But I still need a way to make the rest of them relative.
Which key word should I search for?
Thanks a lot in advance,
Jose
--
--
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.
this is a quick question about how to modify my .vimrc and all my
plugins so I can copy all of them to different hosts (under different
usernames) and still work.
I have all of them (vimrc and all plugin directories) in a github account.
So my intention is, when I login to a remote host -either root or any
other user account-, I would like to clone that account, and being
able to keep using them.
I don't want to place them under the usual locations (~/.vimrc and
~/.vim) because, as mentioned, sometimes I log as root, on a shared
host, so I cannot interfere with others.
So basically I want to place the files under /tmp/, for example.
However, I have things hardcoded in the files. Things like this:
autocmd BufNewFile *.py :-1read ~/.vim/templates/emptypython
So I would like to know if there is a mechanism, like an env var or
similar, to avoid using hardcoded absolute paths, and make everything
relative.
googling, I got that I can use -u to point to .vimrc. That solves part
of the problem.
But I still need a way to make the rest of them relative.
Which key word should I search for?
Thanks a lot in advance,
Jose
--
--
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: history of ". values
Le jeudi 9 novembre 2017 15:03:59 UTC-3, Renato Fabbri a écrit :
> the last inserted text is kept in the ". register (@. variable).
> It would be nice to keep a small history of the last ". values,
> maybe through "lkjh.
> But I found no {event} related to registers
> (necessary to trigger autocommands).
> I will use the InsertLeave {event}. Or something like it,
> but there really isn't any {event} related to registers?
> peace,
> R.
This was discussed at https://groups.google.com/d/topic/vim_use/CZ8KYt1i9BM
--
--
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.
> the last inserted text is kept in the ". register (@. variable).
> It would be nice to keep a small history of the last ". values,
> maybe through "lkjh.
> But I found no {event} related to registers
> (necessary to trigger autocommands).
> I will use the InsertLeave {event}. Or something like it,
> but there really isn't any {event} related to registers?
> peace,
> R.
This was discussed at https://groups.google.com/d/topic/vim_use/CZ8KYt1i9BM
--
--
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: python 3
2017-11-25 3:09 GMT+03:00 Shidong Wang <wsdjeg@outlook.com>:
> no need to install python3.5 ， just set the value of pythonthreedll.
It is not going to work properly if Vim was compiled with python 3.5.
Python version Vim was compiled with and Python version actually used
must match, Python's n.i and n.j are generally not ABI-compatible.
>
> 发自我的华为手机
>
> -------- 原始邮件 --------
> 主题：Re: python 3
> 发件人：Ni Va
> 收件人：vim_use
> 抄送：
>
> Le vendredi 24 novembre 2017 14:58:17 UTC+1, andalou a écrit :
>> On 24/11/2017 03:46 a.m., rameo wrote:
>> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
>> >> Hi,
>> >>
>> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
>> v3.7.0a2) fails and exit vim.
>> >>
>> >>
>> >> May I miss some things to do?
>> >> Thank you
>> >
>> > You're using Python 3.7.
>> > Vim is made for Python 3.5.
>> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
>> > Vim version))
>> >
>>
>> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
>>
>> --
>> Cesar
>
> Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are
> installed.
> Problem always here.
>
> --
> --
> 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.
--
--
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.
> no need to install python3.5 ， just set the value of pythonthreedll.
It is not going to work properly if Vim was compiled with python 3.5.
Python version Vim was compiled with and Python version actually used
must match, Python's n.i and n.j are generally not ABI-compatible.
>
> 发自我的华为手机
>
> -------- 原始邮件 --------
> 主题：Re: python 3
> 发件人：Ni Va
> 收件人：vim_use
> 抄送：
>
> Le vendredi 24 novembre 2017 14:58:17 UTC+1, andalou a écrit :
>> On 24/11/2017 03:46 a.m., rameo wrote:
>> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
>> >> Hi,
>> >>
>> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
>> v3.7.0a2) fails and exit vim.
>> >>
>> >>
>> >> May I miss some things to do?
>> >> Thank you
>> >
>> > You're using Python 3.7.
>> > Vim is made for Python 3.5.
>> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
>> > Vim version))
>> >
>>
>> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
>>
>> --
>> Cesar
>
> Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are
> installed.
> Problem always here.
>
> --
> --
> 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.
--
--
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, November 24, 2017
Re: Apples distributed Vim version
> On 24 Nov 2017, at 11:46, Lifepillar <lifepillar@lifepillar.me> wrote:
>
> I vaguely remember that in older OS versions there was Vim 7.3, and I
> have never seen 7.4. But I have always used the version from Homebrew,
> so I may have missed it.
I'm on El Capitan, 10.11.6, and vim is 7.3.
Stroller.
--
--
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 vaguely remember that in older OS versions there was Vim 7.3, and I
> have never seen 7.4. But I have always used the version from Homebrew,
> so I may have missed it.
I'm on El Capitan, 10.11.6, and vim is 7.3.
Stroller.
--
--
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.
回复: python 3
no need to install python3.5 ， just set the value of pythonthreedll.
发自我的华为手机
-------- 原始邮件 --------
主题：Re: python 3
发件人：Ni Va
收件人：vim_use
抄送：
发自我的华为手机
-------- 原始邮件 --------
主题：Re: python 3
发件人：Ni Va
收件人：vim_use
抄送：
Le vendredi 24 novembre 2017 14:58:17 UTC+1, andalou a écrit :
> On 24/11/2017 03:46 a.m., rameo wrote:
> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
> >> Hi,
> >>
> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
> v3.7.0a2) fails and exit vim.
> >>
> >>
> >> May I miss some things to do?
> >> Thank you
> >
> > You're using Python 3.7.
> > Vim is made for Python 3.5.
> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
> > Vim version))
> >
>
> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
>
> --
> Cesar
Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are installed.
Problem always here.
--
--
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/11/2017 03:46 a.m., rameo wrote:
> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
> >> Hi,
> >>
> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
> v3.7.0a2) fails and exit vim.
> >>
> >>
> >> May I miss some things to do?
> >> Thank you
> >
> > You're using Python 3.7.
> > Vim is made for Python 3.5.
> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
> > Vim version))
> >
>
> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
>
> --
> Cesar
Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are installed.
Problem always here.
--
--
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: python 3
Le vendredi 24 novembre 2017 14:58:17 UTC+1, andalou a écrit :
> On 24/11/2017 03:46 a.m., rameo wrote:
> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
> >> Hi,
> >>
> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
> v3.7.0a2) fails and exit vim.
> >>
> >>
> >> May I miss some things to do?
> >> Thank you
> >
> > You're using Python 3.7.
> > Vim is made for Python 3.5.
> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
> > Vim version))
> >
>
> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
>
> --
> Cesar
Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are installed.
Problem always here.
--
--
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/11/2017 03:46 a.m., rameo wrote:
> > On Wednesday, November 22, 2017 at 11:31:10 PM UTC+1, Ni Va wrote:
> >> Hi,
> >>
> >> Just try from vim.8.0.1330 to execute :py3 import sys (with python
> v3.7.0a2) fails and exit vim.
> >>
> >>
> >> May I miss some things to do?
> >> Thank you
> >
> > You're using Python 3.7.
> > Vim is made for Python 3.5.
> > You need to install Python 3.5 (32 bits or 64 bits (the same as your
> > Vim version))
> >
>
> That's not true. I'm using vim 8.1333 with Python 3.6.3 on Windows 7.
>
> --
> Cesar
Effectively Windows 10, vim.8.0.1333, both python 2.7 and 3.7.0 are installed.
Problem always here.
--
--
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: terminal-normal mode highlighting
Jeremy Armstrong wrote:
> > > Is it possible to preserve coloring from the shell (seen in TERMINAL mode) when in TERMINAL-NORMAL mode?
> > > e.g.
> > > 1. In TERMINAL mode (with an interactive shell) issue 'ls --color' and notice the colorized output
> > > 2. <c-\><c-n> and notice the SHELL's coloring is lost
> >
> > Doesn't happen for me, color remains.
> >
>
> Sorry, I should have tested with '-u NONE', ft was getting set to
> text. It works now, thanks.
>
> > > Also, is it possible to see vim's :hls highlighting from TERMINAL mode in TERMINAL-NORMAL mode?
> > > e.g.
> > > 1. in TERMINAL-NORMAL mode do ':set hls ' then search for a string that gets highlighted
> > > 2. <c-n><c-\> and notice the search string is no longer highlighted
> >
> > I assume you use "a" here to go back to Terminal-Job mode.
> Yes.
> >
> > Once you are back in Terminal-Job mode the window will display the
> > contents of the terminal. It would be confusing if mixing with other
> > highlighting.
> >
>
> How about a setting for this? Something like ':set keeptermhls' that defaults to 0?
>
> Konsole has persistent search highlighting ( <ctrl-shift-f> ...search string... <esc> ) and it is very useful for watching for important strings scroll by in stuff like strace output or 'tail -f /var/log/syslog' etc.
>
> Therefore, this feature in terminal mode vim could be greatly
> appreciated by people who prefer lightweight systems.
I'm afraid this is not easy. The searching happens in a buffer, but
what is displayed in the terminal window comes directly from the
terminal emulator. This would require searching in the terminal screen
(difficult and a lot of code) or transfering the text to a buffer,
locating matches and then applying the positions to the terminal window.
That's quite complicated.
--
Tips for aliens in New York: Land anywhere. Central Park, anywhere.
No one will care or indeed even notice.
-- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
/// 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.
> > > Is it possible to preserve coloring from the shell (seen in TERMINAL mode) when in TERMINAL-NORMAL mode?
> > > e.g.
> > > 1. In TERMINAL mode (with an interactive shell) issue 'ls --color' and notice the colorized output
> > > 2. <c-\><c-n> and notice the SHELL's coloring is lost
> >
> > Doesn't happen for me, color remains.
> >
>
> Sorry, I should have tested with '-u NONE', ft was getting set to
> text. It works now, thanks.
>
> > > Also, is it possible to see vim's :hls highlighting from TERMINAL mode in TERMINAL-NORMAL mode?
> > > e.g.
> > > 1. in TERMINAL-NORMAL mode do ':set hls ' then search for a string that gets highlighted
> > > 2. <c-n><c-\> and notice the search string is no longer highlighted
> >
> > I assume you use "a" here to go back to Terminal-Job mode.
> Yes.
> >
> > Once you are back in Terminal-Job mode the window will display the
> > contents of the terminal. It would be confusing if mixing with other
> > highlighting.
> >
>
> How about a setting for this? Something like ':set keeptermhls' that defaults to 0?
>
> Konsole has persistent search highlighting ( <ctrl-shift-f> ...search string... <esc> ) and it is very useful for watching for important strings scroll by in stuff like strace output or 'tail -f /var/log/syslog' etc.
>
> Therefore, this feature in terminal mode vim could be greatly
> appreciated by people who prefer lightweight systems.
I'm afraid this is not easy. The searching happens in a buffer, but
what is displayed in the terminal window comes directly from the
terminal emulator. This would require searching in the terminal screen
(difficult and a lot of code) or transfering the text to a buffer,
locating matches and then applying the positions to the terminal window.
That's quite complicated.
--
Tips for aliens in New York: Land anywhere. Central Park, anywhere.
No one will care or indeed even notice.
-- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
/// 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: using vim to add <a href= ...> links to an epub index file
On Thursday, November 23, 2017 at 3:53:58 PM UTC-8, Chris Jones wrote:
> I am currently in the final stages of putting together an epub version of
> Auguste Escoffier's _Le Guide Culinaire_.
>
> Since this is a "cookbook" of sorts, the last step before proofreading
> pretty much requires building a working index with html style links to
> the text relative to each entry.
>
> In an epub context this can be achieved by wrapping the text of each
> entry in something of the form:
>
> <a href="../Text/file.xhtml#p0001">index_entry</a>
>
> where "file.xhtml" is one of the files making up the text of the e-book
> and "p0001" has been defined as an "< ... id="p0001"> within the file.
>
> There are over 6000 entries in this index, which (loudly) suggests that
> in this instance it might be worth spending a few hours concocting some
> form of automated solution to add all the < href > links to the file in
> one fell swoop rather than doing it manually.
>
> The index is a repetition of lines with the following structure:
>
>
> <div class="ind-01"></div>
> <div class="ind-02">Abatis</div>
> <div class="ind-03">621</div>
>
> <div class="ind-01"></div>
> <div class="ind-02"> — à la Bourguignonne</div>
> <div class="ind-03">621</div>
>
> ...
>
>
> After loading the index file in a vim buffer I have found that:
>
> 1. I can match all page entries in a non-ambiguous manner by a search
> with the following pattern: "/\d\+<"
>
> The match as highlighted via ":set hlsearch" includes the page number
> and nothing else and the cursor sits on the first digit of the page
> number.
>
> 2. I can invoke the following one-liner from vim with the page number as
> an argument and it returns the generated link:
>
>
> #!/bin/bash
>
> grep -o 'p0[0-9][0-9][0-9]' *.htm | \
> awk 'BEGIN { FS=":"} {print "<a href=\"../Text/" $1 "#" $2 "\"" ">" }' | \
> grep "$1"
>
> exit 0
>
>
> ... like so:
>
> :r ! My_script 0621
>
> generates the link and writes it to the vim buffer:
>
> <a href="../Text/gc0306.htm#p0621">
>
> What I am missing at this point:
>
> 1. I need to retrieve the matched string of the current "/\d\+<" search
> and place it in some kind of vim variable (?) that I can use to
> invoke the script so that it can be done iteratively without having
> to tyoe the page number manually:
>
> :r ! my_script $vim_variable
>
> 2. I need to find a way to remove any new-line character(s) so that the
> output of "My_script $vim_variable" is placed at the right spot in
> the buffer: after I invoke the script using ":r ! My_script"... the
> output is inserted in column 0 on a new line immediately after the
> matching string:
>
>
> <div class="ind-01"></div>
> <div class="ind-02">Abatis</div>
> <div class="ind-03">621</div>
> <a href="../Text/gc0306.htm#p0621">
>
>
> 3. A third issue is adding the closing "</a>" tag after the targeted
> text, thus completing the wrapping of the entry so that the end
> result of one iteration looks exactly like this:
>
>
> <div class="ind-01"></div>
> <div class="ind-02"><a href="../Text/gc0306.htm#p0621"> Abatis</a></div>
> <div class="ind-03">621</div>
>
>
> In other words, I need to put together some kind of front-end...
> presumably in vimscript (so that I have ability to navigate the lines in
> the buffer)... that does the three things described above:
>
> 1. grab the current matched string/page number, pass it to the bash
> one-liner to generate the corresponding <a href="..."> and return
> the result to vim.
>
> 2. move the cursor to the first character of the corresponding index
> entry (the text and the page number are vertically aligned so that
> hitting "k" on the keyboard does exactly that...) and insert the
> generated text before the cursor (iow, what a Shift-P would do)
>
> 3. jump to the opening "<" of the closing </div> tag and insert "</a>"
> before the cursor.
>
> Another approach I considered might consist in recording a vim macro
> that would reproduce manual actions at the keyboard and run it
> iteratively against the buffer. But I doubt line-mode commands such as
> ":r ! ..." would be recorded.
>
> Please let me know if this is at all feasible in vim (and vim might
> offer better means of achieving what I am trying to do) or whether
> I should look at other options.
>
> Thanks,
>
> C]
Substitute (:h :s) will do all you need. In the case of links and anchors, I modify this model to the specific situation in each case:
:%s/ \(_\(\w\+\)\)/ <a href="#\1">\2<\/a>/g|:%s/^_\w\+$/<a name="&"><\/a>/
Being simple minded, I just ensure that anchors always occur at the start of lines, and that links never do.
--
--
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 am currently in the final stages of putting together an epub version of
> Auguste Escoffier's _Le Guide Culinaire_.
>
> Since this is a "cookbook" of sorts, the last step before proofreading
> pretty much requires building a working index with html style links to
> the text relative to each entry.
>
> In an epub context this can be achieved by wrapping the text of each
> entry in something of the form:
>
> <a href="../Text/file.xhtml#p0001">index_entry</a>
>
> where "file.xhtml" is one of the files making up the text of the e-book
> and "p0001" has been defined as an "< ... id="p0001"> within the file.
>
> There are over 6000 entries in this index, which (loudly) suggests that
> in this instance it might be worth spending a few hours concocting some
> form of automated solution to add all the < href > links to the file in
> one fell swoop rather than doing it manually.
>
> The index is a repetition of lines with the following structure:
>
>
> <div class="ind-01"></div>
> <div class="ind-02">Abatis</div>
> <div class="ind-03">621</div>
>
> <div class="ind-01"></div>
> <div class="ind-02"> — à la Bourguignonne</div>
> <div class="ind-03">621</div>
>
> ...
>
>
> After loading the index file in a vim buffer I have found that:
>
> 1. I can match all page entries in a non-ambiguous manner by a search
> with the following pattern: "/\d\+<"
>
> The match as highlighted via ":set hlsearch" includes the page number
> and nothing else and the cursor sits on the first digit of the page
> number.
>
> 2. I can invoke the following one-liner from vim with the page number as
> an argument and it returns the generated link:
>
>
> #!/bin/bash
>
> grep -o 'p0[0-9][0-9][0-9]' *.htm | \
> awk 'BEGIN { FS=":"} {print "<a href=\"../Text/" $1 "#" $2 "\"" ">" }' | \
> grep "$1"
>
> exit 0
>
>
> ... like so:
>
> :r ! My_script 0621
>
> generates the link and writes it to the vim buffer:
>
> <a href="../Text/gc0306.htm#p0621">
>
> What I am missing at this point:
>
> 1. I need to retrieve the matched string of the current "/\d\+<" search
> and place it in some kind of vim variable (?) that I can use to
> invoke the script so that it can be done iteratively without having
> to tyoe the page number manually:
>
> :r ! my_script $vim_variable
>
> 2. I need to find a way to remove any new-line character(s) so that the
> output of "My_script $vim_variable" is placed at the right spot in
> the buffer: after I invoke the script using ":r ! My_script"... the
> output is inserted in column 0 on a new line immediately after the
> matching string:
>
>
> <div class="ind-01"></div>
> <div class="ind-02">Abatis</div>
> <div class="ind-03">621</div>
> <a href="../Text/gc0306.htm#p0621">
>
>
> 3. A third issue is adding the closing "</a>" tag after the targeted
> text, thus completing the wrapping of the entry so that the end
> result of one iteration looks exactly like this:
>
>
> <div class="ind-01"></div>
> <div class="ind-02"><a href="../Text/gc0306.htm#p0621"> Abatis</a></div>
> <div class="ind-03">621</div>
>
>
> In other words, I need to put together some kind of front-end...
> presumably in vimscript (so that I have ability to navigate the lines in
> the buffer)... that does the three things described above:
>
> 1. grab the current matched string/page number, pass it to the bash
> one-liner to generate the corresponding <a href="..."> and return
> the result to vim.
>
> 2. move the cursor to the first character of the corresponding index
> entry (the text and the page number are vertically aligned so that
> hitting "k" on the keyboard does exactly that...) and insert the
> generated text before the cursor (iow, what a Shift-P would do)
>
> 3. jump to the opening "<" of the closing </div> tag and insert "</a>"
> before the cursor.
>
> Another approach I considered might consist in recording a vim macro
> that would reproduce manual actions at the keyboard and run it
> iteratively against the buffer. But I doubt line-mode commands such as
> ":r ! ..." would be recorded.
>
> Please let me know if this is at all feasible in vim (and vim might
> offer better means of achieving what I am trying to do) or whether
> I should look at other options.
>
> Thanks,
>
> C]
Substitute (:h :s) will do all you need. In the case of links and anchors, I modify this model to the specific situation in each case:
:%s/ \(_\(\w\+\)\)/ <a href="#\1">\2<\/a>/g|:%s/^_\w\+$/<a name="&"><\/a>/
Being simple minded, I just ensure that anchors always occur at the start of lines, and that links never do.
--
--
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: Apple's and openSUSE's distributed Vim versions
On Fri, Nov 24, 2017 at 4:16 PM, Tony Mechelynck
<antoine.mechelynck@gmail.com> wrote:
> On Fri, Nov 24, 2017 at 3:35 PM, Lifepillar <lifepillar@lifepillar.me> wrote:
>> On 24/11/2017 15:03, Christian Brabandt wrote:
>>>
>>>
>>> On Fr, 24 Nov 2017, Lifepillar wrote:
>>>
>>>> On 24/11/2017 12:46, Lifepillar wrote:
>>>>>
>>>>> On 24/11/2017 11:36, Christian Brabandt wrote:
>>>>>>
>>>>>> Hi,
>>>>>> has anybody stumbled over the fact, that Apple seems to distribute a
>>>>>> Vim
>>>>>> version 7.4.8056, which is a version that never actually existed?
>>>>>>
>>>>>> See here
>>>>>>
>>>>>> https://github.com/Valloric/YouCompleteMe/issues/2721#issuecomment-317234769
>>>>>>
>>>>>> or here:
>>>>>>
>>>>>> https://medium.com/@amit.kulkarni/learn-linux-vim-basic-features-19134461ab85
>>>>>>
>>>>>> (more information here:
>>>>>> https://www.reddit.com/r/vim/comments/7etvld/why_i_love_vim/dq88yk3/)
>>>>>>
>>>>>> I find it very strange, if this is true.
>>>>>
>>>>>
>>>>> In macOS 10.13.1, `/usr/bin/vim --version` returns Vim 8.0 (Included
>>>>> patches: 1-503, 505-642). Vim 8.0.642 is what is shown in the intro
>>>>> screen.
>>>>>
>>>>> (Btw, any idea on why patch 504 has been skipped?)
>>>>>
>>>>> I vaguely remember that in older OS versions there was Vim 7.3, and I
>>>>> have never seen 7.4. But I have always used the version from Homebrew,
>>>>> so I may have missed it.
>>>>
>>>>
>>>> I put my hands on a machine with macOS Sierra, and, in fact, its version
>>>> is 7.4.8056. It has patch 8.0.0056, though, because invalid filetype
>>>> names raise E474, so that explains the version number.
>>>>
>>>> Much more interesting, IMHO, is trying to understand why they skipped
>>>> patch 504 in the current release. The commit message reads:
>>>>
>>>> patch 8.0.0504: looking up an Ex command is a bit slow
>>>>
>>>> Problem: Looking up an Ex command is a bit slow.
>>>> Solution: Instead of just using the first letter, also use the second
>>>> letter
>>>> to skip ahead in the list of commands. Generate the table
>>>> with a
>>>> Perl script. (Dominique Pelle, closes #1589)
>>>>
>>>> Maybe related to the fact that they built Vim without +perl (so, maybe
>>>> they didn't have Perl in their build environment)? Are there are commits
>>>> between 1 and 642 that require Perl?
>>>
>>>
>>> Don't know, but +perl is not needed for that patch I believe.
>>
>>
>> No, but in 8.0.0504, perl was needed to generate the Ex command
>> lookup table. My *wild* guess is that their build environment didn't
>> have Perl (corroborated by the fact that they didn't include +perl),
>> so they skipped the patch.
>>
>> Patch 8.0.0572 removed the Perl requirement, but they didn't notice,
>> didn't care or didn't have time to care, so the gap remains.
>>
>> Of course, this is pure, and somewhat frivolous, speculation :)
>>
>> Life.
>
> On openSUSE Linux 42.3 (which is the current "stable" version) the
> included Vim (without GUI) and gvim (with GTK2 but not Gnome) binaries
> are 7.4.326 without patch 208 "compiler warnings on 64 bit Windows"
> which is "don't care" on Linux AFAICT. What puzzles me here is why
> they stayed with such an outdated version. No other version of Vim is
> currently available on the various software repositories for openSUSE
> 42.3. Maybe there won't be any Vim upgrade before openSUSE 42.4 or
> 43.0, whichever comes first; I don't know if there is a later Vim on
> their Tumbleweed (development) "rolling release" which is supposed to
> be "bleeding-edge state-of-the-art" and even "not fully tested".
>
> Best regards,
> Tony.
Oops, without patch *208* "Mercurial picks up files that are not
distributed (empty)". Maybe they update their Vim sources by the older
"patch" method rather than with the easier Mercurial or git (easier,
that is, unless you want to exclude some individual intermediary
changeset).
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.
<antoine.mechelynck@gmail.com> wrote:
> On Fri, Nov 24, 2017 at 3:35 PM, Lifepillar <lifepillar@lifepillar.me> wrote:
>> On 24/11/2017 15:03, Christian Brabandt wrote:
>>>
>>>
>>> On Fr, 24 Nov 2017, Lifepillar wrote:
>>>
>>>> On 24/11/2017 12:46, Lifepillar wrote:
>>>>>
>>>>> On 24/11/2017 11:36, Christian Brabandt wrote:
>>>>>>
>>>>>> Hi,
>>>>>> has anybody stumbled over the fact, that Apple seems to distribute a
>>>>>> Vim
>>>>>> version 7.4.8056, which is a version that never actually existed?
>>>>>>
>>>>>> See here
>>>>>>
>>>>>> https://github.com/Valloric/YouCompleteMe/issues/2721#issuecomment-317234769
>>>>>>
>>>>>> or here:
>>>>>>
>>>>>> https://medium.com/@amit.kulkarni/learn-linux-vim-basic-features-19134461ab85
>>>>>>
>>>>>> (more information here:
>>>>>> https://www.reddit.com/r/vim/comments/7etvld/why_i_love_vim/dq88yk3/)
>>>>>>
>>>>>> I find it very strange, if this is true.
>>>>>
>>>>>
>>>>> In macOS 10.13.1, `/usr/bin/vim --version` returns Vim 8.0 (Included
>>>>> patches: 1-503, 505-642). Vim 8.0.642 is what is shown in the intro
>>>>> screen.
>>>>>
>>>>> (Btw, any idea on why patch 504 has been skipped?)
>>>>>
>>>>> I vaguely remember that in older OS versions there was Vim 7.3, and I
>>>>> have never seen 7.4. But I have always used the version from Homebrew,
>>>>> so I may have missed it.
>>>>
>>>>
>>>> I put my hands on a machine with macOS Sierra, and, in fact, its version
>>>> is 7.4.8056. It has patch 8.0.0056, though, because invalid filetype
>>>> names raise E474, so that explains the version number.
>>>>
>>>> Much more interesting, IMHO, is trying to understand why they skipped
>>>> patch 504 in the current release. The commit message reads:
>>>>
>>>> patch 8.0.0504: looking up an Ex command is a bit slow
>>>>
>>>> Problem: Looking up an Ex command is a bit slow.
>>>> Solution: Instead of just using the first letter, also use the second
>>>> letter
>>>> to skip ahead in the list of commands. Generate the table
>>>> with a
>>>> Perl script. (Dominique Pelle, closes #1589)
>>>>
>>>> Maybe related to the fact that they built Vim without +perl (so, maybe
>>>> they didn't have Perl in their build environment)? Are there are commits
>>>> between 1 and 642 that require Perl?
>>>
>>>
>>> Don't know, but +perl is not needed for that patch I believe.
>>
>>
>> No, but in 8.0.0504, perl was needed to generate the Ex command
>> lookup table. My *wild* guess is that their build environment didn't
>> have Perl (corroborated by the fact that they didn't include +perl),
>> so they skipped the patch.
>>
>> Patch 8.0.0572 removed the Perl requirement, but they didn't notice,
>> didn't care or didn't have time to care, so the gap remains.
>>
>> Of course, this is pure, and somewhat frivolous, speculation :)
>>
>> Life.
>
> On openSUSE Linux 42.3 (which is the current "stable" version) the
> included Vim (without GUI) and gvim (with GTK2 but not Gnome) binaries
> are 7.4.326 without patch 208 "compiler warnings on 64 bit Windows"
> which is "don't care" on Linux AFAICT. What puzzles me here is why
> they stayed with such an outdated version. No other version of Vim is
> currently available on the various software repositories for openSUSE
> 42.3. Maybe there won't be any Vim upgrade before openSUSE 42.4 or
> 43.0, whichever comes first; I don't know if there is a later Vim on
> their Tumbleweed (development) "rolling release" which is supposed to
> be "bleeding-edge state-of-the-art" and even "not fully tested".
>
> Best regards,
> Tony.
Oops, without patch *208* "Mercurial picks up files that are not
distributed (empty)". Maybe they update their Vim sources by the older
"patch" method rather than with the easier Mercurial or git (easier,
that is, unless you want to exclude some individual intermediary
changeset).
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: Apple's and openSUSE's distributed Vim versions
On Fri, Nov 24, 2017 at 3:35 PM, Lifepillar <lifepillar@lifepillar.me> wrote:
> On 24/11/2017 15:03, Christian Brabandt wrote:
>>
>>
>> On Fr, 24 Nov 2017, Lifepillar wrote:
>>
>>> On 24/11/2017 12:46, Lifepillar wrote:
>>>>
>>>> On 24/11/2017 11:36, Christian Brabandt wrote:
>>>>>
>>>>> Hi,
>>>>> has anybody stumbled over the fact, that Apple seems to distribute a
>>>>> Vim
>>>>> version 7.4.8056, which is a version that never actually existed?
>>>>>
>>>>> See here
>>>>>
>>>>> https://github.com/Valloric/YouCompleteMe/issues/2721#issuecomment-317234769
>>>>>
>>>>> or here:
>>>>>
>>>>> https://medium.com/@amit.kulkarni/learn-linux-vim-basic-features-19134461ab85
>>>>>
>>>>> (more information here:
>>>>> https://www.reddit.com/r/vim/comments/7etvld/why_i_love_vim/dq88yk3/)
>>>>>
>>>>> I find it very strange, if this is true.
>>>>
>>>>
>>>> In macOS 10.13.1, `/usr/bin/vim --version` returns Vim 8.0 (Included
>>>> patches: 1-503, 505-642). Vim 8.0.642 is what is shown in the intro
>>>> screen.
>>>>
>>>> (Btw, any idea on why patch 504 has been skipped?)
>>>>
>>>> I vaguely remember that in older OS versions there was Vim 7.3, and I
>>>> have never seen 7.4. But I have always used the version from Homebrew,
>>>> so I may have missed it.
>>>
>>>
>>> I put my hands on a machine with macOS Sierra, and, in fact, its version
>>> is 7.4.8056. It has patch 8.0.0056, though, because invalid filetype
>>> names raise E474, so that explains the version number.
>>>
>>> Much more interesting, IMHO, is trying to understand why they skipped
>>> patch 504 in the current release. The commit message reads:
>>>
>>> patch 8.0.0504: looking up an Ex command is a bit slow
>>>
>>> Problem: Looking up an Ex command is a bit slow.
>>> Solution: Instead of just using the first letter, also use the second
>>> letter
>>> to skip ahead in the list of commands. Generate the table
>>> with a
>>> Perl script. (Dominique Pelle, closes #1589)
>>>
>>> Maybe related to the fact that they built Vim without +perl (so, maybe
>>> they didn't have Perl in their build environment)? Are there are commits
>>> between 1 and 642 that require Perl?
>>
>>
>> Don't know, but +perl is not needed for that patch I believe.
>
>
> No, but in 8.0.0504, perl was needed to generate the Ex command
> lookup table. My *wild* guess is that their build environment didn't
> have Perl (corroborated by the fact that they didn't include +perl),
> so they skipped the patch.
>
> Patch 8.0.0572 removed the Perl requirement, but they didn't notice,
> didn't care or didn't have time to care, so the gap remains.
>
> Of course, this is pure, and somewhat frivolous, speculation :)
>
> Life.
On openSUSE Linux 42.3 (which is the current "stable" version) the
included Vim (without GUI) and gvim (with GTK2 but not Gnome) binaries
are 7.4.326 without patch 208 "compiler warnings on 64 bit Windows"
which is "don't care" on Linux AFAICT. What puzzles me here is why
they stayed with such an outdated version. No other version of Vim is
currently available on the various software repositories for openSUSE
42.3. Maybe there won't be any Vim upgrade before openSUSE 42.4 or
43.0, whichever comes first; I don't know if there is a later Vim on
their Tumbleweed (development) "rolling release" which is supposed to
be "bleeding-edge state-of-the-art" and even "not fully tested".
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.
> On 24/11/2017 15:03, Christian Brabandt wrote:
>>
>>
>> On Fr, 24 Nov 2017, Lifepillar wrote:
>>
>>> On 24/11/2017 12:46, Lifepillar wrote:
>>>>
>>>> On 24/11/2017 11:36, Christian Brabandt wrote:
>>>>>
>>>>> Hi,
>>>>> has anybody stumbled over the fact, that Apple seems to distribute a
>>>>> Vim
>>>>> version 7.4.8056, which is a version that never actually existed?
>>>>>
>>>>> See here
>>>>>
>>>>> https://github.com/Valloric/YouCompleteMe/issues/2721#issuecomment-317234769
>>>>>
>>>>> or here:
>>>>>
>>>>> https://medium.com/@amit.kulkarni/learn-linux-vim-basic-features-19134461ab85
>>>>>
>>>>> (more information here:
>>>>> https://www.reddit.com/r/vim/comments/7etvld/why_i_love_vim/dq88yk3/)
>>>>>
>>>>> I find it very strange, if this is true.
>>>>
>>>>
>>>> In macOS 10.13.1, `/usr/bin/vim --version` returns Vim 8.0 (Included
>>>> patches: 1-503, 505-642). Vim 8.0.642 is what is shown in the intro
>>>> screen.
>>>>
>>>> (Btw, any idea on why patch 504 has been skipped?)
>>>>
>>>> I vaguely remember that in older OS versions there was Vim 7.3, and I
>>>> have never seen 7.4. But I have always used the version from Homebrew,
>>>> so I may have missed it.
>>>
>>>
>>> I put my hands on a machine with macOS Sierra, and, in fact, its version
>>> is 7.4.8056. It has patch 8.0.0056, though, because invalid filetype
>>> names raise E474, so that explains the version number.
>>>
>>> Much more interesting, IMHO, is trying to understand why they skipped
>>> patch 504 in the current release. The commit message reads:
>>>
>>> patch 8.0.0504: looking up an Ex command is a bit slow
>>>
>>> Problem: Looking up an Ex command is a bit slow.
>>> Solution: Instead of just using the first letter, also use the second
>>> letter
>>> to skip ahead in the list of commands. Generate the table
>>> with a
>>> Perl script. (Dominique Pelle, closes #1589)
>>>
>>> Maybe related to the fact that they built Vim without +perl (so, maybe
>>> they didn't have Perl in their build environment)? Are there are commits
>>> between 1 and 642 that require Perl?
>>
>>
>> Don't know, but +perl is not needed for that patch I believe.
>
>
> No, but in 8.0.0504, perl was needed to generate the Ex command
> lookup table. My *wild* guess is that their build environment didn't
> have Perl (corroborated by the fact that they didn't include +perl),
> so they skipped the patch.
>
> Patch 8.0.0572 removed the Perl requirement, but they didn't notice,
> didn't care or didn't have time to care, so the gap remains.
>
> Of course, this is pure, and somewhat frivolous, speculation :)
>
> Life.
On openSUSE Linux 42.3 (which is the current "stable" version) the
included Vim (without GUI) and gvim (with GTK2 but not Gnome) binaries
are 7.4.326 without patch 208 "compiler warnings on 64 bit Windows"
which is "don't care" on Linux AFAICT. What puzzles me here is why
they stayed with such an outdated version. No other version of Vim is
currently available on the various software repositories for openSUSE
42.3. Maybe there won't be any Vim upgrade before openSUSE 42.4 or
43.0, whichever comes first; I don't know if there is a later Vim on
their Tumbleweed (development) "rolling release" which is supposed to
be "bleeding-edge state-of-the-art" and even "not fully tested".
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: Apples distributed Vim version
On 24/11/2017 15:03, Christian Brabandt wrote:
>
> On Fr, 24 Nov 2017, Lifepillar wrote:
>
>> On 24/11/2017 12:46, Lifepillar wrote:
>>> On 24/11/2017 11:36, Christian Brabandt wrote:
>>>> Hi,
>>>> has anybody stumbled over the fact, that Apple seems to distribute a Vim
>>>> version 7.4.8056, which is a version that never actually existed?
>>>>
>>>> See here
>>>> https://github.com/Valloric/YouCompleteMe/issues/2721#issuecomment-317234769
>>>>
>>>> or here:
>>>> https://medium.com/@amit.kulkarni/learn-linux-vim-basic-features-19134461ab85
>>>>
>>>> (more information here:
>>>> https://www.reddit.com/r/vim/comments/7etvld/why_i_love_vim/dq88yk3/)
>>>>
>>>> I find it very strange, if this is true.
>>>
>>> In macOS 10.13.1, `/usr/bin/vim --version` returns Vim 8.0 (Included
>>> patches: 1-503, 505-642). Vim 8.0.642 is what is shown in the intro
>>> screen.
>>>
>>> (Btw, any idea on why patch 504 has been skipped?)
>>>
>>> I vaguely remember that in older OS versions there was Vim 7.3, and I
>>> have never seen 7.4. But I have always used the version from Homebrew,
>>> so I may have missed it.
>>
>> I put my hands on a machine with macOS Sierra, and, in fact, its version
>> is 7.4.8056. It has patch 8.0.0056, though, because invalid filetype
>> names raise E474, so that explains the version number.
>>
>> Much more interesting, IMHO, is trying to understand why they skipped
>> patch 504 in the current release. The commit message reads:
>>
>> patch 8.0.0504: looking up an Ex command is a bit slow
>>
>> Problem: Looking up an Ex command is a bit slow.
>> Solution: Instead of just using the first letter, also use the second
>> letter
>> to skip ahead in the list of commands. Generate the table with a
>> Perl script. (Dominique Pelle, closes #1589)
>>
>> Maybe related to the fact that they built Vim without +perl (so, maybe
>> they didn't have Perl in their build environment)? Are there are commits
>> between 1 and 642 that require Perl?
>
> Don't know, but +perl is not needed for that patch I believe.
No, but in 8.0.0504, perl was needed to generate the Ex command
lookup table. My *wild* guess is that their build environment didn't
have Perl (corroborated by the fact that they didn't include +perl),
so they skipped the patch.
Patch 8.0.0572 removed the Perl requirement, but they didn't notice,
didn't care or didn't have time to care, so the gap remains.
Of course, this is pure, and somewhat frivolous, speculation :)
Life.
--
--
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 Fr, 24 Nov 2017, Lifepillar wrote:
>
>> On 24/11/2017 12:46, Lifepillar wrote:
>>> On 24/11/2017 11:36, Christian Brabandt wrote:
>>>> Hi,
>>>> has anybody stumbled over the fact, that Apple seems to distribute a Vim
>>>> version 7.4.8056, which is a version that never actually existed?
>>>>
>>>> See here
>>>> https://github.com/Valloric/YouCompleteMe/issues/2721#issuecomment-317234769
>>>>
>>>> or here:
>>>> https://medium.com/@amit.kulkarni/learn-linux-vim-basic-features-19134461ab85
>>>>
>>>> (more information here:
>>>> https://www.reddit.com/r/vim/comments/7etvld/why_i_love_vim/dq88yk3/)
>>>>
>>>> I find it very strange, if this is true.
>>>
>>> In macOS 10.13.1, `/usr/bin/vim --version` returns Vim 8.0 (Included
>>> patches: 1-503, 505-642). Vim 8.0.642 is what is shown in the intro
>>> screen.
>>>
>>> (Btw, any idea on why patch 504 has been skipped?)
>>>
>>> I vaguely remember that in older OS versions there was Vim 7.3, and I
>>> have never seen 7.4. But I have always used the version from Homebrew,
>>> so I may have missed it.
>>
>> I put my hands on a machine with macOS Sierra, and, in fact, its version
>> is 7.4.8056. It has patch 8.0.0056, though, because invalid filetype
>> names raise E474, so that explains the version number.
>>
>> Much more interesting, IMHO, is trying to understand why they skipped
>> patch 504 in the current release. The commit message reads:
>>
>> patch 8.0.0504: looking up an Ex command is a bit slow
>>
>> Problem: Looking up an Ex command is a bit slow.
>> Solution: Instead of just using the first letter, also use the second
>> letter
>> to skip ahead in the list of commands. Generate the table with a
>> Perl script. (Dominique Pelle, closes #1589)
>>
>> Maybe related to the fact that they built Vim without +perl (so, maybe
>> they didn't have Perl in their build environment)? Are there are commits
>> between 1 and 642 that require Perl?
>
> Don't know, but +perl is not needed for that patch I believe.
No, but in 8.0.0504, perl was needed to generate the Ex command
lookup table. My *wild* guess is that their build environment didn't
have Perl (corroborated by the fact that they didn't include +perl),
so they skipped the patch.
Patch 8.0.0572 removed the Perl requirement, but they didn't notice,
didn't care or didn't have time to care, so the gap remains.
Of course, this is pure, and somewhat frivolous, speculation :)
Life.
--
--
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: Apples distributed Vim version
On Fr, 24 Nov 2017, Lifepillar wrote:
> On 24/11/2017 12:46, Lifepillar wrote:
> >On 24/11/2017 11:36, Christian Brabandt wrote:
> >>Hi,
> >>has anybody stumbled over the fact, that Apple seems to distribute a Vim
> >>version 7.4.8056, which is a version that never actually existed?
> >>
> >>See here
> >>https://github.com/Valloric/YouCompleteMe/issues/2721#issuecomment-317234769
> >>
> >>or here:
> >>https://medium.com/@amit.kulkarni/learn-linux-vim-basic-features-19134461ab85
> >>
> >>(more information here:
> >>https://www.reddit.com/r/vim/comments/7etvld/why_i_love_vim/dq88yk3/)
> >>
> >>I find it very strange, if this is true.
> >
> >In macOS 10.13.1, `/usr/bin/vim --version` returns Vim 8.0 (Included
> >patches: 1-503, 505-642). Vim 8.0.642 is what is shown in the intro
> >screen.
> >
> >(Btw, any idea on why patch 504 has been skipped?)
> >
> >I vaguely remember that in older OS versions there was Vim 7.3, and I
> >have never seen 7.4. But I have always used the version from Homebrew,
> >so I may have missed it.
>
> I put my hands on a machine with macOS Sierra, and, in fact, its version
> is 7.4.8056. It has patch 8.0.0056, though, because invalid filetype
> names raise E474, so that explains the version number.
>
> Much more interesting, IMHO, is trying to understand why they skipped
> patch 504 in the current release. The commit message reads:
>
> patch 8.0.0504: looking up an Ex command is a bit slow
>
> Problem: Looking up an Ex command is a bit slow.
> Solution: Instead of just using the first letter, also use the second
> letter
> to skip ahead in the list of commands. Generate the table with a
> Perl script. (Dominique Pelle, closes #1589)
>
> Maybe related to the fact that they built Vim without +perl (so, maybe
> they didn't have Perl in their build environment)? Are there are commits
> between 1 and 642 that require Perl?
Don't know, but +perl is not needed for that patch I believe.
Best,
Christian
--
"Denn die Götter lehren uns ihr eigenstes Werk nachahmen; doch
wissen wir nur, was wir tun, erkennen aber nicht, was wir nachahmen."
-- Goethe, Maximen und Reflektionen, Nr. 101
--
--
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/11/2017 12:46, Lifepillar wrote:
> >On 24/11/2017 11:36, Christian Brabandt wrote:
> >>Hi,
> >>has anybody stumbled over the fact, that Apple seems to distribute a Vim
> >>version 7.4.8056, which is a version that never actually existed?
> >>
> >>See here
> >>https://github.com/Valloric/YouCompleteMe/issues/2721#issuecomment-317234769
> >>
> >>or here:
> >>https://medium.com/@amit.kulkarni/learn-linux-vim-basic-features-19134461ab85
> >>
> >>(more information here:
> >>https://www.reddit.com/r/vim/comments/7etvld/why_i_love_vim/dq88yk3/)
> >>
> >>I find it very strange, if this is true.
> >
> >In macOS 10.13.1, `/usr/bin/vim --version` returns Vim 8.0 (Included
> >patches: 1-503, 505-642). Vim 8.0.642 is what is shown in the intro
> >screen.
> >
> >(Btw, any idea on why patch 504 has been skipped?)
> >
> >I vaguely remember that in older OS versions there was Vim 7.3, and I
> >have never seen 7.4. But I have always used the version from Homebrew,
> >so I may have missed it.
>
> I put my hands on a machine with macOS Sierra, and, in fact, its version
> is 7.4.8056. It has patch 8.0.0056, though, because invalid filetype
> names raise E474, so that explains the version number.
>
> Much more interesting, IMHO, is trying to understand why they skipped
> patch 504 in the current release. The commit message reads:
>
> patch 8.0.0504: looking up an Ex command is a bit slow
>
> Problem: Looking up an Ex command is a bit slow.
> Solution: Instead of just using the first letter, also use the second
> letter
> to skip ahead in the list of commands. Generate the table with a
> Perl script. (Dominique Pelle, closes #1589)
>
> Maybe related to the fact that they built Vim without +perl (so, maybe
> they didn't have Perl in their build environment)? Are there are commits
> between 1 and 642 that require Perl?
Don't know, but +perl is not needed for that patch I believe.
Best,
Christian
--
"Denn die Götter lehren uns ihr eigenstes Werk nachahmen; doch
wissen wir nur, was wir tun, erkennen aber nicht, was wir nachahmen."
-- Goethe, Maximen und Reflektionen, Nr. 101
--
--
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.