Re: [PATCH 1 of 3] new exandos %r/%R to get a listing of the To: and Cc: headers

On Fri, Sep 18, 2015 at 17:22:19 -0400, Derek Schrock wrote: > + * %r = comma seperated list of To: recipients > + * %R = comma seperated list of Cc: recipients separated

Re: [PATCH 2 of 3] update docs for %r/%R

On Fri, Sep 18, 2015 at 17:22:20 -0400, Derek Schrock wrote: > +default (2015-09-18): > + + New expando %r and %R command seperated list of To: and Cc: > +recipients respectfully "separated" and "respectively". > + ** .dt %r .dd comma seperated list of ``To:'' recipients > + ** .dt %R .dd

Re: Fwd: mutt returns a 256 error code

On Tue, Oct 13, 2015 at 20:28:08 +0200, mathieu.c...@free.fr wrote: > I am currently using mutt 1.5.18 Why? mutt's release cycles are really slow, and this version is old enough to go to school, is has been seven years since its release. (Okay, I won't argue against 1.4.x here now... "Release ear

Re: mutt: Fix error message for attach-message. (closes #3785)

On Sat, Oct 17, 2015 at 14:06:42 +0200, Oswald Buddenhagen wrote: > > Fix error message for attach-message. (closes #3785) > fwiw, the use of the present tense is an unwise choice to describe a > transition (e.g., a commit). you clarify that in the next sentence, but > it's still confusing at first

Re: 1.6.0 release plans

On Sun, Nov 22, 2015 at 20:01:03 -0800, Kevin J. McCarthy wrote: > I was originally thinking about one more 1.5.x release just to give > more time, but I'm definitely open to just pushing straight for a > 1.6.0 as the next release. I'm all for this. Do it like Linux Torvalds: Just bump the versio

Re: 1.6.0 release plans

Hi, I pretty much "+1" the NNTP support. Disregarding the intrusive nature of the patch, the "similarity" (I know, not "equality") of features in and the nature of SMTP and e-mail vs. NNTP make mutt an *extremely* wise choice for me as a newsreader. NNTP not being widespread anymore would indeed be

Re: Problem with key bindings

On Thu, Jan 14, 2016 at 14:10:04 -0800, Jeffery Small wrote: > One more question: How do you exit from the :exec mode and is there > documentation available on its usage? If I use :exec what-key I get prompted with instructions: Enter keys (^G to abort): :-) Moritz

Re:

Hi Mathieu, On Thu, Feb 11, 2016 at 14:11:36 +0100, mathieu.c...@free.fr wrote: > unsubscribe Your subscription email and the header of every mail you receive contain this instruction: List-Unsubscribe: send mail to majord...@mutt.org, body only "unsubscribe mutt-dev"

Re: NeoMutt[2/4] - Bug Fixes

On Mon, Mar 07, 2016 at 19:34:55 -0600, Derek Martin wrote: > be avoided. Though, if you really need them, the C standard has > provided these two since 2008, and GLIBC, and I'd imagine BSD libc, > for probably considerably longer (though I'm too lazy to actually > look). If your system is runnin

Re: Translator string freeze tomorrow

On Fri, Mar 18, 2016 at 16:56:02 -0700, Kevin J. McCarthy wrote: > Just a reminder that tomorrow I will be generating the mutt.pot file for > the translators. Once that is done, please don't commit any changes > that modify translation strings. (At this point, all commits should be > for bug fixe

Re: Kevin McCarthy taking over as the mutt maintainer

> On behalf of the other committers and the whole mutt community, > congratulations Kevin! A big "yay!" to *both* of you. Thanks for your excellent efforts. Moritz

Re: your mail

On Wed, May 11, 2016 at 17:59:27 +0300, Egor Smolyakov wrote: > unsubscribe Nope. List-Unsubscribe: send mail to majord...@mutt.org, body only "unsubscribe mutt-dev"

Re: ncurses tinfo library

