[30] in bug-owl
long zwrite command line
daemon@ATHENA.MIT.EDU (Jeremy Daniel)
Wed Jun 26 01:00:07 2002
To: bug-owl@MIT.EDU
Cc: nim@MIT.EDU
From: Jeremy Daniel <jdaniel@MIT.EDU>
Date: 26 Jun 2002 00:59:54 -0400
Message-ID: <skefzzabpo5.fsf@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
When the zwrite command line is longer than the width of the screen
and it doesn't wrap onto a second line then the message editing part
deals poorly. This happens especially often when you reply to
messages with long instances or classes, but not when you type
normally as it adds a newline then. The bug that happens is that the
cursor ends up on line 2 of the command line, but the text being typed
appears in the blank line below it.
Type your zephyr below. End with ^D or a dot on a line by itself. ^C will quit.
----> zwrite -c this-is-a-really-long-classname-1-2-3-4-5-6-7-8-98-9-1-2-3-4-5-6
-76-7-8-8-8-9-9-0-1-2-3-4-5-6-7 # <-- cursor here
this is a really weird situation here
--------
In a bug I noticed while preparing this report. The command history will
loose spaces that are wrapped over newlines.
zwrite -c
1234567890123456789012345678901234567890123456789012345678901234567890
will become
zwrite
-c1234567890123456789012345678901234567890123456789012345678901234567890
when you go up to get it from the history
--
Jer
------------------------------------------------------------------
Tulgey Wood - tulgeywood@attbi.com Cell Phone: 617-429-8573 /
4 Farragut Ave (617-629-3983) jdaniel-phone@mit.edu
Somerville, MA 02144-1709 AIM: jdanielmit
Zephyr athena users over the web: http://webzephyr.mit.edu/
