> I don't think that was meant. What was meant (I think) was this: when
> writing some reply to a message in a thread, you want to re-read a part
> of it and possibly refer to another message ala "foo wrote this" or "bar
> wrote that".
>
> If you have the editor in a different window and mutt s
> > JUst out of curiosity, how do you compose message out of different
> > mails ? For example you reply to someone, but need to include part
> > of another mail you got the day before.
[...]
> > I'm just wondering if someone is using some trick or something
> > more user friendly.
>
> Tag the mes
[...]
> > FWIW, I've also always wanted Mutt to have a multi-paned interface,
> > not unlike most GUI mailers: one pane for the folder list, one for the
> > message index, and one to display messages.
>
> Incidentally, I wouldn't want to have that particular kind of UI for
> myself. The current
Hi,
Thanks for all your opinions. I would like to submit it for second
consideration. Unfortunately I can't set the mycrc to zero, because the
workaround does not work then :)
--
Vlad
diff -r 80bd3c060b8d hcache.c
--- a/hcache.c Mon Jun 25 03:42:41 2007 +0200
+++ b/hcache.c Mon Jun 25
> >last few days I'm getting mails containing application/octet-stream
> >attachments, even that they could have valid mime types. Up till now I
> >solved this by having octet-stream definition in ~/.mimetypes, and
> >having external script deciding on how to open file according to the
> >extension
Hi,
last few days I'm getting mails containing application/octet-stream
attachments, even that they could have valid mime types. Up till now I
solved this by having octet-stream definition in ~/.mimetypes, and
having external script deciding on how to open file according to the
extension.
Mutt ha
> > #!/bin/sh
> > vim "$@"; true
>
> This is no better than ignoring errors entirely, without even
> bothering to check to see if the file changed.
You mentioned that the file has changed. Someone else might wish to
ignore first three lines which contain message date and which is set
automaticall
[...]
> I don't think having some editor_error_code configuration list is
> substantially easier for users than
>
> #!/bin/sh
> vim "$@"; true
>
> The script approach, on the other hand, is a lot simpler for mutt.
+1
Writing shell wrappers is in unix so easy, why not just define &
document mutt
> >>>Wow, that's voodoo. I don't see any harm in making the change though.
> >>
> >>Making the variable static makes compiler to store the value to physical
> >>memory and not just to register. I can confirm that on SS12 the problem
> >
> >you'd think &mycrc would have the same effect :)
>
> It *
> > Hi, I found bug in SS11 which is triggered by mutt source. It makes
> > function crc_matches return false even if the crc is correct. This
> > virtually disables header cache.
> > unsigned int mycrc = 0;
> > to
> > static unsigned int mycrc = 0;
[...]
> Wow, that's voodoo. I don't see any ha
> > SS11 which is triggered by mutt source. It makes function crc_matches
> > return false even if the crc is correct. This virtually disables
> > header cache.
> >
> > Workaround I found is to change the definition
> >
> > unsigned int mycrc = 0;
> >
> > to
> >
> > static unsigned int mycrc =
Hi, I found bug in SS11 which is triggered by mutt source. It makes
function crc_matches return false even if the crc is correct. This
virtually disables header cache.
Workaround I found is to change the definition
unsigned int mycrc = 0;
to
static unsigned int mycrc = 0;
I don't want to file
Hi,
> [...]
> > Sometimes Mutt seems to forget marking messages as read. Most of the
> > time it works fine, but every now and then I read a newly received
> > message, close Mutt, start it again, and the message I had just read
> > still has the 'N' message flag.
>
> I could just reproduce this
The following reply was made to PR mutt/2560; it has been noted by GNATS.
From: =?iso-8859-2?Q?Vladim=EDr?= Marek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc:
Subject: Re: mutt/2560: Mutt chokes on invalid charset in UTF environment
Date: Mon, 26 Mar 2007 23:14:36 +0200
[...]
> > Sorry ab
> > > > From: =?utf-8?Q?Vladim=EDr?= Marek <[EMAIL PROTECTED]>
> > >
> > > Your locale or charset setup is misconfigured. Probably at least a
> > > bad $config_charset and a suboptimal $send_charset.
> >
> > Thanks for pointing this out, I forgot to recode .muttrc when moving to
> > utf-8 env
The following reply was made to PR mutt/2560; it has been noted by GNATS.
From: =?iso-8859-2?Q?Vladim=EDr?= Marek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc:
Subject: Re: mutt/2560: Mutt chokes on invalid charset in UTF environment
Date: Mon, 26 Mar 2007 08:35:22 +0200
[...]
> Hell! Thi
Hi,
> > From: =?utf-8?Q?Vladim=EDr?= Marek <[EMAIL PROTECTED]>
>
> Your locale or charset setup is misconfigured. Probably at least a
> bad $config_charset and a suboptimal $send_charset.
Thanks for pointing this out, I forgot to recode .muttrc when moving to
utf-8 environmnet.
--
V
17 matches
Mail list logo