On Wed, Jun 29, 2016 at 19:09:17 +0200, Fabian Groffen wrote: > In Gentoo we've used the following patch since 1.5.22: Since ncurses doesn't provide pkgconfig support, shouldn't at least ncurses{,w}w5-config provide this info correctly in ther build environment? (Not sure whether mutt chooses not

Re: [Mutt] #3852: Problem with Compiler: section of "mutt -v" output for version 1.6.1 on Solaris

On Fri, Jul 08, 2016 at 18:15:15 -, Mutt wrote: > ) 2>&1 | ${srcdir}/txt2c.sh cc_version >conststrings_c Does the script really need to capture stderr? (But I agree - the output of the failing commands in the '||' shell chain should be omitted. As your patch does.) Moritz

Re: inconsistencies in error messages

On Fri, Nov 18, 2016 at 13:40:21 +0100, Vincent Lefevre wrote: > Moreover, sometimes "Can't" is used, sometimes "Cannot": Consistency is a good point. What's more, these messages don't differentiate between something that is impossible to do (mutt refuses to do): > browser.c:mutt_error _("Ca

Re: how to escape the edit-fcc prompt?

On Tue, Jan 03, 2017 at 13:39:02 +0100, Olaf Hering wrote: > Is the only way to escape the 'edit-fcc' prompt in the Compose menu? > If one accidently hits 'f', which allows to adjust the location of the > "Sent" folder, its not easy to undo changes. Perhaps should be > used to leave the prompt an

Re: how to escape the edit-fcc prompt?

On Sat, Jan 14, 2017 at 14:00:46 +0100, Olaf Hering wrote: > >Ctrl+G works for me, as for most prompts. > > Thanks. Should this be documented? I have not checked if it is > already in the man page. I assume its a readline feature. I realize it's not obvious, but at least it's hinted at in the ta

trac Message-ID reuse (Was: #3914: mutt stores duplicate certificates into $certificate-file on hostname mismatch and interactive_check_cert = "allow always")

For the second time recently I have noticed that trac, when generating e-mails to the list, reuses Message-IDs (and the References:). That's sort of illegal, isn't it? In this case, it was: Message-ID: <050.da24e57bea3eb6937ef6f482f8705...@mutt.org> References: <035.3631c5e28fb60e50efad023998fad..

Re: Crash after failed [C]opy

On Fri, Apr 28, 2017 at 11:25:28 -0700, Kevin J. McCarthy wrote: > I haven't been able to duplicate the segv yet, so I have a few questions > I'm hoping will help me track it down. I can reproduce with my patched 1.8.0, but not with 1.8.2, patched or vanilla. I have mbox_type=mbox, and I can repr

Warnings from pgp.c

Hi, I just checked my build of pgp.c: gcc -std=gnu99 -Wall -pedantic -Wno-long-long -g -O2 -o pgpring pgppubring.o pgplib.o lib.o extlib.o sha1.o md5.o pgppacket.o ascii.o pgp.c: In function ‘pgp_decrypt_mime’: pgp.c:1010: warning: ‘saved_length’ may be used uninitialized in this function pgp.

Re: Warnings from pgp.c

On Fri, Apr 28, 2017 at 13:08:19 -0700, Kevin J. McCarthy wrote: > In this case, the values are safe. They are initialized if need_decode > is set, and are subsequently read only under the same condition > (need_decode being set). Indeed, I missed that at first glimpse. And so did my gcc. Sorry

Re: corrupted attachments

On Mon, Jun 05, 2017 at 22:12:47 +0200, Andries E. Brouwer wrote: > [The structure of the corruption was also funny: the files were full of > NUL bytes, but these were faithfully preserved. But there were a few > sequences 15 12 (octal), that were interpreted as CR LF > and converted to LF so that

Re: Anyone have an up-to-date color-status patch?

On Thu, Sep 28, 2017 at 08:57:12 +0200, Fabian Groffen wrote: > > I was wondering if anyone has an updated color-status patch, that was > > written by Thomas Glanzmann? The version I have won't apply to mutt > > v1.9.1 . > > Do you mean this patch? > > https://sourceforge.net/p/gentoomuttpatches

Re: Anyone have an up-to-date color-status patch?

On Thu, Sep 28, 2017 at 11:03:30 +0200, Moritz Barsnick wrote: > On Thu, Sep 28, 2017 at 08:57:12 +0200, Fabian Groffen wrote: > > > I was wondering if anyone has an updated color-status patch, that was > > > written by Thomas Glanzmann? The version I have won't

Re: Nit: To view all messages, limit to "all"

On Wed, Oct 18, 2017 at 03:56:43 -0700, Claus Assmann wrote: > That message irritated me every time I started mutt with a limit > (using push '...') when there are no mails at all. > So I wrote this tiny patch for my mutt version, maybe it is > useful for others too? Just a note: The filter remain

Re: mutt: Use fgets_unlocked and fgetc_unlocked if available.

> Cuts load time for a 56k message, 1.8GB /var/mail mailbox from 14 > seconds to ~6 seconds, since we avoid acquiring and releasing a mutex > for every character of input read. Wow. Indeed, on cached mboxes, this has an extremely noticable effect for me. (For uncached ones, my old disk's I/O is st

Re: Mailing list status

On Mon, Mar 12, 2018 at 23:18:51 +0100, Eike Rathke wrote: > On the good side: there's now a > List-Id: > header one can use to filter incoming mail, additionally to > List-Post: Nice! > For who needs it, the old > Sender: owner-mutt-...@mutt.org > is now replaced by >

Re: Mailing list status

On Tue, Mar 13, 2018 at 08:57:29 +, Stuart Henderson wrote: > This has a cost: it breaks DKIM. Okay, I just read up on RFC 6377. So "-1" from myself as well. ;) Thanks, Moritz P.S.: 'L' no longer works without "subscribe". :-P

Re: Mailing list status

On Sun, Mar 18, 2018 at 09:56:12 -0700, Kevin J. McCarthy wrote: > > P.S.: 'L' no longer works without "subscribe". :-P > > This should be working still. The List-Post header is there. Is anyone > else seeing this problem? My bad. Because Stuart put me on Cc:, I only got the direct mail, and no

Re: [Mutt] #3518: IDNA2008 support by libidn2 usage in mutt

On Tue, Feb 27, 2018 at 01:56:28 -, Mutt wrote: > As it is hard (and makes less to no sense) to support IDNA2003 and > IDNA2008 in parallel, I would recommend to replace IDNA2003 by IDNA2008 > support, which means that the requirement in the end switches over from > libidn to libidn2 simply

Re: [Mutt] #3518: IDNA2008 support by libidn2 usage in mutt

On Tue, May 08, 2018 at 10:05:45 -0700, Kevin J. McCarthy wrote: > I'm not going to change the code, because we're supporting both Ah, I didn't think of checking git master, I only saw the open ticket and the patch applied in Fedora. So it already went in... > but it sounds like the checks in con

Re: [PATCH v2] Allow descending into maildir and mh directories in file browser

On Thu, Jan 31, 2019 at 12:21:19 -0600, miny...@acm.org wrote: > This change adds a function that forces mutt to > descend into the directory, and it binds it to ">" by default in > the file browser. [...] > --- [...] > Don't default the function. ">" was already in use. You need to adapt the co

Re: Building master on Fedora fails

On Sun, May 19, 2019 at 12:46:07 -0700, Kevin J. McCarthy wrote: > I've checked upstream, . The 0.8.8 > release includes docbook2texi as a perl script, and it clearly supports > the --string-param argument. If you have any more information on why > Fedora's vers

Re: meaning of number of lines in the message (%l in index_format)

On Tue, Jun 25, 2019 at 10:45:07 -0500, Derek Martin wrote: > On Tue, Jun 25, 2019 at 10:33:11AM -0500, Derek Martin wrote: > > > On Monday, 2019-06-24 18:41:56 -0500, Derek Martin wrote: > > > > Or just remove it. If it's not accurate (or even if it is) what value > > > > can it really provide? >

Re: meaning of number of lines in the message (%l in index_format)

On Tue, Jun 25, 2019 at 21:01:44 +0200, Vincent Lefevre wrote: > Note that the %c value also depends on the encoding, but this may > be less surprising. Quite obviously. It also includes PGP and S/MIME boilerplate and so on. Misleading regarding the size of the actual text, but quite clear about t

Re: Background editing

Hi Kevin, On Sun, Mar 01, 2020 at 12:36:23 -0800, Kevin J. McCarthy wrote: > Last update for this thread. I've merged the branch into master. > Testing and suggestions are most welcome. Please check out the section > in the manual: Since i

Re: mutt 1.14.0 released

On Sat, May 02, 2020 at 18:02:59 -0700, Kevin J. McCarthy wrote: > Hi Mutt Users, > > I'm pleased to announce the release of version 1.14.0. Thank you, great job! I have been using mutt for 23+ years now, and have even been dragging along some somewhat obsolete patches for 17+ years now. I'm real

Re: locking mechanism

On Sun, May 10, 2020 at 22:48:09 +0200, Vincent Lefevre wrote: > Let's recall that dotlocking [...] Haha, I still have one message in that thread from 15 years ago marked as "unread". It was one of the first threads after I subscribed to this list. I stumbled back upon it while checking since when

Re: [PATCH] Interix support in regexp.c

Hi Fabian, list, On Sat, Jul 19, 2008 at 23:59:25 +0200, Fabian Groffen wrote: > * Interix doesn't have btowc, but it does have mbtowc. Linux manpage > also discourages the use of btowc. Same on some obscure version of Solaris - SunOS 5.5.1 to be precise. It does have wide char support, but do

Re: Help needed to configure w3m as my HTML viewer

On Wed, Aug 06, 2008 at 17:58:48 +0100, Lars Hecking wrote: > w3m views the file like any other web browser. > > -dump dumps a formatted version of the page to stdout, so you lose all > hyperlinks. I use the attached lines in my ~/.mailcap to use w3m as an HTML viewer. I also have another ent

atime/mtime (Was: mutt: 5 new changesets)

On Sat, Jun 20, 2009 at 00:00:03 -0700, Brendan Cully wrote: > http://dev.mutt.org/hg/mutt/rev/9ae13dedb5ed > changeset: 5922:9ae13dedb5ed > branch: HEAD > tag: tip > user:Rocco Rutte > date:Fri Jun 19 22:49:54 2009 +0200 > summary: Fixup atime for mbox/mmdf also

Re: atime/mtime

Hi Derek, list, On Tue, Jun 23, 2009 at 11:33:59 -0500, Derek Martin wrote: > For what it's worth, the way I would most prefer to process my mail > would be like this: Thanks for this. It pretty much conforms to my work model. > nagging the user about new mail in folders they visited recently (y

Re: [PATCH] manual: fix wrong spell checker assumptions

Hi, On Sun, Aug 09, 2009 at 14:54:12 +0200, Christian Ebert wrote: > -search (humiliating of words in the pager) > +search (highlighting of words in the pager) > -underline (holing underlined patterns in the body of > messages) > +underline (highlighting underlined patterns in the body of > mess

Re: [Mutt] #3314: segfault when searching "~b something="

(Following up outside the BTS). On Fri, Aug 14, 2009 at 00:45:33 -, Mutt wrote: > (In [053ef7bbaa72]) Bail on missing pattern modifiers at end of pattern. > Closes #3314. Cool, thanks for the quick fix. So, this was not a valid search pattern? I should have used "~b somestring\="? That see

Re: Threading representation within Index

Hi, On Mon, Aug 17, 2009 at 12:08:58 -0700, Mun Johl wrote: > Here's my issue: I forward Outlook e-mails to my Linux box (IMAP/POP are > not supported--don't get me started). When Outlook does the forwarding, > it alters some of the header. How do you forward? Do you attach the email to a new em

Re: Minor documentation fix

On Sun, Feb 14, 2010 at 13:07:49 +0100, Simon Ruderich wrote: > +nthread contains new messages (only if > collapsed) > +othread contains old messagess (only if > collapsed) ^^ You introduced a new typo. Picky, Moritz

Re: Help with mutt integration

> If I correctly understand you, I need my msfech-send to be able to capture > the DATA portion of SMTP communications? > Kind of "expect" pattern? I will need to emulate that kind of behaviour? That's incorrect. Though sendmail can do SMTP, mutt's "sendmail" interface is totally different to mu

what-key (Was: [PATCH] experimental support for ncurses extended keys)

> to use ":exec what-key" to find out the octal code for a particular Hey cool. could someone _please_ tell me and document(!) how to exit the "what-key" function? This is probably the first time in years I've had to actively kill mutt! :-P Thanks, Moritz

Re: what-key (Was: [PATCH] experimental support for ncurses extended keys)

Hi me, On Tue, Apr 06, 2010 at 09:27:31 -0700, Michael Elkins wrote: > > could someone _please_ tell me and document(!) how to exit the > > "what-key" function? This is probably the first time in years I've had > It's in the initial prompt: > Enter keys (^G to abort): > You can exit most pro

Re: What about NNTP support? :)

On Mon, Apr 12, 2010 at 00:38:04 +0300, Andriy N. Gritsenko wrote: > Dear author, let's merge NNTP support into Mutt at last! I absolutely second this! I have been using the NNTP patch for more than five years now, albeit only for occasional company internal usenet, and minor other stuff. I r

mutt+NNTP: new articles are threaded incorrectly

Hi, I'm using mutt with the fabulous NNTP patch. I'm seeing a minor but annoying issue: If a new article arrives while reading a certain group (mostly happens if I write a follow-up), this article often isn't threaded correctly in thread view. It is put at the bottom of the thread with a "*>" (so

Re: [PATCH] Adequately read mailboxes with s/@/ at / obfuscations

On Tue, May 04, 2010 at 22:55:46 -0500, David Champion wrote: > Adequately read mailboxes with s/@/ at / obfuscations. > > This handles mbox From_ separators and rfc822 address parsing. Ah, nice! Just when I had dug up the "un-at-" script for being able to read some mailing lists archives. Yes,

Re: [ANNOUNCE] 1.5.21 released

On Wed, Sep 15, 2010 at 10:31:22 -0700, Brendan Cully wrote: > After much too long, I'm happy to announce the release of mutt 1.5.21, Hurray! Thanks! 1.) freshmeat.net please. 2.) an update of the NNTP patches please :-) Moritz

Re: [PATCH] Include extra information in mutt version string for developer builds

Creative nit-pick mood. :-) > +[ -d .hg ] || { cat VERSION; exit 0; } > +hg >/dev/null 2>&1 || { cat VERSION; exit 0; } { [ -d .hg ] && hg >/dev/null 2>&1 } || { cat VERSION; exit 0; } BTW, I think it's cool, if and when it works. Moritz

Re: [ANNOUNCE] 1.5.21 released

On Thu, Sep 16, 2010 at 18:50:16 +0300, Vsevolod Volkov wrote: > On Thu, Sep 16, 2010 at 05:18:01PM +0200, Moritz Barsnick wrote: > MB> 2.) an update of the NNTP patches please :-) > Done. You're a hero, VV! It works fine (as always). Building the docs gives this remark: ID rec

