I've never had to worry about the order of my folder-hooks. They seem
to work regardless of where and in what order I put them in my .muttrc.
Now I'm experimenting with fcc-save-hook, save-hook, and fcc-hook, and
I'm finding that my default setting (fcc-save-hook . "...") has to be
placed after
Brian Kimball [EMAIL PROTECTED] wrote on Tue, 15 Feb 2000:
Now I'm experimenting with fcc-save-hook, save-hook, and fcc-hook, and
I'm finding that my default setting (fcc-save-hook . "...") has to be
placed after all my other fcc-hooks and save-hooks in order to get it to
work. Is this the
Mikko Hänninen [EMAIL PROTECTED] wrote:
Dave Lorand [EMAIL PROTECTED] wrote on Mon, 14 Feb 2000:
When I issue a mutt -y or mutt -Z, mutt exits silently even when I
know there is new mail in a mailbox. mutt -y in particular shouldn't
ever just exit silently, if I understand the docs
Glyn Millington [EMAIL PROTECTED]:
I'm using fetchmail to collect, have settled on procmail as delivery
agent and after much tweaking have got mail to land in
/var/spool/mail/Glyn, which is where I initially want it!
BUT
mutt consistently tells me that there is nothing there! Because of
Dave Lorand [EMAIL PROTECTED] wrote on Tue, 15 Feb 2000:
Well, there *was* a core file in my home directory, but it could have
been from KDE for all I know.
At least on my system, I can see from which program the core was left
behind with "file core". With gdb (or other debugger), it's
Well, there *was* a core file in my home directory, but it could have
been from KDE for all I know. I deleted the core file, tried mutt -y
The datestamp on the core file may give an indication which application
crashed. Also, you can often tell by checking the output of
$ strings core |
Mikko Hänninen [EMAIL PROTECTED] wrote:
Dave Lorand [EMAIL PROTECTED] wrote on Tue, 15 Feb 2000:
Well, there *was* a core file in my home directory, but it could have
been from KDE for all I know.
At least on my system, I can see from which program the core was left
behind with "file
Mikko Hänninen [EMAIL PROTECTED] wrote:
Dave Lorand [EMAIL PROTECTED] wrote on Tue, 15 Feb 2000:
Yes, with a little inconsistency with mutt -y: it jumped to the first
unread message, which happened to be one marked with an "O" - that is,
I had seen it in the listing before but hadn't
On Tue, Feb 15, 2000 at 05:53:56AM +0100, Byrial Jensen wrote:
On Tue, Feb 15, 2000 at 03:39:30 +, rex wrote:
On Tue, Feb 15, 2000 at 12:15:28AM +0100, Byrial Jensen wrote:
On Mon, Feb 14, 2000 at 15:50:42 -0600, David DeSimone wrote:
I don't remember if it is legal to put more
On Tue, Feb 15, 2000 at 01:48:02PM +0100, Reinoud Koornstra wrote:
when i mail to myself i see at the a Delivered-To: header. I set the
Delivered-To: is appended by Postfix
--
Ralf Hildebrandt [EMAIL PROTECTED] www.stahl.bau.tu-bs.de/~hildeb
I'm locked in a maze of little projects, all of
On Tue, Feb 15 2000, at 11:10 -0500, Peter Dominguez wrote:
I am using Mutt 1.1.3i (2000-02-08). In the .muttrc file I have the
line set sendmail_wait=0. When mutt starts I get the following error:
Error in /acct/peter/.muttrc, line 1001: 0: invalid value
source: errors in /acct/peter/.muttrc
Peter Dominguez [EMAIL PROTECTED] wrote on Tue, 15 Feb 2000:
Error in /acct/peter/.muttrc, line 1001: 0: invalid value
Is this a bug?
No. Try this:
set sendmail_wait=-1
Regards,
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list
Reinoud Koornstra [EMAIL PROTECTED] wrote on Tue, 15 Feb 2000:
As you can see twice an X-Mailer and a Delivered-To:
I set for X-Mailer this: Mutt, see http://www.mutt..org/
But the first X-Mailer header i didnt set and i want to get rid of that
one. Placing unmy_hdr X-Mailer: before defining
Hi!
I'm new with mutt (v1.1.3) and I have two problems I can't solve with
the documentation.
I have a mailing list with 200 and more mails per day. I keep these
messages for two month - so I have 10.000 - 15.000 mails in the mbox
file.
They are sorted by threads, that helps to keep an overview
On Tue, Feb 15, 2000 at 22:08:19 +0100, Thomas Mueller wrote:
How can I tell mutt to hide all mails that are not marked as new?
Limit to the new messages.
My other problem is that I couldn't find out how to remove the 'new'
flag from all mails. I found the 'toggle-new' command, but I don't
Jeremy Blosser [[EMAIL PROTECTED]] wrote:
The following links have been added to/updated on www.mutt.org:
...
Someone mailed me a couple weeks ago about another site in Lithuania, but I
seem to have misplaced the mail. If you're out there, please mail me
again.
Ok, there is now a mirror
Buffy and Biff were/are slang names for generic yuppie scum. Biff
is *the* original program to notify a user about mail. Xbiff is a
version for X. Xbuffy is an improved version. Buffy the vampire
slayer came along after the original yuppie scum.
HTH,
Jeffrey
Quoting Russell Hoover
[yes] replies to the first address ([EMAIL PROTECTED])
[no] replies to the second address ([EMAIL PROTECTED])
My Mutt (1.1.3) behaves differently too. Pressing "r" and "y" will
reply to both addresses, "r" and "n" to just the iberia.es address.
I'm not sure, but could this be somehow
Hi, I'm new to the list and new to mutt - and indeed to Linux
(running Mandrake 6.1 - beautiful!)
However I'm keen to get a text-based mail system up and running and
mutt seems the best option.
I'm using fetchmail to collect, have settled on procmail as delivery
agent and after much tweaking
Hello,
Glyn Millington [EMAIL PROTECTED] wrote on Tue, 15 Feb 2000:
mutt consistently tells me that there is nothing there! Because of
the "From" line with which each message begins.
Each message starts
X_From:
If I use Vim (!) to produce Fromaat the start of each message
then
Hmm, doesn`t work here. Upon launching mutt, I get the error
/home/frank/.muttrc, line 1: too few arguments
Wouldn't it be nice to do this directly, e.g. via
set limit ! ~f "Mail System Internal Data"
or is there another way to do it?
Cheers,
Frank
On Mon, Feb 14, 2000 at 01:29:26PM
On Tue, Feb 15, 2000 at 05:03:05PM +0100, Frank Joerdens wrote:
Hmm, doesn`t work here. Upon launching mutt, I get the error
/home/frank/.muttrc, line 1: too few arguments
Sorry. I could've sworn that worked when I tried it... Well, in the
past few minutes multiple tests of the following
Dave Lorand [EMAIL PROTECTED] wrote on Tue, 15 Feb 2000:
Yes, with a little inconsistency with mutt -y: it jumped to the first
unread message, which happened to be one marked with an "O" - that is,
I had seen it in the listing before but hadn't gotten around to
reading it.
I don't know about
On 2000-02-14 15:49:21 -0800, Michael Elkins wrote:
Not sure, I don't know what the motivate for having the
"subscribe" command separate from the "lists" command was.
Imagine the case that you (1) know about a list but (2) aren't
subscribed to it. Further, imagine there are discussions CCed
Hi All,
I wanted to set some header info.
All worked fine, exept some which i cant get out.
When i now mail to someone he/she will see two X-Mailer: headers, and
when i mail to myself i see at the a Delivered-To: header. I set the
hdr-order, in fact i set this from the beginning:
set hdrs
unset
I am using Mutt 1.1.3i (2000-02-08). In the .muttrc file I have the
line set sendmail_wait=0. When mutt starts I get the following error:
Error in /acct/peter/.muttrc, line 1001: 0: invalid value
source: errors in /acct/peter/.muttrc
Is this a bug?
--
Peter Dominguez
72 Belvedere Dr
Yonkers,
Not sure, I don't know what the motivate for having the "subscribe" command
separate from the "lists" command was.
Check out the archives for mutt-dev from last year November. tlr posted
an explanation why the distinction between "known" and "subscribed"
mailing lists would be useful.
On Tue, Feb 15, 2000 at 11:10:25AM -0500, Peter Dominguez wrote:
I am using Mutt 1.1.3i (2000-02-08). In the .muttrc file I have the
line set sendmail_wait=0. When mutt starts I get the following error:
Error in /acct/peter/.muttrc, line 1001: 0: invalid value
source: errors in
Thomas Mueller [EMAIL PROTECTED] wrote on Tue, 15 Feb 2000:
They are sorted by threads, that helps to keep an overview but it's
still too much. That is why I only want to see threads with new
messages! How can I tell mutt to hide all mails that are not marked as
new?
Limit to new only:
Hello,
I have a problem with mutt's insistent translating between charsets
when I view messages in Russian.
Such messages typically belong to the 'koi8-r' charset, yet there are
three types of messages:
a) With charset=iso-8859-1 incorrectely written in Content-Type: header
b) With
Anatoly Vorobey [EMAIL PROTECTED] wrote:
a) With charset=iso-8859-1 incorrectely written in Content-Type: header
b) With charset=koi8-r correctly written in Content-Type: header
Messages of type (a) are broken, and you should inform the sender that
their mail software is incorrectly
I find it very strange that kde doesn't source the .Xdefaults file for
xterm, whereas gnome does this. Is this a bug, or just some sort of
configuration that I am not seeing???
Jason Helfman [[EMAIL PROTECTED]] wrote:
I find it very strange that kde doesn't source the .Xdefaults file for
xterm, whereas gnome does this. Is this a bug, or just some sort of
configuration that I am not seeing???
Why not ask one of the kde lists. This has nothing to do with Mutt.
--
On Mon 02/14/00 at 01:20 AM -0500, Russell Hoover [EMAIL PROTECTED] wrote:
Could someone explain where or how the BUFFY_SIZE option got its name?
Still hoping for an answer here. Does no one the list know why BUFFY_SIZE
or xbuffy were given that name? Who wrote the xbuffy patch?
I mean,
From the xbuffy README:
### ### ### ### ### ### ### ### ###
XBuffy
08/20/97
Xbuffy was written by Bill Pemberton ([EMAIL PROTECTED]) and was based on
Xmultibiff by John Reardon. Xmultibiff
On Tue 02/15/00 at 10:29 PM -0500, Russell Hoover [EMAIL PROTECTED] wrote:
there isn't a DRAGON option is there?
I mean a --VAMPIRES option . . .
--
// [EMAIL PROTECTED] //
On 000215, at 22:29:25, Russell Hoover wrote:
On Mon 02/14/00 at 01:20 AM -0500, Russell Hoover [EMAIL PROTECTED] wrote:
Could someone explain where or how the BUFFY_SIZE option got its name?
Still hoping for an answer here. Does no one the list know why
BUFFY_SIZE or xbuffy were given
"Jeffrey L . Taylor" wrote:
Buffy and Biff were/are slang names for generic yuppie scum. Biff
is *the* original program to notify a user about mail.
I remember having read ("Life with Unix" by somebody Ressler?) that Biff
was a dog who lived with its owner in Berkeley (in the beginning of
38 matches
Mail list logo
