Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Working with MH ... not

I am having trouble with mutt and trying to use MH mailboxes. I am able to get my mail into MH format just fine, and mutt will read from those directories too. However, it is constantly telling me that I have new mail. My mailboxes line has a number of mailboxes listed, but the behavior is that

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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" > > >

Re: Cut and paste annoyance...

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 > >

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

> > 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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

> 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

Re: Cut and paste annoyance...

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

copy and paste problem - jpeg

I took part of a screen shot of the mutt pager with a block of text highlighted. . This is with using vim as a pager with tw set to 70 if it makes any difference. -Ken -- [EMAIL PROTECTED]AIM: ScopusFest

Re: Solaris segfaults on replying with mutt 1.0pre3i

On 1999-10-01 00:14:59 +0200, [EMAIL PROTECTED] wrote: > This mail is a messages which has been converted by an in-house > utility from a Lotus Notes database document, and I suspect that > some headers are missing / incorrect. Actually, the message-id header was missing. Here's a quick fix for

Re: Solaris segfaults on replying with mutt 1.0pre3i

On Thu, Sep 30, 1999 at 12:14:04PM -0500, MSCS Technician wrote: > > Hello, > >I upgraded our Solaris 7 machine from mutt 0.95.4i to mutt 1.0pre3i > following the recent security announcement. > >We've noticed that when one of our users sends a message from Solaris > 7's dtmail, I can r

Re: there is new mail in ...

Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > But it could, in theory, keep track of how many messages were in the > "new" dir when it left that folder, and if that number is the same > currently then there is no "really new" mail. As you mention, that's not a very accurate way to do it, and woul

Re: How can I ?

On Tue, Sep 28, 1999 at 01:22:37PM -0400, Fairlight wrote: > On Tue, Sep 28, 1999 at 12:04:17PM -0500, David DeSimone thus spoke: > > [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > 5) Can one convert a .PST file to unix-like(text) format ? > > > > What's a .PST file? > > Microsoft Outlook's

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: mutt in Mandrake

On Thu, Sep 30, 1999 at 10:35:57AM -0400, Michael P. Soulier wrote: > Hey guys. I just installed Mandrake 6.0, and things seem to be a little > different. Mutt, or any other mail program for that matter, doesn't have > permission to write to /var/spool/mail/ like in RedHat 5.1. Mutt [...] A

Re: Cut and paste annoyance...

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]

Re: Cut and paste annoyance...

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

Re: Solaris segfaults on replying with mutt 1.0pre3i

I'd be willing to look at a copy, or if you can just send it to mutt-dev, that would be even better. Perhaps the best thing to do would be to make a mailbox with just that message and gzip it to avoid any changes during transport, and send it as an attachement. Also, it would be helpful to see a

Re: Cut and paste annoyance...

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

Solaris segfaults on replying with mutt 1.0pre3i

Hello, I upgraded our Solaris 7 machine from mutt 0.95.4i to mutt 1.0pre3i following the recent security announcement. We've noticed that when one of our users sends a message from Solaris 7's dtmail, I can read the message in mutt, but attempts to 'r'eply wind up in a mutt segfault.

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Re: Cut and paste annoyance...

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

Cut and paste annoyance...

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 using the mouse cut and paste in X-Windows, I find that when I paste it into something else, all

Re: mutt in Mandrake

On Thu, Sep 30, 1999 at 05:11:57PM +0200, Gero Treuner wrote: > Please complain to the packager of the rpm file if his/her setup > is not correct. Reading Changelog is always a good idea, anyway. ^ Sorry, should have been NEWS , Changelog isn't nice to read. Gero

Re: mutt in Mandrake

Hi! On Thu, Sep 30, 1999 at 10:35:57AM -0400, Michael P. Soulier wrote: > Hey guys. I just installed Mandrake 6.0, and things seem to be a little > different. Mutt, or any other mail program for that matter, doesn't have > permission to write to /var/spool/mail/ like in RedHat 5.1. Mutt > o

Re: mutt in Mandrake

On Thu, Sep 30, 1999 at 10:35:57AM -0400, Michael P. Soulier wrote: > Hey guys. I just installed Mandrake 6.0, and things seem to be a little > different. Mutt, or any other mail program for that matter, doesn't have > permission to write to /var/spool/mail/ like in RedHat 5.1. Mutt > origin

mutt in Mandrake

Hey guys. I just installed Mandrake 6.0, and things seem to be a little different. Mutt, or any other mail program for that matter, doesn't have permission to write to /var/spool/mail/ like in RedHat 5.1. Mutt originally was group mail, with the group SUID bit set. I tried the same thing w

Re: segmentation fault

On Sat Sep 25 1999, peter pilsl wrote: > I was using mutt for a long time without any problems. A few days ago I > decided to upgrade to mutt1.0pre2i and now I am doomed. If this is a problem related to a new glibc, you have to recompile a few things, e.g. ncurses and slang, they have to be link

Re: there is new mail in ...

On Wed, 29 Sep 1999, Edmund GRIMLEY EVANS wrote: > I can get a duplicate X-Mailer header by editing a message that was > sent with mutt and then resending it. That's what I did. I first sent it to the list, and got a reply that my address isn't registered (because I subscribe the list on another

[1.0pre3i bug] Last access time

Mutt 1.0pre3i doesn't always set the last access time of the mailbox after I read my mail (mailbox format). The problem is that some programs say that I have new mail. -- Vincent Lefèvre <[EMAIL PROTECTED]> - PhD student in Computer Science Web: or

Re: Automating send

On Thu, Sep 30, 1999 at 10:32:35AM +0200, Eric Smith wrote: > I use vim as my editor in mutt and have mapped to save and exit. Now > is there a way to set some command in vim to save, exit and send (which 99% > of the time is what I do anyway. (Just want to save having to manually do > that f

Re: Automating send

On Thu, Sep 30, 1999 at 10:32:35AM +0200, Eric Smith thus spoke: > I use vim as my editor in mutt and have mapped to save and exit. Now > is there a way to set some command in vim to save, exit and send (which 99% > of the time is what I do anyway. (Just want to save having to manually do > tha

Automating send

I use vim as my editor in mutt and have mapped to save and exit. Now is there a way to set some command in vim to save, exit and send (which 99% of the time is what I do anyway. (Just want to save having to manually do that final "y" for sending? thanx -- Eric Smith [EMAIL PROTECTED] True w

Re: bind r to reply with include=yes and R to reply with include=no

Thanks. It works great. > (not tested). "Beware of the above code; I have only proved it correct, not tried it." - Donald Knuth Cheers, Shao. Roland Rosenfeld [[EMAIL PROTECTED]] wrote: > On Thu, 30 Sep 1999, Shao Zhang wrote: > > > Is there a way to bind the following two keys to

Re: bind r to reply with include=yes and R to reply with include=no

On Thu, 30 Sep 1999, Shao Zhang wrote: > Is there a way to bind the following two keys to behave like > this? > > bind r reply include = yes > bind R reply include = no Try the following: macro index r ":set include=yes\n" "Reply with include" macro index R ":set includ