Re: [Mutt] #3453: mutt-1.5.18: wrap line as they can be selected with a double click

Hi Michael, Thomas, On Fri, Sep 24, 2010 at 18:37:36 -0700, Michael Elkins wrote: > However, when I view the source code in vim or with less, double clicking > *does* select the wrapped portion. I seem to recall that selecting wrapped lines in less never worked...until it started working at some

Re: [PATCH] Squelch compiler warnings

On Fri, Nov 05, 2010 at 11:28:32 +0100, Vincent Lefevre wrote: > On 2010-11-04 18:41:55 +0530, Ramkumar Ramachandra wrote: > > * Replace several 'mktemp' with safer 'mkstemp' alternative. > But there is a difference in case of error. According to the man pages, The reasoning for using mktemp vs. m

Re: Auto-complete address when sending email

This has moved into mutt-users land, by I like it here. :) On Wed, Jan 19, 2011 at 16:45:40 +0100, Luca Matteis wrote: > grep $1 > ~/.mutt/cache/bodies/imap\:lmatteis\@imap.bioversity.cgiar.org/INBOX/* | awk > -F \< '{print $2}' | awk 'NF != 0 {print}' | awk -F \> '{print $1}' |awk 'NF > !=

Re: Compatibility with Outlook threading

Hi, I understand your situation and your motivation quite well. I work in an Outlook-centric corporation too. > I've determined that Outlook disregards References and In-Reply-To > headers, and instead relies on Thread-Topic and Thread-Index headers. > Mutt doesn't preserve either of these headers

Re: [PATCH 17 of 20] folder_file: change type of new from short to int

On Fri, Jul 01, 2011 at 17:24:35 -0700, Brendan Cully wrote: > On Monday, 23 May 2011 at 14:22, Olaf Hering wrote: > > As requested by Rocco Rutte in bug #2421 increase the type to int. > > Signed-off-by: Olaf Hering > Applied, thanks. Five years later, dear Rocco leaves another mark.

Re: attaching multiple files

On Mon, Jul 09, 2012 at 03:05:00 +0200, Andries E. Brouwer wrote: > How does one tag all files? How does one tag all files fitting a pattern? Press "a" () -> "Attach file ('?' for list):" Press "?" -> Get directory browser. Press "t" for every file you find appropriate. ;-) Indeed, the and comm

Re: [PATCH RFC] Add compiler and configure info to mutt -v output

On Tue, Oct 16, 2012 at 18:14:54 -0500, David Champion wrote: > Comments? - Does this introduce a new dependency on python for building mutt? - Would the build fail mysteriously if "python txt2c.py" fails? Because of leaving an empty conststrings.c which would fulfil the make rule's requiremen

Re: mutt 1.5.20

On Tue, Feb 26, 2013 at 15:23:47 +0100, Darfeuille.Pierre wrote: > To validate the smtp I should have + USE_SMTP ? Yes, exactly. Moritz

Re: the mutt development vacuum

On Tue, Apr 09, 2013 at 18:17:28 +0200, Petr Pisar wrote: > And all of this work would be saved if mutt upstream released new > versions more frequently. That has been a recurring topic on this list, year over year. :-) Sometimes such threads, especially w.r.t. 1.6, initiate(d) a hustle to define

Re: the mutt development vacuum

On Thu, Apr 11, 2013 at 08:56:32 +0100, Andras Salamon wrote: > View -> select HTML attachment -> |elinks .muttrc: # this uses the copiousoutput mailcap entry auto_view text/html .mailrc: # no %{charset} exists text/html; w3m -T text/html -I ISO-8859-1 -o frame=0 -o meta_refresh=0 -o auto_i

Re: [PATCH] Don't exit pager if quit=ask is answered "no"

On Tue, Apr 16, 2013 at 20:12:29 -0700, Kevin J. McCarthy wrote: > This patch addresses ticket 2788. > > Currently if you quit ('Q') from inside the pager, with quit=ask-yes > or quit=ask-no, and you respond "no", mutt leaves you back in the index > menu. Nice, thanks! A long standing, even if mi

Re: From 1.5.19 onwards no option to Move read messages to mbox

On Fri, Jul 05, 2013 at 14:38:56 -0600, The Doctor wrote: > I build mutt from source. Do you also describe issues verbosely? - What did you do? - What did you expect to happen? - What happened? and in your case perhaps - Starting with which version did this begin to happen? It makes answering qu

Date (Was: [PATCH 1/5] Attach multiple files by tagging)

Hi, On Sun, Jun 18, 2006 at 22:53:40 +0200, Thomas Glanzmann wrote: > Date: Sun, 18 Jun 2006 22:53:40 +0200 Are you sure you really originally sent that email back in 2006? ;-) Moritz

Re: mutt: mutt-1.5.23 signed

> mutt-1.5.23 signed Yay! "Release early, release often." ;-) (Less than six months this time, instead of three years.) Moritz

Re: Fix buffer overrun ...

On Wed, Mar 12, 2014 at 19:36:24 -0700, Claus Assmann wrote: > > (Less than six months this time, instead of three years.) > > Thanks to a buffer overflow... Okay, let's introduce some more, if this brings us more releases. ;-) > muttlib.o(.text+0x38f8): In function `mutt_adv_mktemp': > muttlib.

Re: bug report

On Wed, Jan 07, 2015 at 15:45:25 +0100, Joel Marchand wrote: > > causes mutt to "core dumped" for the I can reproduce for group reply with an old version of mine, but not with latest hg development version. So it's either caused a patch that your version and my old version both have, or it has b

Re: 1.6 release

On Thu, Jan 15, 2015 at 11:30:50 -0800, Will Yardley wrote: > I know I've said this in the past, but nothing has happened, so just > another gentle nudge I'm glad you brought it up. :-) Brendan once started a thread on Thu, 22 Feb 2007 - and it certainly wasn't the first discussion around this

Re: [PATCH] Fix smime_encrypt_with documentation

On Tue, Feb 03, 2015 at 21:31:35 +, isdtor wrote: > Fedora is probably a bad example. True, because it has no LTS, and is sort-of bleeding edge. > I seriously doubt any Fedora users are running more than one or two > releases behind current, this is just unlike the target audience. I saw a s

Re: choices in crypt-gpgme.c

On Sun, May 10, 2015 at 21:47:07 -0500, Derek Martin wrote: > There's a discussion about this in the archives... if anyone cares to > dig it up. Probably about 10 or 11 years ago I'm guessing, but I > could be wrong. Wow, that was (slightly) before I subscribed to the list. ;-) It must be this t

Re: [Mutt] #3756: Toggling headers [h] duplicates header and replaces menu

Hi Bat_Guano, this sounds like display corruption by something in the content of that email, or its headers. Does pressing Ctrl+L clean it up? I know of other display corruptions (even in the index), but I believe it's presumed that the terminal settings are at fault.

Re: map-based hooks

On Wed, Jun 03, 2015 at 18:15:36 +1000, Cameron Simpson wrote: > On 30May2015 06:05, Xu Wang wrote: > >. > Since I can't find that message-id, could you outline what you mean here? http://thread.gmane.org/gmane.mail.mutt.devel/22216 Subject: Matching "from" matches against alternates Date: 2015-0

Re: Upcoming freeze for 2.2.0 and maintainer update

On Tue, Jan 25, 2022 at 09:32:00 -0800, Omen Wild wrote: > > I can't thank you enough for keeping mutt being the mailer that sucks less! > > This to infinity. Thank you Kevin for supporting mutt! Same here - many thanks for these eight successful years! > It is the only client I have used for ove

Re: What's needed for mutt 1.6?

Hi, On Thu, Feb 22, 2007 at 11:09:13 -0700, Kyle Wheeler wrote: > For simplicity and sanity, I really like the crypt-autoselectkey patch > (http://www.woolridge.org/mutt/crypt-autoselectkey.html). I second this one. Very practical indeed, and even annoying when missing. ;-) Moritz

Re: trial conversion from gnats to trac

> Hi all, Hi Brendan, > I've just done a trial conversion of the gnats BTS to trac: BTW, what's with the email content > Comment added by brendan on Tue, 27 Mar 2007 04:21:15 +0200 Does the system (whichever it is, it doesn't mention gnats in the header) care to tell us _what_ brendan

Re: [ANNOUNCE] mutt-1.5.15 released

On Fri, Apr 06, 2007 at 14:17:45 -0700, Brendan Cully wrote: > Mutt 1.5.15 has just been released, at: Thanks, I can finally use the new SMTP _and_ NNTP, as soon as the latter patches are updated. :) Anyone care to announce on frshmeat.net? Moritz

Building doc: manual.txt success despite missing manual.html

Hi, I just noticed a peculiar one: When building the documentation, neither lynx nor w3m bomb out on missing input files. So both lynx -dump -nolist -with_backspaces manual.html > manual.txt and w3m -dump manual.html > manual.txt have a return value of 0. Thus make succeeds, and I have an empty ma

Note re NNTP and 1.5.15

Hi, just a note to all who use the NNTP patch on 1.5.15: It seems the syntax folder-hook nntp "bla" as used in many examples found on the web doesn't work anymore. I changed this to folder-hook "^news://"; "bla" BTW, I also keep getting confused on what works and what doesn't in send-hooks vs.

Re: Note re NNTP and 1.5.15

On Tue, Apr 10, 2007 at 16:19:50 +0200, Moritz Barsnick wrote: > just a note to all who use the NNTP patch on 1.5.15: Another note on the NNTP patch, basically a bug: With SMTP support, if $smtp_url is set, an NNTP posting won't be delivered to the NNTP server: SMTP session failed: 50

Re: Note re NNTP and 1.5.15

On Wed, Apr 11, 2007 at 18:41:51 +0300, Vsevolod Volkov wrote: > Fixed: > http://mutt.org.ua/download/mutt-1.5.15/patch-1.5.15.vvv.nntp.2.gz Wow, great! I started browsing through the source code (i.e. the first patch) a little, and didn't expect such a quick response (though I did consider contac

Re: [Mutt] #2884: 256 color support

Hi, On Tue, Apr 24, 2007 at 12:13:11 -0600, Kyle Wheeler wrote: > The easiest way to do this is like so: Only "something like this", I would guess: > source $HOME/.muttrc-color-`infocmp | grep colors# | sed > 's/.*#\([0-9]\+\).*/\1'` PROMPT> infocmp | grep colors# | sed 's/.*#\([0-9]\+\

