On 11.06.2018, Bertram Scharpf wrote:
> Last week I detected that there is an option doing partially
> what I suggested since 2017, yet eight years after my
> proposal. The patch still isn't as good as mine but knowing
> that the noble people that sent me away nine years ago
> weren't right makes
On 13.03.2018, Moritz Barsnick wrote:
> That's probably why these two mails slipped though my procmail filters.
> Am I the 0.01 % still using that?
Nope. Procmail rocks :-)
> Would it be asking a lot to request an automatic "[mutt-dev] " subject
> prefix? It really makes identifying the ema
On 01.03.2017, Ulrich Lauther wrote:
> when I look at a subject line I see e.g. "Scale: Kursfeuerwerk am ersten Tag
> des neuen BM-CM-6rsensegments".
> With 1.5.24 or 1.7.1 I see "Scale: Kursfeuerwerk am ersten Tag des neuen
> Börsensegments".
> I.e., o-umlaut is displayed as "M-CM-6" since 1
On 24.01.2017, Brendan Cully wrote:
> changeset: 6909:f05df6b258f3
> user: David Champion
> date: Mon Jan 23 19:01:36 2017 -0800
> link: http://dev.mutt.org/hg/mutt/rev/f05df6b258f3
> This lets you define regular expressions-replacement pairs for subject
> display. When a Subjec
On 17.09.2016, Robin Sommer wrote:
> I'd be interested to hear if the attached patch would be suitable for
> inclusion. It adds a new option 'mark_read' that marks all messages as
> read when exiting a mailbox. If 'move' is enabled, they will then be
> moved out of the mailbox as well.
As long a
On 09.06.2015, Ian Zimmerman wrote:
> 1. What version of mutt do you use?
The latest from hg repository, as available. In other words, 1.5.23.
At the moment, mutt says it's "Mutt 1.5.23+92".
> 2. Do you use the "y" key, or the -y option when starting mutt, at all?
No.
> 3. Do you have any
On 09.06.2015, Kevin J. McCarthy wrote:
> It sounds like you have something like this set up in your muttrc:
> macro index,pager "?"
Yes, you're right, there's this one:
macro index ":exec change-folder?"
> The patch makes it unnecessary to "" at the end. If
> you hit Tab again, do yo
On 09.06.2015, Ian Zimmerman wrote:
> Press TAB where? In the browser?
When I start mutt, I'm in my inbox. From there, I'm used to press TAB
to change to my other mailboxes, and that's quite comfortable to me.
First, I want to read my personal mail, and then I'm used to have a
look at different
On 09.06.2015, Kevin J. McCarthy wrote:
> A huge concern with this patch is changing long-standing behavior.
Call me stupid, but even as a long time (~1995) mutt user, after
applying this patch, I couldn't even find my mailboxes. I'm used to
press TAB to change to my mailboxes when reading mail.
On 02.06.2015, Michael Tatge wrote:
> I cannot reproduce. Neither with imap nor local folders.
> Mutt 1.5.23 (2014-03-12)
FWIW: I can't reproduce it either. Latest -hg.
On 09.05.2015, Mutt wrote:
> Also, note that since most MUA's include such a header,
> not giving one will also give some information.
If you are concerned, you could also unset the User Agent string
("unset user_agent"), and mutt won't generate any. Even more, if it makes you
feel better, you
On 30.04.2015, Mutt wrote:
> With Snowden, we know for a fact that metadata matters, in fact
> "[http://www.nybooks.com/blogs/nyrblog/2014/may/10/we-kill-people-based-
> metadata/ We Kill People Based on Metadata]".
According to the column you cited, the relevant metadata is whom you connect
Hi,
looks like a minor thing, but anyway. Compiling mutt produces amongst others the
output below:
[]
touch stamp-doc-xml
xsltproc --nonet -o manual.html ./html.xsl manual.xml
I/O error : Attempt to load network entity
http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl
warn
On 27.03.2015, Kevin J. McCarthy wrote:
> The key doesn't appear to be usable for encryption: it only has the sign
> and certify capabilities set (the last field on the pub line).
Why would somebody want to upload a key which isn't suitable for encryption?
Weird...
Thanx for clarifying this.
Hi,
using mutt-1.5.23 or latest hg, the key linked here (*) mutt does not find it.
When composing a message and hitting (p) and (e) for encrypt, then
hitting ENTER in order to pick up the right key, it is not listed. "gpg
--list-keys"
shows it, and the same is valid for enigmail/thunderbird.
Tha
On 10.02.2015, Kevin J. McCarthy wrote:
> Would you mind trying this patch and seeing if it fixes the problem?
Bingo! This fixes the bug.
Thanks, Heinz.
Hi,
please Cc: me since I'm not subscribed to this list.
Using latest mutt from the hg repository, mutt crashes while choosing a GPG key
for encryption. Official 1.5.23 works flawlessly. Mutt says:
Looking for keys matching "x...@.xx"...Segmentation fault (core dumped)
This is what's in the
17 matches
Mail list logo
