Re: Counting single inline-part "attachments"

Thanks, Kevin. I responded to the issue. In short this is indeed the only way it works presently, and I think it was the right design choice, but I don't see a problem with extending the user customization logic to allow counting content in the MIME root element. (E.g. "attachments +R image/*") *

Re: Attachments counter broken?

's fair to consider it their responsibility to know the software they're configuring. > In any case, I'll see to this for Gentoo's next release. Awesome, thanks! -- David Champion • d...@bikeshed.us

Re: Attachments counter broken?

those defaults from its Muttrc, it's breaking the functionality of the software and it's a bug. Simply defining the attachments parameters costs nothing: these are passive and not evaluated unless and until your index_format uses %X. So there's zero benefit to excluding it from the Muttrc. -- David Champion • d...@bikeshed.us

Re: mutt: Add 1.8.0 entries to the UPDATING file.

eomutt.org/feature/compress It sounds like it. I don't know what neomutt has but Roland Rosenfeld wrote this patch very long ago. -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: From vs Reply-To when replying and the address mailboxes match

ame as Vincent's description and is what the OP is asking for, but I'm trying to frame the logic in terms that make sense in documentation rather than code. -- David Champion • d...@bikeshed.us

Re: mutt: Adds the '@' pattern modifier to limit matches to known al...

the documentation moved around. I'll make a fix unless someone else does. -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: mutt: Adds the '@' pattern modifier to limit matches to known al...

* On 17 Nov 2016, Vincent Lefevre wrote: > On 2016-11-16 16:08:49 -0800, Brendan Cully wrote: > > changeset: 6857:91b3449f426b > > user: David Champion > > date: Wed Nov 16 16:05:02 2016 -0800 > > link: http://dev.mutt.org/hg/mutt/rev/91b3449f426b &g

Re: [PATCH] search muttrc file according to XDG Base Specification (closes #3207)

iles. Good improvement. Idea: for your next trick, want to make it find [/etc/]Muttrc using the same search procedure (in a different invocation with different parameters, of course)? -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: [PATCH] search muttrc file according to XDG Base Specification (closes #3207)

ght need to refactor a little if other personal config management systems want in, but we can cross that bridge when we get there. -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

[SPAM?] Re: [PATCH] setenv/unsetenv for altering process environment (to affect children)

eling on specific lines of code ad hoc. To be clear, I'm totally fine with Kevin's suggested change, and will make it. I just don't want acceptance of a single patch to depend on an open-ended discussion about mutt's preferred style or the broader issues of C string safety.

[SPAM?] Re: Mutt code style

* On 02 Sep 2016, Vincent Lefevre wrote: > On 2016-09-02 10:22:12 -0400, Damien Riegel wrote: > > On Wed, Aug 31, 2016 at 03:14:34PM -0700, David Champion wrote: > > > I suggest that we decide upon a style and a target release (1.8? 1.9?) > > > > It's not clea

[SPAM?] Mutt code style

ard-set about style conformance in patches afterward. -- David Champion • d...@bikeshed.us

[SPAM?] Re: [PATCH] Permit tab completion of pattern expressions with ~y (labels)

dn't realize that the mailing list had gotten so slow. I used to be able to count on in order arrival within a minute or two. Knowing this now I'll use patchbomb more effectively next time. -- David Champion • d...@bikeshed.us

[SPAM?] Re: [PATCH] Permit tab completion of pattern expressions with ~y (labels)

re, and I agree that we need it - which is one reason I'm trying to flush these patches out now. If they start failing to apply in any major way, it'll be another 8 years before I get them out again. (My personal preference is to tab-indent lines and space-indent continuations, so I lose either way. :) ) -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

[SPAM?] Re: [PATCH] Adds compose menu bindings for grouping and moving attachments

insertions(+), 0 deletions(-) > > > > > > # HG changeset patch > > # User David Champion > > # Date 1472600048 25200 > > # Tue Aug 30 16:34:08 2016 -0700 > > # Node ID a347a5b31a5a032d4b3753045c9fc1a73f6023f8 > > # Parent b8cc2b58219505f3d5f

[SPAM?] Re: [PATCH] When $flag_safe is set, flagged messages cannot be deleted

in the documentation. I think it's useful to describe new features in the first commit message as well. I'll note that you disagree. :) > i'll go through all the patches as time permits. it won't be a terribly > thorough review, though. Thanks. -- David Champion • d...@bikeshed.us

