If the csv plugin is used while editing two files using gvimdiff, then
the number of key strokes to navigate out of a fold is equal to the
number of lines in that fold. Normally, this would be a single key
stroke. Here the key stroke can be a right or left arrow depending on
whether the user is trying to navigate down or up.
To reproduce the issue, consider the following files.
rajulocal@hogwarts:~/x$ cat file3.csv
k,k,k
a,a,a
m,m,m
a,a,a
r,r,r
a,a,a
j,j,j
u,u,u
k,k,k
a,a,a
m,m,m
a,a,a
r,r,r
a,a,a
j,j,j
u,u,u
rajulocal@hogwarts:~/x$ cat file4.csv
1,1,1
2,2,2
3,3,3
k,k,k
a,a,a
m,m,m
a,a,a
r,r,r
a,a,a
j,j,j
u,u,u
k,k,k
a,a,a
m,m,m
a,a,a
r,r,r
a,a,a
j,j,j
u,u,u
1,1,1
2,2,2
3,3,3
When I do
rajulocal@hogwarts:~/x$ gvimdiff file3.csv file4.csv
The lines 7-10 in file3.csv, 10-13 in file4.csv are folded into a
single line. However, to traverse down the fold, I need to use the
right arrow key 4 times instead of just one.
I am using a Debian Jessie machine with the following vim packages
rajulocal@hogwarts:~/x$ dpkg -l vim\* | grep ^ii
ii vim 2:7.4.488-2 amd64 Vi IMproved - enhanced vi editor
ii vim-common 2:7.4.488-2 amd64 Vi IMproved - Common files
ii vim-gtk 2:7.4.488-2 amd64 Vi IMproved - enhanced
vi editor - with GTK2 GUI
ii vim-gui-common 2:7.4.488-2 all Vi IMproved - Common GUI files
ii vim-runtime 2:7.4.488-2 all Vi IMproved - Runtime files
ii vim-tiny 2:7.4.488-2 amd64 Vi IMproved - enhanced
vi editor - compact version
The csv plugin, csv-0.30.vmb is from
http://www.vim.org/scripts/script.php?script_id=2830
The problem occurs only when the filetype is set to 'csv'. If I
manually change it to 'text', then there is no problem.
thanks
raju
--
Kamaraju S Kusumanchi
http://malayamaarutham.blogspot.com/
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wednesday, December 31, 2014
Re: gvim visual mode selection changes as you scroll up and down, how to fix it?
On 2014-12-31 12:59, Bao Niu wrote:
>>> On Sun, Dec 28, 2014 at 7:24 PM, Bao Niu wrote:
>>>> If I select a long patch of code spanning several pages, I'd
>>>> like to view how much I actually selected by scrolling up and
>>>> down. However this will automatically 'ruins' what I have
>>>> selected because it changes the anchor!
>
> So is this a bug? I mean, scrolling a screen up or down shouldn't
> affect my selection, should it?
It may be an annoyance, but it's a documented behavior rather than a
bug. You can read at
:help scrolling
where the first paragraph states "If the cursor position is
moved off of the window, the cursor is moved onto the window (with
'scrolloff' screen lines around it)."
This is because historically it's been safe to assume that the cursor
was always within the window, so changing this would likely break
numerous plugins.
A little further testing shows that you can drop a mark in visual
mode, scroll around, and then jump back to that mark when you're done:
v
{move to the other end of the desired selection}
ma " drop the "a" mark
{move around wherever you want in visual mode}
`a " jump back to where you dropped the "a" mark
which differs from my previous suggestion by allowing you to remain
in visual mode, and only using one mark rather than two (not that I
ever use more than about 4 marks in any one editing session)
-tim
--
--
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 Sun, Dec 28, 2014 at 7:24 PM, Bao Niu wrote:
>>>> If I select a long patch of code spanning several pages, I'd
>>>> like to view how much I actually selected by scrolling up and
>>>> down. However this will automatically 'ruins' what I have
>>>> selected because it changes the anchor!
>
> So is this a bug? I mean, scrolling a screen up or down shouldn't
> affect my selection, should it?
It may be an annoyance, but it's a documented behavior rather than a
bug. You can read at
:help scrolling
where the first paragraph states "If the cursor position is
moved off of the window, the cursor is moved onto the window (with
'scrolloff' screen lines around it)."
This is because historically it's been safe to assume that the cursor
was always within the window, so changing this would likely break
numerous plugins.
A little further testing shows that you can drop a mark in visual
mode, scroll around, and then jump back to that mark when you're done:
v
{move to the other end of the desired selection}
ma " drop the "a" mark
{move around wherever you want in visual mode}
`a " jump back to where you dropped the "a" mark
which differs from my previous suggestion by allowing you to remain
in visual mode, and only using one mark rather than two (not that I
ever use more than about 4 marks in any one editing session)
-tim
--
--
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: gvim visual mode selection changes as you scroll up and down, how to fix it?
On Sunday, December 28, 2014 12:22:41 PM UTC-8, Tim Chase wrote:
> On 2014-12-28 20:59, Mathias Rav wrote:
> > On Sun, Dec 28, 2014 at 7:24 PM, Bao Niu <niubao56@gmail.com> wrote:
> > > If I select a long patch of code spanning several pages, I'd like
> > > to view how much I actually selected by scrolling up and down.
> > > However this will automatically 'ruins' what I have selected
> > > because it changes the anchor!
> > >
> > > How can I fix the two ends of what I have selected in visual
> > > mode? Many thanks.
> >
> > You can press 'o' in visual mode to go to the other end of the
> > selected text -- see :help v_o.
> >
> > You can also press g CTRL-G in visual mode to see how many
> > lines/words/bytes you have selected -- see :help v_g_CTRL-G.
>
> Additionally, instead of using visual mode right-out, you can drop a
> mark at the two ends (such as 'a and 'b) and then scroll between them
> to your heart's content. Once verified, you can
>
> v`ao`b
>
> (or use V/^V if you want line/block selection) and operate on the
> resulting selection that you've verified.
>
> -tkc
So is this a bug? I mean, scrolling a screen up or down shouldn't affect my selection, should it?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On 2014-12-28 20:59, Mathias Rav wrote:
> > On Sun, Dec 28, 2014 at 7:24 PM, Bao Niu <niubao56@gmail.com> wrote:
> > > If I select a long patch of code spanning several pages, I'd like
> > > to view how much I actually selected by scrolling up and down.
> > > However this will automatically 'ruins' what I have selected
> > > because it changes the anchor!
> > >
> > > How can I fix the two ends of what I have selected in visual
> > > mode? Many thanks.
> >
> > You can press 'o' in visual mode to go to the other end of the
> > selected text -- see :help v_o.
> >
> > You can also press g CTRL-G in visual mode to see how many
> > lines/words/bytes you have selected -- see :help v_g_CTRL-G.
>
> Additionally, instead of using visual mode right-out, you can drop a
> mark at the two ends (such as 'a and 'b) and then scroll between them
> to your heart's content. Once verified, you can
>
> v`ao`b
>
> (or use V/^V if you want line/block selection) and operate on the
> resulting selection that you've verified.
>
> -tkc
So is this a bug? I mean, scrolling a screen up or down shouldn't affect my selection, should it?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Vim for Windows build, contains all 3rd party dependencies
On Wed, Dec 31, 2014 at 12:41 PM, Shiny Bling <kybuliak@gmail.com> wrote:
>
> My main reason doing the build is that Vim Windows builds like the
> above don't include 3rd party dependencies(ruby, python, ...). You
> have to install them yourself. I needed ruby for some plugin and when
> I added it, the whole Vim process was crashing. There was also a case,
> when I downloaded some Vim build and it required Ruby version, which
> was not yet released at http://rubyinstaller.org/
You can use the dynamic flags for several dependencies to avoid this.
My builds use them for these major ones:
+gettext/dyn
+iconv/dyn
+lua/dyn
+multi_byte_ime/dyn
+perl/dyn
+python/dyn
+python3/dyn
+ruby/dyn
> Also, I had to modify Vim and Ruby source code (not makefiles) to
> actually get them working properly.
The Cream builds are always vanilla, depending on an upstream fix on
build or feature bugs. Sometimes I'm motivated to track them down
myself, but usually they are simply omitted. :)
> When I started I thought it would be just a matter of compiling it
> all but it turned out to be quite long endeavour.
You've got that right! I maintain a DOS batch script for everything
from the download/update to the NSIS installer build. Over the years
it has grown to 1,300 lines!
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
SteveHallArchitecture http://SteveHallArchitecture.com
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Vim for Windows build, contains all 3rd party dependencies
On Wednesday, 31 December 2014 18:11:47 UTC+1, Дарио Ѓорѓевски wrote:
> Another possible alternative: https://tuxproject.de/projects/vim/
My main reason doing the build is that Vim Windows builds like the above don't include 3rd party dependencies(ruby, python, ...). You have to install them yourself. I needed ruby for some plugin and when I added it, the whole Vim process was crashing. There was also a case, when I downloaded some Vim build and it required Ruby version, which was not yet released at http://rubyinstaller.org/
This build includes these dependencies, so you don't need to copy any dlls from who knows where, etc ...
Also, I had to modify Vim and Ruby source code (not makefiles) to actually get them working properly.
When I started I thought it would be just a matter of compiling it all but it turned out to be quite long endeavour.
kybu
--
--
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.
> Another possible alternative: https://tuxproject.de/projects/vim/
My main reason doing the build is that Vim Windows builds like the above don't include 3rd party dependencies(ruby, python, ...). You have to install them yourself. I needed ruby for some plugin and when I added it, the whole Vim process was crashing. There was also a case, when I downloaded some Vim build and it required Ruby version, which was not yet released at http://rubyinstaller.org/
This build includes these dependencies, so you don't need to copy any dlls from who knows where, etc ...
Also, I had to modify Vim and Ruby source code (not makefiles) to actually get them working properly.
When I started I thought it would be just a matter of compiling it all but it turned out to be quite long endeavour.
kybu
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Vim for Windows build, contains all 3rd party dependencies
On Wednesday, 31 December 2014 17:41:50 UTC+1, Steve Hall wrote:
> On Wed, Dec 31, 2014 at 10:51 AM, Shiny Bling <kybu...@gmail.com> wrote:
> >
> > There is a newer installer at
> > http://bitbucket.org/kybu/vim-for-windows-single-drop/downloads/vim-single-drop-7.4.560.exe
>
>
> Do you have a :version of this anywhere? I've been maintaining a
> Windows build for over eight years here:
> https://sourceforge.net/projects/cream/files/Vim/
Here it goes:
Huge version with GUI. Features included (+) or not (-):
+acl +digraphs +libcall +profile +textobjects
+arabic -directx +linebreak -python +title
+autocmd -dnd +lispindent +python3 +toolbar
+balloon_eval -ebcdic +listcmds +quickfix +user_commands
+browse +emacs_tags +localmap +reltime +vertsplit
++builtin_terms +eval +lua +rightleft +virtualedit
+byte_offset +ex_extra +menu +ruby +visual
+cindent +extra_search +mksession +scrollbind +visualextra
+clientserver +farsi +modify_fname +signs +viminfo
+clipboard +file_in_path +mouse +smartindent +vreplace
+cmdline_compl +find_in_path +mouseshape -sniff +wildignore
+cmdline_hist +float +multi_byte +startuptime +wildmenu
+cmdline_info +folding +multi_lang +statusline +windows
+comments -footer -mzscheme -sun_workshop +writebackup
+conceal +gettext/dyn +netbeans_intg +syntax -xfontset
+cryptv -hangul_input +ole +tag_binary -xim
+cscope +iconv/dyn +path_extra +tag_old_static -xterm_save
+cursorbind +insert_expand +perl -tag_any_white +xpm_w32
+cursorshape +jumplist +persistent_undo -tcl
+dialog_con_gui +keymap -postscript -tgetent
+diff +langmap +printer -termresponse
>
> But over the last few years, there have been build issues with a
> number of the features. Recently, most of these have been fixed, but I
> still lack the following:
>
>
> -directx -dnd -ebcdic -footer -hangul_input -mzscheme -ole
> -postscript -profile -sniff -sun_workshop -tag_any_white -tcl
> -termresponse -tgetent -xfontset -xim -xpm_w32 -xterm_save
Thanks for pointing these out. I have got xpm_w32, others haven't been included in my build. I would say quite a few are irrelevant on Windows. For instance xfontsel, xim, sun_workshop. I will look at the rest and see what could be built.
>
> I'm particularly curious if you've solved +mzscheme or +tcl.
I can try, even though I can't imagine anyone lusting for TCL ;)
BTW thanks for your Cream build, I used it for a while.
--
--
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, Dec 31, 2014 at 10:51 AM, Shiny Bling <kybu...@gmail.com> wrote:
> >
> > There is a newer installer at
> > http://bitbucket.org/kybu/vim-for-windows-single-drop/downloads/vim-single-drop-7.4.560.exe
>
>
> Do you have a :version of this anywhere? I've been maintaining a
> Windows build for over eight years here:
> https://sourceforge.net/projects/cream/files/Vim/
Here it goes:
Huge version with GUI. Features included (+) or not (-):
+acl +digraphs +libcall +profile +textobjects
+arabic -directx +linebreak -python +title
+autocmd -dnd +lispindent +python3 +toolbar
+balloon_eval -ebcdic +listcmds +quickfix +user_commands
+browse +emacs_tags +localmap +reltime +vertsplit
++builtin_terms +eval +lua +rightleft +virtualedit
+byte_offset +ex_extra +menu +ruby +visual
+cindent +extra_search +mksession +scrollbind +visualextra
+clientserver +farsi +modify_fname +signs +viminfo
+clipboard +file_in_path +mouse +smartindent +vreplace
+cmdline_compl +find_in_path +mouseshape -sniff +wildignore
+cmdline_hist +float +multi_byte +startuptime +wildmenu
+cmdline_info +folding +multi_lang +statusline +windows
+comments -footer -mzscheme -sun_workshop +writebackup
+conceal +gettext/dyn +netbeans_intg +syntax -xfontset
+cryptv -hangul_input +ole +tag_binary -xim
+cscope +iconv/dyn +path_extra +tag_old_static -xterm_save
+cursorbind +insert_expand +perl -tag_any_white +xpm_w32
+cursorshape +jumplist +persistent_undo -tcl
+dialog_con_gui +keymap -postscript -tgetent
+diff +langmap +printer -termresponse
>
> But over the last few years, there have been build issues with a
> number of the features. Recently, most of these have been fixed, but I
> still lack the following:
>
>
> -directx -dnd -ebcdic -footer -hangul_input -mzscheme -ole
> -postscript -profile -sniff -sun_workshop -tag_any_white -tcl
> -termresponse -tgetent -xfontset -xim -xpm_w32 -xterm_save
Thanks for pointing these out. I have got xpm_w32, others haven't been included in my build. I would say quite a few are irrelevant on Windows. For instance xfontsel, xim, sun_workshop. I will look at the rest and see what could be built.
>
> I'm particularly curious if you've solved +mzscheme or +tcl.
I can try, even though I can't imagine anyone lusting for TCL ;)
BTW thanks for your Cream build, I used it for a while.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Vim for Windows build, contains all 3rd party dependencies
Another possible alternative: https://tuxproject.de/projects/vim/
Windows users may also find this useful: http://sourceforge.net/projects/msys2/
31.12.2014, 16:52, "Shiny Bling" <kybuliak@gmail.com>:
> There is a newer installer at http://bitbucket.org/kybu/vim-for-windows-single-drop/downloads/vim-single-drop-7.4.560.exe
>
> The important addition is vimproc (asynchronous execution library) which wasn't there in the previous installer. It requires a native extension being built so I included it.
>
> Other than that:
> - Vim was updated to 7.4.560
> - Ruby was updated to 2.1.5
> - Perl was updated to 5.20.1
> - Python was updated to 3.4.2
> - SQLite was updated to 3.8.7.4
>
> Enjoy,
> kybu
>
> --
> --
> 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.
Windows users may also find this useful: http://sourceforge.net/projects/msys2/
31.12.2014, 16:52, "Shiny Bling" <kybuliak@gmail.com>:
> There is a newer installer at http://bitbucket.org/kybu/vim-for-windows-single-drop/downloads/vim-single-drop-7.4.560.exe
>
> The important addition is vimproc (asynchronous execution library) which wasn't there in the previous installer. It requires a native extension being built so I included it.
>
> Other than that:
> - Vim was updated to 7.4.560
> - Ruby was updated to 2.1.5
> - Perl was updated to 5.20.1
> - Python was updated to 3.4.2
> - SQLite was updated to 3.8.7.4
>
> Enjoy,
> kybu
>
> --
> --
> 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: Search and hilight in several buffers
ivan.mercier@gmail.com wrote:
> Hi,
> I'm looking for a command to search and hilight a pattern in several buffers.
>
> My problem is that the non-active splits don't move to the pattern found's line when I use /pattern or * for example.
>
> Any idea?
>
I can help you with your first problem (search & highlight patterns in
several windows):
windo match Error /pattern-here/
Regards,
Chip Campbell
--
--
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'm looking for a command to search and hilight a pattern in several buffers.
>
> My problem is that the non-active splits don't move to the pattern found's line when I use /pattern or * for example.
>
> Any idea?
>
I can help you with your first problem (search & highlight patterns in
several windows):
windo match Error /pattern-here/
Regards,
Chip Campbell
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Vim for Windows build, contains all 3rd party dependencies
On Wed, Dec 31, 2014 at 10:51 AM, Shiny Bling <kybuliak@gmail.com> wrote:
>
> There is a newer installer at
Do you have a :version of this anywhere? I've been maintaining a
Windows build for over eight years here:
But over the last few years, there have been build issues with a
number of the features. Recently, most of these have been fixed, but I
still lack the following:
-directx -dnd -ebcdic -footer -hangul_input -mzscheme -ole
-postscript -profile -sniff -sun_workshop -tag_any_white -tcl
-termresponse -tgetent -xfontset -xim -xpm_w32 -xterm_save
I'm particularly curious if you've solved +mzscheme or +tcl.
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
SteveHallArchitecture http://SteveHallArchitecture.com
--
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: Can not diff more than 4 buffers
Hi Peng!
On Mi, 31 Dez 2014, Peng Yu wrote:
> Hi,
>
> I get the error when I run vimdiff on multiple file. Is there a way to enable the comparison of multiple files? Thanks.
>
> "Can not diff more than 4 buffers"
That is a compiled limit of Vim. You would need to change the DB_COUNT
macro and recompile Vim if you need more. Not sure, if you wouldn't
still need even more adjustments.
BTW: Why do you need to diff more than 4 buffers at the same time?
Best,
Christian
--
Wer sich über das Christentum nicht empört, kennt es nicht.
-- Joachim Kahl
--
--
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 Mi, 31 Dez 2014, Peng Yu wrote:
> Hi,
>
> I get the error when I run vimdiff on multiple file. Is there a way to enable the comparison of multiple files? Thanks.
>
> "Can not diff more than 4 buffers"
That is a compiled limit of Vim. You would need to change the DB_COUNT
macro and recompile Vim if you need more. Not sure, if you wouldn't
still need even more adjustments.
BTW: Why do you need to diff more than 4 buffers at the same time?
Best,
Christian
--
Wer sich über das Christentum nicht empört, kennt es nicht.
-- Joachim Kahl
--
--
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: Smarter sintax coloring
Hi Paolo!
On Mi, 31 Dez 2014, Paolo Bolzoni wrote:
> Really? No-one knows how to change the syntax coloring rules?
It can probably be done, you simply need to add custom syntax rules for
each operator and color each one directly. I have not seen such a thing,
however (which doesn't mean anything however).
Best,
Christian
--
Bernd Eckenfels: gut geklaut :)
Lutz Donnerhacke: Natürlich, auf gute Gedanken komme ich eh' nicht von allein.
--
--
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 Mi, 31 Dez 2014, Paolo Bolzoni wrote:
> Really? No-one knows how to change the syntax coloring rules?
It can probably be done, you simply need to add custom syntax rules for
each operator and color each one directly. I have not seen such a thing,
however (which doesn't mean anything however).
Best,
Christian
--
Bernd Eckenfels: gut geklaut :)
Lutz Donnerhacke: Natürlich, auf gute Gedanken komme ich eh' nicht von allein.
--
--
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: PL/I
Hi Joydeep!
On Mi, 31 Dez 2014, Joydeep Chakrabarty wrote:
> Hello,
>
> I want to write some PL/I programs on Vim. PL/I does not accept the first
> column. Is there a way to disable the first column of the editor so that
> the cursor does not appear there and first column will always be
> unwritable?
I do not think so. You can possibly work around that, by writing some
BufWritePre autocommand that will shift your buffer by one char to the
right and a BufWritePost autocommand, that will reshift it backwards.
But then you would probably also a BufRead autocommand that will shift
you buffer to the left by one char.
Well, you get the idea. This will get pretty ugly soon, plus you lose
the ability to see how the written buffer actually looks like...
Best,
Christian
--
Das Element der Lüsternheit, in dem er sich so zierlich und
sinnig benimmt, würde vielen andern zum Verderben gereichen.
-- Goethe, Maximen und Reflektionen, Nr. 199
--
--
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 Mi, 31 Dez 2014, Joydeep Chakrabarty wrote:
> Hello,
>
> I want to write some PL/I programs on Vim. PL/I does not accept the first
> column. Is there a way to disable the first column of the editor so that
> the cursor does not appear there and first column will always be
> unwritable?
I do not think so. You can possibly work around that, by writing some
BufWritePre autocommand that will shift your buffer by one char to the
right and a BufWritePost autocommand, that will reshift it backwards.
But then you would probably also a BufRead autocommand that will shift
you buffer to the left by one char.
Well, you get the idea. This will get pretty ugly soon, plus you lose
the ability to see how the written buffer actually looks like...
Best,
Christian
--
Das Element der Lüsternheit, in dem er sich so zierlich und
sinnig benimmt, würde vielen andern zum Verderben gereichen.
-- Goethe, Maximen und Reflektionen, Nr. 199
--
--
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.
Can not diff more than 4 buffers
Hi,
I get the error when I run vimdiff on multiple file. Is there a way to enable the comparison of multiple files? Thanks.
"Can not diff more than 4 buffers"
Regards,
Peng
--
--
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 get the error when I run vimdiff on multiple file. Is there a way to enable the comparison of multiple files? Thanks.
"Can not diff more than 4 buffers"
Regards,
Peng
--
--
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: Smarter sintax coloring
Paolo Bolzoni wrote:
> I program in C++ using vim and, as most developers, I use syntax
> coloring. I have a weak spot for colorful terminal screens...
>
> However, I have the feeling that syntax coloring is little more
> than eye candy.
>
> Lets see this two lines of code:
>
> a -= b;
>
> against
>
> a =- b;
>
> The meaning is totally different, yet coloring won't help you at all.
>
> It is possible to setup syntax coloring so different operators
> have a different color?
>
Check on ,,,./syntax/cpp.vim (its part of your distribution; on linux,
its usually /usr/share/vim/vim##/syntax/cpp.vim. where ## is your vim's
version number).
Copy said file to your ~/.vim/syntax directory.
Modify it to suit you.
Regards,
Chip Campbell
--
--
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 program in C++ using vim and, as most developers, I use syntax
> coloring. I have a weak spot for colorful terminal screens...
>
> However, I have the feeling that syntax coloring is little more
> than eye candy.
>
> Lets see this two lines of code:
>
> a -= b;
>
> against
>
> a =- b;
>
> The meaning is totally different, yet coloring won't help you at all.
>
> It is possible to setup syntax coloring so different operators
> have a different color?
>
Check on ,,,./syntax/cpp.vim (its part of your distribution; on linux,
its usually /usr/share/vim/vim##/syntax/cpp.vim. where ## is your vim's
version number).
Copy said file to your ~/.vim/syntax directory.
Modify it to suit you.
Regards,
Chip Campbell
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Vim for Windows build, contains all 3rd party dependencies
There is a newer installer at http://bitbucket.org/kybu/vim-for-windows-single-drop/downloads/vim-single-drop-7.4.560.exe
The important addition is vimproc (asynchronous execution library) which wasn't there in the previous installer. It requires a native extension being built so I included it.
Other than that:
- Vim was updated to 7.4.560
- Ruby was updated to 2.1.5
- Perl was updated to 5.20.1
- Python was updated to 3.4.2
- SQLite was updated to 3.8.7.4
Enjoy,
kybu
--
--
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 important addition is vimproc (asynchronous execution library) which wasn't there in the previous installer. It requires a native extension being built so I included it.
Other than that:
- Vim was updated to 7.4.560
- Ruby was updated to 2.1.5
- Perl was updated to 5.20.1
- Python was updated to 3.4.2
- SQLite was updated to 3.8.7.4
Enjoy,
kybu
--
--
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.
PL/I
Hello,
I want to write some PL/I programs on Vim. PL/I does not accept the first
column. Is there a way to disable the first column of the editor so that
the cursor does not appear there and first column will always be
unwritable?
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 want to write some PL/I programs on Vim. PL/I does not accept the first
column. Is there a way to disable the first column of the editor so that
the cursor does not appear there and first column will always be
unwritable?
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.
Re: bashide
Actually, forget what I said. The answer is in *README.bashsupport* file:
<quote>
40 (1.3) Set at least some personal details in the file
41 '$HOME/.vim/bash-support/templates/Templates'
42 Here is the minimal personalization (my settings as an example):
43
44 SetMacro( 'AUTHOR', 'Dr. Fritz Mehner' )
45 SetMacro( 'AUTHORREF', 'fgm' )
46 SetMacro( 'EMAIL', 'mehner.fritz@fh-swf.de' )
47 SetMacro( 'ORGANIZATION','FH Südwestfalen, Iserlohn' )
48 SetMacro( 'COPYRIGHT', 'Copyright (c) |YEAR|, |AUTHOR|' )
49
50 (Read more about the template system in the plugin documentation)
</quote>
On Monday, 1 December 2014 14:17:23 UTC, Johnny Baloney wrote:
> Try a different version.
>
> This one worked for me:
>
> http://www.vim.org/scripts/download_script.php?src_id=9890
--
--
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.
<quote>
40 (1.3) Set at least some personal details in the file
41 '$HOME/.vim/bash-support/templates/Templates'
42 Here is the minimal personalization (my settings as an example):
43
44 SetMacro( 'AUTHOR', 'Dr. Fritz Mehner' )
45 SetMacro( 'AUTHORREF', 'fgm' )
46 SetMacro( 'EMAIL', 'mehner.fritz@fh-swf.de' )
47 SetMacro( 'ORGANIZATION','FH Südwestfalen, Iserlohn' )
48 SetMacro( 'COPYRIGHT', 'Copyright (c) |YEAR|, |AUTHOR|' )
49
50 (Read more about the template system in the plugin documentation)
</quote>
On Monday, 1 December 2014 14:17:23 UTC, Johnny Baloney wrote:
> Try a different version.
>
> This one worked for me:
>
> http://www.vim.org/scripts/download_script.php?src_id=9890
--
--
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: Smarter sintax coloring
Really? No-one knows how to change the syntax coloring rules?
On Sat, Dec 20, 2014 at 7:04 PM, Paolo Bolzoni
<paolo.bolzoni.brown@gmail.com> wrote:
> I program in C++ using vim and, as most developers, I use syntax
> coloring. I have a weak spot for colorful terminal screens...
>
> However, I have the feeling that syntax coloring is little more
> than eye candy.
>
> Lets see this two lines of code:
>
> a -= b;
>
> against
>
> a =- b;
>
> The meaning is totally different, yet coloring won't help you at all.
>
> It is possible to setup syntax coloring so different operators
> have a different color?
>
>
> Yours faithfully,
> Paolo
--
--
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, Dec 20, 2014 at 7:04 PM, Paolo Bolzoni
<paolo.bolzoni.brown@gmail.com> wrote:
> I program in C++ using vim and, as most developers, I use syntax
> coloring. I have a weak spot for colorful terminal screens...
>
> However, I have the feeling that syntax coloring is little more
> than eye candy.
>
> Lets see this two lines of code:
>
> a -= b;
>
> against
>
> a =- b;
>
> The meaning is totally different, yet coloring won't help you at all.
>
> It is possible to setup syntax coloring so different operators
> have a different color?
>
>
> Yours faithfully,
> Paolo
--
--
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: Which chars can't be removed from keyword list
Hi Nick!
On Di, 30 Dez 2014, Nick Gieschen wrote:
> If I try set iskeyword-=a it doesn't actually work. That is, the char a is still seen as part of a word. Can someone tell me the rules for what chars cannot be removed from the keyword list?
Check the actual setting of your 'isk'. It probably looks like this:
@,48-57,_,192-255
Note, the '@' which means all alphanumeric characters. Therefore,
issuing :set isk-=a won't work (since the 'a' is not included, it can't
be removed). To explicitly remove the 'a', use :set isk+=^a
Read the gory details of the syntax at :h 'isfname'
Please also note, that changing this option is not advised and even if
you do it, you should probably only change it for the current buffer,
e.g. use :setlocal instead of :set.
Best,
Christian
--
Wie man sein Kind nicht nennen sollte:
Pia Nist
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Di, 30 Dez 2014, Nick Gieschen wrote:
> If I try set iskeyword-=a it doesn't actually work. That is, the char a is still seen as part of a word. Can someone tell me the rules for what chars cannot be removed from the keyword list?
Check the actual setting of your 'isk'. It probably looks like this:
@,48-57,_,192-255
Note, the '@' which means all alphanumeric characters. Therefore,
issuing :set isk-=a won't work (since the 'a' is not included, it can't
be removed). To explicitly remove the 'a', use :set isk+=^a
Read the gory details of the syntax at :h 'isfname'
Please also note, that changing this option is not advised and even if
you do it, you should probably only change it for the current buffer,
e.g. use :setlocal instead of :set.
Best,
Christian
--
Wie man sein Kind nicht nennen sollte:
Pia Nist
--
--
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.
cParenError in included C++ filetype
I find that C++ parentheses are sometimes marked as error
(cParenError) in the code block embedded in markdown. A little
more investigation shows this is what happens:
* markdown.vim can conditionally include cpp.vim for embedded C++
code (users need to manually set markdown_fenced_languages)
* cpp.vim includes c.vim
* c.vim has special logic based on this conditional:
if (s:ft ==# 'cpp') && !exists("cpp_no_cpp11")
So normally C++ will not exhibit the problem, if s:ft (assigned at
the beginning from &ft) is "cpp". However, in this case s:ft is
"markdown", but not "cpp".
Is there any good method to handle the problem (excepting hacking
c.vim to check whether the current syntax is markdown)?
Best regards,
Yongwei
--
Wu Yongwei
URL: http://wyw.dcweb.cn/
--
--
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.
(cParenError) in the code block embedded in markdown. A little
more investigation shows this is what happens:
* markdown.vim can conditionally include cpp.vim for embedded C++
code (users need to manually set markdown_fenced_languages)
* cpp.vim includes c.vim
* c.vim has special logic based on this conditional:
if (s:ft ==# 'cpp') && !exists("cpp_no_cpp11")
So normally C++ will not exhibit the problem, if s:ft (assigned at
the beginning from &ft) is "cpp". However, in this case s:ft is
"markdown", but not "cpp".
Is there any good method to handle the problem (excepting hacking
c.vim to check whether the current syntax is markdown)?
Best regards,
Yongwei
--
Wu Yongwei
URL: http://wyw.dcweb.cn/
--
--
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, December 30, 2014
RE: Site error
Gabor Urban wrote:
> I wanted to check something among the scripts, and encountered
> the following error:
> An error has been encountered in accessing this page.
> 1. Server: www.vim.org
> 2. URL path: /scripts/script_search_results.php
The site is hosted on sourceforge.org and they have problems
from time to time. I check the above every day and it has been
broken for the last few days. However, it is now ok. There is
not much we can do about it, but thanks for reporting.
John
--
--
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 wanted to check something among the scripts, and encountered
> the following error:
> An error has been encountered in accessing this page.
> 1. Server: www.vim.org
> 2. URL path: /scripts/script_search_results.php
The site is hosted on sourceforge.org and they have problems
from time to time. I check the above every day and it has been
broken for the last few days. However, it is now ok. There is
not much we can do about it, but thanks for reporting.
John
--
--
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: Is there a way to incsearch with folded context
Christian Brabandt於 2014年12月30日星期二UTC+8下午8時13分30秒寫道：
> On Mo, 29 Dez 2014, Gary Johnson wrote:
>
> > On 2014-12-29, Kevin Wu wrote:
> > > Gary Johnson於 2014年12月30日星期二UTC+8上午3時30分04秒寫道：
> > > > On 2014-12-28, Kevin Wu wrote:
> > > > > When I do searching, the cursor would jump to the first match, if
> > > > > I set "incsearch".
> > > > > But it's not true with folded context.
> > > > > Specifically speaking, What I want to get is that when searching,
> > > > > the folded context would be unfold automatically and the cursor
> > > > > would jump into where the first match is, and moreover when the
> > > > > cursor jump to another line, the unfolded context would be folded
> > > > > again.
> > > > >
> > > > > Is there any way to satisfy my need?
> > > >
> > > > Take a look at
> > > >
> > > > :help 'foldopen'
> > > > :help 'foldclose'
> > > >
> > > > Regards,
> > > > Gary
> > >
> > > Hi Gary,
> > >
> > > When I searched the solution for my issue, I found the option
> > > 'foldopen', and I also had checked it, which is
> > > :se fdo?
> > > foldopen=block,hor,mark,percent,quickfix,search,tag,undo
> > > Is it OK?
> > >
> > > Sorry, it's my poor English to let you misunderstand my issue.
> > > After finishing a search, the cursor will jump to the first match,
> > > even it's in the fold, that is OK.
> > > But what I want is "incremental" search, that is, when I typing
> > > the word a character by character, the cursor would jump into the
> > > corresponding match instantly with automatically folding and
> > > unfolding.
> > > If I set "incsearch" and no fold here, everything is fine.
> > > But if the 1st match is in a fold, there is no window responding,
> > > just like "noincsearch".
> > >
> > > Is there a way to satisfy my need?
> > >
> > > Regards,
> > > Kevin
> >
> > Hi Kevin,
> >
> > You explained your issue well. The fault is mine. I thought that
> > including "search" in 'foldopen' and setting 'foldclose' to "all"
> > might do what you wanted, or be close enough, but I didn't try it
> > before replying and I see now that it doesn't work for incremental
> > searches. Odd. It seems to me that it should. I don't know of a
> > way to do that.
>
> Here is a patch, that will do that, if the foldopen option contains
> 'search'
>
> Best,
> Christian
> --
> Neue Meldungen von Windows 2000:
> Sie beenden hiermit die aktuelle Windows Sitzung. Wollen Sie noch
> ein Spiel spielen (j/n)?
Hi All,
It works.
Now when searching, cursor will jump into a fold,
if set "incsearch" and "search" in "foldopen" option.
And after complete the searching command, the folds which the cursor is not in would be closed, if "foldclose=all"
Thanks for Christian's patch and Gary's responding.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Mo, 29 Dez 2014, Gary Johnson wrote:
>
> > On 2014-12-29, Kevin Wu wrote:
> > > Gary Johnson於 2014年12月30日星期二UTC+8上午3時30分04秒寫道：
> > > > On 2014-12-28, Kevin Wu wrote:
> > > > > When I do searching, the cursor would jump to the first match, if
> > > > > I set "incsearch".
> > > > > But it's not true with folded context.
> > > > > Specifically speaking, What I want to get is that when searching,
> > > > > the folded context would be unfold automatically and the cursor
> > > > > would jump into where the first match is, and moreover when the
> > > > > cursor jump to another line, the unfolded context would be folded
> > > > > again.
> > > > >
> > > > > Is there any way to satisfy my need?
> > > >
> > > > Take a look at
> > > >
> > > > :help 'foldopen'
> > > > :help 'foldclose'
> > > >
> > > > Regards,
> > > > Gary
> > >
> > > Hi Gary,
> > >
> > > When I searched the solution for my issue, I found the option
> > > 'foldopen', and I also had checked it, which is
> > > :se fdo?
> > > foldopen=block,hor,mark,percent,quickfix,search,tag,undo
> > > Is it OK?
> > >
> > > Sorry, it's my poor English to let you misunderstand my issue.
> > > After finishing a search, the cursor will jump to the first match,
> > > even it's in the fold, that is OK.
> > > But what I want is "incremental" search, that is, when I typing
> > > the word a character by character, the cursor would jump into the
> > > corresponding match instantly with automatically folding and
> > > unfolding.
> > > If I set "incsearch" and no fold here, everything is fine.
> > > But if the 1st match is in a fold, there is no window responding,
> > > just like "noincsearch".
> > >
> > > Is there a way to satisfy my need?
> > >
> > > Regards,
> > > Kevin
> >
> > Hi Kevin,
> >
> > You explained your issue well. The fault is mine. I thought that
> > including "search" in 'foldopen' and setting 'foldclose' to "all"
> > might do what you wanted, or be close enough, but I didn't try it
> > before replying and I see now that it doesn't work for incremental
> > searches. Odd. It seems to me that it should. I don't know of a
> > way to do that.
>
> Here is a patch, that will do that, if the foldopen option contains
> 'search'
>
> Best,
> Christian
> --
> Neue Meldungen von Windows 2000:
> Sie beenden hiermit die aktuelle Windows Sitzung. Wollen Sie noch
> ein Spiel spielen (j/n)?
Hi All,
It works.
Now when searching, cursor will jump into a fold,
if set "incsearch" and "search" in "foldopen" option.
And after complete the searching command, the folds which the cursor is not in would be closed, if "foldclose=all"
Thanks for Christian's patch and Gary's responding.
--
--
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.
Which chars can't be removed from keyword list
If I try set iskeyword-=a it doesn't actually work. That is, the char a is still seen as part of a word. Can someone tell me the rules for what chars cannot be removed from the keyword list?
--
--
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: Search and hilight in several buffers
Hi ivan.mercier!
On Di, 30 Dez 2014, ivan.mercier@gmail.com wrote:
> Hi,
> I'm looking for a command to search and hilight a pattern in several buffers.
>
> My problem is that the non-active splits don't move to the pattern found's line when I use /pattern or * for example.
>
Does
windo /foobar
not work?
Best
Christian
--
Es ist schwer, jemanden so zu achten, wie er geachtet werden will.
-- Luc de Clapiers Vauvenargues (Reflexionen und Maximen)
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Di, 30 Dez 2014, ivan.mercier@gmail.com wrote:
> Hi,
> I'm looking for a command to search and hilight a pattern in several buffers.
>
> My problem is that the non-active splits don't move to the pattern found's line when I use /pattern or * for example.
>
Does
windo /foobar
not work?
Best
Christian
--
Es ist schwer, jemanden so zu achten, wie er geachtet werden will.
-- Luc de Clapiers Vauvenargues (Reflexionen und Maximen)
--
--
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.
Search and hilight in several buffers
Hi,
I'm looking for a command to search and hilight a pattern in several buffers.
My problem is that the non-active splits don't move to the pattern found's line when I use /pattern or * for example.
Any idea?
thanks a lot
--
--
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 looking for a command to search and hilight a pattern in several buffers.
My problem is that the non-active splits don't move to the pattern found's line when I use /pattern or * for example.
Any idea?
thanks a lot
--
--
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: How do I open a new window without losing focus in the current one?
On 2014-12-29 18:35, Ben Fritz wrote:
> There is the :pedit command to open that file in the preview
> window.
Over a decade of using vim and I'm still learning nifty new things.
Thanks!
-tim
--
--
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.
> There is the :pedit command to open that file in the preview
> window.
Over a decade of using vim and I'm still learning nifty new things.
Thanks!
-tim
--
--
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: Is there a way to incsearch with folded context
diff --git a/src/ex_getln.c b/src/ex_getln.c
--- a/src/ex_getln.c
+++ b/src/ex_getln.c
@@ -1843,6 +1843,10 @@ cmdline_changed:
validate_cursor();
end_pos = curwin->w_cursor;
curwin->w_cursor = save_pos;
+#ifdef FEAT_FOLDING
+ if (fdo_flags & FDO_SEARCH)
+ foldOpenCursor();
+#endif
}
else
end_pos = curwin->w_cursor; /* shutup gcc 4 */
On Mo, 29 Dez 2014, Gary Johnson wrote:
> On 2014-12-29, Kevin Wu wrote:
> > Gary Johnson於 2014年12月30日星期二UTC+8上午3時30分04秒寫道：
> > > On 2014-12-28, Kevin Wu wrote:
> > > > When I do searching, the cursor would jump to the first match, if
> > > > I set "incsearch".
> > > > But it's not true with folded context.
> > > > Specifically speaking, What I want to get is that when searching,
> > > > the folded context would be unfold automatically and the cursor
> > > > would jump into where the first match is, and moreover when the
> > > > cursor jump to another line, the unfolded context would be folded
> > > > again.
> > > >
> > > > Is there any way to satisfy my need?
> > >
> > > Take a look at
> > >
> > > :help 'foldopen'
> > > :help 'foldclose'
> > >
> > > Regards,
> > > Gary
> >
> > Hi Gary,
> >
> > When I searched the solution for my issue, I found the option
> > 'foldopen', and I also had checked it, which is
> > :se fdo?
> > foldopen=block,hor,mark,percent,quickfix,search,tag,undo
> > Is it OK?
> >
> > Sorry, it's my poor English to let you misunderstand my issue.
> > After finishing a search, the cursor will jump to the first match,
> > even it's in the fold, that is OK.
> > But what I want is "incremental" search, that is, when I typing
> > the word a character by character, the cursor would jump into the
> > corresponding match instantly with automatically folding and
> > unfolding.
> > If I set "incsearch" and no fold here, everything is fine.
> > But if the 1st match is in a fold, there is no window responding,
> > just like "noincsearch".
> >
> > Is there a way to satisfy my need?
> >
> > Regards,
> > Kevin
>
> Hi Kevin,
>
> You explained your issue well. The fault is mine. I thought that
> including "search" in 'foldopen' and setting 'foldclose' to "all"
> might do what you wanted, or be close enough, but I didn't try it
> before replying and I see now that it doesn't work for incremental
> searches. Odd. It seems to me that it should. I don't know of a
> way to do that.
Here is a patch, that will do that, if the foldopen option contains
'search'
Best,
Christian
--
Neue Meldungen von Windows 2000:
Sie beenden hiermit die aktuelle Windows Sitzung. Wollen Sie noch
ein Spiel spielen (j/n)?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--- a/src/ex_getln.c
+++ b/src/ex_getln.c
@@ -1843,6 +1843,10 @@ cmdline_changed:
validate_cursor();
end_pos = curwin->w_cursor;
curwin->w_cursor = save_pos;
+#ifdef FEAT_FOLDING
+ if (fdo_flags & FDO_SEARCH)
+ foldOpenCursor();
+#endif
}
else
end_pos = curwin->w_cursor; /* shutup gcc 4 */
On Mo, 29 Dez 2014, Gary Johnson wrote:
> On 2014-12-29, Kevin Wu wrote:
> > Gary Johnson於 2014年12月30日星期二UTC+8上午3時30分04秒寫道：
> > > On 2014-12-28, Kevin Wu wrote:
> > > > When I do searching, the cursor would jump to the first match, if
> > > > I set "incsearch".
> > > > But it's not true with folded context.
> > > > Specifically speaking, What I want to get is that when searching,
> > > > the folded context would be unfold automatically and the cursor
> > > > would jump into where the first match is, and moreover when the
> > > > cursor jump to another line, the unfolded context would be folded
> > > > again.
> > > >
> > > > Is there any way to satisfy my need?
> > >
> > > Take a look at
> > >
> > > :help 'foldopen'
> > > :help 'foldclose'
> > >
> > > Regards,
> > > Gary
> >
> > Hi Gary,
> >
> > When I searched the solution for my issue, I found the option
> > 'foldopen', and I also had checked it, which is
> > :se fdo?
> > foldopen=block,hor,mark,percent,quickfix,search,tag,undo
> > Is it OK?
> >
> > Sorry, it's my poor English to let you misunderstand my issue.
> > After finishing a search, the cursor will jump to the first match,
> > even it's in the fold, that is OK.
> > But what I want is "incremental" search, that is, when I typing
> > the word a character by character, the cursor would jump into the
> > corresponding match instantly with automatically folding and
> > unfolding.
> > If I set "incsearch" and no fold here, everything is fine.
> > But if the 1st match is in a fold, there is no window responding,
> > just like "noincsearch".
> >
> > Is there a way to satisfy my need?
> >
> > Regards,
> > Kevin
>
> Hi Kevin,
>
> You explained your issue well. The fault is mine. I thought that
> including "search" in 'foldopen' and setting 'foldclose' to "all"
> might do what you wanted, or be close enough, but I didn't try it
> before replying and I see now that it doesn't work for incremental
> searches. Odd. It seems to me that it should. I don't know of a
> way to do that.
Here is a patch, that will do that, if the foldopen option contains
'search'
Best,
Christian
--
Neue Meldungen von Windows 2000:
Sie beenden hiermit die aktuelle Windows Sitzung. Wollen Sie noch
ein Spiel spielen (j/n)?
--
--
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.
Site error
Hi guys,
I wanted to check something among the scripts, and encountered the following error:An error has been encountered in accessing this page.
1. Server: www.vim.org
2. URL path: /scripts/script_search_results.php
3. Error notes: NONE
4. Error type: 404
5. Request method: GET
6. Request query string: NONE
7. Time: 2014-12-30 12:05:38 UTC (1419941138)
Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net).
If this is a severe or recurring/persistent problem, please do one of the following, and provide the error text (numbered 1 through 7, above):
- Contact the project via their designated support resources.
- Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page for their usernames) at user-name@users.sourceforge.net
If you are a maintainer of this web content, please refer to the Site Documentation regarding web services for further assistance.
NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name ".htaccess" with this line:
Options +Indexes
-----------------------------
I thought it important to publish :-(
--
Urbán Gábor
Linux is like a wigwam: no Gates, no Windows and an Apache inside.
--
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: How do I open a new window without losing focus in the current one?
Thank you - that works!
Jeff
On Tuesday, 30 December 2014 02:35:19 UTC, Ben Fritz wrote:
> On Monday, December 29, 2014 8:18:54 AM UTC-6, Jeff Baxter wrote:
> > If I use
> >
> > :new [filename]
> >
> > the file is opened in a split window, but the focus is also shifted there, whereas I want it to stay in the current window.
> >
> > How can I do that?
>
> There is the :pedit command to open that file in the preview window. But the preview window is special; you probably don't want to do any editing in there, just reading. If that suits your needs, then this is probably what you were looking for.
--
--
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.
Jeff
On Tuesday, 30 December 2014 02:35:19 UTC, Ben Fritz wrote:
> On Monday, December 29, 2014 8:18:54 AM UTC-6, Jeff Baxter wrote:
> > If I use
> >
> > :new [filename]
> >
> > the file is opened in a split window, but the focus is also shifted there, whereas I want it to stay in the current window.
> >
> > How can I do that?
>
> There is the :pedit command to open that file in the preview window. But the preview window is special; you probably don't want to do any editing in there, just reading. If that suits your needs, then this is probably what you were looking for.
--
--
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, December 29, 2014
Re: Is there a way to incsearch with folded context
On 2014-12-29, Kevin Wu wrote:
> Gary Johnson於 2014年12月30日星期二UTC+8上午3時30分04秒寫道：
> > On 2014-12-28, Kevin Wu wrote:
> > > When I do searching, the cursor would jump to the first match, if
> > > I set "incsearch".
> > > But it's not true with folded context.
> > > Specifically speaking, What I want to get is that when searching,
> > > the folded context would be unfold automatically and the cursor
> > > would jump into where the first match is, and moreover when the
> > > cursor jump to another line, the unfolded context would be folded
> > > again.
> > >
> > > Is there any way to satisfy my need?
> >
> > Take a look at
> >
> > :help 'foldopen'
> > :help 'foldclose'
> >
> > Regards,
> > Gary
>
> Hi Gary,
>
> When I searched the solution for my issue, I found the option
> 'foldopen', and I also had checked it, which is
> :se fdo?
> foldopen=block,hor,mark,percent,quickfix,search,tag,undo
> Is it OK?
>
> Sorry, it's my poor English to let you misunderstand my issue.
> After finishing a search, the cursor will jump to the first match,
> even it's in the fold, that is OK.
> But what I want is "incremental" search, that is, when I typing
> the word a character by character, the cursor would jump into the
> corresponding match instantly with automatically folding and
> unfolding.
> If I set "incsearch" and no fold here, everything is fine.
> But if the 1st match is in a fold, there is no window responding,
> just like "noincsearch".
>
> Is there a way to satisfy my need?
>
> Regards,
> Kevin
Hi Kevin,
You explained your issue well. The fault is mine. I thought that
including "search" in 'foldopen' and setting 'foldclose' to "all"
might do what you wanted, or be close enough, but I didn't try it
before replying and I see now that it doesn't work for incremental
searches. Odd. It seems to me that it should. I don't know of a
way to do that.
Regards,
Gary
--
--
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.
> Gary Johnson於 2014年12月30日星期二UTC+8上午3時30分04秒寫道：
> > On 2014-12-28, Kevin Wu wrote:
> > > When I do searching, the cursor would jump to the first match, if
> > > I set "incsearch".
> > > But it's not true with folded context.
> > > Specifically speaking, What I want to get is that when searching,
> > > the folded context would be unfold automatically and the cursor
> > > would jump into where the first match is, and moreover when the
> > > cursor jump to another line, the unfolded context would be folded
> > > again.
> > >
> > > Is there any way to satisfy my need?
> >
> > Take a look at
> >
> > :help 'foldopen'
> > :help 'foldclose'
> >
> > Regards,
> > Gary
>
> Hi Gary,
>
> When I searched the solution for my issue, I found the option
> 'foldopen', and I also had checked it, which is
> :se fdo?
> foldopen=block,hor,mark,percent,quickfix,search,tag,undo
> Is it OK?
>
> Sorry, it's my poor English to let you misunderstand my issue.
> After finishing a search, the cursor will jump to the first match,
> even it's in the fold, that is OK.
> But what I want is "incremental" search, that is, when I typing
> the word a character by character, the cursor would jump into the
> corresponding match instantly with automatically folding and
> unfolding.
> If I set "incsearch" and no fold here, everything is fine.
> But if the 1st match is in a fold, there is no window responding,
> just like "noincsearch".
>
> Is there a way to satisfy my need?
>
> Regards,
> Kevin
Hi Kevin,
You explained your issue well. The fault is mine. I thought that
including "search" in 'foldopen' and setting 'foldclose' to "all"
might do what you wanted, or be close enough, but I didn't try it
before replying and I see now that it doesn't work for incremental
searches. Odd. It seems to me that it should. I don't know of a
way to do that.
Regards,
Gary
--
--
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: How do I open a new window without losing focus in the current one?
On Monday, December 29, 2014 8:18:54 AM UTC-6, Jeff Baxter wrote:
> If I use
>
> :new [filename]
>
> the file is opened in a split window, but the focus is also shifted there, whereas I want it to stay in the current window.
>
> How can I do that?
There is the :pedit command to open that file in the preview window. But the preview window is special; you probably don't want to do any editing in there, just reading. If that suits your needs, then this is probably what you were looking for.
--
--
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.
> If I use
>
> :new [filename]
>
> the file is opened in a split window, but the focus is also shifted there, whereas I want it to stay in the current window.
>
> How can I do that?
There is the :pedit command to open that file in the preview window. But the preview window is special; you probably don't want to do any editing in there, just reading. If that suits your needs, then this is probably what you were looking for.
--
--
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: Makefile editing slightly broken
On Monday, December 29, 2014 1:32:39 PM UTC-6, Kevin O'Gorman wrote:
> I dunno what happened, I'm still using the same .vimrc I have for years, but lately there's
> a glitch when I'm editing a Unix makefile.
>
> When I start to edit the commands for a rule, it uses spaces instead of a tab to position
> the command. For makefiles, of course, this is wrong. Vim even knows this, and highlights
> the line in red.
>
> If I add lines after existing commands it gets the indentation right, perhaps because it copies the indentation of the previous line.
>
>
>
>
>
>
>
> What should I look for? What should I fix?
>
Probably your 'expandtab' option has been set somewhere. You can figure out where using the command ":verbose set expandtab?"
Probably, you will need to fix this by creating or adding to an ftplugin file for makefiles, or use a Filetype autocmd event. Either way you'll want to "setlocal noexpandtab" for the makefile filetype.
--
--
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 dunno what happened, I'm still using the same .vimrc I have for years, but lately there's
> a glitch when I'm editing a Unix makefile.
>
> When I start to edit the commands for a rule, it uses spaces instead of a tab to position
> the command. For makefiles, of course, this is wrong. Vim even knows this, and highlights
> the line in red.
>
> If I add lines after existing commands it gets the indentation right, perhaps because it copies the indentation of the previous line.
>
>
>
>
>
>
>
> What should I look for? What should I fix?
>
Probably your 'expandtab' option has been set somewhere. You can figure out where using the command ":verbose set expandtab?"
Probably, you will need to fix this by creating or adding to an ftplugin file for makefiles, or use a Filetype autocmd event. Either way you'll want to "setlocal noexpandtab" for the makefile filetype.
--
--
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: Is there a way to incsearch with folded context
Gary Johnson於 2014年12月30日星期二UTC+8上午3時30分04秒寫道：
> On 2014-12-28, Kevin Wu wrote:
> > When I do searching, the cursor would jump to the first match, if
> > I set "incsearch".
> > But it's not true with folded context.
> > Specifically speaking, What I want to get is that when searching,
> > the folded context would be unfold automatically and the cursor
> > would jump into where the first match is, and moreover when the
> > cursor jump to another line, the unfolded context would be folded
> > again.
> >
> > Is there any way to satisfy my need?
>
> Take a look at
>
> :help 'foldopen'
> :help 'foldclose'
>
> Regards,
> Gary
Hi Gary,
When I searched the solution for my issue, I found the option 'foldopen', and I also had checked it,
which is
:se fdo?
foldopen=block,hor,mark,percent,quickfix,search,tag,undo
Is it OK?
Sorry, it's my poor English to let you misunderstand my issue.
After finishing a search, the cursor will jump to the first match,
even it's in the fold, that is OK.
But what I want is "incremental" search, that is, when I typing the word a character by character,
the cursor would jump into the corresponding match instantly with automatically folding and unfolding.
If I set "incsearch" and no fold here, everything is fine.
But if the 1st match is in a fold, there is no window responding, just like "noincsearch".
Is there a way to satisfy my need?
Regards,
Kevin
--
--
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 2014-12-28, Kevin Wu wrote:
> > When I do searching, the cursor would jump to the first match, if
> > I set "incsearch".
> > But it's not true with folded context.
> > Specifically speaking, What I want to get is that when searching,
> > the folded context would be unfold automatically and the cursor
> > would jump into where the first match is, and moreover when the
> > cursor jump to another line, the unfolded context would be folded
> > again.
> >
> > Is there any way to satisfy my need?
>
> Take a look at
>
> :help 'foldopen'
> :help 'foldclose'
>
> Regards,
> Gary
Hi Gary,
When I searched the solution for my issue, I found the option 'foldopen', and I also had checked it,
which is
:se fdo?
foldopen=block,hor,mark,percent,quickfix,search,tag,undo
Is it OK?
Sorry, it's my poor English to let you misunderstand my issue.
After finishing a search, the cursor will jump to the first match,
even it's in the fold, that is OK.
But what I want is "incremental" search, that is, when I typing the word a character by character,
the cursor would jump into the corresponding match instantly with automatically folding and unfolding.
If I set "incsearch" and no fold here, everything is fine.
But if the 1st match is in a fold, there is no window responding, just like "noincsearch".
Is there a way to satisfy my need?
Regards,
Kevin
--
--
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: How do I open a new window without losing focus in the current one?
On 2014-12-29 06:18, Jeff Baxter wrote:
> If I use
>
> :new [filename]
>
> the file is opened in a split window, but the focus is also shifted
> there, whereas I want it to stay in the current window.
>
> How can I do that?
I'm not sure it's possible to open an unfocused window. However, you
can use ^W-p or ":wincmd p"
:help CTRL-W_p
:h :wincmd
to return to the previous window you were in regardless of where the
new window was opened. Granted, that does alter what the previous
"previous window" was before you opened the new window, but I'm not
sure there's much one can do about that.
-tim
--
--
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.
> If I use
>
> :new [filename]
>
> the file is opened in a split window, but the focus is also shifted
> there, whereas I want it to stay in the current window.
>
> How can I do that?
I'm not sure it's possible to open an unfocused window. However, you
can use ^W-p or ":wincmd p"
:help CTRL-W_p
:h :wincmd
to return to the previous window you were in regardless of where the
new window was opened. Granted, that does alter what the previous
"previous window" was before you opened the new window, but I'm not
sure there's much one can do about that.
-tim
--
--
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 7.2.411 won't work on CentOS 2.6.32-504.3.3.el6.x86_64
On 2014-12-28, eiger3970 wrote:
> Hello,
> I install Vim on CentOS with command # yum install vim.
> This works, but then running vim gives error:
>
> [root@centos public_html]# vim contactus.html
> Error detected while processing /etc/vimrc:
> line 50:
> E484: Can't open file /usr/share/vim/syntax/syntax.vim
> Press ENTER or type command to continue
>
> The Vim file opens in green, rather than the usual colours I
> prefer to view code.
>
> Vimdiff has the same problem, as well as being unable to edit a
> file.
I logged on to a machine running Centos 6.6 and ran the following
command.
$ rpm -qa | grep vim
vim-minimal-7.2.411-1.8.el6.x86_64
vim-X11-7.2.411-1.8.el6.x86_64
vim-common-7.2.411-1.8.el6.x86_64
vim-enhanced-7.2.411-1.8.el6.x86_64
vim-clustershell-1.6-1.el6.noarch
According to that, there is no "vim" package. The vim-minimal,
vim-X11 and vim-enhanced packages provide executables but not the
runtime files. You appear to be missing the runtime files, which
are provided by the vim-common package. Try installing vim-common
and see if that fixes the problem.
Regards,
Gary
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Hello,
> I install Vim on CentOS with command # yum install vim.
> This works, but then running vim gives error:
>
> [root@centos public_html]# vim contactus.html
> Error detected while processing /etc/vimrc:
> line 50:
> E484: Can't open file /usr/share/vim/syntax/syntax.vim
> Press ENTER or type command to continue
>
> The Vim file opens in green, rather than the usual colours I
> prefer to view code.
>
> Vimdiff has the same problem, as well as being unable to edit a
> file.
I logged on to a machine running Centos 6.6 and ran the following
command.
$ rpm -qa | grep vim
vim-minimal-7.2.411-1.8.el6.x86_64
vim-X11-7.2.411-1.8.el6.x86_64
vim-common-7.2.411-1.8.el6.x86_64
vim-enhanced-7.2.411-1.8.el6.x86_64
vim-clustershell-1.6-1.el6.noarch
According to that, there is no "vim" package. The vim-minimal,
vim-X11 and vim-enhanced packages provide executables but not the
runtime files. You appear to be missing the runtime files, which
are provided by the vim-common package. Try installing vim-common
and see if that fixes the problem.
Regards,
Gary
--
--
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.
Makefile editing slightly broken
I dunno what happened, I'm still using the same .vimrc I have for years, but lately there's
a glitch when I'm editing a Unix makefile.
When I start to edit the commands for a rule, it uses spaces instead of a tab to positiona glitch when I'm editing a Unix makefile.
the command. For makefiles, of course, this is wrong. Vim even knows this, and highlights
the line in red.
What should I look for? What should I fix?
--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb)) /* Shakespeare */ | Please consider the environment before printing this email. |
--
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: Is there a way to incsearch with folded context
On 2014-12-28, Kevin Wu wrote:
> When I do searching, the cursor would jump to the first match, if
> I set "incsearch".
> But it's not true with folded context.
> Specifically speaking, What I want to get is that when searching,
> the folded context would be unfold automatically and the cursor
> would jump into where the first match is, and moreover when the
> cursor jump to another line, the unfolded context would be folded
> again.
>
> Is there any way to satisfy my need?
Take a look at
:help 'foldopen'
:help 'foldclose'
Regards,
Gary
--
--
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.
> When I do searching, the cursor would jump to the first match, if
> I set "incsearch".
> But it's not true with folded context.
> Specifically speaking, What I want to get is that when searching,
> the folded context would be unfold automatically and the cursor
> would jump into where the first match is, and moreover when the
> cursor jump to another line, the unfolded context would be folded
> again.
>
> Is there any way to satisfy my need?
Take a look at
:help 'foldopen'
:help 'foldclose'
Regards,
Gary
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Vim for Windows build, contains all 3rd party dependencies
Me too. I hate wordpad.
On Sun, Dec 28, 2014 at 8:53 AM, Shiny Bling <kybuliak@gmail.com> wrote:
On Sunday, 28 December 2014 14:21:18 UTC+1, Fernando Basso wrote:
> On Saturday, December 27, 2014 7:47:14 PM UTC-2, Shiny Bling wrote:
> >
> > Please let me know whether any of you find my effort useful.
> >
> > Thanks,
> > kybu
>
> I do because although my preferred OS is Linux, I am forced to use windows at my current job and your project will greatly help and simplify things for me. I really appreciate your effort. Thanks a lot.
Glad to hear that. I had been focusing on creating the installer before I announced it here, but now I am going to update 3rd party dependencies so there will be another installer in about a week or so.
--
--
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.
--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb)) /* Shakespeare */ | Please consider the environment before printing this email. |
--
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.
How do I open a new window without losing focus in the current one?
If I use
:new [filename]
the file is opened in a split window, but the focus is also shifted there, whereas I want it to stay in the current window.
How can I do that?
--
--
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.
:new [filename]
the file is opened in a split window, but the focus is also shifted there, whereas I want it to stay in the current window.
How can I do that?
--
--
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, December 28, 2014
Re: How to redirect output of cscope to a specified file
On 2014-12-28, Ying Huang wrote:
> Hi,
> I am using the cscope to search code in vim.
> The default behaviour, after press ctrl+space+ctrl+space+s is
> split or open a "quickfix"(not sure whether it is) temporarily to
> show the output.
> What I want is to persist the query result to a file
> /somewhere/<cword>.findresult.
> I notice some one suggest following way:
> :redir > filename
> :cs find f s word
> :redir end
> But the shortness for this method is if the result is more than
> one page, I need to manually scroll. Otherwise, only the current page
> would be put into my expected file. Thus it is very inconvenient to
> do this in shell.
> Any more ideas?
1. For the problem of scrolling more than one page, you might try
executing
:set nomore
before the :cs command and executing
:set more
afterward. See
:help 'more'
2. For the problem of saving a result to a file, are you aware of
the quickfix stack and the :colder and :cnewer commands? Vim
remembers the last ten quickfix error lists and keeps them in a
stack. That might work for you if you just want to keep track
of more than one error list per Vim session. See
:help quickfix-error-lists
3. To really save the results to a file, you could use the
getqflist() function obtain the results as a list, then save
that list to a file, perhaps using writefile(). That approach
will require a bit of programming since the getqflist() list
format is different from that used by setqflist() and from that
read by :cfile. See
:help getqflist()
:help writefile()
:help getqflist()
:help :cfile
4. Still another approach to saving the results to a file would be
to ignore Vim's internal :cscope commands and set 'makeprg' to a
pipeline or a script that would execute cscope and tee the
output to a file. That file could later be read in using
:cfile. That approach is probably more than you want to tackle
unless you are pretty comfortable with 'errorformat' and Vim
scripting. It also requires running cscope for each query
instead of running it as a coprocess as Vim's ":cscope find"
command does.
Regards,
Gary
--
--
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 am using the cscope to search code in vim.
> The default behaviour, after press ctrl+space+ctrl+space+s is
> split or open a "quickfix"(not sure whether it is) temporarily to
> show the output.
> What I want is to persist the query result to a file
> /somewhere/<cword>.findresult.
> I notice some one suggest following way:
> :redir > filename
> :cs find f s word
> :redir end
> But the shortness for this method is if the result is more than
> one page, I need to manually scroll. Otherwise, only the current page
> would be put into my expected file. Thus it is very inconvenient to
> do this in shell.
> Any more ideas?
1. For the problem of scrolling more than one page, you might try
executing
:set nomore
before the :cs command and executing
:set more
afterward. See
:help 'more'
2. For the problem of saving a result to a file, are you aware of
the quickfix stack and the :colder and :cnewer commands? Vim
remembers the last ten quickfix error lists and keeps them in a
stack. That might work for you if you just want to keep track
of more than one error list per Vim session. See
:help quickfix-error-lists
3. To really save the results to a file, you could use the
getqflist() function obtain the results as a list, then save
that list to a file, perhaps using writefile(). That approach
will require a bit of programming since the getqflist() list
format is different from that used by setqflist() and from that
read by :cfile. See
:help getqflist()
:help writefile()
:help getqflist()
:help :cfile
4. Still another approach to saving the results to a file would be
to ignore Vim's internal :cscope commands and set 'makeprg' to a
pipeline or a script that would execute cscope and tee the
output to a file. That file could later be read in using
:cfile. That approach is probably more than you want to tackle
unless you are pretty comfortable with 'errorformat' and Vim
scripting. It also requires running cscope for each query
instead of running it as a coprocess as Vim's ":cscope find"
command does.
Regards,
Gary
--
--
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.
Vim 7.2.411 won't work on CentOS 2.6.32-504.3.3.el6.x86_64
Hello,
I install Vim on CentOS with command # yum install vim.
This works, but then running vim gives error:
[root@centos public_html]# vim contactus.html
Error detected while processing /etc/vimrc:
line 50:
E484: Can't open file /usr/share/vim/syntax/syntax.vim
Press ENTER or type command to continue
The Vim file opens in green, rather than the usual colours I prefer to view code.
Vimdiff has the same problem, as well as being unable to edit a file.
--
--
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 install Vim on CentOS with command # yum install vim.
This works, but then running vim gives error:
[root@centos public_html]# vim contactus.html
Error detected while processing /etc/vimrc:
line 50:
E484: Can't open file /usr/share/vim/syntax/syntax.vim
Press ENTER or type command to continue
The Vim file opens in green, rather than the usual colours I prefer to view code.
Vimdiff has the same problem, as well as being unable to edit a file.
--
--
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 there a way to incsearch with folded context
When I do searching, the cursor would jump to the first match, if I set "incsearch".
But it's not true with folded context.
Specifically speaking, What I want to get is that when searching, the folded context would be unfold automatically and the cursor would jump into where the first match is, and moreover when the cursor jump to another line, the unfolded context would be folded again.
Is there any way to satisfy my need?
Thanks,
Kevin
--
--
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.
But it's not true with folded context.
Specifically speaking, What I want to get is that when searching, the folded context would be unfold automatically and the cursor would jump into where the first match is, and moreover when the cursor jump to another line, the unfolded context would be folded again.
Is there any way to satisfy my need?
Thanks,
Kevin
--
--
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.
How to redirect output of cscope to a specified file
Hi,
I am using the cscope to search code in vim.
The default behaviour, after press ctrl+space+ctrl+space+s is split
or open a "quickfix"(not sure whether it is) temporarily to show the output.
What I want is to persist the query result to a file
/somewhere/<cword>.findresult.
I notice some one suggest following way:
:redir > filename
:cs find f s word
:redir end
But the shortness for this method is if the result is more than one
page, I need to manually scroll. Otherwise, only the current page would
be put into my expected file. Thus it is very inconvenient to do this in
shell.
Any more ideas?
--
Best Regards,
Ying
--
--
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 using the cscope to search code in vim.
The default behaviour, after press ctrl+space+ctrl+space+s is split
or open a "quickfix"(not sure whether it is) temporarily to show the output.
What I want is to persist the query result to a file
/somewhere/<cword>.findresult.
I notice some one suggest following way:
:redir > filename
:cs find f s word
:redir end
But the shortness for this method is if the result is more than one
page, I need to manually scroll. Otherwise, only the current page would
be put into my expected file. Thus it is very inconvenient to do this in
shell.
Any more ideas?
--
Best Regards,
Ying
--
--
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: gvim visual mode selection changes as you scroll up and down, how to fix it?
On 2014-12-28 20:59, Mathias Rav wrote:
> On Sun, Dec 28, 2014 at 7:24 PM, Bao Niu <niubao56@gmail.com> wrote:
> > If I select a long patch of code spanning several pages, I'd like
> > to view how much I actually selected by scrolling up and down.
> > However this will automatically 'ruins' what I have selected
> > because it changes the anchor!
> >
> > How can I fix the two ends of what I have selected in visual
> > mode? Many thanks.
>
> You can press 'o' in visual mode to go to the other end of the
> selected text -- see :help v_o.
>
> You can also press g CTRL-G in visual mode to see how many
> lines/words/bytes you have selected -- see :help v_g_CTRL-G.
Additionally, instead of using visual mode right-out, you can drop a
mark at the two ends (such as 'a and 'b) and then scroll between them
to your heart's content. Once verified, you can
v`ao`b
(or use V/^V if you want line/block selection) and operate on the
resulting selection that you've verified.
-tkc
--
--
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 Sun, Dec 28, 2014 at 7:24 PM, Bao Niu <niubao56@gmail.com> wrote:
> > If I select a long patch of code spanning several pages, I'd like
> > to view how much I actually selected by scrolling up and down.
> > However this will automatically 'ruins' what I have selected
> > because it changes the anchor!
> >
> > How can I fix the two ends of what I have selected in visual
> > mode? Many thanks.
>
> You can press 'o' in visual mode to go to the other end of the
> selected text -- see :help v_o.
>
> You can also press g CTRL-G in visual mode to see how many
> lines/words/bytes you have selected -- see :help v_g_CTRL-G.
Additionally, instead of using visual mode right-out, you can drop a
mark at the two ends (such as 'a and 'b) and then scroll between them
to your heart's content. Once verified, you can
v`ao`b
(or use V/^V if you want line/block selection) and operate on the
resulting selection that you've verified.
-tkc
--
--
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: gvim visual mode selection changes as you scroll up and down, how to fix it?
On Sun, Dec 28, 2014 at 7:24 PM, Bao Niu <niubao56@gmail.com> wrote:
> If I select a long patch of code spanning several pages, I'd like to view how much I actually selected by scrolling up and down. However this will automatically 'ruins' what I have selected because it changes the anchor!
>
> How can I fix the two ends of what I have selected in visual mode? Many thanks.
You can press 'o' in visual mode to go to the other end of the
selected text -- see :help v_o.
You can also press g CTRL-G in visual mode to see how many
lines/words/bytes you have selected -- see :help v_g_CTRL-G.
Best,
Mathias Rav
--
--
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.
> If I select a long patch of code spanning several pages, I'd like to view how much I actually selected by scrolling up and down. However this will automatically 'ruins' what I have selected because it changes the anchor!
>
> How can I fix the two ends of what I have selected in visual mode? Many thanks.
You can press 'o' in visual mode to go to the other end of the
selected text -- see :help v_o.
You can also press g CTRL-G in visual mode to see how many
lines/words/bytes you have selected -- see :help v_g_CTRL-G.
Best,
Mathias Rav
--
--
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.
gvim visual mode selection changes as you scroll up and down, how to fix it?
If I select a long patch of code spanning several pages, I'd like to view how much I actually selected by scrolling up and down. However this will automatically 'ruins' what I have selected because it changes the anchor!
How can I fix the two ends of what I have selected in visual mode? Many 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.
How can I fix the two ends of what I have selected in visual mode? Many 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.
Re: [ANN] Vim for Windows build, contains all 3rd party dependencies
On Sunday, 28 December 2014 14:21:18 UTC+1, Fernando Basso wrote:
> On Saturday, December 27, 2014 7:47:14 PM UTC-2, Shiny Bling wrote:
> >
> > Please let me know whether any of you find my effort useful.
> >
> > Thanks,
> > kybu
>
> I do because although my preferred OS is Linux, I am forced to use windows at my current job and your project will greatly help and simplify things for me. I really appreciate your effort. Thanks a lot.
Glad to hear that. I had been focusing on creating the installer before I announced it here, but now I am going to update 3rd party dependencies so there will be another installer in about a week or so.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Saturday, December 27, 2014 7:47:14 PM UTC-2, Shiny Bling wrote:
> >
> > Please let me know whether any of you find my effort useful.
> >
> > Thanks,
> > kybu
>
> I do because although my preferred OS is Linux, I am forced to use windows at my current job and your project will greatly help and simplify things for me. I really appreciate your effort. Thanks a lot.
Glad to hear that. I had been focusing on creating the installer before I announced it here, but now I am going to update 3rd party dependencies so there will be another installer in about a week or so.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Vim for Windows build, contains all 3rd party dependencies
On Saturday, December 27, 2014 7:47:14 PM UTC-2, Shiny Bling wrote:
> Hi,
>
> I just released the first VIM installer which contains all(hopefully) 3rd party dependencies.
>
> I have been using VIM on Windows for a while but I only recently started using 'more recent' plugins. I ran into issues because quite often, the plugins were written in some popular scripting language (ruby, python, ...) So I ventured to hunt down required libraries but to get it fully working turned out to be quite painful. It is not only about installing required dlls, but also about making sure they actually work.
>
> I can only imagine that for a casual VIM user, this is close to impossible to get working.
>
> So I decided to build VIM with all 3rd party dependencies myself in hope that it will be useful for others as well.
>
> This really is a build with the dependencies built as well, not just them being bundled in. Which in turn means that they share compiler optimisation flags. It is possible to build it with, for instance, AVX instruction set (modern Intel CPUs).
>
> The installer for Win7 and whole repository can be found at https://bitbucket.org/kybu/vim-for-windows-single-drop
>
> The repository is structured in a way which allows for continuous updating of the 3rd party dependencies. I will go into more detail later on in the readme file.
>
> Please let me know whether any of you find my effort useful.
>
> Thanks,
> kybu
I do because although my preferred OS is Linux, I am forced to use windows at my current job and your project will greatly help and simplify things for me. I really appreciate your effort. Thanks a lot.
--
--
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 just released the first VIM installer which contains all(hopefully) 3rd party dependencies.
>
> I have been using VIM on Windows for a while but I only recently started using 'more recent' plugins. I ran into issues because quite often, the plugins were written in some popular scripting language (ruby, python, ...) So I ventured to hunt down required libraries but to get it fully working turned out to be quite painful. It is not only about installing required dlls, but also about making sure they actually work.
>
> I can only imagine that for a casual VIM user, this is close to impossible to get working.
>
> So I decided to build VIM with all 3rd party dependencies myself in hope that it will be useful for others as well.
>
> This really is a build with the dependencies built as well, not just them being bundled in. Which in turn means that they share compiler optimisation flags. It is possible to build it with, for instance, AVX instruction set (modern Intel CPUs).
>
> The installer for Win7 and whole repository can be found at https://bitbucket.org/kybu/vim-for-windows-single-drop
>
> The repository is structured in a way which allows for continuous updating of the 3rd party dependencies. I will go into more detail later on in the readme file.
>
> Please let me know whether any of you find my effort useful.
>
> Thanks,
> kybu
I do because although my preferred OS is Linux, I am forced to use windows at my current job and your project will greatly help and simplify things for me. I really appreciate your effort. Thanks a lot.
--
--
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, December 27, 2014
[ANN] Vim for Windows build, contains all 3rd party dependencies
Hi,
I just released the first VIM installer which contains all(hopefully) 3rd party dependencies.
I have been using VIM on Windows for a while but I only recently started using 'more recent' plugins. I ran into issues because quite often, the plugins were written in some popular scripting language (ruby, python, ...) So I ventured to hunt down required libraries but to get it fully working turned out to be quite painful. It is not only about installing required dlls, but also about making sure they actually work.
I can only imagine that for a casual VIM user, this is close to impossible to get working.
So I decided to build VIM with all 3rd party dependencies myself in hope that it will be useful for others as well.
This really is a build with the dependencies built as well, not just them being bundled in. Which in turn means that they share compiler optimisation flags. It is possible to build it with, for instance, AVX instruction set (modern Intel CPUs).
The installer for Win7 and whole repository can be found at https://bitbucket.org/kybu/vim-for-windows-single-drop
The repository is structured in a way which allows for continuous updating of the 3rd party dependencies. I will go into more detail later on in the readme file.
Please let me know whether any of you find my effort useful.
Thanks,
kybu
--
--
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 just released the first VIM installer which contains all(hopefully) 3rd party dependencies.
I have been using VIM on Windows for a while but I only recently started using 'more recent' plugins. I ran into issues because quite often, the plugins were written in some popular scripting language (ruby, python, ...) So I ventured to hunt down required libraries but to get it fully working turned out to be quite painful. It is not only about installing required dlls, but also about making sure they actually work.
I can only imagine that for a casual VIM user, this is close to impossible to get working.
So I decided to build VIM with all 3rd party dependencies myself in hope that it will be useful for others as well.
This really is a build with the dependencies built as well, not just them being bundled in. Which in turn means that they share compiler optimisation flags. It is possible to build it with, for instance, AVX instruction set (modern Intel CPUs).
The installer for Win7 and whole repository can be found at https://bitbucket.org/kybu/vim-for-windows-single-drop
The repository is structured in a way which allows for continuous updating of the 3rd party dependencies. I will go into more detail later on in the readme file.
Please let me know whether any of you find my effort useful.
Thanks,
kybu
--
--
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, December 25, 2014
Latest Vim version not updated at http://www.vim.org/
Hi
http://www.vim.org/ says... "Vim 7.4.557 is the current version".
Yet the latest is Vim has been 7.4.560 for 9 days already.
Dominique
--
--
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.
http://www.vim.org/ says... "Vim 7.4.557 is the current version".
Yet the latest is Vim has been 7.4.560 for 9 days already.
Dominique
--
--
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: CSCOPE ERROR: E429: File "path/to/file.c" does not exist
Do not set autochdir in your vimrc file.
On Thursday, August 13, 2009 1:08:29 PM UTC+8, newvimuser wrote:
> Hi,
>
> 1. I created a cscope.out file in my project root directory.
> 2. Next, set the CSCOPE_DB variable to that cscope.out file and
> exported the variable.
> 3. Then, I go into a subdirectory and launch vim on a file in that
> directory.
> 4. I execute "cs find 0 symbol" in that file and I get a list of
> instances where this symbol is found.
> 5. When I select an instance and hit Enter, I get the following
> error:
> "E429: File "path/to/file.c" does not exist"
>
> Can someone please help me out here.
>
> 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.
On Thursday, August 13, 2009 1:08:29 PM UTC+8, newvimuser wrote:
> Hi,
>
> 1. I created a cscope.out file in my project root directory.
> 2. Next, set the CSCOPE_DB variable to that cscope.out file and
> exported the variable.
> 3. Then, I go into a subdirectory and launch vim on a file in that
> directory.
> 4. I execute "cs find 0 symbol" in that file and I get a list of
> instances where this symbol is found.
> 5. When I select an instance and hit Enter, I get the following
> error:
> "E429: File "path/to/file.c" does not exist"
>
> Can someone please help me out here.
>
> 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.
Re: how to display different color in vi
Thank you everyone for your kind help. Until now I only succeeded in Sven's method.
I guess what I should do in the future is:
:syn match search_pattern "\<search_pattern\>"
:hi search_pattern ctermbg=color guibg=color
Is this correct? thanks
在 2014年12月24日星期三UTC+8下午5时14分02秒，skyworld写道：
> Hi,
>
> normally I use gvim instead of vi. My question is for gvim is: can i use different color to show diffent word? For example, I would like to highlight word "red" with red and "yellow" with color yellow in one document. Is this possible? 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 guess what I should do in the future is:
:syn match search_pattern "\<search_pattern\>"
:hi search_pattern ctermbg=color guibg=color
Is this correct? thanks
在 2014年12月24日星期三UTC+8下午5时14分02秒，skyworld写道：
> Hi,
>
> normally I use gvim instead of vi. My question is for gvim is: can i use different color to show diffent word? For example, I would like to highlight word "red" with red and "yellow" with color yellow in one document. Is this possible? 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.
Subscribe to:
Posts (Atom)