Sorry to respond to myself -- but this version has minor improvements.
--
Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F
http://camdensoftware.com | http://chipstips.com| http://chipsquips.com
#!/usr/bin/env ruby
require 'optparse'
abook = '~/.abook/addressbook
Quoth Steve Schmerler on Thursday, 02 September 2010:
> Hi
>
> Say I have abook entries like
>
> [0]
> name=Bob B.
> email=...@gmail.com
> nick=bob
> notes=friend,coworker
>
> [1]
> name=Alice A.
> email=al...@gmail.com
> nick=alice
> notes=friend
>
> Is it possible to query the notes field?
>
On Thu, Sep 02, 2010 at 07:20:18PM -0400, Ed Blackman wrote:
Does mutt rely on the fact that encoded-text shouldn't have "?" or
SPACE because it makes the implementation easier? Or is it just
following the RFC strictly? Reading the RFC, it's not clear to me
*why* encoded-text can't have "?" o
On Thu, Sep 02, 2010 at 03:11:30PM -0700, Michael Elkins wrote:
On Thu, Sep 02, 2010 at 02:49:00PM -0700, Michael Elkins wrote:
The problem is that the sender's MUA has not produced a valid RFC2047
encoding. Here is the ABNF (RFC2047, section 2, "Syntax of
encoded-words"):
Conincidentally,
On Thu, Sep 02, 2010 at 02:49:00PM -0700, Michael Elkins wrote:
The problem is that the sender's MUA has not produced a valid RFC2047
encoding. Here is the ABNF (RFC2047, section 2, "Syntax of
encoded-words"):
Conincidentally, it appears that even Twitter doesn't get this right. From an
ema
On Thu, Sep 02, 2010 at 04:39:23PM -0400, Ed Blackman wrote:
I did a little searching and found that RFC 2047 is the technical
specification for these encoded strings, and that mutt does have RFC
2047 support. However, none of the muttrc entries that mention it
seem relevant to RFC 2047 decodi
I've been seeing more and more "=?US-ASCII?Q?...?=" in email Subject
lines lately. At first, it was all from a particular (and not very
technically apt) source, and I assumed that they were doing something
wrong, and more or less ignored it. But as I get emails from more and
more sources, it'
Hi
Say I have abook entries like
[0]
name=Bob B.
email=...@gmail.com
nick=bob
notes=friend,coworker
[1]
name=Alice A.
email=al...@gmail.com
nick=alice
notes=friend
Is it possible to query the notes field?
abook --mutt-query friend
abook --mutt-query coworker
abook returns "Not found" i
On Thu, Sep 02, 2010 at 07:00:56PM +0200, Louis-David Mitterrand wrote:
In any case it matches contact@ and root@ without any quoting. Are your
sure it is necessary to quote the regexp?
I suppose not since it worked. :-)
Also I made a send-hook for when 'alt-e'dit an existing message:
On Thu, Sep 02, 2010 at 09:22:11AM -0700, Michael Elkins wrote:
> On Thu, Sep 02, 2010 at 04:02:01PM +0200, Louis-David Mitterrand wrote:
> >reply-hook '~h(X-Original-)?To:@example.net' "set hostname='example.net'"
>
> try this:
>
> reply-hook '~h "(X-Original-)?To:@example.net"' set host
On Thu, Sep 02, 2010 at 03:43:46PM +0200, chs...@freenet.de wrote:
Now I wonder if I need that line at all since I am setting the sent
folder in my folder hooks again like:
folder-hook imaps://mx.freenet.de/ 'set
folder=imaps://mx.freenet.de/INBOX
record=imaps://mx.freenet.de/INBOX/sent from=...
On Thu, Sep 02, 2010 at 04:02:01PM +0200, Louis-David Mitterrand wrote:
reply-hook '~h(X-Original-)?To:@example.net' "set hostname='example.net'"
try this:
reply-hook '~h "(X-Original-)?To:@example.net"' set hostname=example.net
The regexp needs to be quoted, otherwise the parenthesis
On Thursday, 02 September 2010, 15:43:46 +0200,
chs...@freenet.de wrote:
> Now I wonder if I need that line at all since I am setting the sent
> folder in my folder hooks again like:
>
> folder-hook imaps://mx.freenet.de/ 'set
> folder=imaps://mx.freenet.de/INBOX
> record=imaps://mx.freenet.de/INB
Hi,
Using mutt 1.5.20 I have this reply-hook:
reply-hook '~h(X-Original-)?To:@example.net' "set hostname='example.net'"
But the message-id always has the default 'hostname' (defined earlier in
the ~/.muttrc) not 'example.net'.
Am I missing something?
On Wed, 1 Sep 2010 09:42:18 -0700
Michael Elkins wrote:
> Try running Mutt in debug mode (mutt -d 5) and look at
> ~/.muttdebug0. I would be surprised if Mutt were saving to the wrong
> folder by capitalizing the first letter of the last word.
>
Thanks for help. I found the error. I had anothe
Hello Mutt users,
I am in the process of moving my mutt platform from a
Sparce Solaris 9 box to an x86 Solaris 10 box.
In order to resolve issues with the terminal color map
I am now (trying) to run a newer version of mutt but
am receiving an error when I invoke it.
I'm able to provide use
16 matches
Mail list logo