On Wed, Feb 15, 2017 at 5:48 AM, <gordon55gg@gmail.com> wrote:
> Thanks for reading.
> I am using Terminal VIM and it works very well.
> And the scroll bar for Terminal works fine.
> But when I run VIM (from Terminal or batch file),
> the scroll bar has no "scroll box".
> The "scroll box" is that small rectangle indicating
> the location of the current window.
>
> Batch file:
> @echo off
> chdir C:/cygwin64/bin
> start mintty.exe -p 0,0 /usr/bin/vim.exe %1
>
> How can I get the scroll bar working for Terminal VIM?
In Console mode, the scrollbar is a console feature, not a Vim
feature. But Vim will tell you at which "percentage" of the file you
are looking, usually in the bottom-right corner of the current
split-window, where it says one of the following:
All
Top
Bot
nn%
The first three tell you that you see one end, or the other, or both,
of the file, Otherwise it tells you a percentage, from 01% to 99%,
meaning you are at that "percentage point" within the file. If you use
a custom 'statusline' setting, it is the %P element (or you can use %p
instead, for more verbosity).
To get a Vim scrollbar, use gvim (or, on the Mac, macvim) instead of
vim. Then you can set 'guioptions' to have or not have scrollbars on
the left, right and/or bottom depending on some conditions (see ":help
'guioptions' " with the single quotes but not the double quotes).
Best regards,
Tony.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wednesday, February 15, 2017
Re: Buffer number explodes when :vimgrep is called.
2017-02-15 3:00 GMT+03:00 <jrfranklin@georgiasouthern.edu>:
> Hello all,
>
> When I call :vimgrep, I'll usually search a directory of 600-1000 files. The number of unlisted buffers explodes after the call (I assume because buffers must be loaded into vim in order for the text to be searched). Lately I've been using buffer numbers for navigation, but entering three-digit buffer numbers has become annoying. Is this property of :vimgrep able to be switched off with a Vim setting? I'm surprised I can't find another instance of this question being asked online...
>
> On the note of buffer numbers, is it advisable that I side-step using buffer numbers for navigation/file switching and find a better way? What would more experienced users suggest?
I like fuzzy-finder plugins for navigating buffers. Specifically I use
Command-T which requires +ruby, but there are lots of alternatives:
unite/denite, CtrlP, FUF, ku, constructing something on top of tlib, I
also saw a Command-T reimplementation in Python somewhere.
My workflow also suggests that I open all project file with a single
shell command and then use Command-T to navigate through
already-created (though not yet loaded, Vim does not load all files
specified on command-line immediately) buffers because scanning
filesystem of large projects sucks; or, at least, sucket last time I
bothered to use it in Command-T: zsh does scanning much faster (also
because it does not attept to scan absolutely everything: I have
specific globs) though yet it can't beat `find` if you consider only
speed.
There is also a good replacement for :vimgrep: ag.vim uses less
verbose PCRE syntax (via ag aka the_silver_searcher), runs much faster
and will not load all files ag visits.
>
> Best,
> Jason
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and 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.
> Hello all,
>
> When I call :vimgrep, I'll usually search a directory of 600-1000 files. The number of unlisted buffers explodes after the call (I assume because buffers must be loaded into vim in order for the text to be searched). Lately I've been using buffer numbers for navigation, but entering three-digit buffer numbers has become annoying. Is this property of :vimgrep able to be switched off with a Vim setting? I'm surprised I can't find another instance of this question being asked online...
>
> On the note of buffer numbers, is it advisable that I side-step using buffer numbers for navigation/file switching and find a better way? What would more experienced users suggest?
I like fuzzy-finder plugins for navigating buffers. Specifically I use
Command-T which requires +ruby, but there are lots of alternatives:
unite/denite, CtrlP, FUF, ku, constructing something on top of tlib, I
also saw a Command-T reimplementation in Python somewhere.
My workflow also suggests that I open all project file with a single
shell command and then use Command-T to navigate through
already-created (though not yet loaded, Vim does not load all files
specified on command-line immediately) buffers because scanning
filesystem of large projects sucks; or, at least, sucket last time I
bothered to use it in Command-T: zsh does scanning much faster (also
because it does not attept to scan absolutely everything: I have
specific globs) though yet it can't beat `find` if you consider only
speed.
There is also a good replacement for :vimgrep: ag.vim uses less
verbose PCRE syntax (via ag aka the_silver_searcher), runs much faster
and will not load all files ag visits.
>
> Best,
> Jason
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and 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: gVim under Linux starts too low when it is configured to take all vertical space.
> Works for me on openSUSE Linux (currently openSUSE Leap 42.2) in gvim
> for GTK3 (and previously for GTK2) with the following in my vimrc:
Well, it looks like it is a problem with my particular setup / window manager. I should write to vim's developer group to see if someone can help me find the source of the problem by activating some traces.
Thank you for your kind reply.
Hans Deragon
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> for GTK3 (and previously for GTK2) with the following in my vimrc:
Well, it looks like it is a problem with my particular setup / window manager. I should write to vim's developer group to see if someone can help me find the source of the problem by activating some traces.
Thank you for your kind reply.
Hans Deragon
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Buffer number explodes when :vimgrep is called.
Hi Tony!
I'm working on a plugin that relies on numbering the buffers in some way. The idea is to make switching among them far easier. I think I have it figured out... I'll just enumerate the buffers based on their relative position in the buffer list. This will provide numbering that is consistent.
My only worry is that the user will get confused. The buffer "id" being used to reference a buffer specifically will be different from the buffer's numeric position in the buffer list, of course. I think it will all turn out fine though.
Thanks!
Jason
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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 working on a plugin that relies on numbering the buffers in some way. The idea is to make switching among them far easier. I think I have it figured out... I'll just enumerate the buffers based on their relative position in the buffer list. This will provide numbering that is consistent.
My only worry is that the user will get confused. The buffer "id" being used to reference a buffer specifically will be different from the buffer's numeric position in the buffer list, of course. I think it will all turn out fine though.
Thanks!
Jason
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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, February 14, 2017
Re: VIM scroll bar is missing scroll box
Hi gordon55gg!
On Di, 14 Feb 2017, gordon55gg@gmail.com wrote:
> Thanks for reading.
> I am using Terminal VIM and it works very well.
> And the scroll bar for Terminal works fine.
> But when I run VIM (from Terminal or batch file),
> the scroll bar has no "scroll box".
> The "scroll box" is that small rectangle indicating
> the location of the current window.
>
> Batch file:
> @echo off
> chdir C:/cygwin64/bin
> start mintty.exe -p 0,0 /usr/bin/vim.exe %1
>
> How can I get the scroll bar working for Terminal VIM?
Isn't that a question for the cygwin guys?
Best,
Christian
--
Zur tiefsten Freude an dem, was ist, gehört die Freude an dem, was
ist.
-- Karl Foerster
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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, 14 Feb 2017, gordon55gg@gmail.com wrote:
> Thanks for reading.
> I am using Terminal VIM and it works very well.
> And the scroll bar for Terminal works fine.
> But when I run VIM (from Terminal or batch file),
> the scroll bar has no "scroll box".
> The "scroll box" is that small rectangle indicating
> the location of the current window.
>
> Batch file:
> @echo off
> chdir C:/cygwin64/bin
> start mintty.exe -p 0,0 /usr/bin/vim.exe %1
>
> How can I get the scroll bar working for Terminal VIM?
Isn't that a question for the cygwin guys?
Best,
Christian
--
Zur tiefsten Freude an dem, was ist, gehört die Freude an dem, was
ist.
-- Karl Foerster
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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 scroll bar is missing scroll box
Thanks for reading.
I am using Terminal VIM and it works very well.
And the scroll bar for Terminal works fine.
But when I run VIM (from Terminal or batch file),
the scroll bar has no "scroll box".
The "scroll box" is that small rectangle indicating
the location of the current window.
Batch file:
@echo off
chdir C:/cygwin64/bin
start mintty.exe -p 0,0 /usr/bin/vim.exe %1
How can I get the scroll bar working for Terminal VIM?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I am using Terminal VIM and it works very well.
And the scroll bar for Terminal works fine.
But when I run VIM (from Terminal or batch file),
the scroll bar has no "scroll box".
The "scroll box" is that small rectangle indicating
the location of the current window.
Batch file:
@echo off
chdir C:/cygwin64/bin
start mintty.exe -p 0,0 /usr/bin/vim.exe %1
How can I get the scroll bar working for Terminal VIM?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Buffer number explodes when :vimgrep is called.
On Wed, Feb 15, 2017 at 1:00 AM, <jrfranklin@georgiasouthern.edu> wrote:
> Hello all,
>
> When I call :vimgrep, I'll usually search a directory of 600-1000 files. The number of unlisted buffers explodes after the call (I assume because buffers must be loaded into vim in order for the text to be searched). Lately I've been using buffer numbers for navigation, but entering three-digit buffer numbers has become annoying. Is this property of :vimgrep able to be switched off with a Vim setting? I'm surprised I can't find another instance of this question being asked online...
>
> On the note of buffer numbers, is it advisable that I side-step using buffer numbers for navigation/file switching and find a better way? What would more experienced users suggest?
>
> Best,
> Jason
You could call them by filepathname instead. Or you could check the
list using :ls! (with bang) then use :bwipeout (not :bdelete) on any
of them you want to forget, and finally restart Vim. (Without
restarting the buffers will be forgotten but the next one will still
be after those three-digit buffer numbers.)
Best regards,
Tony.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Hello all,
>
> When I call :vimgrep, I'll usually search a directory of 600-1000 files. The number of unlisted buffers explodes after the call (I assume because buffers must be loaded into vim in order for the text to be searched). Lately I've been using buffer numbers for navigation, but entering three-digit buffer numbers has become annoying. Is this property of :vimgrep able to be switched off with a Vim setting? I'm surprised I can't find another instance of this question being asked online...
>
> On the note of buffer numbers, is it advisable that I side-step using buffer numbers for navigation/file switching and find a better way? What would more experienced users suggest?
>
> Best,
> Jason
You could call them by filepathname instead. Or you could check the
list using :ls! (with bang) then use :bwipeout (not :bdelete) on any
of them you want to forget, and finally restart Vim. (Without
restarting the buffers will be forgotten but the next one will still
be after those three-digit buffer numbers.)
Best regards,
Tony.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Posts (Atom)