[SPAM?] Re: [SPAM?] some patches

* On 30 Aug 2016, David Champion wrote: > Now that we're solidly past 1.6, and since I've taken a couple of > weekends to firm up some work, I'm going to shoot out a few patches > that I've been hoarding for-- well, years. > > @Kevin, I don't mean to dump

[SPAM?] some patches

want to get these in front of mutt-dev one last time before I do. They're prioritized in approximate order of impact, relatively trivial things first. -- David Champion • d...@bikeshed.us

Re: anybody up for coding conversation view?

let above) potentially applicable to a variety of scenarios, even letting you page through an entire folder as a sequence of messages. And it give us a scope for applying actions to all messages in the conversation. More later perhaps, I just wanted to get this reaction out before I lose track. -- David Champion • d...@bikeshed.us

Re: Neomutt - Release 20160404 (Mutt-1.6.0)

cally completely replace the UI, and to implement > new mail store types. If we used console-based widgets for the UI I believe there was a discussion a while back -- maybe 10 years or so, even -- about building on the mx.c framework to make mailbox drivers more of a thing. Anyone remember th

Re: Neomutt - Release 20160404 (Mutt-1.6.0)

oject momentum. I agree completely. Personally I deeply dislike git, but I have to use it virtually everywhere except with Mutt (and my personal projects), so I could live with it. However, I still find it much easier to use than git, and I think it's very easy for a git user to adopt. -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: Neomutt - Release 20160404 (Mutt-1.6.0)

umber, or 0 in absence of current message. I think either of these is worth the work. One of mutt's unspoken principles is that leveraging macros and patterns (which are really recombinable atomic selectors) is preferable to building implicit selection into the behavior code. -- David Champion • d...@bikeshed.us

Re: Neomutt - Release 20160404 (Mutt-1.6.0)

mean we can't commit. We just need to know that it can be cleaned up. I haven't evaluated this specifically with the current code, and I don't know whether I'll get a chance, but that's my take. > > it's like tag/labels vs folders. > > Speaking of which, your keywords patch is in my in-tray. Great! There are a couple of minor issues with it but I've been using it continuously. Since it changes things somewhat with keyword handling, I've hoped for more field testing (and comments) before committing. NeoMutt can provide that. -- David Champion • d...@bikeshed.us

Re: Neomutt - Release 20160404 (Mutt-1.6.0)

atus Bar Curious how in-demand this is too. > TLS-SNI Negotiate with a Server for a Certificate +0. Seems good, but haven't reviewed. > Trash Folder Move 'deleted' emails to a trash folder Overlaps functionally with quasi-delete. I sort of like quasi deletion more - it's like tag/labels vs folders. -- David Champion • d...@bikeshed.us

Re: make build date in version string configurable?

source, incorporating any packaging-specific modifications. For example, in Debian, the timestamp of the latest entry in debian/changelog. To meet that, we need to determine whether files have been changed since the latest commit, and then capture either the latest commit

Re: [PATCH RFC 0 of 2] Complete RFC 2369 support

tribute with less entry overhead. Anyone else have remarks on this? > 5. Feel free to add a copyright line in listmenu.c (and also put > yourself in the COPYRIGHT file!) Eh, I've never been too concerned about overtly claiming copyright, but I probaby should after all this time. :) I'm travelling so it will be a little while before I can revise this, but I will. Thanks again! -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

[PATCH RFC 0 of 2] Complete RFC 2369 support

