Re: Bug/non-determinism in output of maparg() and map commands

On Mon, May 29, 2017 at 3:31 PM, Nikolay Aleksandrovich Pavlov wrote: > 2017-05-29 22:17 GMT+03:00 Brett Stahlman : >> On Mon, May 29, 2017 at 3:19 AM, Nikolay Aleksandrovich Pavlov >> wrote: >> [...] > > This is not actually

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-29 22:17 GMT+03:00 Brett Stahlman : > On Mon, May 29, 2017 at 3:19 AM, Nikolay Aleksandrovich Pavlov > wrote: > [...] This is not actually different from the current situation: was needing to check for `exists('*win_id2win')`,

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-29 4:25 GMT+03:00 Brett Stahlman : > On Sun, May 28, 2017 at 4:19 PM, Nikolay Aleksandrovich Pavlov > wrote: > [...] >> >> And why do you think that “do not make plugins reinwent the wheel” is >> the same statement as “write needed

Re: Bug/non-determinism in output of maparg() and map commands

On Sun, May 28, 2017 at 4:19 PM, Nikolay Aleksandrovich Pavlov wrote: [...] > > And why do you think that “do not make plugins reinwent the wheel” is > the same statement as “write needed functionality in C code”? You can > always add a new file to `autoload`,

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-28 23:16 GMT+03:00 Brett Stahlman : > On Sun, May 28, 2017 at 1:10 PM, Nikolay Aleksandrovich Pavlov > wrote: > > [...] You may also ask Brett Stahlman whether my proposal is enough, it does not look like he thinks it is not, just

Re: Bug/non-determinism in output of maparg() and map commands

On Sun, May 28, 2017 at 1:10 PM, Nikolay Aleksandrovich Pavlov wrote: [...] >>> >>> You may also ask Brett Stahlman whether my proposal is enough, it does >>> not look like he thinks it is not, just that it may be less >>> convenient. >> >> I believe it would be possible to do

Re: Bug/non-determinism in output of maparg() and map commands

Am 22.05.2017 um 20:14 schrieb Brett Stahlman: I would like to be able to save and restore mappings programmatically. In order to do so, however, I need to be able to determine the exact lhs and rhs used to create the mapping. I had assumed the lhs/rhs members of the dictionary returned by

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-28 19:05 GMT+03:00 Brett Stahlman : > On Sun, May 28, 2017 at 6:50 AM, Nikolay Aleksandrovich Pavlov > wrote: >> 2017-05-28 8:57 GMT+03:00 Bram Moolenaar : >>> >>> Nikolay Pavlov wrote: >>> >>> [..] >>> >> Enable,

Re: Bug/non-determinism in output of maparg() and map commands

On Sun, May 28, 2017 at 6:50 AM, Nikolay Aleksandrovich Pavlov wrote: > 2017-05-28 8:57 GMT+03:00 Bram Moolenaar : >> >> Nikolay Pavlov wrote: >> >> [..] >> >>> >> Enable, disable, query, execute plus two callbacks. *Four* functions >>> >> and two callbacks

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-28 8:57 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > > [..] > >> >> Enable, disable, query, execute plus two callbacks. *Four* functions >> >> and two callbacks in place of just two simple functions, mostly using >> >> the functionality that is already there.

Re: Bug/non-determinism in output of maparg() and map commands

Nikolay Pavlov wrote: [..] > >> Enable, disable, query, execute plus two callbacks. *Four* functions > >> and two callbacks in place of just two simple functions, mostly using > >> the functionality that is already there. Five if you remember about > >> :mkvimrc and that somebody may want to

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-27 20:29 GMT+03:00 Brett Stahlman : > On Sat, May 27, 2017 at 11:51 AM, Nikolay Aleksandrovich Pavlov > wrote: >> 2017-05-27 19:32 GMT+03:00 Brett Stahlman : >>> On Sat, May 27, 2017 at 10:39 AM, Nikolay Aleksandrovich

Re: Bug/non-determinism in output of maparg() and map commands

