Re: My patch was not accepted in 2009
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 me quite satified. How about stopping complaining and submitting your code? "Here are friendly creatures, not at all evil" :-)
Re: Mailing list status
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 emails outside of the flashy > luxurious filterung Unix world (i.e. on my smartphone or in the > webmailer) so much easier! Subject tagging is... plain ugly. But I see why you would want to have it.
Re: problems with German umlauts in mutt 1.8.0
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.8.0 > The problem occurs not just in subject lines, but also in the body of > messages. I'm using both German and some of the Scandinavian languages (mostly Norwegian) a lot, and both ü, ö, ä, ø, æ and å are displayed correctly, both in the subject line and the message body.
Re: mutt: 2 new changesets
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 Subject: matches the regular expression, the replacement > value will be displayed instead in the message index. Backreferences > are supported. > This is especially nice for simplifying subjects that are overly wordy, > such as mailing list posts (with [Listname] tags, etc), mail from > ticketing systems or bug trackers, etc. It lets you reduce clutter in > your mutt display without altering the messages themselves. Thanks a lot for this one! Over more than a decade, I have been piping my email through perlscripts which did exactly that - clean up mailing list tagging and similar. Cool! :-)
Re: [PATCH] Mark messages as read when leaving mailbox
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 as this is configurable and not the default behaviour, it should be ok.
Re: [PATCH] Browse mailboxes by default when changing folders.
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 mailboxes defined with the mailboxes command in .muttrc? Yes, of course. I use the following in .muttrc to generate them dynamically, based on the content of Maildir: mailboxes ! + `\ for file in ~/Maildir/.*; do \ box=$(basename "$file"); \ if [ ! "$box" = '.' -a ! "$box" = '..' -a ! "$box" = '.customflags' \ -a ! "$box" = '.subscriptions' ]; then \ echo -n "\"+$box\" "; \ fi; \ done` -- OpenPGP Fingerprint: 531E 8E75 4395 ED38 CEC2 FD75 A1EB 6944 60F4 A92C
Re: [PATCH] Browse mailboxes by default when changing folders.
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 your mailboxes appear? Yes, they do. So it would be trivial to restore my old and well-known behaviour by just adding an additional :-) macro index ":exec change-folder?" > In any case, this is pretty quick confirmation that the patch probably > isn't a good idea. In any case, sufficient explanation will be absolutely crucial. In my opinion, most mutt users prefer mutt over any other MUA because of its simplicity and customisability (including me - my basic .muttrc is last edited in 1997 and still works as expected). I think if this patch is a *real* improvement and its potential drawbacks can easily be fixed in .muttrc, it may be worth the effort. To judge both, more people should try the patch and report back.
Re: [PATCH] Browse mailboxes by default when changing folders.
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 mailing lists. > How is having to press TAB to see the > mailboxes better than seeing them immediately, which is what the patch > is trying to do? I don't see them immediately.. > Heinz> Now, I get a directory listing > Sure, after you hit TAB unnecessarily ... In my case, it's not unnecessary, as shown above. > Heinz> and even when moving into my mail folder (I'm using maildir), > Heinz> nothing shows up. > Now _this_ is not quite stupid, but unfair. _Of course_ you have to be > in the directory containing your maildirs to see them, and not in the > maildirs themselves. Maybe I was imprecise: after entering the top level dir where my maildirs reside, I see nothing. Just to make it clear: there was a call for discussion, and that are my own experiences. Nothing more and nothing less. I'm not interested in either combatting or promoting your patch. There was raised concern about user experience, and here we go. So maybe I'm doing something wrong, pressing the wrong buttons? I don't know. -- OpenPGP Fingerprint: 531E 8E75 4395 ED38 CEC2 FD75 A1EB 6944 60F4 A92C
Re: [PATCH] Browse mailboxes by default when changing folders.
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. Now, I get a directory listing, and even when moving into my mail folder (I'm using maildir), nothing shows up.
Re: [Mutt] #3756: Toggling headers [h] duplicates header and replaces menu
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.
Re: [Mutt] #3752: default user_agent to no
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 could also fake one. Unset the mutt user agent header, and set
e.g.
my_hdr User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; rv:2.2)
Gecko/20110201
or what you prefer.
Re: [Mutt] #3752: default user_agent to no
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 to, who sends you mail and receives mail from you, as well as the frequency of mails and the location of your communication partners. The "User-Agent" header indicates the piece of software and that you're using Linux. Everybody can easily find out that, because you're posting to public mailing lists related to Linux. And most of the email sent worldwide isn't encrypted either.. > So please, let's change the default to "no". For me it doesn't matter if its "yes" or "no". And I'm surely not the one who will decide that. But does it really matter?
Compile errors
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 warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"; compilation error: file ./html.xsl line 3 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl Makefile:702: recipe for target 'manual.html' failed make[2]: [manual.html] Error 5 (ignored) rm -f Muttrc stamp-doc-rc sed -e 's,[@]docdir[@],/usr/local/share/doc/mutt,' ./Muttrc.head > Muttrc gcc -E -I. -I.. -I/usr/local/include -I.. -DSYSCONFDIR=\"/usr/local/etc\" -DBINDIR=\"/usr/local/bin\" -DHAVE_CONFIG_H=1 -I/include -I../intl -D_MAKEDOC -C \ ../init.h | ./makedoc -c >> Muttrc touch stamp-doc-rc xsltproc --nonet ./chunk.xsl manual.xml I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl"; compilation error: file ./chunk.xsl line 3 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl Makefile:705: recipe for target 'stamp-doc-chunked' failed make[2]: [stamp-doc-chunked] Error 5 (ignored) touch stamp-doc-chunked [] The docbook links are however valid and load in my browser.. Thanks, Heinz.
Re: GPG public key not shown
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.
GPG public key not shown
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. Thanks, Heinz. (*) https://pgp.mit.edu/pks/lookup?op=get&search=0x8B055AE86DEFF458
Re: Mutt/GPG crash
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.
Mutt/GPG crash
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 logs: Feb 10 20:07:10 keera kernel: [ 8156.462648] mutt[13922]: segfault at 0 ip 00454c59 sp 78ab7ea0 error 4 in mutt[40+b5000] Feb 10 20:07:10 keera kernel: mutt[13922]: segfault at 0 ip 00454c59 sp 78ab7ea0 error 4 in mutt[40+b5000] Feb 10 20:07:11 keera systemd-coredump: Process 13922 (mutt) of user 1000 dumped core. Stack trace of thread 13922: #0 0x00454c59 rfc822_parse_adrlist (mutt) #1 0x00473f8a pgp_getkeybyaddr (mutt) #2 0x00471332 pgp_findKeys (mutt) #3 0x004118ed crypt_get_keys (mutt) #4 0x0045c38b ci_send_message (mutt) #5 0x0041f363 mutt_index_menu (mutt) #6 0x0040750b main (mutt) #7 0x00351e81ffe0 __libc_start_main (libc.so.6) #8 0x00407551 _start (mutt) [htd@keera mutt]$ ./mutt -v Mutt 1.5.23+55 (2fd1b9f17b80) (2014-03-12) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 3.19.0 (x86_64) ncurses: ncurses 5.9.20140323 (compiled with 5.9) hcache backend: GDBM version 1.11. 25/12/2013 (built Aug 16 2014 16:34:31) Compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.9.2/lto-wrapper Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --enable-multilib --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --enable-plugin --enable-initfini-array --disable-libgcj --with-isl=/builddir/build/BUILD/gcc-4.9.2-20141101/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.9.2-20141101/obj-x86_64-redhat-linux/cloog-install --enable-gnu-indirect-function --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux Thread model: posix gcc version 4.9.2 20141101 (Red Hat 4.9.2-1) (GCC) Configure options: '--enable-imap' '--enable-hcache' '--with-ssl' '--with-sasl' Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL="/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" EXECSHELL="/bin/sh" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. Thanks, Heinz.
