Lars Hecking on Fri 5/03 12:35 +:
> > The fix would involve making `:/usr/sbin:/usr/lib' from line 1159
> > above to be the value of a variable, defined before this line, and
> > expanded in the line instead of that string itself. While I am not
> > familiar with autoconf or m4, the attached
> Either that, or Mutt thinks there's something wrong with the line just
> previous to the Reply-To header, and so it thinks that that must be the
> end of the headers, and parses the Reply-To as if it was part of the
> body. On my system, the line just above Reply-To is the Subject header.
It o
Ron Johnson <[EMAIL PROTECTED]> wrote:
>
> When I first edit the message, everything looks fine. If I return to
> the compose screen and then edit again, my original Reply-To header is
> in the body and I have a new Reply-To header in the headers. Most
> odd.
What editor are you using? Is it
Oddly, if I reply to a message the Reply-To stays in the header. The problem
only manifests itself when I compose a new message.
Cheers,
Ron
--
Ronald L. Johnson
Sr. Systems and Networks Administrator, Perl Addict
MERL - A Mitsubishi Electric Research Laboratory
http://www.merl.com
Yup, if I do multiple edits, I get multiple Reply-To headers. Here is an
example of editing, going to compose, and editing again 4 times over:
From: Ron Johnson <[EMAIL PROTECTED]>
To: Ron Johnson <[EMAIL PROTECTED]>
Cc:
Bcc:
Subject: test
Reply-To:
Reply-To:
Test 3
Reply-
Quoting David DeSimone <[EMAIL PROTECTED]>:
> What if you edit the message, return to the compose screen, then select
> edit again? Does the header move to the body of the message? If it
> doesn't, then I don't see how it could be the editor's fault.
>
> Strange, either way.
When I first edit
On Fri, Mar 05, 1999 at 02:21:07PM -0600, David DeSimone <[EMAIL PROTECTED]> wrote:
> Eric Smith <[EMAIL PROTECTED]> wrote:
> >
> > I am almost 37, all grown up now and if I press `b' that means I have
> > made my decision and am prepared to suffer the consequences.
>
> If you are man enough that
Ron Johnson <[EMAIL PROTECTED]> wrote:
>
> I think that it must be some kind of bad interaction between
> edit_headers and my editor (vim). When I edit mail everything looks
> OK and the Reply-To field is in the headers. It just seems to add a
> blank line before it is sent out.
What if you edi
Eric Smith <[EMAIL PROTECTED]> wrote:
>
> I am almost 37, all grown up now and if I press `b' that means I have
> made my decision and am prepared to suffer the consequences.
If you are man enough that you can always type the bounce-to address
correctly before you press , you're a better man than
David DeSimone <[EMAIL PROTECTED]> writes:
> This is an odd problem. Mutt normally does not insert a Reply-To header
> unless it has a value to assign the header. However, if you have
> full-header editing turned on, a blank Reply-To header will be inserted
> so that you can put something in, i
How do I force bounce a mail message so as to avoid the prompt message:
"Are you sure you want to bounce this message? (Y)es/(N)o"
I am almost 37, all grown up now and if I press `b' that means I have made
my decision and am prepared to suffer the consequences.
GTFM but got nothing (no its not a
Ron Johnson <[EMAIL PROTECTED]> wrote:
>
> I do not have a REPLYTO environment variable. I do have the reply_to
> option set in my .muttrc, but according to the doco that is just used
> for replying to listmail. I've tried unsetting it just in case, but
> that did not help.
This is an odd probl
Ollivier Robert <[EMAIL PROTECTED]> writes:
> Do you have a REPLYTO environment variable ? If yes, remove it.
I do not have a REPLYTO environment variable. I do have the reply_to
option set in my .muttrc, but according to the doco that is just used
for replying to listmail. I've tried unsettin
According to Ron Johnson:
> I've just made the switch from gnus to mutt, and so far I really like it.
> The only real problem I've seen so far is getting rid of this bothersome
> Reply-To header that is appended to my messages. It does not even seem
Do you have a REPLYTO environment variable ? I
Reply-To:
Howdy,
I've just made the switch from gnus to mutt, and so far I really like it. The only
real problem I've seen so far is getting rid of this bothersome Reply-To header that
is appended to my messages. It does not even seem to get put into the headers
correctly (as can be seen ab
On Thu, Mar 04, 1999 at 04:09:22PM +, Einar Indridason wrote:
> Yes, I was looking for an easy way within mutt to "this message will expire
> at this time in the future" without having to manually mess with the
> 'Expire: ' header. (I'm still looking :-)
Looks like another reason for havin
> The fix would involve making `:/usr/sbin:/usr/lib' from line 1159 above
> to be the value of a variable, defined before this line, and expanded in
> the line instead of that string itself. While I am not familiar with
> autoconf or m4, the attached patch for `configure.in' seems to produce a
Thomas Roessler on Wed 3/03 21:35 +0100:
> Mutt 0.95.4 is out. This version should be considered BETA.
There is a bug in the `configure' script that comes with this
distribution.
1158 IFS="${IFS= . }"; ac_save_ifs="$IFS"; IFS="${IFS}:"
1159 for ac_dir in $PATH:/usr/sbin:/usr/lib$ac_du
On Thu, Mar 04, Vikas Agnihotri wrote:
> On Wed, Mar 03, 1999 at 02:17:25PM -0600, David DeSimone wrote:
>
> > If I set $LANG to this value, Mutt is then able to display ISO-8859-1
> [...]
>
> Solaris 2.6. I have never mucked around with the $LANG or locale stuff
> either in Mutt or my .profile,
Or use Jed and get mail_mode.sl. It will reformat to standard line length
using Alt Q and has some handy functions for adding and deleting quotes from
lines and paragraphs, just read the begining of the slang file for
instructions.
Pat
--
_
Le Thu 04/03/1999, David DeSimone disait
> Vikas Agnihotri <[EMAIL PROTECTED]> wrote:
> >
> > Thats not right. If getenv("LANG") == NULL, applications are supposed
> > to deal with it by defaulting to the "C" locale or some such
> > appropriate default. Not croak and whine about it.
>
> I'm not
21 matches
Mail list logo