Re: Make of docs and other stuff

Hi, On Thu, May 10, 2007 at 13:52:06 +1000, Brian Salter-Duke wrote: > > On Wednesday, May 9 at 05:32 PM, quoth Brian Salter-Duke: > > This is explained in mutt/doc/devel-notes.txt. Essentially, you need > > to export some environment variables to tell it where the XML catalog > > files are. >

Re: [PATCH] when using `which` send errors to /dev/null

On Thu, May 24, 2007 at 07:57:45 +0100, David Laight wrote: > Except that &> isn't posix-compliant shell syntax (it is from csh), and > isn't supported by all shells. Except that some standard (i.e. #!/bin/sh) shells are _not_ POSIX, such as on Solaris. That was already mentioned somewhere else in

Re: mbox From_ line format over-strict expectations

Hi, On Tue, May 29, 2007 at 02:26:55 -, Mutt wrote: > 1.5.15 continues to fail on mailman/pipermail archives, like this one: > http://www.mindrot.org/pipermail/openssh-unix-dev/2004-January.txt I've had that once in a while too. I know this is a question for mutt-users, but I'll just try

Re: mbox From_ line format over-strict expectations

On Tue, May 29, 2007 at 16:54:47 +0200, Moritz Barsnick wrote: A > gzipped SPAM is attached as an example. :) Well, d'uh, it wasn't. Here goes. M. mutt.GMX_mbox.01.txt.gz Description: GNU Zip compressed data

Re: [Mutt] #2890: SMTP support: "...sending in background"

On Fri, Aug 03, 2007 at 05:42:43 -, Mutt wrote: > #2890: SMTP support: "...sending in background" > Did you ever reproduce this with vanilla mutt? I'll try at work on Monday. Thanks, Moritz

Re: UI enhancements

Hi, On Mon, Sep 03, 2007 at 10:17:43 +0200, Thomas Roessler wrote: > That mutt is starting to show its age is doubtlessly true. That its > heavy reliance on a single text terminal is quite limiting is true > as well. At the same time, there are use cases where that > limitation is actually a plu

Re: [Mutt] #2989: strsep not available on solaris

On Tue, Nov 20, 2007 at 04:19:31 -, Mutt wrote: > Commit 5307:033eba2d6834 broke Solaris build, as we don't have strsep > function. While looking around for alternative solution, I found this > reference: Wow, since when is mutt replacing missing Solaris functions? I found another one! ;-)