Re: mailboxes
On 1999-05-24 19:22:19 +, Bennett Todd wrote: > MH enjoys the advantages mentioned for Maildir that come with > file-per-message --- applicability of Unix tools, > performance edge for huge messages --- but without the > locking benefit, since both the index file and the choice of > filenames for messages require locking to prevent concurrent > updates. Even worse, there is no defined locking protocol for these files so far. So I'd suggest you don't use MH folders in any situation which MAY involve concurrent access to the same folder.
Re: Lost PGP after upgrade to 95.5i
On 1999-05-24 13:36:47 -0500, G. T. Francisco, III wrote: > I've just upgraded via RPM to 95.5i to take advantage of the compressed > folders patch. I did it via RPM as I'm really not that comfortable > compiling and installing tarballs. Just out of curiosity: What's the source for 0.95.5 RPMs with the compressed folders patch? Is this the "vanilla" RedHat RPM?
Re: Lost PGP after upgrade to 95.5i
On Mon, May 24, 1999 at 02:12:52PM -0500, David DeSimone said: > G. T. Francisco, III <[EMAIL PROTECTED]> wrote: > > > > After upgrading, I've lost the ability to do PGP (I'm using PGP5), > > e.g. if I get a signed message, I just get a "sh: v: command not > > found" message. > > Mutt is trying to run the "pgpv" command, by taking your configured > "pgp" command and adding a "v" to it. However, this is failing because > your configured PGP command is blank. > > Examine your settings of your "pgp_v5" variable. It perhaps was > previously set in a default Muttrc, which is now replaced by the new > version. Either fix it there, or put the setting into your .muttrc. > I was careful to preserve my /etc/Muttrc and my ~/.muttrc and restored them after the install. They correctly reflect the "pgp_v5" variable. Any other thoughts? Thanks g-3
Re: Lost PGP after upgrade to 95.5i
On Tue, May 25, 1999 at 12:23:11PM +0200, Thomas Roessler said: > On 1999-05-24 13:36:47 -0500, G. T. Francisco, III wrote: > > > I've just upgraded via RPM to 95.5i to take advantage of the compressed > > folders patch. I did it via RPM as I'm really not that comfortable > > compiling and installing tarballs. > > Just out of curiosity: What's the source for 0.95.5 RPMs with the > compressed folders patch? Is this the "vanilla" RedHat RPM? > No, I downloaded the RPM generated by Thomas Ribbrock. The rpm and src.rpm are both available at www.bigfoot.com/~kaytan/tuxior.html. Cheers, G-3
vim -g/gvim problem
For some reason if I use gvim/vim -g as my $EDITOR I always get 'Aborted unmodified message.' and vim -g opens on my screen with proper filename and it's completely empty. This works perfectly with other programs. -- --ytti - ::3585:0512:1378
Re: Lost PGP after upgrade to 95.5i
Warning Could not process message with given Content-Type: multipart/signed; boundary=ReaqsoxgOBHFXBhH; micalg=pgp-md5;protocol="application/pgp-signature"
Problems with long address lines
I am having problems with mutt-0.95.4i. I use an external query to return a list of addresses from LDAP. I then tag each one as I want to send the message to many people. However, the To: line seems to hit a buffer limit and doesn't get all of the addresses. Is there another/better way to send messages to a large group of people? It would be nice if I didn't have to tag each address in order to get them all -- there are 150 of them. -- Eric M. Boehm [EMAIL PROTECTED]
Odd hook question
I'm looking to do something resembling the following pseudo-code: I have some arbitrary field, say sender (~e in mutt) I want to say: ~e =~ /^(.*)@(.*)$/ if -d $2, then savehook becomes $2/$1. Suggestions, or time to look at hacking in a feature? (As soon as I can get autoconf to behave...) -- Jeffrey Haas [EMAIL PROTECTED] "Normal" is a local phenomenon.
Re: vim -g/gvim problem
Saku Ytti <[EMAIL PROTECTED]> wrote: > > For some reason if I use gvim/vim -g as my $EDITOR I always get > 'Aborted unmodified message.' and vim -g opens on my screen with > proper filename and it's completely empty. Vim probably forks itself into the background, thinking that you must be at a shell prompt and you want to have your prompt back so you can type another command. But instead, Mutt is waiting for the editor to finish, and when it returns control back to Mutt, the file has not been touched, so Mutt aborts, and deletes the file before gvim can really get a good look at it. Don't let vim background itself. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Replying with headers
Hello all, I've got a question about mutt and replying with headers. I want to see the headers, but not all of them. What should I do? regards, Gerrit. -- The Dutch Linuxgames website. De Nederlandse Linuxgames pagina. Everything about games on Linux.Alles over spelletjes onder Linux. Site address: http://linuxgames.nl.linux.org Personal homepage: http://nl.linux.org/~gerrit/
Re: vim -g/gvim problem
Am Tue, May 25, 1999 at 05:03:23PM +0300 schrieb Saku Ytti: > For some reason if I use gvim/vim -g as my $EDITOR I always get 'Aborted > unmodified message.' and vim -g opens on my screen with proper filename and > it's completely empty. This works perfectly with other programs. Same happens to me on AMIGA some times ago... gvim seems to detach from the shell - and mutt "thinks", the editor exits. There's a flag (-x?) to tell vim not to detach from the starting shell. Faroul -- Henning `Faroul' Peters - [EMAIL PROTECTED] http://www.beyond.kn-bremen.de - PBeMs, Rollenspiel, LARP, DragonDice If a=b and b=c, then we've got a messed up alphabet.
