Thomas Roessler <[EMAIL PROTECTED]>:
> > So, either there is some over-enthusiastic internationalisation
> > going on, or signing and RFC-2047-encoding are happening in the
> > wrong order.
>
> The latter. Please try the attached patch. *sigh*
That fixes it. Thanks.
Edmund
=?utf-8?Q?PGP-=C5
Hi Mikko!
> > No, I only see really new messages, and not the whole thread where the
> > new message is in :-/
>
> Oh, I misunderstood you originally. As far as I know, you can't limit
> the view to specific but full threads only. All the limits work
> per-message, not per-thread.
That is wh
Is is possible to have mail from mailing lists coloured according to a
color index recipe:
a la
color index brightmagentablack ~l # List mail
thanx
--
Eric Smith
[EMAIL PROTECTED]
00 27 21 4265311
It is easier to fix Unix than to live with NT.
On Thu, Feb 17, 2000 at 06:56:38PM +0100, Thomas Roessler wrote:
> On 2000-02-17 11:57:22 -0500, Adam Sherman wrote:
>
> > The exact same string that I have in my muttrc for signing works fine
> > on the command line. Of course, I can't use --batch or the passphrase
> > fd...
>
> You want to cre
I just switched to Mutt from Elm yesterday, and it seems to be working
fine, but I can't seem to make the color work in an SGI "winterm"
window. Any help would be greatly appreciated... I tried the normal
curses support, then tried slang, neither worked in my term windows...
Here's my "mutt -v"
Or, from the OpenBSD man pages:
The biff command appeared in 4.0BSD. biff was Heidi Stettner's dog. He
died in August 1993, at 15.
which suggests an earlier etymology than the hacker's dictionary.
--
-e
On Wed, Feb 16, 2000 at 10:12 AM, Thomas Roessler ([EMAIL PROTECTED]) typed:
>
On 2000-02-17 17:59:35 +, Edmund GRIMLEY EVANS wrote:
> So, either there is some over-enthusiastic internationalisation
> going on, or signing and RFC-2047-encoding are happening in the
> wrong order.
The latter. Please try the attached patch. *sigh*
--
http://www.guug.de/~roessler/
Ind
Is there any way to find out exactly what mutt is doing? What command
it runs and what the input and output is?
Thanks,
A.
--
Adam Sherman
<[EMAIL PROTECTED]>
+1 (613) 223-5746
PGP signature
On 2000-02-17 11:57:22 -0500, Adam Sherman wrote:
> The exact same string that I have in my muttrc for signing works fine
> on the command line. Of course, I can't use --batch or the passphrase
> fd...
You want to create ascii-armored signatures.
--
http://www.guug.de/~roessler/
Aha. I've found what's going wrong. The attached public key has these
MIME headers:
Content-Type: application/pgp-keys
Content-Description: =?utf-8?Q?PGP-=C5=9Dlosilo_0x245F71FA=2E?=
Content-Disposition: attachment
If you don't recognise =C5=9Dlosilo, it's "key" translated into
Esperanto in UTF-
On Thu, Feb 17, 2000 at 02:53:22PM +, [EMAIL PROTECTED] wrote:
:
:I sometimes need to preprocess a message I 'm about to reply
:(eg. to reformat it so that long lines fit at a particular screen width)
:
:After reading the manual and performing a search in 'comp.mail.mutt',
:I am still puzzled,
On Wed, Feb 16, 2000 at 05:40:29PM -0500, Brendan Cully wrote:
> > I have --armor in the gpg sign command... Why is this happening?
> >
> > > Content-Type: application/pgp-signature
> > > Content-Disposition: inline
> > >
> > > ?¨ávB-· ¨ø#¶Jǽ
>
> Maybe it's your key. Have you successfully
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote on Thu, 17 Feb 2000:
> I sometimes need to preprocess a message I 'm about to reply
> (eg. to reformat it so that long lines fit at a particular screen width)
>
> After reading the manual and performing a search in 'comp.mail.mutt',
> I am still puzzled
Hi all,
I sometimes need to preprocess a message I 'm about to reply
(eg. to reformat it so that long lines fit at a particular screen width)
After reading the manual and performing a search in 'comp.mail.mutt',
I am still puzzled, whether and how it could be done.
Any clues ?
Thanks in advanc
2000-02-16-16:51:43 Adam Sherman:
> I have --armor in the gpg sign command... Why is this happening?
Beats the heck out of me. I'm using mutt-1.0, which has custom
support or gpg, which works fine; for signing to work all I needed
was (in muttrc):
set pgp_default_version=gpg
set
Hi!
On Thu, Feb 17, 2000 at 03:33:58PM +0518, Vikram Vaswani wrote:
> I'm running a RH5.0 box with kernel 2.2.9. Have just downloaded mutt 1.0.1, but am
>unable to compile because of the following error:
>
> commands.c: In function `mutt_display_message':
> commands.c:131: `EPIPE' undeclared (f
Hi there!
I'm running a RH5.0 box with kernel 2.2.9. Have just downloaded mutt 1.0.1, but am
unable to compile because of the following error:
commands.c: In function `mutt_display_message':
commands.c:131: `EPIPE' undeclared (first use this function)
commands.c:131: (Each undeclared identifier
Mikko Hänninen <[EMAIL PROTECTED]>:
> Create a wrapper shell script which sets the variables and then calls
> qmail-inject (or the qmail sendmail wrapper if you prefer that). That's
> the only way to change those environment variables from the values that
> they had when Mutt started.
>
> > I t
18 matches
Mail list logo