On Sat, May 27, 2017 at 11:51 AM, Nikolay Aleksandrovich Pavlov wrote: > 2017-05-27 19:32 GMT+03:00 Brett Stahlman : >> On Sat, May 27, 2017 at 10:39 AM, Nikolay Aleksandrovich Pavlov >> wrote: >>> 2017-05-27 18:02 GMT+03:00 Brett

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-27 19:48 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> 2017-05-27 18:02 GMT+03:00 Brett Stahlman : >> > On Sat, May 27, 2017 at 8:35 AM, Nikolay Aleksandrovich Pavlov >> > wrote: >> >> 2017-05-27 12:45 GMT+03:00

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-27 19:32 GMT+03:00 Brett Stahlman : > On Sat, May 27, 2017 at 10:39 AM, Nikolay Aleksandrovich Pavlov > wrote: >> 2017-05-27 18:02 GMT+03:00 Brett Stahlman : >>> On Sat, May 27, 2017 at 8:35 AM, Nikolay Aleksandrovich

Re: Bug/non-determinism in output of maparg() and map commands

Nikolay Pavlov wrote: > 2017-05-27 18:02 GMT+03:00 Brett Stahlman : > > On Sat, May 27, 2017 at 8:35 AM, Nikolay Aleksandrovich Pavlov > > wrote: > >> 2017-05-27 12:45 GMT+03:00 Bram Moolenaar : > >>> > >>> Nikolay Pavlov wrote: >

Re: Bug/non-determinism in output of maparg() and map commands

On Sat, May 27, 2017 at 10:39 AM, Nikolay Aleksandrovich Pavlov wrote: > 2017-05-27 18:02 GMT+03:00 Brett Stahlman : >> On Sat, May 27, 2017 at 8:35 AM, Nikolay Aleksandrovich Pavlov >> wrote: >>> 2017-05-27 12:45 GMT+03:00 Bram

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-27 18:02 GMT+03:00 Brett Stahlman : > On Sat, May 27, 2017 at 8:35 AM, Nikolay Aleksandrovich Pavlov > wrote: >> 2017-05-27 12:45 GMT+03:00 Bram Moolenaar : >>> >>> Nikolay Pavlov wrote: >>> 2017-05-26 20:43 GMT+03:00

Re: Bug/non-determinism in output of maparg() and map commands

On Sat, May 27, 2017 at 8:35 AM, Nikolay Aleksandrovich Pavlov wrote: > 2017-05-27 12:45 GMT+03:00 Bram Moolenaar : >> >> Nikolay Pavlov wrote: >> >>> 2017-05-26 20:43 GMT+03:00 Bram Moolenaar : >>> > >>> > Brett Stahlman wrote: >>> > >>>

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-27 12:45 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> 2017-05-26 20:43 GMT+03:00 Bram Moolenaar : >> > >> > Brett Stahlman wrote: >> > >> >> >> On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: >> >> >> > On Tue, May

Re: Bug/non-determinism in output of maparg() and map commands

On Sat, May 27, 2017 at 4:45 AM, Bram Moolenaar wrote: > > Nikolay Pavlov wrote: > >> 2017-05-26 20:43 GMT+03:00 Bram Moolenaar : >> > >> > Brett Stahlman wrote: >> > >> >> >> On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: >> >> >> > On

Re: Bug/non-determinism in output of maparg() and map commands

Nikolay Pavlov wrote: > 2017-05-26 20:43 GMT+03:00 Bram Moolenaar : > > > > Brett Stahlman wrote: > > > >> >> On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: > >> >> > On Tue, May 23, 2017 at 4:35 AM, Bram Moolenaar > >> >> > wrote: >

Re: Bug/non-determinism in output of maparg() and map commands

On Fri, May 26, 2017 at 5:24 PM, Nikolay Aleksandrovich Pavlov wrote: > 2017-05-27 0:32 GMT+03:00 Brett Stahlman : >> On Fri, May 26, 2017 at 4:12 PM, Nikolay Aleksandrovich Pavlov >> wrote: >>> 2017-05-26 20:43 GMT+03:00 Bram

Re: Bug/non-determinism in output of maparg() and map commands

