Re: undojoin after an undo

On Fri, Aug 17, 2007 at 10:31:27PM +0200, Bram Moolenaar wrote: > There is a generic way to silence errors, there is no need to add this > functionality to every command: > > :silent! undojoin Ah. I should RTFM more. Thanks, GI -- 'Common' Proof Techniques: 21. Proof by mutual referenc

Re: and backslashes

Bram Moolenaar wrote: >Charles Campbell wrote: > > > >>So, a feature request: how about a that breaks the input >>arguments at whitespace (but otherwise leaves the arguments alone). The >>"p" is to be vaguely reminescent of: pattern-arguments (as in regular >>expression patterns)? >> >

Re: and backslashes

Charles Campbell wrote: > I just had an error report about Align that's curious. I've been > passing arguments to Align and AlignCtrl with -- has that > recently changed? At issue is backslashes and input argument > processing. I see where now converts \\ to \ , but \x (where x > is not

Re: undojoin after an undo

Gautam Iyer wrote: > On Thu, Aug 16, 2007 at 08:33:29PM +0200, Bram Moolenaar wrote: > > > > If I undo a change, and then do > > > > > > undojoin | delete > > > > > > I get an error. Perhaps you could add a "undojoin!" command that > > > silently ignores the "undojoin" if the previous ope

Re: and backslashes

Charles E Campbell Jr wrote: >So, a feature request: how about a that breaks the input >arguments at whitespace (but otherwise leaves the arguments alone). The >"p" is to be vaguely reminescent of: pattern-arguments (as in regular >expression patterns)? > > Hello! If anyone's interested, h

Re: Problems with Vim lists on Google Groups

Bram Moolenaar wrote: > > Hello Vim users, > > A few weeks ago the Vim maillists were moved to the Google Groups > system. For most people this worked well, but some experienced problems > receiving and posting messages. That means one is successfully > subscribed, but messages are not receive

and backslashes

Hello! I just had an error report about Align that's curious. I've been passing arguments to Align and AlignCtrl with -- has that recently changed? At issue is backslashes and input argument processing. I see where now converts \\ to \ , but \x (where x is not a \ ) is left as \x . Seve

Re: Bug (regression in 7.1.077 ?) :mks with Unicode chars in 'lcs'

Bram Moolenaar wrote: > Tony Mechelynck wrote: > >> :mksession (in 7.1.077) or gvim -S (in 7.1.079) doesn't work properly >> in UTF-8 locale with Unicode codepoints (> U+007F) in 'listchars' >> >> gvim 7.1.077 in UTF-8 locale >> [...] >> :set lcs=tab:\|_,eol:=B6,nbsp:~ >> [...] >> :mks!