On 2019-02-15, James McCoy wrote:
> On Fri, Feb 15, 2019, 11:13 Gary Johnson wrote:
>
> On 2019-02-15, Bram Moolenaar wrote:
> > Gary Johnson wrote:
> > > My guess is that Vim is swallowing the Normal Cursor Keys command.
> > >
> > > I'm cc'ing the vim_dev list because I
On 2019-02-15, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > On 2019-02-14, Gary Johnson wrote:
> > > On 2019-02-14, Paul wrote:
> > > > ":" normally scrolls through command history. However, after
> > > > I pipe the buffer to less, that no longer happens. With or without
> > > > any LESS*
Gary Johnson wrote:
> On 2019-02-14, Gary Johnson wrote:
> > On 2019-02-14, Paul wrote:
> > > ":" normally scrolls through command history. However, after
> > > I pipe the buffer to less, that no longer happens. With or without
> > > any LESS* environment variables set:
> > >
> > > 1. vim -Nu
On Thu, Feb 14, 2019 at 05:04:17PM -0800, Gary Johnson wrote:
I found that the problem can be avoided by using the --no-keypad
option to less, like this:
:w !less --no-keypad
Nice one :)
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below
On 2019-02-14, Gary Johnson wrote:
> On 2019-02-14, Paul wrote:
> > ":" normally scrolls through command history. However, after
> > I pipe the buffer to less, that no longer happens. With or without
> > any LESS* environment variables set:
> >
> > 1. vim -Nu NONE
> > 2. : " Fine
> > 3. " To
On 2019-02-14, Paul wrote:
> ":" normally scrolls through command history. However, after
> I pipe the buffer to less, that no longer happens. With or without
> any LESS* environment variables set:
>
> 1. vim -Nu NONE
> 2. : " Fine
> 3. " To cancel the scrolling from step 2
> 4. :w !less
> 5.
q: most likely is what you're talking about. It is the history of all your
commands.
Similarly, q/ is your recent searches.
On Sun, Jan 6, 2013 at 9:14 PM, Laskhara Singh relativity...@gmail.comwrote:
Hello
New to vim and sometimes I type some keystrokes by mistake and they lead
to some
Hi Chris,
On Mon, Jan 7, 2013 at 12:16 AM, Chris Schneider
ch...@christopher-schneider.com wrote:
q: most likely is what you're talking about. It is the history of all your
commands.
Similarly, q/ is your recent searches.
Thanks! I had thought about that myself.
--
You received this
Laskhara Singh wrote:
How do I recall the keystrokes history?
In Vim, a command history is a log of the Ex commands entered
(those commands that with :, like :tabe or :help :tabe.
As stated, you can see that history by typing q:
See
http://vim.wikia.com/wiki/Using_command-line_history
I
On Aug 17, 10:17 am, Paul paul.domas...@gmail.com wrote:
The foldcolumn option is listed as local to window. Whenever I recall
the command history (q:), the foldcolumn is set to the same as the
window in which the cursor resided when issuing q:. Is there a way
to prevent this? I am using
On Wed, August 17, 2011 4:22 pm, Paul wrote:
On Aug 17, 10:17 am, Paul paul.domas...@gmail.com wrote:
The foldcolumn option is listed as local to window. Whenever I recall
the command history (q:), the foldcolumn is set to the same as the
window in which the cursor resided when issuing q:.
On Aug 17, 10:41 am, Christian Brabandt cbli...@256bit.org wrote:
On Wed, August 17, 2011 4:22 pm, Paul wrote:
On Aug 17, 10:17 am, Paul paul.domas...@gmail.com wrote:
The foldcolumn option is listed as local to window. Whenever I recall
the command history (q:), the foldcolumn is set to
On 17 August 2011 10:52, Paul paul.domas...@gmail.com wrote:
According to the help, foldcolumn is local to window. I can try
:setg foldcolumn=0, but when I issue :setg? foldcolumn, the result
depends is determined by whatever window I happen to be in. So does
the foldcolumns showing in the
On Wed, August 17, 2011 4:52 pm, Paul wrote:
According to the help, foldcolumn is local to window. I can try
:setg foldcolumn=0, but when I issue :setg? foldcolumn, the result
depends is determined by whatever window I happen to be in. So does
the foldcolumns showing in the command history.
On Aug 17, 11:06 am, Christian Brabandt cbli...@256bit.org wrote:
On Wed, August 17, 2011 4:52 pm, Paul wrote:
According to the help, foldcolumn is local to window. I can try
:setg foldcolumn=0, but when I issue :setg? foldcolumn, the result
depends is determined by whatever window I
Hi Tim,
On 7/15/2011 3:20 AM, Tim Chase wrote:
On 07/14/2011 12:58 PM, Gelonida N wrote:
When I connect as one user I can access thevim command
history.
I press ':' and then the cursor-up key to get to the previous
command, that I typed.
when I connect on the same host as user root (I use su
16 matches
Mail list logo
