ssh and default bg color problem

2000-12-26 Thread Nathan Cullen

I currently run mutt in two different situations:
1. on my home machine (linux) in a transparent Eterm window
2. ssh-ing into my home machine from a Windows box.

When I'm home, I set all my background colors to "default" so that the
transparent Eterm effect works in X.  However, when I'm on a Windows box
and I ssh into my machine, the "default" background color causes
problems.  The "current message" bar's colors bleed into the next item
in the message index, and when viewing in the pager, the header colors
bleed into my message text.

To solve this issue, I set the background to "black" when I ssh into the
box and everything color-wise is ok.  This works because I don't need
the transparent backgrounds when I ssh in.

But now, based on where I am, I constantly have to rename my
.mutt_colors file (which is "sourced" by my .muttrc) depending on
whether I'm using ssh or whether I'm local, running under X.  This is
very frustrating.

So who's at fault?  Is it mutt for not using slang/ncurses correctly?
Is it slang/ncurses not being able to handle the default color?  Is it
my ssh client not supporting the correct terminal type?

-- 
Nathan Cullen
[EMAIL PROTECTED]




Re: Several mutt questions

1999-12-11 Thread Nathan Cullen

On Sat, Dec 11, 1999 at 03:46:03PM -0500, Richard Hakim wrote:
 - In the index of a folder, I'd like the arrow key to scroll over deleted
 messages as well.  Right now if I delete a message and then want the 
 scrollbar to go back to that message, I have to type the msg #.

Yeah, this drove me crazy as well.  Basically, you just need to bind
next-entry and previous-entry in the index.  If you use a
split-screen view (you set pager_index_lines), you'll also need to bind
the next-entry and previous-entry in the pager as well.  Here's the
entry in my .muttrc:

bind index j   next-entry
bind index k   previous-entry
bind pager j   next-entry
bind pager k   previous-entry

Just change j and k to whatever your tastes are. 

 - When I get to the end of the message, right now if I scroll down any more
 (either via space bar or arrow key or whatever) it automatically jumps me
 to the next one.  I want it to stop doing that - I often don't know that's 
 the end, so I dont' get to read the bottom (or hit the delete key).  Ideally
 

Add "set pager_stop" to your .muttrc. 

-- 
======
 Nathan Cullen [EMAIL PROTECTED]
==



Re: Dazed Confused

1999-11-27 Thread Nathan Cullen

 The primary advantage of Maildirs is that there is no need for folder
 locking, therefore you can have (in theory) an arbitrary number of
 Maildirs store each email message as a separate file, which is the
 - faster operations when operating on single messages -- no need to
 write out the entire folder like with mbox when deleting a message from
 the top, for example
 - more reliable checking of whether the folder has new mail or not
 (no need to play with file timestamps)
 - no need for locking (see discussion above)
 - much simpler to create custom tools for handling the mail that work
 on individual messages, on the other hand it's slightly more complex to
 create "mail filters" which operate on an entire folder

Okay, I'm sold. :)   But first, is there a simple way to convert my
current mbox folders(files) into maildir format?  Is this handled by
mutt or another utility?

-- 
======
 Nathan Cullen [EMAIL PROTECTED]
==



Re: flag 'A' for multiple attachments

1999-11-17 Thread Nathan Cullen

On Wed, Nov 17, 1999 at 05:42:08PM -0600, David DeSimone wrote:
 What I remember is that, as more mailbox formats were being added
 (IMAP), it became clear that Mutt couldn't always get all the
 information needed in order to display the flag.  That is, you'd have to
 pretty much scan the folder itself to determine which mails have
 attachments and which do not.  And that is expensive, over a network.
 

I use fetchmail to deliver my mail locally, and I'm certainly willing to
take a performance hit if I could have a cool feature like an attachment
flag.

Would it be possible to implement it as a variable we can set and unset?
Something like 'set attachment_flag' ?

If nobody wants to do it, I'd certainly be willing to give it a shot.

-- 
==
 Nathan Cullen [EMAIL PROTECTED]
==



Re: Alternates

1999-11-12 Thread Nathan Cullen

