On Thu, Sep 30, 1999 at 07:25:24PM -0700, Michael Jennings wrote:
> On Thursday, 30 September 1999, at 21:53:18 (-0400),
> Michael H. Warfield wrote:
> > Interesting... Except I'm not running eterm or rxvt.
> I can't say I sympathize with your plight much, in that case. :-)
> > I'm using xterm.
> Then you're pretty much screwed. See below.
Hmmm...
Not as badly screwed as the last time I tried eterm. See below.
> > System #1, RedHat 5.2: xterm -v => XFree86 3.3.3(88)
> > System #2, RedHat 6.0: xterm -v => XFree86 3.3.3.1b(88b)
> > Simple question... If it's the terminal and not mutt, why does
> > it only occur with mutt? I can do the same thing with vi (vim) in color
> > mode and not have the problem. I can do the same thing with cat and less
> > and more and man and not have the same problem. I never had the problem
> > with elm, but elm didn't have a color mode so that's not a point on the
> > curve after all... If it's the terminal, why is mutt different than all
> > of these others? If it's the terminal, what is mutt doing different (than
> > vim specifically since vim is using color mode just like mutt) that
> > is triggering the problem?
> > I hope that doesn't come across sounding like I'm irritated
> > 'cause I'm not. I'm just curious as to what the parameters are that
> > are causing this...
> It doesn't only occur with mutt. It will occur with any program or
> screen management library/utility which chooses to use spaces to fill
> to the end of a line rather than using the EL sequence (termcap field
> "ce", clear to end). For example, jed has the exact same behavior on
That sounds like an application error to me...
To be perfectly honest, if an application padded a line out with
spaces, I would expect to be able to cut and paste those spaces. If
an app is at the end of a line, it should indicate so without spacing
out (figuratively and literally). When you say "It will occur with any
... which chooses to use spaces to fill to the end of a line..." it occurs
to me "Ok... It sound to me like we just identified the source of the
problem and the choice was wrong." What's the downside to using the EL
sequence?
> my system. (It's interesting to note, however, that elm does not. It
> uses ncurses. So does emacs, and it doesn't have this behavior
> either.)
Uh... Mutt was compiled with ncurses on my system.
> There is nothing the terminal can do about what a given program
> chooses to use. However, it *can* determine whether to ignore those
> extraneous spaces. Eterm allows you to choose this for yourself at
> any time. No other terminal does, AFAIK.
> Is that the correct solution? I don't know, since I can't really
> speak to why SLang is choosing that route. All I'm saying is that you
Am I missing something here...
] alcove:~$ mutt -v
] Mutt 1.0pre3i (1999-09-25)
] Copyright (C) 1996-9 Michael R. Elkins and others.
] Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
] Mutt is free software, and you are welcome to redistribute it
] under certain conditions; type `mutt -vv' for details.
]
] System: Linux 2.2.12 [using ncurses 4.2]
^^^^^^^^^^^^^^^^^
That says that mutt was compiled with ncurses 4.2, not slang. Same
thing on both my RedHat 5.2 system and my RedHat 6.0 system. This isn't
something peculiar to slang or am I missinterpreting something here (like
libc6 being the same thing as glibc2).
> can use a terminal that leaves the choice to you, or you can stick
> with your current terminal and leave the choice to
> SLang/ncurses/curses. It's entirely up to you. I can't think of any
> other "solution."
> Michael
> PS: I swear I'm not trying to sound like a sales pitch here, although
> I probably am. :-)
Lost me on that one... What are you selling?
Sorry for being dense. I only switched to mutt less than a week
ago (and I'll never fire up elm again) and am still getting over some of
the minor (incredibly minor) differences that I have to retrain my fingers
for. I'm fairly new to this list and I've missed some past discussions.
BTW... I've played with eterm in the past. Didn't like it.
Too much of the eye candy got seriously in the way and I couldn't figure
out (didn't have the time to figure out) how to make it behave. On
the KISS level (at least the default KISS level) the suckage factor
was less with xterm than eterm. Like I don't WANT every terminal window
to come up with a different image unless I have explicity told it to.
> --
> "I am I am I said I'm not myself, I'm not dead, and I'm not for sale.
> So keep your bankroll lottery eat your salad day deathbed motor-
> cade." -- Stone Temple Pilots, "Trippin' on a Hole in a Paper Heart"
> =======================================================================
> Michael Jennings <[EMAIL PROTECTED]> www.tcserv.com PGP Key ID: BED09971
> Software Engineer, VA Linux Systems Author, Eterm (www.eterm.org)
Mike
--
Michael H. Warfield | (770) 985-6132 | [EMAIL PROTECTED]
(The Mad Wizard) | (770) 331-2437 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
