[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vile] bug report - split window, unnamed file

From: Thomas Dickey
Subject: Re: [vile] bug report - split window, unnamed file
Date: Fri, 9 Jan 2015 20:28:13 -0500
User-agent: Mutt/1.5.20 (2009-06-14)

On Fri, Jan 09, 2015 at 11:51:41AM -0500, address@hidden wrote:
> Greetings.
> I found a pretty obscure bug.  It probably doesn't affect anything
> important, but I figured I'd mention it.
> vile version 9.8n for linux-gnu, installed Sun Jul  6 21:34:34 2014
> 1. Run "vile" with no file name to edit an "unnamed" buffer
> 2. Split the window with ^x 2
> 3. In the top window, type some text.  The matching text will appear in
>    the bottom window.
> 4. Issue the ":e!" command.  The system will ask "Reread current buffer?"
>    Answer "y".  It will then ask "Discard changes to [unnamed]?"
>    Answer "y".
> 5. The top window is cleared, but the bottom window is not.
> At this point, I can switch to the other window, and the cursor is placed
> on the first character of the improperly-displayed text.  I cannot edit
> the text, and any attempt to "i"nsert or "a"ppend text will erase the
> window properly.
> This does not appear to happen with a named buffer -- that is, if I
> "vile testfile" then :e! works correctly.

odd.  Offhand, the logic for the two cases should be the same.
(I'll investigate - thanks)

Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]