Rocco Rutte writes:
> Hi,
>
> * Lars Hecking wrote:
>
> > The subject line starts with "RC(ci): [string]". Problem is, I cannot get
> > any combination of "'\ to recognise the parentheses and square brackets
> > as non-special. E.g. nei
I'm trying to set up a save-hook to save mails with a certain subject
to a particular folder.
The subject line starts with "RC(ci): [string]". Problem is, I cannot get
any combination of "'\ to recognise the parentheses and square brackets
as non-special. E.g. neither of
save-hook '~s "RC(c
Mun Johl writes:
> Hi,
>
> I've been using w3m to render HTML messages within my mutt window for
> quite a while. My HTML mailcap entries are as follows:
>
> text/html;$HOME/bin/mutt_opera %s
> text/html; w3m -dump %s; nametemplate=%s.html; copiousoutput
>
> However, I've noticed that if I view
S?bastien Hinderer writes:
> Hi,
>
> > The email addresses in the archive have been modified to protect against
> > address harvesting. You need to sed -i 's/ at /@/g' 2008-May.txt.
>
> Okay, thanks !
> However:
>
> 1. I guess such a simple sed script works only for messages that are not
> wr
S?bastien Hinderer writes:
> Dear all,
>
> Mailman makes it possible to download archives of the lists it handels
> as gzipped text-files. Once decompressed, these files can't be read by
> mutt as found in Debian unstable, i.e. it seems that mutt does not
> recognize these files as valid mbox file
>> Yes, I'm using an external pager. It appears that there is no status line at
>> all when the internal pager is used, regardless of the pager_format setting.
>
> What are your settings for the $help and $status_on_top variables? Maybe
> it's just not where you're looking for it? :)
They are u
>> Also, the fact that the status line appears as ... () seems to indicate
>> that the %P part of "-%Z- %C/%m: %-20.20n %s%* -- (%P)" doesn't work.
>
> Umm. Reading the code there's no way %P can ever be empty in the pager (it
> can be empty in $index_format though, as both share the same code
Patrick Shanahan writes:
[...]
> not sure if you are referring to the pager view or index view, but
> they are controlled by the following entries in your ~/.muttrc or
> /etc/Muttrc (I am on a single user system and remove the /etc/Muttrc):
>
> set pager_format="%-.20n: %.40s' '-%Z- %C/%m: %-20.20
Not quite sure how to put this ...
When viewing a message in the pager, the top line looks like
- flags - sender subject -- ()
The "-- ()" bit is new in 1.5.17. Is this configured somewhere so that I
can restore the pre-1.5.17 behaviour (no "-- ()" and subject wraps to next
line)?
Lars Hecking writes:
>
> Since I upgraded to 1.5.16, I'm observing some bizarre behaviour related to
> Reply-To. The situation is similar to the one described by Derek in
> #2304. Actually, I just found this in 1.5.15 as well, so who knows when
> the change actually occur
Since I upgraded to 1.5.16, I'm observing some bizarre behaviour related to
Reply-To. The situation is similar to the one described by Derek in
#2304. Actually, I just found this in 1.5.15 as well, so who knows when
the change actually occurred.
Basically, I tried to reply to a ticketing sys
> I'm trying to figure out where in the email transmission/reception
> process the names are being stripped for me, and why. But after looking
> at my raw mbox, this is not a mutt issue.
I think the problem is that Outlook doesn't quote properly, and never has.
It purely quotes the hell out o
Lars Hecking writes:
> Mutt writes:
> > #2545: Cannot open message with pgp key attachment
> >
> > Changes (by brendan):
> >
> > * status: new => closed
> > * resolution: => worksforme
> >
> > Comment:
> >
> > Cannot
Mutt writes:
> #2545: Cannot open message with pgp key attachment
>
> Changes (by brendan):
>
> * status: new => closed
> * resolution: => worksforme
>
> Comment:
>
> Cannot reproduce; got no followup.
Sorry, must have gotten lost in the volume of mutt-dev emails.
This is still broke
> configure.patch
> might be useful in the future, enables X_CFLAGS to be recognised and
> added to CFLAGS after configure has done its tests
X_CFLAGS is already used by standard autoconf macros. It is also not
advisable to have different compiler flags at configure and compile
time as co
Paul Walker writes:
> On Mon, Mar 19, 2007 at 09:18:42PM +, Rocco Rutte wrote:
>
> > than before: When replying to f=f messages, empty lines are left empty
> > whereby an empty line is a line without further content after the quoting
> > characters.
>
> I'm not entirely certain I understand t
> It would also be nice to have mechanisms to simplify composing
> multipart/alternative e-mail.
Can you show me one single case where using multipart/alternative is
justified and actually makes any sense? It's bad enough to receive
bloated text+html email from clueless Outlook users, I don
> BTW, Lars, can you have a look at #1431 again?
Your latest comment on that is completely misquoting me.
I wrote:
| I'll take a look at the issue when I find some time (just back from holidays).
^
> What's the output of the command shown below?
>
> strings `which mutt` | awk "/mime\.types$/{sub(\"%s\",\"$HOME\");print}" |
> xargs grep -sw pdf
Empty. But of the three files, only the one in my $HOME exists.
/usr/local/etc/mime.types and /usr/local/share/mutt/mime.types don't.
That is
> file magic created mutt mime
>
> PDF v1.2 Distiller 3.01a text/plain
> PDF v1.3 5D PDFlib text/plain
> PDF v1.3 5D PDFlib application/octet-stream
> PDF v1.4 50BW-1 (Koni
Michael Tatge writes:
[...]
> Is is just this one pdf, or does it happen with all of them?
I did some systematic testing with pdfs in my account. see below.
> As a workaround you should be able to resp. .
Which is what I have resorted to doing ...
Paul Walker writes:
[...]
> Out of intere
I have a strange problem here with pdf attachemnts. Mutt 1.5.13 (2007-01-26),
i.e. cvs.
Normally, attaching a pdf file creates an attachemnt of type
application/pdf, encoding base64. But I have one particular
file that gets attached as text/plain qp. WTH?
The problem is most certainly in m
22 matches
Mail list logo
