> That said I cannot reproduce the problem on Redhat Linux with slang,
I am running RH 6.0 and I'm having this annoying problem...
Best regards,
Daniel
* Michael H. Warfield ([EMAIL PROTECTED]) wrote:
> 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 sympathiz
On 1999-09-30 21:25:37 +0100, Edmund GRIMLEY EVANS wrote:
> I suffer this annoyance with Debian 2.1's mutt, which uses slang (mutt
> -v below).
>
> I seem to remember that there are reasons for some people to prefer
> slang rather than ncurses, so, is there any way of solving the problem
> while
I found the trailing-space-cut-and-paste-annoyance mostly disappeared
when I changed my environment variable COLORFGBG from default;default
to black;16. (My background is actually white, but
COLORFGBG='black;white' gave me a light blue background. I found the
value 16 by trial and error.)
Now I c
Hmm, since we're talking about ncurses, S-Lang, and terminals, I have a
question that may be better answered by John E. Davis, the author of S-Lang,
and Thomas E. Dickey, the maintainer of ncurses (or may be not?), or by any
other developer.
I have two questions:
1- What are the differences you
Michael Jennings <[EMAIL PROTECTED]> wrote on Thu, 30 Sep 1999:
> But it's your terminal, folks, not mutt.
I don't agree. I've been using the same xterm binary for a long time,
apparently the timestamp says "Aug 4 1997". I used to get this problem
with Mutt, but I don't anymore. Unfortunately
Michael H. Warfield <[EMAIL PROTECTED]> wrote:
> 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
I do not know how to say it any other way. Neither ncurses nor slang
have any idea about the context of wh
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 x
FYI, I do not use color and use the CRT telnet application under
Windows NT. Again, here is my 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
David DeSimone <[EMAIL PROTECTED]> wrote:
>There's more to it than that, I believe. You need to also set an
>environment variable:
>
>export COLORFGBG="default;default"
>
>> (It's black lettering on a white background, which is my
>> terminal mode).
If you know e
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.
> System #1, Re
On Thu, 30 Sep 1999 18:59:45 -0500, David DeSimone <[EMAIL PROTECTED]> said:
>If Mutt is printing lots of spaces to the end of the line, why doesn't
>this cut/paste behavior always show up? Why is it only happening when
>color is enabled?
It is probably using an escape sequence (ESC[K) for t
On Thu, Sep 30, 1999 at 06:46:33PM -0500, David DeSimone wrote:
[...]
> At any rate, though, having done this, I can report that the problem
> persists. What I find is that, the spaces that are printed out to the
> right margin, now use the default color, instead of the last color used
On Thu, Sep 30, 1999 at 05:05:46PM -0700, Michael Jennings wrote:
> On Thursday, 30 September 1999, at 18:46:33 (-0500),
> David DeSimone wrote:
> > There's more to it than that, I believe. You need to also set an
> > environment variable:
> > export COLORFGBG="default;default"
> > >
On Thursday, 30 September 1999, at 18:46:33 (-0500),
David DeSimone wrote:
> There's more to it than that, I believe. You need to also set an
> environment variable:
>
> export COLORFGBG="default;default"
>
> > (It's black lettering on a white background, which is my
> >
John E. Davis <[EMAIL PROTECTED]> wrote:
>
> Maybe, or maybe not. The simple truth is that this is neither an
> ncurses, slang, nor a mutt problem. The root of the problem is with
> the terminal itself second guessing the context of what is on the
> screen. Not even the screen management softwa
Michael H. Warfield <[EMAIL PROTECTED]> wrote:
>
> > This arises the theory, that the problems will vanish if "default"
> > is used as background color (means transparent). Could someone
> > verify this?
>
> 2) If this is the option you mean, I guess I'm using default.
>
> "c
> > This arises the theory, that the problems will vanish if "default" is
> > used as background color (means transparent). Could someone verify this?
> "color normal default default# default"
> 3) I am having the problem with Mutt 1.0pre3i.
OK, then I think w
On Fri, Oct 01, 1999 at 01:02:23AM +0200, Daniel Roesen wrote:
> > The center of the problem seems to be that slang fills all lines to
> > colorize the complete line. And these fill characters are then
> > copied...
> This arises the theory, that the problems will vanish if "default" is used as
On Thu, Sep 30, 1999 at 02:05:59PM -0700, brian moore wrote:
> On Thu, Sep 30, 1999 at 12:47:45PM -0400, Daniel Eisenbud wrote:
> > On Thu, Sep 30, 1999 at 12:04:04PM -0400, Michael H. Warfield <[EMAIL PROTECTED]>
>wrote:
> > > Hello,
> > > Hmmm Just noticed a "cut and paste" annoyance th
> The center of the problem seems to be that slang fills all lines to
> colorize the complete line. And these fill characters are then
> copied...
This arises the theory, that the problems will vanish if "default" is used as
background color (means transparent). Could someone verify this?
Best
Roland Rosenfeld:
> As far as I can see this problem depends on the curses library and
> your use of colors. I just tried the following combinations:
>
> slang without any color settings -> no problems
> slang with color settings (background set to black) -> your problem
> ncurses with or withou
At 10:29 PM 9/30/99 +0200, Ollivier Robert wrote:
>According to Goran Koruga:
>> it works fine here.
>
>And I see the problem here with slang. It is very annoying. I seem to recall
>it was done in order to get the colors on the full line but still.
>
>Mutt 1.0pre2i (1999-08-31)
>Copyright (C) 1996
On Thu, Sep 30, 1999 at 12:47:45PM -0400, Daniel Eisenbud wrote:
> On Thu, Sep 30, 1999 at 12:04:04PM -0400, Michael H. Warfield <[EMAIL PROTECTED]>
>wrote:
> > Hello,
> >
> > Hmmm Just noticed a "cut and paste" annoyance that I had never
> > encounted with elm or with any other pager l
David DeSimone <[EMAIL PROTECTED]> wrote:
>That's interesting, because it does *not* work fine here.
>
>Mutt 0.96.6i (1999-08-31)
>System: HP-UX B.10.20 [using slang 9938]
>
>Perhaps that Slang upgrade that I've been putting off, would be a good
>idea... :)
Maybe, or maybe not. The simp
According to Goran Koruga:
> it works fine here.
And I see the problem here with slang. It is very annoying. I seem to recall
it was done in order to get the colors on the full line but still.
Mutt 1.0pre2i (1999-08-31)
Copyright (C) 1996-9 Michael R. Elkins and others.
Mutt comes with ABSOLUTEL
On Thu, Sep 30, 1999 at 12:47:45PM -0400, Daniel Eisenbud wrote:
> Could the people saying that this does and doesn't happen to them post
> the output of "mutt -v"?
It *does* happen for me as well.
Mutt 1.0pre3i (1999-09-25)
Copyright (C) 1996-9 Michael R. Elkins and others.
Mutt comes with AB
Goran Koruga <[EMAIL PROTECTED]> wrote:
>
> On Thu, Sep 30 1999, Michael H. Warfield wrote:
>
> it works fine here.
>
> System: HP-UX B.10.20 [using slang 10202]
That's interesting, because it does *not* work fine here.
Mutt 0.96.6i (1999-08-31)
System: HP-UX B.10.20 [using slang 9938]
On Thu, 30 Sep 1999, Michael H. Warfield wrote:
> Hmmm Just noticed a "cut and paste" annoyance that I had
> never encounted with elm or with any other pager like more or less.
> If I'm viewing a message and copy part of the message using the
> mouse cut and paste in X-Windows, I find
On Thu, Sep 30, 1999, Daniel Eisenbud wrote:
> I have a vague recollection that this may be a ncurses vs. slang issue.
> Could the people saying that this does and doesn't happen to them post
> the output of "mutt -v"? This is in general good practice when
> reporting a problem,
Mutt 1.0pre3i (1
On Thu, Sep 30 1999, Michael H. Warfield wrote:
it works fine here.
Mutt 1.0pre2i (1999-08-31)
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 condi
Daniel Eisenbud <[EMAIL PROTECTED]> wrote on Thu, 30 Sep 1999:
> > Hmmm Just noticed a "cut and paste" annoyance that I had never
> > encounted with elm or with any other pager like more or less.
I used to get this too, but I think it went away when I upgraded from
something like 0.94 to
On Thu, Sep 30, 1999 at 12:47:45PM -0400, Daniel Eisenbud wrote:
> On Thu, Sep 30, 1999 at 12:04:04PM -0400, Michael H. Warfield <[EMAIL PROTECTED]>
>wrote:
> > Hello,
> > Hmmm Just noticed a "cut and paste" annoyance that I had never
> > encounted with elm or with any other pager like
On Thu, Sep 30, 1999 at 12:04:04PM -0400, Michael H. Warfield <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Hmmm Just noticed a "cut and paste" annoyance that I had never
> encounted with elm or with any other pager like more or less. If I'm
> viewing a message and copy part of the message
On Thu, Sep 30, 1999, Michael H. Warfield wrote:
> Hmmm Just noticed a "cut and paste" annoyance that I had never
> encounted with elm or with any other pager like more or less. If I'm
> viewing a message and copy part of the message using the mouse cut and
> paste in X-Windows, I find
35 matches
Mail list logo
