Re: Bothersome Reply-To header
On Fri, Mar 05, 1999 at 04:11:19PM -0500, Ron Johnson wrote: > 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-To: > Test 2 > Reply-To: > Test 1 > > Each edit adds a Reply-To to the body. I hava n idea. Did you leave an empty line between the reply-to header and your text ? If not, mutt is trying to be smart and figure it out on its own. This might fail on empty headers. Try leaving a blank line between Reply-To: and you actual text. CU, Sec -- It's so nice to be insane, nobody asks you to explain.
Re: bounce! as opposed to bounce
Warning Could not process message with given Content-Type: multipart/signed; boundary=8NvZYKFJsRX2Djef; micalg=pgp-md5;protocol="application/pgp-signature"
preferred editor?...
Which editor do mutt users generally recommend for creating emails? Sender: [EMAIL PROTECTED] Precedence: bulk I would prefer something which works fairly intuitively using a PC keyboard - ie uses cursor keys, PgUp, PgDn, Home, End etc..., and use of colour would be nice. I've looked at VIM recently but can't see anything special about it. Maybe I need a specific config file for use with mutt... If anyone has such a file, could I have a copy? Many thanks, -- John
Re: 0.95.3: Characters
On Friday 05.03.1999 Tomas Calvo Gomez ([EMAIL PROTECTED]) wrote: > > Hi, I'm just joined the discussion, so maybe I'm missing something, but > this is a very important issue for me. I'm using Solaris 2.5.1 but I can't > see correctly Spanish characters. Mutt is version 0.95.1i > > I've never played with Locale values but these are by default: > LANG= > LC_CTYPE="C" > LC_NUMERIC="C" > LC_TIME="C" > LC_COLLATE="C" > LC_MONETARY="C" > LC_MESSAGES="C" > LC_ALL= > > What could be done to see those characters in the pager? > I was told to see which locales are supported by my system by typing locale -a There will appear a list of locales that are supported if the locales aren't broken. Then, you can set LC_CTYPE and LANG to a locale that supports the characters you need (for example es or es_ES or whatever was shown by locale -a). In my case, this didn't help, because my locales are broken. I had to run configure --enable-locales-fix and recompile mutt. -dirk -- D i r k F "o r s t e r l i n g [EMAIL PROTECTED] http://www.DeathsDoor.com/milliByte/ - "Was für Sie schwer ist, ist für mich leicht, und was für mich leicht ist, ist für Sie schwer." - R.K.
Xterm, Mutt, and color
What is a good Xterm to use so the color works with Mutt. The color support is nice under the Linux virtual consoles, but I work mostly in X. Thanx Jeff
Re: preferred editor?...
On Sat, 06 Mar 1999, John Poltorak wrote: > I've looked at VIM recently but can't see anything special about > it. Maybe I need a specific config file for use with mutt... If anyone > has such a file, could I have a copy? Maybe you will find here what you want: URL:http://www.math.fu-berlin.de/~guckes/setup/vimrc.gz bye - Wilhelm -- > Wilhelm Wienemann, Amselweg 10, D-47546 Kalkar/Germany < ==> E-Mail: [EMAIL PROTECTED] <=== "And since you are the future keepers of everything, including music, we hope you will keep it well, with love, and in joy." (Frederick Fennell)
Re: bounce! as opposed to bounce
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.
>
> you are probably also man enough to go into the source and edit out the
> offending prompt. :)
>
> Better yet, create a config variable for it, and submit a patch. :)
Try the attached patch: it creates a quad option for bounce.
--
David Ellement
--- commands.c.orig Tue Feb 9 12:53:38 1999
+++ commands.c Sat Mar 6 14:57:54 1999
@@ -202,7 +202,7 @@
snprintf (prompt, (COLS > sizeof(prompt) ? sizeof(prompt) : COLS) - 13,
(h ? _("Bounce message to %s") : _("Bounce messages to %s")), buf);
strcat(prompt, "...?");
- if (mutt_yesorno (prompt, 1) != 1)
+ if (query_quadoption (OPT_BOUNCE, prompt) == M_NO)
{
rfc822_free_address (&adr);
CLEARLINE (LINES-1);
--- init.h.orig Wed Feb 10 08:20:11 1999
+++ init.h Sat Mar 6 14:57:54 1999
@@ -85,6 +85,7 @@
{ "auto_tag",DT_BOOL, R_NONE, OPTAUTOTAG, 0 },
{ "beep",DT_BOOL, R_NONE, OPTBEEP, 1 },
{ "beep_new",DT_BOOL, R_NONE, OPTBEEPNEW, 0 },
+ { "bounce", DT_QUAD, R_NONE, OPT_BOUNCE, M_ASKYES },
{ "charset", DT_STR, R_NONE, UL &Charset, UL "iso-8859-1" },
{ "check_new", DT_BOOL, R_NONE, OPTCHECKNEW, 1 },
{ "collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, 1 },
--- mutt.h.orig Sun Feb 28 00:06:08 1999
+++ mutt.h Sat Mar 6 14:57:54 1999
@@ -259,7 +259,8 @@
OPT_REPLYTO,
OPT_ABORT,
OPT_RECALL,
- OPT_SUBJECT
+ OPT_SUBJECT,
+ OPT_BOUNCE
};
/* flags to ci_send_message() */
--- recvattach.c.orig Sat Jan 9 09:51:32 1999
+++ recvattach.cSat Mar 6 14:57:54 1999
@@ -670,12 +670,10 @@
static void query_bounce_attachment (int tag, BODY *top, HEADER *hdr)
{
char prompt[SHORT_STRING];
- char buf[HUGE_STRING];
+ char buf[HUGE_STRING] = { 0 };
ADDRESS *adr = NULL;
int rc;
- buf[0] = 0;
-
if(!tag)
strfcpy(prompt, _("Bounce message to: "), sizeof(prompt));
else
@@ -686,13 +684,19 @@
if (rc || !buf[0])
return;
- adr = rfc822_parse_adrlist (adr, buf);
+ if (!(adr = rfc822_parse_adrlist (adr, buf)))
+ {
+mutt_error _("Error parsing address!");
+return;
+ }
+
adr = mutt_expand_aliases (adr);
+
buf[0] = 0;
rfc822_write_address (buf, sizeof (buf), adr);
snprintf (prompt, sizeof (prompt), tag ? _("Bounce messages to %s...?")
: _("Bounce message to %s...?"), buf);
- if (mutt_yesorno (prompt, 1) != 1)
+ if (query_quadoption (OPT_BOUNCE, prompt) == M_NO)
{
rfc822_free_address (&adr);
CLEARLINE (LINES-1);
--- doc/manual.sgml.in.orig Thu Feb 11 04:41:53 1999
+++ doc/manual.sgml.in Sat Mar 6 14:57:54 1999
@@ -2586,6 +2586,13 @@
message notifying you of new mail. This is independent of the
setting of the variable.
+bounce
+
+Type: quadoption
+Default: ask-yes
+
+Controls whether you will be asked to confirm bouncing messages.
+
charset
Type: string
Re: Xterm, Mutt, and color
On Sat, Mar 06, 1999 at 16:06 (+), [EMAIL PROTECTED] wrote: > What is a good Xterm to use so the color works with Mutt. The color > support is nice under the Linux virtual consoles, but I work mostly in > X. I use rxvt, mutt compiled with slang, and make sure $COLORTERM=rxvt. Of course, YMMV. -- your man pann
Re: Xterm, Mutt, and color
At 11:06 AM EST on March 6 [EMAIL PROTECTED] sent off: > What is a good Xterm to use so the color works with Mutt. The color > support is nice under the Linux virtual consoles, but I work mostly in > X. rxvt. It even takes less memory than xterm. There are a lot of variants of rxvt out there, but rxvt is a good place to start, and you probably already have it. -- If you think the problem is bad now, just wait until we've solved it. -- Arthur Kasspe Robert I. Reid <[EMAIL PROTECTED]> http://astro.utoronto.ca/~reid/ PGP Key: http://astro.utoronto.ca/~reid/pgp.html
Re: Xterm, Mutt, and color
On Sat, Mar 06, 1999 at 04:06:15PM +, [EMAIL PROTECTED] wrote: > What is a good Xterm to use so the color works with Mutt. The color > support is nice under the Linux virtual consoles, but I work mostly in > X. > > Thanx > Jeff I have several xterm variants (xterm, color_xterm, hanterm) running in Slackware 3.3. And, all support color with mutt.