Proposed changes to more fully support RFC 2369, "The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields" -- i.e. the List-*: headers. No documentation update is included - will add when there's consensus. (I've been wanting this a long time,

[PATCH RFC 2 of 2] add list actions for remaining RFC 2369 List-* headers

# HG changeset patch # User David Champion # Date 1451647488 21600 # Fri Jan 01 05:24:48 2016 -0600 # Node ID 19d38f8f81fb41dc88e20a8295db39d953371e7a # Parent cd7be2bfff1cd15592b15adc21f44f7b50ecc312 add list actions for remaining RFC 2369 List-* headers As part of enhancing RFC 2369

[PATCH RFC 1 of 2] favor List-Reply over List-Post

# HG changeset patch # User David Champion # Date 1451647188 21600 # Fri Jan 01 05:19:48 2016 -0600 # Node ID cd7be2bfff1cd15592b15adc21f44f7b50ecc312 # Parent 9480a363a68a7472d61c8e27a29fd2312cac8721 favor List-Reply over List-Post The longstanding function originally worked only for

Re: 1.6.0 release plans

series), but if 1.6 is otherwise ready I don't want to be the reason it's not coming out. I may actually have some time to work on this in the next 5-6 weeks though. -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: Tidying the Mutt Code

existing code formatter. (I would be -0 to indent though, because there are too many incompatible variants. We can work around this with documentation, but it'll still be a PITA.) -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: Feature Request: Pattern Modifier Corresponding to Format String %F

g. > > Searching for "Derek" with the default $simple_search "~f %s | ~s %s" > returns lots and lots of messages from "Derek Martin". The default $simple_search works for me as well. -- David Champion • d...@bikeshed.us

Re: Fwd: mutt returns a 256 error code

* On 13 Oct 2015, David Champion wrote: > Hi Mathieu - > > The return from python's os.system is not the same as the exit status. > You need os.WEXITSTATUS(os.system(command)), which should be 0, or > success. I should add that you really should check other values as wel

Re: Fwd: mutt returns a 256 error code

ch should be 0, or success. 256 is not a valid exit code - these are 8-bit quantities. :) For more details, see: * pydoc os * man 2 wait -- David Champion • d...@bikeshed.us

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

iewers. If the patch update were more complex it would be more important to resend right away, but for a minor change it's pretty good to hold off. In short: update now and let us know, patchbomb later. Thanks! :) -- David Champion • d...@bikeshed.us

Re: Fwd: broken strings compiled-in into mutt

tion to a logged ticket, so was probably looking for minimal impact on the rest of the build at the time. Now that it's survived and is really part of the big picture, it makes sense to treat it like a member of the family. -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: Outlook.com issue

event. (1) Do you see resets (RST, flags -> R) while running mutt? (2) Do you see RST followed by SYN (flags -> S) while running Thunderbird? -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: Fwd: broken strings compiled-in into mutt

erstand) congruent to POSIX, so by adapting to BSD sed we should fit with all POSIX sed. I feel awful about using a GNU extension to sed when I wrote this. My code quality has dropped dramatically since I resumed developing primarily on Linux. Does the attached patch work on BSD? (Please save to

Re: Fwd: broken strings compiled-in into mutt

ich is why the C version exists; there's a C compiler by definition). 1. We can support BSD's sed for txt2c.sh. The difference is just that BSD sed only supports \n a an ascii escape. (Will need literals in the makefile.) But - 2. Why does the compiler fail? That needs to be add

Re: choices in crypt-gpgme.c

s any harm. If we keep it, it deserves a comment though. Maybe just '/* f: backward compatibility to (f)orget it; see */'. -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: null string deref in pgpkey.c

parse_adrlist call). Ugh. I'm sure you're right. I'm doing five things at once and it appears I forgot to pull from my tracking repo into my build repo. Sorry about that! -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

null string deref in pgpkey.c

