Re: autoconf and mutt-1.3.14

2001-02-12 Thread Lloyd Zusman
't find any documentation on the web site describing where to go to find the mutt-1.3.14i.tar.gz tarball that I was referred to here, nor explaining differences between the contents of the tarballs in the "devel" and "snapshots" directories. The "downloads" l

Re: autoconf and mutt-1.3.14

2001-02-11 Thread Lloyd Zusman
site a little better, so in the future I won't get lost again. But is there any documentation that would direct people to the "devel" directory instead of "snapshots"? But anyway, all's well that ends well. Thanks again to everyone. -- Lloyd Zusman [EMAIL PROTECTED]

Re: autoconf and mutt-1.3.14

2001-02-11 Thread Lloyd Zusman
Lars Hecking <[EMAIL PROTECTED]> writes: > Michael Tatge writes: > > Lloyd Zusman muttered: > > > I have recently downloaded the current unstable mutt release, version > > > 1.3.14. It doesn't come with a `configure' script > > > > Mine d

Re: autoconf and mutt-1.3.14

2001-02-11 Thread Lloyd Zusman
Michael Tatge <[EMAIL PROTECTED]> writes: > Lloyd Zusman muttered: > > I have recently downloaded the current unstable mutt release, version > > 1.3.14. It doesn't come with a `configure' script > > Mine does: > tar tvfz mutt-1.3.14i.tar.gz | grep co

autoconf and mutt-1.3.14

2001-02-10 Thread Lloyd Zusman
./configure: syntax error near unexpected token `AM_CONFIG_HEADER(config.h)' ./configure: ./configure: line 584: `AM_CONFIG_HEADER(config.h)' Is there a special way to run `autoconf' for mutt-1.3.14? Thanks in advance. -- Lloyd Zusman [EMAIL PROTECTED]

Something complex that I'm not sure mutt can handle.

2001-01-16 Thread Lloyd Zusman
d. Is this just too much complexity for mutt, or do you folks think that this is possible? Thanks in advance. -- Lloyd Zusman [EMAIL PROTECTED] PGP signature

Preventing CC from appearing at all when composing messages?

2000-11-26 Thread Lloyd Zusman
[ Note: I subscribed to "[EMAIL PROTECTED]", but it wouldn't let me post. So, I hope that this email address is the correct one for posting queries to the mutt users mailing list. ] Is there a way to prevent the Cc: header from appearing when composing or replying to

Problem fixed (Was: Infinite "Sign as:" loop with GPG)

2000-11-26 Thread Lloyd Zusman
Lloyd Zusman <[EMAIL PROTECTED]> writes: > [ ... ] > > I have chosen not to auto-sign (i.e., I set 'pgp_sign_as' to "" within > .muttrc), and when I type 'pa' after composing a message, I very > nicely get the "Sign as:" prompt. Ho

Infinite "Sign as:" loop with GPG.

2000-11-26 Thread Lloyd Zusman
I'm using mutt-1.2.5 with gnupg-1.0.4 under Linux 2.2.14. Within my .muttrc, I include 'gpg.rc' from the 'contrib' subdirectory in the mutt-1.2.5 source tree, and I use this without any changes. I have chosen not to auto-sign (i.e., I set 'pgp_sign_as' to "" within .muttrc), and when I type 'pa'

Preventing CC from appearing at all when composing messages?

2000-11-25 Thread Lloyd Zusman
Is there a way to prevent the Cc: header from appearing when composing or replying to messages? I know that I can use "unmy_hdr cc" to make the Cc: header show up empty, but I don't want to see this header at all. I can think of two ways to hack this: (1) Set the "editor" (and "visual"?) varia