Christian Brabandt wrote:
> On Mo, 16 Nov 2015, Christian Brabandt wrote:
> > So how about adding some warning into the documentation that putting
> > from the same register that is used for recording won't likely work as
> > one would expect and perhaps also mention in the status line which
> >
On Mo, 16 Nov 2015, Christian Brabandt wrote:
> So how about adding some warning into the documentation that putting
> from the same register that is used for recording won't likely work as
> one would expect and perhaps also mention in the status line which
> register is used for recording (e.g. i
On Tue, Nov 17, 2015 at 9:21 AM, Jeff Felchner
wrote:
> Tony, I definitely don't think there should be a prompt, but I think maybe a
> status line warning would be appropriate?
That's what I said in my reply to Christian.
Best regards,
Tony.
--
--
You received this message from the "vim_dev
On Mon, Nov 16, 2015 at 12:41 PM, Christian Brabandt
wrote:
>
> So how about adding some warning into the documentation that putting from the
> same register that is used for recording won't likely work as one would
> expect and perhaps also mention in the status line which register is used for
> perhaps also mention in the status line which register is used for recording
> (e.g. instead of "recording" use "recording @a" or
+1
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
On Mon, Nov 16, 2015 at 2:33 AM, Jeff Felchner
wrote:
>
> If one is looking at weighing the benefits of allowing such a thing, and the
> downsides of allowing such a thing, I think it's pretty clear that the
> current behavior is:
>
> a) not very useful even if it's something that someone wants
