Re: :wn to :x like map/abbrev ?

2018-12-07 Thread Bram Moolenaar


> Thanks.  I will look into that func, or something like it.
> 
> > Making the one act like the other would confuse me.
> 
> I think I'm really only asking for a :x to save and move on with out 
> prompting.

Something like:
:update|next
perhaps?

-- 
"Beware of bugs in the above code; I have only proved
it correct, not tried it." -- Donald Knuth

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: :p & :P bugs?

2018-12-07 Thread Bram Moolenaar


Tim Chase wrote:

> Brought to my attention by this thread:
> 
> https://www.reddit.com/r/vim/comments/a3e80i/is_vim_right_for_me/
> 
> It seems to me that :p should always only print the line, even if
> 'number' is set.  If you want to print the line with its line-number,
> you can either use ":p#" (:help ex-flags) or even just ":#".  But
> without storing 'nu' and deactivating it before issuing and restoring
> the state of 'nu' after, there's no way to get unnumbered results.
> 
> Additionally, while reading over those docs, I encountered that
> ":P[rint]" should do the same thing as ":p", but netrwPlugin.vim
> overrides ":P" in a fairly stock environment (in a fresh OpenBSD
> system, installed vim; invoking "vim" had netrwPlugin loaded).  That
> said, if invoked as "vim -u NONE", the `:P` works as documented.  So
> it seems like either the docs should be updated so that ":help :P"
> goes to netrw docs; or netrw's "Pexplore" shouldn't override the
> built-in ":P"
> 
> (and here's hoping that your mail-client doesn't turn all those
> colon-P strings into smile-with-tongue-out emoji)

These are old Vi commands.  Keeping them working as they did in the past
40 years is more important than some tuning of their behavior.

If you actually use :P for printing a line (I never do that), you can
redefine :Pexplore somehow.  I don't think there are enough users that
run into this for it to matter.

-- 
OLD WOMAN: King of the WHO?
ARTHUR:The Britons.
OLD WOMAN: Who are the Britons?
 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.