I'm unable with current mutt to send PGP-encrypted mail. Mutt crashes during preparation for key selection: [669/0]$ gdb /sw/bin/mutt core.29412 GNU gdb (GDB) Amazon Linux (7.6.1-51.27.amzn1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: Can not delete attachements

y thinking: when taking action that invalidates a signature, we should change the signature to application/invalidated-pgp-signature or somesuch (and leave the signature content as-is). Then they can delete the sig if they wish. -- David Champion • d...@bikeshed.us

Re: Can not delete attachements

aybe we should allow deleting the signature itself, so that there's a two-step process for deleting any attachment? Just a passing thought, put out for discussion if anyone is interested. (In either case I think the error message is wrong and we need to change that, but I'll wait for any discussion.) -- David Champion • d...@bikeshed.us

Re: [PATCH] Fix smime_encrypt_with documentation

out then it's better to go with the more secure option. If the change sidelines a majority, then it's less appealing. But I think as Kevin pointed out aes256 is very widely supported. I think all the major server releases support it, just a question to me of popular desktop platforms (which I don't use, so...). So yes, let's push aes256 as default unless someone gives a compelling case for not doing so. -- David Champion • d...@bikeshed.us

Re: [PATCH] Fix smime_encrypt_with documentation

quot;support" fedora 12 and fedora 12's openssl doesn't have aes256, then there's a problem.) I don't think that there are any actual issues here, but that's the underlying question I think. So +0, +1 if it's certain that aes256 is pretty much universal at this point. -- David Champion • d...@bikeshed.us signature.asc Description: PGP signature

Re: Unknown Variables

ally valuable. > Thank you all for your hard work keeping this sort of project going. > I follow other open source communities, as well, and the work that all > of you do is both amazing and exciting! Thanks! -- David Champion • d...@bikeshed.us

Re: Patch to execute a command when getting new mail

* On 28 Jan 2015, Oswald Buddenhagen wrote: > On Wed, Jan 28, 2015 at 04:08:15AM -0600, David Champion wrote: > > > at first sight this doesn't look like anything that would actually need > a persistent dbus connection (e.g., to *receive* notifications), so why > don'

Re: Patch to execute a command when getting new mail

or a review and commit of my patch, then you rebase your patch onto that and resend. This is less disruptive but puts more work on you. I'm fine with either approach, I just want to make sure you get credit for and control over your work. :) My patches are not quite ready to send but unless this whole idea is roundly despised I will send soon for deeper comment. -- David Champion • d...@bikeshed.us

Re: Patch to execute a command when getting new mail

t; + /* > + ** .pp >** When this variable is \fIset\fP, mutt will beep when an error occurs. >*/ >{ "beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, 0 }, > Finally, a mention of this in the New Mail Detection section of the manual would be appropriate; just make it part of the resubitted patch. A sentence or two is fine, with a link back to the $newmail_command documentation. The source file is doc/manual.xml.head and its published form is at: http://dev.mutt.org/doc/manual.html#new-mail Thanks! -- David Champion • d...@bikeshed.us

Re: Unknown Variables

d a different packager build, or else to compile yourself from source. Add --enable-imap (--enable-pop) to the ./configure command to activate this feature set in your build. -- David Champion • d...@bikeshed.us

Re: mutt: Fix the hcache type punning warning.

* On 21 Jan 2015, Vincent Lefevre wrote: > On 2015-01-20 15:08:52 -0600, David Champion wrote: > > BE and LE may pack structs differently, but I believe members of a > > union should have the same alignment even if of differing size. This > > should be safe for byte transpo

Re: mutt: Fix the hcache type punning warning.

different end of the char[] to transpose into the int on BE vs LE systems, but that's OK within the same CPU so long as the hash algorithm is fairly well distributed across the 16 bytes. -- David Champion • d...@bikeshed.us

Re: [Mutt] #3727: Allow selection of multitple GPG-keys to encrypt to

e sense. Folder-hook, crypt-hook, account-hook, message-hook, reply-hook, send-hook, send2-hook at least. -- David Champion • d...@bikeshed.us

Re: bug report

lid but it should not crash. (A strict parser should turn this into an empty address because the : in the address makes it a group label rather than an "addr-spec", but it's not completely valid because there's no ; at the end.) Current mutt handles this by ignoring the add

Re: Mutt code indentation style?

's code uses 2-space indents, but 8 spaces become a tab. (This is a traditional emacsism.) -- David Champion • d...@bikeshed.us

Re: Mutt code indentation style?

I'd like to see what indent.pro someone can invent -- or a config for some other code-prettifying tool -- that results in a small changeset against the current code. Or in other words: there's an indent.pro for the standard we say we follow. But what config or tool describes th

Re: Mutt code indentation style?

* On 11 Sep 2014, Óscar Pereira wrote: > On Wed, Sep 10, 2014 at 12:32:04PM -0500, David Champion wrote: > >>>So I guess the question is... does someone still care about code > >>>indentation, or is it just the page [1] that is hopelessly outdated? > > > >

Re: Mutt code indentation style?

nge it. If we do so it should be a distinct decision, and should have its own isolated commit. Unrelated changes should not be mixed together if avoidable. I think I've seen an indent.pro for mutt's coding style somewhere, but I can't find it now. Anyone know? It might be a

Re: PGP format command %a for pgp_encrypt_only_command

ches being committed! Philip - thanks for testing! Kevin - I don't see any harm in this. I'm willing to push the patch you sent, but do you want to expand it to cover other operations as well? -- David Champion • d...@bikeshed.us pgpQnqhtr_1ry.pgp Description: PGP signature

Re: DEBUG by default - Yes or No?

ebug -d2 for debugging runs. On my system a stripped mutt exec with most options enabled is under 900K. -- David Champion • d...@bikeshed.us

Re: OT: question concerning hg rebase and mq patches

amp;& hg pull -u && hg qpush -a qpr = ! hg qpush && hg qrefresh So I run 'hg qup' to begin, and if an error is encountered during a patch push, it breaks. Then I fix, qrefresh, and qpush -a again. ("hg qpr" is just something related to this procedure that's sometimes useful.) -- David Champion • d...@bikeshed.us

[PATCH r2] unbind patch

# HG changeset patch # User David Champion # Date 1385592820 21600 # Wed Nov 27 16:53:40 2013 -0600 # Node ID 3cca2c103f2abdaa2d711b11b27bc18e782c9fd4 # Parent 3306cb186f49e83edf15aac91c51f4c6131ef8fe add `unbind' and `unmacro' commands This is a refresh and update of a very

Re: [PATCH 1 of 1] add `unbind' and `unmacro' commands

> > +} > > +if (neededitorbindings == 2) > > + create_bindings (OpEditor, MENU_EDITOR); > > Why do we only restore the bindings when needitorbindings == 2? > Should we restore them if we do "unbind editor *"? You're right, I suspec

[PATCH 0 of 1] unbind patch

The wish for an unbind command is at least 12 years old -- I first noticed it in 2001. There's been recurrent discussion on what the right approach is, and despite having written the standard(?) unbind patch using the standard bind-to-noop approach, I think there's merit to the argument that a tru

[PATCH 1 of 1] add `unbind' and `unmacro' commands

# HG changeset patch # User David Champion # Date 1385592820 21600 # Wed Nov 27 16:53:40 2013 -0600 # Node ID 44c56715ef8bb953bfda7a271a2c0544b55941cc # Parent 3306cb186f49e83edf15aac91c51f4c6131ef8fe add `unbind' and `unmacro' commands This is a refresh and update of a very

Re: [IMPORTANT] changes to the Mutt repository

Alternatively you could use a local tag for this purpose: $ hg up -C tip $ hg tag -l mybase $ hg pull -u $ hg --config extensions.rebase= rebase -b mybase -d default Using a local tag is a touch longer, but less sensitive to working directory state. It's also possible to accomplish

Re: [PATCH] Allow filename prompt when saving multiple attachments to a directory. (closes #3083)

get_field (_("File under directory: "), tmp, sizeof (tmp), > +M_FILE | M_CLEAR) != 0 || !tmp[0]) > + return (-1); > +mutt_concat_path (fname, path, tmp, flen); >} > >if (*append == 0 && access (fname, F_OK) ==

Re: [PATCH] Fix postpone/resume to not remove a Mail-Followup-To header

> +FREE (&newhdr->env->message_id); > +FREE (&newhdr->env->mail_followup_to); > + } > >/* decrypt pgp/mime encoded messages */ > >if ((WithCrypto & (APPLICATION_PGP|APPLICATION_SMIME) & hdr->security) >&& mutt_is

Re: [PATCH 0 of 6] Add crypt_opportunistic_encrypt option

.c | 30 +++- > mutt_crypt.h | 10 +++- > send.c|2 +- > compose.c | 17 +++ > init.h|8 +++ > mutt.h|1 + > send.c|8 +++- > 43 files changed, 307 insertions(+), 239 deletions(-) -- David Champion • d...@bikeshed.us

Re: [Mutt] #3660: Expose RFC 3464 functionality unavailable through sendmail(1)

ct the user to configure > support for this? Agreed, however: the 3464 extensions are primarily server-to-server. Can the OP describe applicability to an SMTP client that does not have retry/spooling capability? -- David Champion • d...@bikeshed.us

Re: The future of mutt...

* On 02 Oct 2013, Alexander Gattin wrote: > On Wed, Oct 02, 2013 at 03:58:25AM -0500, David > Champion wrote: > > Lacking a regular contibutor who expresses > > interest in joining the leadership team, it's > > premature to discuss a handoff of project > > leade

Re: The future of mutt...

distinct Mercurial revisions where possible; 2. fully engaging in the cycle of review and revision; 3. developing patches in a manner that makes patch review easier. Further, we encourage review from non-committing members of the community -- but we need to be careful about diverging into long, abstract discussions during the review itself. That consumes our limited resource, time. -- David Champion • d...@bikeshed.us

Re: the mutt development vacuum

t-1-5-17-rel 120 changesets between mutt-1-5-17-rel and mutt-1-5-18-rel 274 changesets between mutt-1-5-18-rel and mutt-1-5-19-rel 234 changesets between mutt-1-5-19-rel and mutt-1-5-20-rel 260 changesets between mutt-1-5-20-rel and mutt-1-5-21-rel 152 changesets between mutt-1-5-21-rel and tip -- David Champion • d...@bikeshed.us

Re: the mutt development vacuum

haps with a target in the makefile: "make pretty". Indent is probably too variable for this; there are at least three incompatible versions. I've used uncrustify, but would be open to anything portable, well-versioned, and unforked. -- David Champion • d...@bikeshed.us

Re: the mutt development vacuum

; than by forking. He never made that effort, to my knowledge. Indeed I don't believe he's ever posted to this list. To me, that offsets any reasons for the fork, leaving zero. -- David Champion • d...@bikeshed.us

Re: [PATCH] Add support for changing X-Label

y patch even lets you tab-complete against any existing label. -- David Champion • d...@bikeshed.us

Re: [PATCH] Add support for changing X-Label

, Vincent Lefevre wrote: > I'd like to be able to execute a script (this can be an option) for > changing X-Label, e.g. if the string starts with the | character > (or have a different function for that). The script could take the > current X-Label value an input and output the new value. -- David Champion • d...@bikeshed.us

Re: [PATCH] Add support for changing X-Label

the past, but I hope that with the added capabilities, it appears as a more integrated subsystem than as a tack-on feature. Barring any overt objections from the team, I will push this. I would like more bug testing, but I guess it's high time to just do it and let the bugs sort themsel

Re: [PATCH] Add support for changing X-Label

x27;s any gap between the patch sequence at that URL and your code, and you want to produce a patch based on my patch sequence to bring them even, I'd be interested in including your changes (properly tagged as yours, of course). Of course I still would like feedback on the patch sequence's in general from anyone reading this. :) -- David Champion • d...@bikeshed.us

Re: embedded Perl vs Python vs Lua vs Tcl

on the table. A few of us have rated our preferences for the greater benefit of the group, but that's not governing. Personally it would be hard to sell me on anything besides python and lua, but until someone is willing to implement something, this is academic. -- David Champion • d...@bikeshed.us

Re: Lua vis-a-vis Python

s I've seen argued. I'm sure there are others where lua is a clear winner; my point is that you take these arguments case by case, not by principle. -- David Champion • d...@uchicago.edu • University of Chicago

Re: Mutt and scripting

one working scripting now, but it seems like a > worthwile project :) FWIW: +1 python, +0 lua, -1 guile -- David Champion • d...@bikeshed.us

