David DeSimone <[EMAIL PROTECTED]> wrote on Wed, 26 Jan 2000:
> By the way, something to watch out for in .mutrrc's:
>
> set reply_regexp = "^(re|aw):[ \t]*"
>
> This doesn't do what you think it does; Mutt sees the "\t" as simply
> "t", because backslashes are parsed within double-quotes.
Hi,
I would like to bind a key where when I am in the brower mode
with a list of folders, I would like to press a key that goes to
the next folder which contains unread message.
Something very similar to the next-new in the index mode.
Thanks.
Shao.
--
Michael Thies <[EMAIL PROTECTED]>:
> Hi You all,
>
> I wonder, if I could use a my_hdr-command in my .muttrc defaultly like
> send-hook . "my_hdr Return-Receipt-To: "
> and appending the specific email-adress in my editor, when I want to
> get a return-receipt?
> Just like the Cc:, Bcc: or Reply
2000-01-26-16:43:44 Jean-Sebastien Morisset:
> I'm stumped. When I encrypt a message to a friend, mutt will ask
> me to select his public key.
I don't know how to make mutt solve this automagically for all your
correspondents, but if you're willing to add a line to your .muttrc,
by hand, for ever
Edmund GRIMLEY EVANS [[EMAIL PROTECTED]] wrote:
> Jimmy Mäkelä <[EMAIL PROTECTED]>:
> > Is it possible to look at the original To: of the message which I wan't
> > to reply to, and execute commands based on the contents of that.
> >
> > This would be nice since it is pretty common to have more th
I'm stumped. When I encrypt a message to a friend, mutt will ask me to
select his public key. The list which comes up doesn't show his key and
several entries are missing! There are only 14 keys listed, but when I use
"pgp -kv" it shows 20 keys! I've checked my pgp variables and they all seem
ok..
On Wed, Jan 26, 2000 at 02:13:23PM -0600, David DeSimone wrote:
> By the way, something to watch out for in .mutrrc's:
>
> set reply_regexp = "^(re|aw):[ \t]*"
>
> This doesn't do what you think it does; Mutt sees the "\t" as simply
> "t", because backslashes are parsed within double-quotes.
Jim B <[EMAIL PROTECTED]> wrote:
>
> I believe this can be corrected by a well-written regular expression, but
> I'm not so good at that so I'm wondering if anyone can help.
This won't work with Mutt as it's currently coded, because Mutt assumes
that the reply_regexp matches something at the *beg
On Wed, Jan 26, 2000 at 16:30:45 +0200, Mikko Hänninen wrote:
> Byrial Jensen <[EMAIL PROTECTED]> wrote on Wed, 26 Jan 2000:
> > You could make a macro to:
> >
> > 1) copy the current message to some other mailbox,
> > 2) move the cursor to the next message
> > 3) call itself
> >
> > and start i
David T-G <[EMAIL PROTECTED]> wrote:
>
> Mutt regexp gurus: Is specifying the A-Z necessary if we don't care
> about the case? If we do and have to use A-Z, will the re|aw exp
> match upper case versions?
Specifying any capital letter in your regexp will cause Mutt to match
the regexp case-sens
On Wed, Jan 26, 2000 at 04:54:50PM +0200, [EMAIL PROTECTED] wrote:
>Steve Heitke <[EMAIL PROTECTED]> wrote on Wed, 26 Jan 2000:
>> # delete current message and go to next new
>> macro index "d" "\t"
>>
>> unset resolve
>>
>> This works great but now when I (s)ave a message the delete built
On 2000-01-26 13:25:33 +, Edmund GRIMLEY EVANS wrote:
> See reverse_name in the latest mutt. Unfortunately this isn't in
> mutt-1.0, I think.
Reverse_name is a pretty old feature, and certainly present in
stable.
However, it's more useful together with the new versions' "from"
variable.
--
Jason Helfman <[EMAIL PROTECTED]>:
> Does anyone see why this wouldn't work on checking multiple mailboxes
> using the bash shell?
>
> MAILPATH="/var/spool/mail/jgh?You have mail:$USER/Mail/mutt?You
> has mutt mail:$USER/Mail/clug?You have clug mail"
Don't you mean $HOME rather than $USER?
Steve Heitke <[EMAIL PROTECTED]> wrote on Wed, 26 Jan 2000:
> # delete current message and go to next new
> macro index "d" "\t"
>
> unset resolve
>
> This works great but now when I (s)ave a message the delete builtin no
> longer advances me to the next message. Is there any way I can ge
Does anyone see why this wouldn't work on checking multiple mailboxes
using the bash shell?
MAILPATH="/var/spool/mail/jgh?You have mail:$USER/Mail/mutt?You
has mutt mail:$USER/Mail/clug?You have clug mail"
I wanted the (d)elete action to delete the current message and advance
to the next unread message so I did the following in my muttrc:
# delete current message and go to next new
macro pager "d" "\t"
macro index "d" "\t"
unset resolve
This works great but now when I (s)ave a message the
Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> wrote on Wed, 26 Jan 2000:
> This must surely be the second most frequently asked question (after
> the one about hooks having a permanent effect unless you also have a
> default hook to reset the state).
Indeed. :-)
> See reverse_name in the latest mutt.
Byrial Jensen <[EMAIL PROTECTED]> wrote on Wed, 26 Jan 2000:
> You could make a macro to:
>
> 1) copy the current message to some other mailbox,
> 2) move the cursor to the next message
> 3) call itself
>
> and start it at the first message in the sorted mailbox
What would cause this macro to s
Jimmy Mäkelä <[EMAIL PROTECTED]>:
> Is it possible to look at the original To: of the message which I wan't
> to reply to, and execute commands based on the contents of that.
>
> This would be nice since it is pretty common to have more than one
> email-address, and it is IMHO better to have t
Is it possible to look at the original To: of the message which I wan't
to reply to, and execute commands based on the contents of that.
This would be nice since it is pretty common to have more than one
email-address, and it is IMHO better to have the address which they wrote
to as From in the r
On Tue, Jan 25, Roland Rosenfeld wrote:
> Olaf Hering schrieb am Dienstag, den 25. Januar 2000:
>
> > how can I sort the list of available mailboxes ( c - ? or TAB ) by date,
> > recent first?
> set sort_browser=reverse-date
> in your muttrc.
First read the source, Luke, then ask. Shame on me :
Hello,
I'm using Mutt Version 0.91.1 and am having trouble printing. I tried
setting the "set print_command = "lpr -Plp1", but mutt gives me the
following error: "print_command: unknown variable" What is the correct
configuration variable.
I'm running on Linux 2.0.38. I can not upgrade to the m
Jim B <[EMAIL PROTECTED]> wrote on Wed, 26 Jan 2000:
> I've been looking at how Mutt uses these regexps, and it seems I may need
> something more like:
>
>
>
> From what I can tell, the expression actually is more of the "ignore" part
> rather than the "match" part... like a "negative" match.
23 matches
Mail list logo
