[Top][All Lists]

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

Re: trying

From: OKUJI Yoshinori
Subject: Re: trying
Date: Tue, 24 Oct 2000 09:02:26 +0900

  Hi Jeff,

From: Jeff Sheinberg <address@hidden>
Subject: trying
Date: Mon, 23 Oct 2000 19:04:23 -0400 (EDT)

>     1. When run in batch mode, the echoing of long lines is
>     incorrect, this is probably related to the next issue.

  I intentionally ignored this, as I was tired from correctly
implementing string handling routines. If that's really annoying, I'll
fix that.

>     2. When run in interactive mode, the command editing uses a
>     truncate mode (like ksh), I find this difficult to work with,
>     I like to see the complete command that I am entering.

  As you know, the command-line interface has been switched to
single-line editing mode, for dumb terminal support. I understand what
you mean, but I don't want to work on this issue at the moment.

  When I was working on dumb terminal support, my original goal was to
manage both full-screen editing mode and single-line editing mode,
sharing most of the code, and turning on the single-line editing mode
only if the user uses a dumb terminal. But I soon realized that this
wouldn't be so easy. Thus, I had to choose either of implementing the
two features as two distinct functions, or having everyone to use only
the single-line editing mode. I concluded that the former would be
worse than the latter, since the code size of get_cmdline wasn't
negligible (>1KB), and it could be painful to maintain separate
functions for the same purpose.

  I'll revamp the interface some day, but please let me concentrate on
more critical issues.


reply via email to

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