On Fri, May 26, 2017 at 4:12 PM, Nikolay Aleksandrovich Pavlov wrote: > 2017-05-26 20:43 GMT+03:00 Bram Moolenaar : >> >> Brett Stahlman wrote: >> >>> >> On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: >>> >> > On Tue, May 23, 2017 at

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-27 0:12 GMT+03:00 Nikolay Aleksandrovich Pavlov : > 2017-05-26 20:43 GMT+03:00 Bram Moolenaar : >> >> Brett Stahlman wrote: >> >>> >> On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: >>> >> > On Tue, May 23, 2017 at 4:35 AM, Bram

Re: Bug/non-determinism in output of maparg() and map commands

2017-05-26 20:43 GMT+03:00 Bram Moolenaar : > > Brett Stahlman wrote: > >> >> On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: >> >> > On Tue, May 23, 2017 at 4:35 AM, Bram Moolenaar >> >> > wrote: >> >> > > >> >> > > Brett Stahlman

Re: Bug/non-determinism in output of maparg() and map commands

On Fri, May 26, 2017 at 12:43 PM, Bram Moolenaar wrote: > > Brett Stahlman wrote: > %--snip--% >> >> Yes. Very much like that. I'm implementing a sort of transient mode, in >> which I'll "shadow" existing maps with very short (generally single >> character) mappings, which

Re: Bug/non-determinism in output of maparg() and map commands

Brett Stahlman wrote: > >> On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: > >> > On Tue, May 23, 2017 at 4:35 AM, Bram Moolenaar > >> > wrote: > >> > > > >> > > Brett Stahlman wrote: > >> > > > >> %--snip--% > >> > > > >> > > The best solution is

Re: Bug/non-determinism in output of maparg() and map commands

On Wed, May 24, 2017 at 9:28 AM, Brett Stahlman wrote: > On Wed, May 24, 2017 at 2:08 AM, Bram Moolenaar wrote: >> >> Brett Stahlman wrote: >> >>> On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: >>> > On Tue, May 23, 2017 at 4:35

Re: Bug/non-determinism in output of maparg() and map commands

On Wed, May 24, 2017 at 2:08 AM, Bram Moolenaar wrote: > > Brett Stahlman wrote: > >> On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: >> > On Tue, May 23, 2017 at 4:35 AM, Bram Moolenaar wrote: >> > > >> > > Brett Stahlman wrote: >> > >

Re: Bug/non-determinism in output of maparg() and map commands

Brett Stahlman wrote: > On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: > > On Tue, May 23, 2017 at 4:35 AM, Bram Moolenaar wrote: > > > > > > Brett Stahlman wrote: > > > > %--snip--% > > > > > > The best solution is probably to also add the raw rhs, with

Re: Bug/non-determinism in output of maparg() and map commands

On Tuesday, May 23, 2017 at 8:25:33 AM UTC-5, Brett Stahlman wrote: > On Tue, May 23, 2017 at 4:35 AM, Bram Moolenaar wrote: > > > > Brett Stahlman wrote: > > %--snip--% > > > > The best solution is probably to also add the raw rhs, with the terminal > > codes replaced. This

Re: Bug/non-determinism in output of maparg() and map commands

On Tue, May 23, 2017 at 4:35 AM, Bram Moolenaar wrote: > > Brett Stahlman wrote: > >> I would like to be able to save and restore mappings programmatically. In >> order to do so, however, I need to be able to determine the exact lhs and >> rhs used to create the mapping. I had

Re: Bug/non-determinism in output of maparg() and map commands

Brett Stahlman wrote: > I would like to be able to save and restore mappings programmatically. In > order to do so, however, I need to be able to determine the exact lhs and > rhs used to create the mapping. I had assumed the lhs/rhs members of the > dictionary returned by maparg() would

Bug/non-determinism in output of maparg() and map commands

I would like to be able to save and restore mappings programmatically. In order to do so, however, I need to be able to determine the exact lhs and rhs used to create the mapping. I had assumed the lhs/rhs members of the dictionary returned by maparg() would provided this information, but as the