Re: Subjectrx patch

* On 07 Jan 2013, Marco wrote: > Will the subjectrx patch provided by David Champion (see post from > Fri, 14 Dec 2012 15:48:30 -0800) make it into the next version? It needs some tweaking, but I will commit it when I can. We have no hard release date for 1.6 so I can't answer firm

Re: [PATCH] Add compiler and configure info to mutt -v output (closes #3537)

* On 24 Dec 2012, Fabian Groffen wrote: > On 18-10-2012 15:12:21 -0500, David Champion wrote: > > +conststrings.c: txt2c config.status > > + ( \ > > + $${CC-cc} --version || \ > > + $${CC-cc} -v || \ > > + $${CC-cc} -V || \ >

Re: [PATCH 4/4] version.sh: Get detailed version info from git

* On 15 Dec 2012, Oswald Buddenhagen wrote: > On Fri, Dec 14, 2012 at 06:10:21PM -0600, David Champion wrote: > > [...] note that the ${a#b} and ${a%b} family of parameter expressions > > is nonportable. These are commonly accepted bashisms [...] > > > wrong. >

Re: [PATCH 4/4] version.sh: Get detailed version info from git

* On 14 Dec 2012, Aaron Schrab wrote: > At 18:10 -0600 14 Dec 2012, David Champion wrote: > >This is good to add support for, but note that the ${a#b} and ${a%b} > >family of parameter expressions is nonportable. These are commonly > >accepted bashisms that also work in

Re: [PATCH 2/4] Generate version string during make not configure

PHONY'; thus `FORCE' appears in > many makefiles. That's good. If mutt still supports non-GNU makes we should leave it that way. Building from CVS (hg) has required GNU for so long I no longer think of as optional. :/ -- David Champion • d...@bikeshed.us

Re: [PATCH 4/4] version.sh: Get detailed version info from git

uot; > + exit 0 > +fi > + > # If nothing else worked, just cat the VERSION file; > # it contains the latest release number. > cat VERSION > -- > 1.7.10.4 -- David Champion • d...@bikeshed.us

Re: [PATCH 2/4] Generate version string during make not configure

tlib.c > index 7e93a3a..1f4982b 100644 > --- a/muttlib.c > +++ b/muttlib.c > @@ -21,6 +21,7 @@ > # include "config.h" > #endif > > +#include "version.h" > #include "mutt.h" > #include "mutt_curses.h" > #include "mime.h" > diff --git a/sendlib.c b/sendlib.c > index 249d6a1..f8d41e1 100644 > --- a/sendlib.c > +++ b/sendlib.c > @@ -22,6 +22,7 @@ > # include "config.h" > #endif > > +#include "version.h" > #include "mutt.h" > #include "mutt_curses.h" > #include "rfc2047.h" > diff --git a/status.c b/status.c > index 1bb9a5a..acf788e 100644 > --- a/status.c > +++ b/status.c > @@ -20,6 +20,7 @@ > # include "config.h" > #endif > > +#include "version.h" > #include "mutt.h" > #include "mutt_menu.h" > #include "mutt_curses.h" > -- > 1.7.10.4 -- David Champion • d...@bikeshed.us

[PATCH 2 of 3] Add subjectrx command to replace matching subjects with something else

# HG changeset patch # User David Champion # Date 1355527743 21600 # Branch HEAD # Node ID ecae1a363182797c2c157e88ff51d07c82f0a20c # Parent 7a90f541ff6942f05c4ad36130c2354238b1d67d Add subjectrx command to replace matching subjects with something else. This lets you define regular expressions

[PATCH 3 of 3] Adds mailboxrx (and unmailboxrx) command

# HG changeset patch # User David Champion # Date 1355527745 21600 # Branch HEAD # Node ID 8f4ff2c8f2e7314e3d62e879aaf91bb035d92da0 # Parent ecae1a363182797c2c157e88ff51d07c82f0a20c Adds mailboxrx (and unmailboxrx) command. Mailboxrx allows you to define a regular expression and replacement

[PATCH 1 of 3] Abstract the SPAM_LIST as a generic REPLACE_LIST

# HG changeset patch # User David Champion # Date 1355527735 21600 # Branch HEAD # Node ID 7a90f541ff6942f05c4ad36130c2354238b1d67d # Parent c4c65eadeb7142764bbd73ae63aeef3970669bed Abstract the SPAM_LIST as a generic REPLACE_LIST REPLACE_LIST can be used more generally as a list of pattern

[PATCH 0 of 3] Regex replacement on Subject

Questions about subject replacement have come up twice recently in mutt-users, and Michael has expressed support for the principle, so I'm resending this patch to the -dev list for review. Patch 1: refactors the regex replacement used by spam matching into a more abstract replacement mechanism, RE

[PATCH RFC] Add support for new mail notifications to DBus

mail events, run dbus-monitor --session --monitor interface=org.mutt.mutt (Note that $dbus is currently unset by default.) # HG changeset patch # User David Champion # Date 1352157645 21600 # Branch HEAD # Node ID ade034b9fcd52b8f8401fa52f10aed29467e07d1 # Parent d414971f0c486570352b573eaca

Re: Dynamic filter

[from mutt-users] * On 28 Oct 2012, David Champion wrote: > * On 28 Oct 2012, Alexis Letessier wrote: > > Hello, > > > > When on the index view, i would like to build a dynamic filter with > > parameters from the current mail under the pointer. For example i

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

Thanks for all the comments. I've reworked it into a third version that adds no new build dependency, but sacrifices as little information as possible. -- David Champion • d...@bikeshed.us

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

and drink myself silly, in whichever order works best 4. Require "make NATIVECC=..." when cross-compiling I'm good with 1 or 4. I'll entertain strong arguments for 2 or 3, especially if you're buying, but I'm not sure either is a complete solution. 1 and 4 are, if you accept the transference of the problem to documented conditions for compilation. -- David Champion • d...@bikeshed.us

Re: [PATCH] Add compiler and configure info to mutt -v output (closes #3537)

Too many things happening at once here. There are other changes: * removes the gcc output stanza from muttbug/flea. * adds cflags (because muttbug showed it) * On 18 Oct 2012, David Champion wrote: > Thanks for the reviews! Changes: > * Uses a C txt2c instead of Python - no new build p

[PATCH] Add compiler and configure info to mutt -v output (closes #3537)

patch # User David Champion # Date 1350429193 18000 # Branch HEAD # Node ID 0dc5d40c97c1810159a2c3e7dbb719d1bc92d81e # Parent 70810a88ce9feb66d5c74e7ec3f2a633bd8b5312 Add compiler and configure info to mutt -v output (closes #3537) This adds txt2c.c for coding text (on stdin) to a C byte array, and

  1   2   3   >