Re: neovim and less

[R Ransbottom <rirans@comcast.net>]

Hi Jonathan,


I was more on the path of confirming a bug.  I got the same behavior on
vim and vim-nox on gnome terminal and the console tty.  Updating
everything updateable and finally rebooting fixed it.

So I suspect some kernel issue, but I don't know.  For all my efforts,
I am no wiser just happier--if I'm happier maybe I am--no that's just
stupid. Ha!

Thanks for the suggestions.

rir

On Mon, Nov 04, 2019 at 02:01:01PM +0000, Jonathan Dowland wrote:
> On Sat, Nov 02, 2019 at 02:27:19PM -0400, R Ransbottom wrote:
> > Issuing a ex command like
> > 
> >    :! perldoc -f close
> > 
> > or
> > 
> >    :! cat some_file | less
> > 
> > brings me directly to the end of the file output, leaving me with
> > the nvim message:
> > 
> >    Press ENTER or type command to continue
> > 
> > requiring me to navigate to the start of the output.  Less does not
> > do this when invoked from bash.
> 
> Side-stepping the issue a little, but you could consider opening a new
> scratch buffer and then reading the output of your shell command into
> it, then just navigating that buffer in nvim directly, rather than using
> an external pager. E.g.
> 
>    :ene
>    :r! perldoc -f close
> 
> Or more simply for your cat|less example, simply open the file in nvim
> directly, in a new pane if you wish
> 
>    :sp
>    :e some_file
>