Hi!
I want to make myself kind of "template" for writing mails. I think the
best way would be a filter, that could put some text in a new mail. The
filter is not a problem, but I wonder how to call it automatically
within Mutt (when I tell Mutt to open my favourite vim :) to edit a
message, but of
Hello Mutt Users!
On wto 18 lip 2000 06:29:01 GMT David T-G wrote:
> Aren't hooks great? :-)
Yes, they surely are :)
> although the possibility of a macro springs to mind.
Can send-hook call macros?
--
Bi-la kaifa
mailto:[EMAIL PROTECTED]
I have noticed a bit annoying behaviour when I set the automatic verify
of PGP signatures. It's because the screen is not refreshed after that.
The worst is when I don't have someone's key in my keyring: I see two
status bars then :( When I got the desired key, it's just one "S"
instead of "-" on
Hello Mutt Users!
On wto 18 lip 2000 14:27:46 GMT David T-G wrote:
> I don't *think* so, but you could specify a push command and push the
> macro keystrokes...
Well, that should work. Thanks for the tip :)
--
Bi-la kaifa
mailto:[EMAIL PROTECTED]
Hi!
I was searching for a simple addressbook that could work with Mutt. I
have found one -- it's called abook. It's almost OK, I can simply query
it for an e-mail address. However there is one problem: I can't mail to
multiple addresses at once. I can ask abook for a pattern or for 'all'
and Mutt
Hello Mutt Users!
On śro 19 lip 2000 13:26:42 GMT Bob Bell wrote:
> Use ';' before the command (e.g. ';m') to have the command apply
> to all tagged records.
Thanks :) I should read doc first -- sorry.
--
Bi-la kaifa
mailto:[EMAIL PROTECTED]
I asked this before but nobody answered.
When I use gpg functions the screen doesn't refresh after calling it.
If I press the refresh screen sequence (^L by default) everything is
alright -- screen backs to normal. Is this a known bug? Does it occure
in your mailers?
--
Bi-la kaifa
mailto:[EMAIL
Hello Mutt Users!
On pon 24 lip 2000 15:17:24 GMT Charles Curley wrote:
> Possibly you have a termcap problem
Well, I think I don't. All other things work great.
> or else mutt is sending the wrong
> sequence of control characters to your terminal program.
It looks like mutt doesn't call the r
Hello Mutt Users!
On wto 25 lip 2000 07:15:55 GMT David T-G wrote:
> I get the same thing with mutt-1.2.4i and gnupg 1.0.1
I see you're using gpg 1.0.2 now and so do I. However, I'm happy now
because I found where the problem was. I filled the pgp_getkeys_command,
but I was offline when Mutt inv
Hello Mutt Users!
On śro 26 lip 2000 12:15:43 GMT David T-G wrote:
> set pgp_getkeys_command="gpg --recv-keys --keyring
> pubring.catch-all-keys.gpg %r"
Mine looks similar, so that's not problem. It's the unexpected output or
return value when an error (can't coonect to keyserver because I'm
Sorry for the offtopic.
Anyway my question is: what pgp keyservers do you use? I searched some
www pages, but couldn't find any real keyservs index.
--
Tomasz Olszewski
[EMAIL PROTECTED]
Hello Mutt Users!
On śro 02 sie 2000 19:14:19 GMT Drew Bloechl wrote:
> $ host -l pgp.net | grep wwwkeys
>
> and pick one in or near your country. Personally I use
> wwwkeys.nl.pgp.net since wwwkeys.us.pgp.net seems to frequently be down.
I thought that wwwkeys are web-based only and didn't
My friend uses PGP 6.x and The Bat. Unfortunately Mutt doesn't recognize
that a message from him is signed. There is a recipe in the FAQ, but it
doesn't work in this case. The recipe begins with:
:0
* !^Content-Type: message/
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
In his
Hello Mutt Users!
On pon 07 sie 2000 10:12:27 GMT David T-G wrote:
> Rather than that I'd create another recipe
I was thinking about that but it's slow.
> (or dig back into the docs to
> figure out how to OR it into the first) to at least match on
It would be the best but it's impossible :( Of
Hello Mutt Users!
On pon 07 sie 2000 13:21:59 GMT David T-G wrote:
> You mean slow for you to write for every user like this, or slow for
> procmail to process because it's another recipe to check?
As you know (after reading the very end of my previous mail) I mean slow
for procmail :)
> I can
Hello Mutt Users!
On pon 07 sie 2000 13:21:59 GMT David T-G wrote:
> That's what I thought you said. Interesting.
Maybe this will interest you. I think the recipe in the PGP-Notes is
wrong. Let's say someone sends me a message with an enclusore. He is
also using PGP and signs the message. There
Hello Mutt Users!
On pon 07 sie 2000 17:33:40 GMT Aaron Schrab wrote:
> I suspect that that's what's happening in this case, since the example
> message (which had Content-Type: text/plain) got modified by my procmail
> rules and mutt successfully checked the signature.
Yes, that's it and that's
Can anybody tell me why this doesn't work:
set indent_string=`for x in %n; do echo $x | cut -c 1; done;`
Normally (when I run it manually from the shell) it works fine (of
course when I replace %n with some words).
--
Tomasz Olszewski
[EMAIL PROTECTED]
Hello Mutt Users!
On wto 08 sie 2000 17:43:40 GMT Caster wrote:
> Can anybody tell me why this doesn't work:
> set indent_string=`for x in %n; do echo $x | cut -c 1; done;`
Of course I forgot about send-hook so it just couldn't work...
Eh...
--
lamest
Tomasz Olszewski
[EMAIL PROTECTED]
Hello Mutt Users!
On pon 07 sie 2000 20:07:21 GMT Thomas Roessler wrote:
> Could you forward a complete message to this list, including all
> relevant headers, and the nested MIME stuff?
Wel, here it goes. I don't think it can be useful, because now I know
why the problems occurs (because his me
Hello Mutt Users!
On wto 08 sie 2000 20:28:16 GMT Thomas Roessler wrote:
> Yep... When I originally saw your note about multipart/mixed with
> PGP nessages, I speculated about a broken attempt to implement
> PGP/MIME, but this is just a MUA being creative and attaching the
> public key to messag
After some tries I found that my idea won't work :( Mutt doesn't
evaluate %n before sending it to a program so that programs receives
just "%n". There is now way to easily change this behaviour, I suppose?
--
Tomasz Olszewski
[EMAIL PROTECTED]
Hello Mutt Users!
On śro 09 sie 2000 16:30:24 GMT Leonid Mamtchenkov wrote:
> Then I have changed "set editor" line in my .muttrc to the path to the
> shell script.
Well, I found that %s in $editor expands to the filename containing the
message, so you can use just something like:
set editor="
Hello Mutt Users!
On czw 10 sie 2000 07:35:56 GMT David T-G wrote:
> It's a valid escape sequence, and I think I've heard of it before. It
> might not, however, be fully documented :-)
In fact I don't see any mention of it in the docs (I mean in refer to
the name of the edited file).
> You can
Hello Mutt Users!
On pią 11 sie 2000 00:19:09 GMT Peter Palfrader wrote:
> set editor="vim +\`awk '/^$/ {print i+2; exit} {i++}' %s\` %s"
Even more clever :)
--
Tomasz Olszewski
[EMAIL PROTECTED]
Hello Mutt Users!
On pią 11 sie 2000 02:40:18 GMT Michael Tatge wrote:
> It's there:
>
> 5.3.3.3. Command Expansion
Well, I missed it. Maybe because I always look for such things in the
"Configuration variables" section :)
--
Tomasz Olszewski
[EMAIL PROTECTED]
PGP signature
Hello Mutt Users!
On pią 11 sie 2000 11:30:03 GMT Kai Blin wrote:
> We don't want Mutt to become something like StarOffice (can do anything, but
> poorly), do we?
I agree but it's just a very little thingie :) This isn't a html viewer.
Look at tin -- is it like Star Office?
--
Tomasz Olszewsk
Hello Mutt Users!
On sob 12 sie 2000 16:05:27 GMT iain truskett wrote:
> Clever, but only useful if your vi clone doesn't support something like:
> set editor="vim +/^$/+1"
Notice, that moving the cursor to the line that comes exactly after the
first blank line is no what I want. I need vi to
Hello Mutt Users!
On nie 13 sie 2000 18:57:31 GMT iain truskett and
Christian Schult wrote:
>set editor="vim -c \":normal 2/^$/^M\" %s"
Tkanks :) I didn't know of ^M.
> That's for vim. My brain hurts doing it for vi all in vi, so your awk
> solution works there =)
In fact it's not mine sol
Hi!
Why something like this doesn't work:
set editor=`if test $DISPLAY ; then echo gvim -c ":normal 2/^$/"
+nohlsearch %s ; else echo vim -c ":normal 2/^$/" +nohlsearch %s ; fi`
It's all in one line. Mutt complains about unknown -c option (!). I've
tried to quote it and escape it somehow but it
Hello Mutt Users!
On pon 14 sie 2000 11:13:40 GMT Michael Elkins wrote:
> It sets $editor to gvim and then tries to set
> the variable -c, which of course does not exist.
Oh, I see. I wrote a shell script which I set as my $editor (set
editor="my_script") and it works (the script calls the edito
Hello Mutt Users!
On pią 11 sie 2000 07:36:37 GMT David T-G wrote:
> Nah; I still like finding a way to let your editor, perhaps with help
> from other tools, do it for you. Let mutt decide whether or not to
> attach your signature and leave it at that.
Well, maybe you're right. Altough such fe
32 matches
Mail list logo