Out of the box, most single keystrokes in most modes do something. On
the MacroSamples page, the Mutt Wiki shows some macros bound to two
keystrokes, thus allowing a very much larger number of keystrokes with
which to play.
So my question is: are there any "good" places to put my macros with
some reasonable assuredness that the next version of Mutt won't assign
those places to new functionality? IOW, is there a special "user space"
of keystrokes (e.g., <f9> followed by a single keystroke) that won't be
stepped on by Mutt itself? Or do I just re-purpose some key(s) normally
attached to functionality I don't think I'll use? Or are there no rules
at all, and the entire keyboard is up to me to map as I see fit?
I know which answer(s) I'd prefer, but I can't find an authoritative
answer one way or the other.
If this is covered somewhere in the documentation or the Wiki or
elsewhere, please feel free to point me to it.
Regards,
Dan
--
Dan Sommers
<http://www.tombstonezero.net/dan/>
> On Sun, 26 Jun 2005 18:59:21 -0400, Dan Sommers wrote:
>
>> So my question is: are there any "good" places to put my
>> macros with some reasonable assuredness that the next version
>> of Mutt won't assign those places to new functionality? IOW,
>> is there a special "user space" of keystrokes (e.g., <f9>
>> followed by a single keystroke) that won't be stepped on by
>> Mutt itself? Or do I just re-purpose some key(s) normally
>> attached to functionality I don't think I'll use? Or are
>> there no rules at all, and the entire keyboard is up to me to
>> map as I see fit?
>
> It's unlikely that the function keys are going to be mapped by
> a stock version of mutt, either as prefixes or base keys, at
> much of any point in the future, simply because function keys
> aren't guaranteed to be properly supported in all environments
> to begin with. Heck, there isn't even reliable agreement on
> what a backspace key is supposed to send. So, you're probably
> safe in using those for your own purposes, as Mutt (and most
> other programs designed for portability) aren't likely to use
> those until every other option has been exhausted.
>
You put "X-No-Archive: yes" in your headers.
Which means that you will be able to deny that you ever posted
a particular article and no one will be able to prove otherwise.
VERY few people do that. Why?
Because any sensible person knows to ignore any advice from
someone who does that.
Generally, people just killfile them. (I prefer to keep my
eyes on such people.)
AC
> On Sun, 26 Jun 2005 18:59:21 -0400, Dan Sommers wrote:
>
>> So my question is: are there any "good" places to put my
>> macros with some reasonable assuredness that the next version
>> of Mutt won't assign those places to new functionality? IOW,
>> is there a special "user space" of keystrokes (e.g., <f9>
>> followed by a single keystroke) that won't be stepped on by
>> Mutt itself? Or do I just re-purpose some key(s) normally
>> attached to functionality I don't think I'll use? Or are
>> there no rules at all, and the entire keyboard is up to me to
>> map as I see fit?
>
> It's unlikely that the function keys are going to be mapped by
> a stock version of mutt, either as prefixes or base keys, at
> much of any point in the future, simply because function keys
> aren't guaranteed to be properly supported in all environments
> to begin with. Heck, there isn't even reliable agreement on
> what a backspace key is supposed to send. So, you're probably
> safe in using those for your own purposes, as Mutt (and most
> other programs designed for portability) aren't likely to use
> those until every other option has been exhausted.
>
> -- 52. I will hire a team of board-certified architects and
> surveyors to examine my castle and inform me of any secret
> passages and abandoned tunnels that I might not know about.
> --Peter Anspach's list of things to do as an Evil Overlord
His headers:
# Newsgroups: comp.mail.mutt
# From: "Peter H. Coffin" <hel...@ninehells.com>
# Subject: Re: Good Keys for Macros?
# References: <m2is00s...@unique.fully.qualified.domain.name.yeah.right>
# Reply-To: hel...@ninehells.com
# X-No-Archive: yes
# Message-ID: <slrndbuouc....@othin.ninehells.com>
# User-Agent: slrn/0.9.7.4 (OpenBSD)
# Date: Sun, 26 Jun 2005 21:26:20 -0500
# NNTP-Posting-Host: ninehells.com
# X-Trace: newspeer2.tds.net 1119840186 216.170.211.219 (26 Jun 2005 21:43:06 CST)
# Lines: 23
# Organization: TDS.NET Internet Services www.tds.net
# Path: newsspool2.news.atl.earthlink.net!stamper.news.atl.earthlink.net!stamper.news.pas.earthlink.net!elnk-nf2-pas!newsfeed.earthlink.net !newshub.sdsu.edu!postnews.google.com!news2.google.com!newsread.com!news-xfer.newsread.com!tdsnet-transit!newspeer.tds.net!news-out.news.tds.net !216.170.153.144.MISMATCH!newspeer2.tds.net!othin.ninehells.com!news
# Xref: news.earthlink.net comp.mail.mutt:25065
# X-Received-Date: Sun, 26 Jun 2005 19:46:29 PDT (newsspool2.news.atl.earthlink.net)
#
My, My. Look at that DNS "MISTMATCH".
That means you've forged that part of the header.
What are you hiding from besides the responsibility for what you
post?
AC