[PATCH] fix :reset to work with empty strings

As it turns out, mutt already handles all the option types correctly except the string types: DT_STR, DT_PATH and DT_ADDR. The following patch makes :reset work properly for all types, tested with :reset all # HG changeset patch # User Aron Griffis # Date 1248406601 14400 # Branch HEAD # Node ID

Re: [Mutt] #3295: postponed email marked new (make this configurable)

#3295: postponed email marked new (make this configurable) ---+ Reporter: anto...@dyne.org | Owner: mutt-dev Type: enhancement | Status: new Priority: trivial | Milestone:

compiler warnings due to ignored attrset return value

Due to the use of attrset, I get many compiler warnings such as: curs_main.c: In function ‘mutt_index_menu’: curs_main.c:563: warning: value computed is not used curs_main.c:566: warning: value computed is not used curs_lib.c: In function ‘curses_message’: curs_lib.c:312: warning: value computed i

[PATCH 0 of 2] Fix several compiler warnings.

These are minor cleanups to fix a few compiler warnings. Two will remain: - one about mktemp() (but I haven't investigated if the workaround is portable; mktemp is used as input for mkdir, so it's safe in spite of the warning) - another about a longish copyright string literal in main.c that

[PATCH 2 of 2] Fix two warnings "the address of 'foo' will always evaluate as 'true'"

# HG changeset patch # User Matthias Andree # Date 1248385934 -7200 # Branch HEAD # Node ID fc00838d5734ea560ac013565226c000fe7e4df4 # Parent 02a82e1ae8cbfaae70e10554198441c150ba1648 Fix two warnings "the address of 'foo' will always evaluate as 'true'". diff -r 02a82e1ae8cb -r fc00838d5734 bcac

[PATCH 1 of 2] Use proper prototype for mutt_get_default_charset(), fix fallout

# HG changeset patch # User Matthias Andree # Date 1248385890 -7200 # Branch HEAD # Node ID 02a82e1ae8cbfaae70e10554198441c150ba1648 # Parent 713a18794bb777570935780758e6a3e963116e61 Use proper prototype for mutt_get_default_charset(), fix fallout. diff -r 713a18794bb7 -r 02a82e1ae8cb charset.h

reset problem

I just noticed something odd. :reset (or :set &var) doesn't restore a compile-time default if the default is empty. :set smtp_url=foo :set ?smtp_url smtp_url="foo" :reset smtp_url :set ?smtp_url smtp_url="foo" Contrast this to a variable that has a non-empty default value

Re: [Mutt] #3304: ungroup not implemented

#3304: ungroup not implemented -+-- Reporter: pdmef | Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: 1.6 Component: mutt| Version: 1.5.20 Resolut

Re: Quoting of parentheses in regular expressions

=- Lars Hecking wrote on Thu 23.Jul'09 at 12:19:53 +0100 -= > Rocco Rutte writes: > > * 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. neith

Re: [Mutt] #3298: Mutt's way to get the FQDN is broken

#3298: Mutt's way to get the FQDN is broken -+-- Reporter: vinc17 | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt| Version: 1.5

Re: Quoting of parentheses in regular expressions

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. neither of > > I think you need to double-escape the bracket

Re: Quoting of parentheses in regular expressions

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. neither of I think you need to double-escape the brackets: save-hook '~s RC\\(ci\\):\ \\[st

Re: [Mutt] #3298: Mutt's way to get the FQDN is broken

#3298: Mutt's way to get the FQDN is broken -+-- Reporter: vinc17 | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt| Version: 1.5

Re: [Mutt] #3298: Mutt's way to get the FQDN is broken

Hi, * Derek Martin wrote: > I would be willing to hack up a patch for this, if someone can explain > the rammifications of IDN here. getaddrinfo() can handle IDN if you > use the AI_IDN flag. Also, I'd like to solicit comments about whether > the code should try to use getaddrinfo(), gethostbyad

Re: [Mutt] #3298: Mutt's way to get the FQDN is broken

#3298: Mutt's way to get the FQDN is broken -+-- Reporter: vinc17 | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt| Version: 1.5

mutt: 3 new changesets

3 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/d41e043fa775 changeset: 5987:d41e043fa775 branch: HEAD tag: tip user:Fabian Groffen date:Wed Jul 22 15:25:59 2009 +0200 summary: Use CRYPT_BACKEND_GPGME instead of non-existent HAVE_GPGME http://dev.mutt