On Fri, Nov 12, 1999 at 01:04:55PM -0600, David DeSimone wrote:
  Why (rhetorical question) can't I do it with alternates?
  alternates dre@chronic\.net
  alternates snoop@lbc\.ca.us
 Actually, it used to be that way, but that was before Mutt really
 supported regular expressions.  Once the regexp ability was added to
 Mutt, a short survey of the then-current Mutt users showed that everyone
 thought it would be just fine to make a single regexp that matched all
 addresses.  So there you have it, the democratic process at work.  :)

The democratic process also gave us Bill Clinton. :(

Seriously though, would it be difficult to make it so that several
alternates would become a big OR'd regexp?  For example, having 
the alternates listed as they are above would be "put together" into
"(dre@chronic\.net)|(snoop@lbc\.ca.us)" ?

-- 
======
 Nathan Cullen [EMAIL PROTECTED]
==



Re: Alternates, Groups, Lists, and Work

1999-11-11 Thread Nathan Cullen

On Thu, Nov 11, 1999 at 07:52:14PM +0100, Sven Guckes wrote:
 And then I'd like to be able to have mutt show
 "/var/mail/guckes" as eg "MAILBOX" - much shorter.
 

I don't know about "MAILBOX", but I wouldn't mind seeing it replaced
with the "!" shortcut.

-- 
==
 Nathan Cullen [EMAIL PROTECTED]
==



Re: Alternates

1999-11-11 Thread Nathan Cullen

On Thu, Nov 11, 1999 at 11:33:29AM -0600, David DeSimone wrote:
 
 Well, if you do like many hackers, and try to make a "clever" regexp,
 it's probably going to be hard to read.  But there's no reason you can't
 just make a "simple" regexp that does the same thing.
 set alternates='^(fox|david|cretin)@(convex|hp).com)$"

But doesn't that seem like such a kludge?  I mean, it isn't even
"standard" with the rest of mutt.  For example, I can setup mailboxes
like:

mailboxes =drdre
mailboxes =snoopdogg
... etc etc

And the same goes for lists.

Why (rhetorical question) can't I do it with alternates?

For example:
alternates dre@chronic\.net
alternates snoop@lbc\.ca.us
... etc etc

Does that just look much cleaner?  It would still allow the use of
regexes.  Even if it meant a performance decrease in comparsion to a
carefully crafed, single regex, i'd rather use something that I can
read.

-- 
======
 Nathan Cullen [EMAIL PROTECTED]
==



Re: Auto-archiving of outgoing mail

1999-10-31 Thread Nathan Cullen

On Sat, Oct 30, 1999 at 09:37:04PM +0200, Peter Schuller wrote:
 is it possible to have mutt automatically archive sent mail in a folder? I
 sometimes need a copy of old mail I've sent, but nowadays when I'm using
 mutt I always have to come to the sad realization that I don't *have* that
 copy :)
 

Place "set record=+sent-mail" in your .muttrc.

-- 
=======
 Nathan Cullen  [EMAIL PROTECTED]
===



Regex Troubles

1999-08-19 Thread Nathan Cullen

I have the following line w/regex in my .muttrc to highlight URLs in my
messages:

color body yellow default (http|ftp)://[_a-zA-Z0-9\./~\-]+

However, when I get a url with a question mark in it, it does not work
properly.  I thought that the simple solution would be to add a \? to the
character class, producing the following regex:

color body yellow default (http|ftp)://[_a-zA-Z0-9\./~\-\?]+

This does not work.  When I run mutt with this in my .muttrc, mutt reports
the following: 

Error in /home/heat/.muttrc, line 67: Invalid range end
source: errors in /home/heat/.muttrc

Line 67, of course, refers to the line described above.  Am I missing
something obvious?  I don't quite understand what "Invalid range end" means.

Thanks for any assitance you folks can give...

-- 
=======
 Nathan Cullen  [EMAIL PROTECTED]
===



Re: Moving (not copying) messages?

1999-06-04 Thread Nathan Cullen

On Tue, Jun 01, 1999 at 04:21:16PM -0400, David Thorburn-Gundlach wrote:
 % This may seem like a stupid question, but is it possible to "move" messages
 
 Not stupid, but also not uncommon.  Perhaps this should be added to
 the manual...
 

Yeah, it (save) just doesn't seem intuitive.  I would guess that the unix
mind is very used to the mv (move) command.  Having this feature renamed, or
merely adding it to the manual would make sense.  I am a fairly new
subscriber to this list and I've already seen this question 2 or 3 times.

-- 
=======
 Nathan Cullen  [EMAIL PROTECTED]
===