nightshade email (default)
send-hook . my_hdr From: Josh Huber <[EMAIL PROTECTED]>
send-hook . 'set signature=~/.mutt/sig.nightshade'
# work email (used internally)
send-hook (missioncriticallinux|mclinux|mclx).com my_hdr 'From: Josh Huber
<[EMAIL PROTECTED]>'
send-ho
ll_ gives you this
> prompt, which seems bizarre ...
Yes, I've gone so far as to wrap the output of gpg so that only one
key show up as selectable, but most of the time mutt segfaulted. I
didn't have enough time to look into it, so I'm not sure what I was
missing from the gpg outp
this". But, there is only a limited amount of ways you
> can get out of the compose menu. You just have to create macros for all
> the possible exit keys in the compose menu, that restore your usual
> setup. They could also un-macro all the compose menu bindings, although
> that
sed internally)
send-hook (missioncriticallinux|mclinux|mclx).com my_hdr 'From: Josh Huber
<[EMAIL PROTECTED]>'
send-hook (missioncriticallinux|mclinux|mclx).com 'set signature=~/.mutt/sig.work'
# mailing list setup
send-hook '~t debian-' my_hdr 'From: Jo
x27;s a
> good practice anyway to clean up after yourself. :-)
Yeah, I've been very happy with mutt's performance on dealing with
very large mailboxes, especially while threading the messages.
thanks again,
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21
ias joework Joe at Work <[EMAIL PROTECTED]>
alias joehome Joe at Home <[EMAIL PROTECTED]>
then when you type in joe, you'll just get a list of aliases that
start with the text 'joe'
> Thanks for your time !
Is that what you wanted?
ttyl,
--
Josh Huber
y
not what I expected.
quoting the whole thing doesn't work either.
neither does this, which I thought might have worked:
bind index \c""
to make sure mutt considered the as a whole character.
Thanks,
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B214
xt. (of all things)
am I clueless here? anyone have hints on how to set this up? I'm
using xemacs with canna for input/sending email, btw.
also, is this the proper place for these questions? people on -dev
might have a better idea :)
thanks in advance,
--
Josh Huber
lem is that mutt only displays the characters properly if I set
the LANG environment variable. kanji support is working great in the
term, I just need to convince mutt to display it properly. Perhaps
I'll try rebuilding xterm with unicode support :)
ttyl,
--
Josh Huber
iling list I'm dealing with.
What's the proper way to keep the default behavior, but still use the
additional handy features you get when using the subscribe command.
Thanks,
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223
gt; "n" expands to the author's real name (or address if the real name
> isn't known). I believe the numbers have to do with the field length.
Yep, ok. Thanks.
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
PGP signature
seriously, no, I don't think there is a way to do this. Change
the content type to text/html (control-T in the compose menu), and
just put html in the body of the email.
but -- never send it to me!
ttyl,
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B2148
.org' 100
> color index yellow default '~C some@list\.org'
You can set colors based on the score:
.
.
.
score '~C some@list\.org' 100
color index yellow default '~n 100-999'
color index red default'~n 1000-'
ttyl,
--
Josh Huber
set charset=utf-8
set send_charset="us-ascii:iso-2022-jp:iso-8859-1:utf-8"
which automatically changes the content-type to iso-2022-jp when there
is japanese text in the mail.
pretty cool.
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
PGP signature
to [EMAIL PROTECTED] after sending
> > the mail to [EMAIL PROTECTED]?
> >
> > --
> > k.
>
>
>
> --
> Prepare for the inevitable, and you will be struck by something worse.
> Before you speak, listen to my fist.
> Walk alone before you walk ahead.
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
PGP signature
one can use [ ] and then double quote the variables
> within, as you have done.
AFAIK, it also doesn't fork a process as well, using [[ ]] the tests
are done internally to bash/ksh, and are thus much faster.
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A
%F author name, or recipient name if the message is from you
hope this helps,
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
PGP signature
historical reason for this? I seem to remember
this being a reason to use [[ ]] in the past.
Thanks for the tip, :)
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
PGP signature
In-Reply-To: but better than having threads scattered all over the
folder)
perhaps the regex wasn't quite right?
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
PGP signature
find any messages with this
problem. (even though I _just_ looked at one).
ttyl,
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
PGP signature
o what you suggest:
Default: "^(re([\[0-9\]+])*|aw):[ \t]*"
I assumed the reply regexp was applied to the subject, and the matched
text is removed, then the resultant string is compared with other
subjects. If this is true (is it not?), then you should
lsign-key with gpg)
> option(s). But these days I'm paying more attention to that statement
> in the manual about this format being deprecated :^) :^). Something
> might be messed up since I switched back? Didn't undo all those
> configurations?
I
en a
short perl script called 'uk' (update-key(s)) which might help you out
a little.
uk , like:
[huber@majere:~]-$> uk huber
2000-01-20 Josh Huber <[EMAIL PROTECTED]>
***
Updating the listed keys from pgp.ai.mit.edu
**
hould try to
# import the key from that server (server do syncronize with each
# others and DNS Round-Robin may give you a random server each time).
# Use "host -l pgp.net | grep www" to figure out a keyserver.
keyserver pgp.ai.mit.edu
--
Josh Huber
;re looking for sort_aux. f. ex:
set sort_aux=date-received
--
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
PGP signature
ou might need a .procmailrc. Something simple like:
PATH=/usr/local/bin:/usr/bin:/bin
MAILDIR=$HOME/mail/
DEFAULT=$HOME/mail/inbox
ttyl,
--
Josh Huber | [EMAIL PROTECTED] |
PGP signature
t the trailing .* ?? The TO address should always end with t
> the ".com" - is there a need for it, or were you just being ultra
> cautious to get everything possible?
The reasoning behind this is:
> > * ^To: .*about.com.*
...often addresses are formatted in a way like:
Joh
On Wed, Feb 21, 2001 at 04:21:30PM -0500, Josh Huber wrote:
> The reasoning behind this is:
>
> > > * ^To: .*about.com.*
>
> ...often addresses are formatted in a way like:
>
> John Doe <[EMAIL PROTECTED]>
> or
> [EMAIL PROTECTED] (John Doe)
>
>
On Sat, Feb 24, 2001 at 12:15:25PM -0500, Rich Lafferty wrote:
> On Sat, Feb 24, 2001 at 08:21:28AM -0500, Josh Huber ([EMAIL PROTECTED]) wrote:
> >
> > * ^TO_about.com
> >
> > the TO_ is expanded to a nice regex which matches the proper text
> > before an ad
the best way to do this, but the
inflexibility of mutt's configuration was one thing that caused me to
look elsewhere for my MUA needs. ;)
Good luck,
--
Josh Huber
hould work fine
though :)
that's what you get for running sid (or maybe woody?)
ttyl,
--
Josh Huber
ng a bitch of a
time when my friend and I couldn't figure out why my signature wasn't
showing up on his key on the keyservers :P
I think the best practice is to just not sign a key unless you meet
in person and verify identity, otherwise, just deal with the
warning. (it is there for a reason, after all :)
ttyl,
--
Josh Huber
Dairy Wall Limey <[EMAIL PROTECTED]> writes:
> in any event, looks like i'm SOL here.
Gnus honors the MFT header. Recent cvs gnus also generates it.
But, if you're dealing with pine users, chances are there aren't any
(many?) Gnus users in the mix..
ally well (like Gnus).
It will be nice when other mailers (maybe even LookOut? perhaps in a
couple years they will innovate this feature) implement this
feature...
Unfortunately, I think that World Peace (TM) will happen before this
occurs.
ttyl,
--
Josh Huber
hings like this to be made standard.
Definately. On lists that are technical and 90% use mutt it is nice.
What would be really nice is if MS OE supported these kinds of
things. Hah, right...how many years until they will? ;)
ttyl,
--
Josh Huber | [EMAIL PROTECTED] |
speed 38400 baud; rows 57; columns 84; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ;
eol2 = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
...
try:
$ stty stop ""
That fixes it for me, although that may not be the right way to do it.
HTH,
--
Josh Huber | [EMAIL PROTECTED] |
se_message(&msg);
+}
+ }
+
for (tmp = Score; tmp; tmp = tmp->next)
{
if (mutt_pattern_exec (tmp->pat, 0, NULL, hdr) > 0)
--
Josh Huber | [EMAIL PROTECTED] |
lag;
+WHERE char *ScoreHeader;
#ifdef USE_IMAP
WHERE short ImapKeepalive;
It builds for me with this, but you'll have to test it yourself :)
--
Josh Huber | [EMAIL PROTECTED] |
Josh Huber <[EMAIL PROTECTED]> writes:
> It builds for me with this, but you'll have to test it yourself :)
Maybe I should mention how to use it.
just add:
score_header "X-Priority"
to your .muttrc, and the messages with this header will use the
integer contents of s
t;
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=
$ export LANG=en_US
$ locale
LANG=en_US
LC_CTYPE="en_US"
LC_NUMERIC="en_US"
LC_TIME="en_US"
LC_COLLATE="en_US"
LC_MONETARY="en_US"
LC_MESSAGES="en_US"
LC_PAPER="en_US"
LC_NAME="en_US"
LC_ADDRESS="en_US"
LC_TELEPHONE="en_US"
LC_MEASUREMENT="en_US"
LC_IDENTIFICATION="en_US"
LC_ALL=
In other words, all you have to do is set LANG :)
You don't need to set each variable, unless you need the values
different.
ttyl,
--
Josh Huber | [EMAIL PROTECTED] |
40 matches
Mail list logo
