Re: [rfc] fork()ing off mutt's compose feature?
On 2000.11.22, in <[EMAIL PROTECTED]>, "john slee" <[EMAIL PROTECTED]> wrote: > > i've been using mutt for a while now. one thing that's always bugged me > (well, pretty much the only thing, now that i know about mime_forward), > is that there's no way that i can find to have a "compose" window as a > kind of separate entity such that i can refer to other messages *while > composing my message*. > > i could start another mutt session, but -R only seems to apply the > readonly flag to the first mailbox i look at. it also feels like i am > approaching the problem in hand (seeing other messages while composing) > from entirely the wrong angle. You can get most of what I expect you want with: set editor="cp %s %s.2; (xterm -e mutt -e 'set editor=vi' -H %s.2; rm %s.2) &" That's starting another session, but it has no need of -R, and the session is strictly instantial -- it lasts only as long as the composition does, and it pops its own terminal. > when mutt detects the child exiting (via sigchld or something), it > brings you back to the appropriate screen whereupon you can decide to > send the message, postpone it, abort it, or whatever. You don't get the compose menu in the original mutt instance with the above $editor, but frankly, that's preferable to me. This approach also doesn't allow the parent instance to know whether a message has really been replied to. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Mutt & PGP.. problem
Thomas Roessler filled my mailbox with: > > > > I created a key for myself on this machine using 'pgp -kg' > > What's your key ID looking like? when I cat on this FreeBSD box, it is all garbled... nothing readable. -=*=- Scott A. Davis...[EMAIL PROTECTED] Austin, Texas USA ...Si vis pacem para bellum "You can get more with a kind word and a gun than you can with a kind word alone." --Al Capone (1899-1947)
Re: Mutt in an Eterm
+ Ben Reser <[EMAIL PROTECTED]>: > Add this to the keyboard section of the MAIN file for the theme you use for > mutt: > [keysyms] Thank you. This works for me. I had the idea, but not the knowledge to do it for myself. Kai. -- ::: mailto:[EMAIL PROTECTED] . http://www.tu-ilmenau.de/~bond/ ::: for my pgp-key mailto:[EMAIL PROTECTED] (automated reply)
Re: Mutt & PGP.. problem
On 2000-11-24 04:31:12 -0600, Scott Davis wrote: > I created a key for myself on this machine using 'pgp -kg' What's your key ID looking like?
Mutt & PGP.. problem
Hi! I have installed Pretty Good Privacy 2.6.3i on this FreeBSD box and all went well. I am trying to integrate it into Mutt 1.2.5i, and that seems to go 99% ok. The problem I have is this: I created a key for myself on this machine using 'pgp -kg' When I go to use Mutt, send mail to myself, and choose to (e)ncrypt the mail, I get the following prompt before it tries to send the mail: 'Enter keyID for [EMAIL PROTECTED]' It wants input here and will not send unless I enter the correct info, which I do not know and don't know where to look. Can anyone shed some light on this for me? Thanks in advance! -=*=- Scott A. Davis...[EMAIL PROTECTED] Si vis pacem ...Si vis pacem para bellum "You can get more with a kind word and a gun than you can with a kind word alone." --Al Capone (1899-1947)
Re: Mutt and BCC and Outlook/KMAIL
On 2000-11-24 01:51:08 +, Jan- Hendrik Palic wrote: > Why is this an option, I want to use. I don't like, when everybdy > can see the Bcc- Header? Does this option make sense? Since Exim - and the relevant RFC - offer two possibilities of handling the Bcc header, it seems reasonable to give users the opportunity to use that option. -- Thomas Roessler <[EMAIL PROTECTED]>
Re: GPG Support
Hi,
Nils Vogels wrote:
>> I use gpg (GnuPG) 1.0.1e-SuSE to encrypt my mail. One of the commands
>> configured in my pgp.rc is
>> #set pgp_getkeys_command="gpg --no-secmem-warning --no-verbose \
>> --batch --with-colons --keyserver wwwkeys.pgp.net --recv-keys %r"
>> which does not work.
>
>Remove the hash ("#") in front of the line. A hash means "start of remark" sop
>your line is being treated as a remark, not a setting.
That was a stupid mistake.
I used the setting without #, I only hashed it away because it littered
the lower part of Mutt with garbled error messages. I use 'set
pgp_getkeys_command=""' until I find out what's wrong with the real
setting.
Sorry for the confusion.
Thorsten
