From hazmat@unixshell.com Mon Feb 2 07:24:45 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (hazmat@unixshell.com [204.170.16.210]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id HAA24656 for ; Mon, 2 Feb 1998 07:24:44 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id KAA24382; Mon, 2 Feb 1998 10:25:01 -0500 (EST) Message-ID: <19980202102500.53462@unixshell.com> Date: Mon, 2 Feb 1998 10:25:00 -0500 From: Ken W To: mutt Subject: Re: feature request Mail-Followup-To: mutt References: <19980128192707.36400@dtthp169.jf.intel.com> <199801301739.MAA03228@unixshell.com> <19980130162431.47274@dtthp169.jf.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980130162431.47274@dtthp169.jf.intel.com>; from Clint Olsen on Fri, Jan 30, 1998 at 04:24:31PM -0800 X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X Content-Length: 1469 Lines: 31 On Fri, Jan 30, 1998, Clint Olsen wrote: > > I liked it as well, but it got me thinking. What use does it serve to > expand aliases in place? If it expands, it's probably the "correct" > address. However, people complained if no expansion took place on certain > addresses (system aliases like postmaster or non-local addresses) and you > had to hit return twice for no apparent reason, so I made it only require > the extra return iff there was a change in the buffer (e.g. expansion > actually occurred). As a result, if you type in the "wrong" address, it > wouldn't expand and you'd have to correct it in the editor anyway (or in > compose if you don't edit_hdrs). So I guess I would have to ask what this > buys us in terms of usability? Sure it looks neat, but... :) I think that it is more than just a novelty. :) I was thinking like in Elm, where you type in the To: address, or in this case an alias, and when you hit enter, it prompts you for the subject, displaying the expanded alias right-justified. I guess it's just a reassurance thing. It doesn't require you, however, to hit ENTER twice. it just shows you the recipient address at the subject prompt. In this case I can't see ANY negative effect at all. Probably a waste of time, but if I realize that I entered an alias incorrectly in elm at the prompt once it's expanded, I just cancel and hit 'm' again. -Ken -- hazmat@unixshell.com hazmat@shore.net http://www.shore.net/~hazmat From fox@fuzzy.rsn.hp.com Mon Feb 2 09:08:42 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id JAA22812 for ; Mon, 2 Feb 1998 09:08:25 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id JAA29307 for ; Mon, 2 Feb 1998 09:08:22 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id LAA00172; Mon, 2 Feb 1998 11:08:21 -0600 (CST) Message-ID: <19980202110820.06302@rsn.hp.com> Date: Mon, 2 Feb 1998 11:08:20 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: Need mutt to read ELM format alias files Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980130103144.55388@dgii.com> <19980130123223.25580@mph124.rh.psu.edu> <19980130125249.11280@dgii.com> <19980130144632.09397@shell9.ba.best.com> <19980130161550.64490@dtthp169.jf.intel.com> <19980130190422.13604@rsn.hp.com> <19980130174747.35505@la.tis.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=zYM0uCDKw75PZbzx X-Mailer: Mutt 0.89i In-Reply-To: <19980130174747.35505@la.tis.com>; from Michael Elkins on Fri, Jan 30, 1998 at 05:47:47PM -0800 Content-Length: 1572 Lines: 46 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Michael Elkins wrote: > > So long as you are still using dotlocking it is ok. The dotlocking is NFS > resistant (thanks to Felix von Leitner). Clint Olsen wrote: > > Well, you always use dotlocking. Enabling fcntl doesn't do any good if > none of the other programs support it. Haven't any of you folks used systems in which the MDA doesn't bother with dot-locking? Our BSD systems here use only flock and fcntl locking. So, if you turn on dot-locking and nothing else on those systems, you would risk mailbox corruption. I'm just trying to debunk the notion that seems to be out there, that there is one true locking method that is "always safe." There isn't. The only way to really know is to find out what the MDA's are going to do for locking, and use the same methods. Unfortunately that is a non-trivial process on some systems. Sigh. -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNX9gQ0lGhIp2tThAQFDhAL+KxkwCW3jI5w1Nq5niaKz90BHb6KwvW4L c8BKL7p9jRzpQWgD01jMwR8J8SiU/4SMF4oAC8HnZH9XqcNKbvyQiBi5O8jpRVXY xHXmuQJHxlzfwd9h5xegqJw68NVJjE/a =6LUU -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx-- From dogcow@zerbina.merit.edu Sun Feb 1 12:48:53 1998 Return-Path: dogcow@zerbina.merit.edu Received: from zerbina.merit.edu (zerbina.merit.edu [198.108.60.181]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA18596 for ; Sun, 1 Feb 1998 12:48:49 -0800 (PST) Received: (from dogcow@localhost) by zerbina.merit.edu (8.8.8/8.8.8) id PAA24281; Sun, 1 Feb 1998 15:48:46 -0500 (EST) Message-ID: <19980201154845.49481@home.merit.edu> Date: Sun, 1 Feb 1998 15:48:45 -0500 From: Tom Spindler To: nicholas harteau , mutt-users@cs.hmc.edu Subject: Re: An impostor? References: <19980130220307.63720@tribe.ping.de> <19980130201019.41915@cs.swarthmore.edu> <19980131144228.38966@tribe.ping.de> <19980131104114.33927@acm.cs.umr.edu> <19980131122812.09326@construct.net> <19980131170402.37205@home.merit.edu> <19980131205916.58045@construct.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 In-Reply-To: <19980131205916.58045@construct.net>; from nicholas harteau on Sat, Jan 31, 1998 at 08:59:16PM -0600 Content-Length: 1004 Lines: 25 > > pts/16 dogcow@zerbina: ~ <7> whois domain.com > > Example Domain (DOMAIN-DOM) > > For use by vendors and authors in > > default configurations, examples, > > This is not the spam-host you're > > looking for. Move along. > > 7, va 35478 > > us > > > > Domain Name: DOMAIN.COM > > > > Administrative Contact, Technical Contact, Zone Contact, Billing Contact: > > Example Domain (DOMAIN-NFO) user@HOST.DOMAIN.COM > > +1 510 540 8000 (FAX) +1 510 548 1891 > > this is actually a private domain, as the contact info is real. > example.com would be a better choice, as Sec noted. > > forever anal-retentive.... To counter-anal (that's an en-dash) your anal-retentive, I would point out that example.com's only hostname resolves to 10.0.0.0, which is a legal private network address. This is bad. In addition, www.example.com points to a real external machine - venera.isi.edu. All of domain.com's hosts (with the exception of the nameservers) point to localhost. From Erwan.David@inria.fr Mon Feb 2 00:07:53 1998 Return-Path: Erwan.David@inria.fr Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA04232 for ; Mon, 2 Feb 1998 00:07:50 -0800 (PST) Received: from gingko.inria.fr (edavid@gingko.inria.fr [128.93.2.61]) by concorde.inria.fr (8.8.7/8.8.5) with ESMTP id JAA03869 for ; Mon, 2 Feb 1998 09:07:31 +0100 (MET) Received: (from edavid@localhost) by gingko.inria.fr (8.8.5/8.8.5) id JAA15734; Mon, 2 Feb 1998 09:07:30 +0100 Message-ID: <19980202090730.10342@gingko.inria.fr> Date: Mon, 2 Feb 1998 09:07:30 +0100 From: Erwan David To: mutt-users@cs.hmc.edu Subject: Re: general lockfile References: <19980130220307.63720@tribe.ping.de> <19980131024521.57916@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980131024521.57916@matrix.42.org>; from Stefan `Sec` Zehl on Sat, Jan 31, 1998 at 02:45:21AM +0100 X-Republicain: =?iso-8859-1?Q?14_pluvi=F4se_an_CCVI_=28Avelinier=29?= Organization: G.I.E. Dyade Content-Length: 746 Lines: 28 Le Sat 31/01/1998, Stefan `Sec` Zehl disait > > move mutt to mutt-real and put the following in an file called mutt: > > #!/bin/sh > > if [ -f $HOME/.vmail.lock ] ; then > echo Vmail is already running, exiting > exit 1 > else > mutt "$@" > fi > > (and chmod a+x it) > > CU, > Sec You'd better use lockfile (comes with procmail). Noting prevents $HOME/.vmail.lock to be created after your test. By the way should'nt your script touch the file to prevent vmail being launched after mutt? -- Erwan David | GIE Dyade, INRIA Domaine de Voluceau GIE Dyade | BP 105, 78153 Le Chesnay CEDEX France --------------------------------------------------------- Je ne parle qu'en mon nom propre, et encore pas toujours. From hazmat@unixshell.com Sun Feb 1 10:26:17 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (hazmat@[204.170.16.210]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA07847 for ; Sun, 1 Feb 1998 10:26:15 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id NAA15921; Sun, 1 Feb 1998 13:25:43 -0500 (EST) Message-ID: <19980201132543.27372@unixshell.com> Date: Sun, 1 Feb 1998 13:25:43 -0500 From: Ken W To: mutt Subject: Re: $point_new variable Mail-Followup-To: mutt References: <19980131163051.62151@unixshell.com> <19980131175703.59924@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980131175703.59924@att.com>; from Vikas Agnihotri on Sat, Jan 31, 1998 at 05:57:03PM -0500 X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X Content-Length: 383 Lines: 16 > folder-hook . "push \t" > ought to do it where TAB (\t) takes you to the first new message Ah, woops. I meant that I UNset it always so it always went to message #1. Thanks for the tip. I set folder-hook . "push =" and it now works fine. Wow, the abilities of Mutt never cease to amaze me... :) -Ken -- hazmat@unixshell.com hazmat@shore.net http://www.shore.net/~hazmat From maccy@c6.hadiko.de Sun Feb 1 04:38:11 1998 Return-Path: maccy@c6.hadiko.de Received: from nz15.rz.uni-karlsruhe.de (nz15.rz.uni-karlsruhe.de [129.13.64.15]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id EAA16370 for ; Sun, 1 Feb 1998 04:38:09 -0800 (PST) Received: from hadic006.hadiko.uni-karlsruhe.de (c6.hadiko.de) [129.13.244.111] (maccy) by nz15.rz.uni-karlsruhe.de with esmtp (Exim 1.80 #4) id 0xyyeX-0003Ef-00; Sun, 1 Feb 1998 13:37:37 +0100 Received: (from maccy@localhost) by c6.hadiko.de (8.8.5/8.8.5) id NAA00286; Sun, 1 Feb 1998 13:37:19 +0100 Message-ID: <19980201133719.52099@c6.hadiko.de> Date: Sun, 1 Feb 1998 13:37:19 +0100 From: Bjoern Jacke To: MUTT Users Subject: Re: [0.89i] Bug fix: extract keys References: <19980131213139.49911@sdd.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980131213139.49911@sdd.hp.com>; from David Ellement on Sat, Jan 31, 1998 at 09:31:39PM -0800 Content-Length: 462 Lines: 14 On 31.01. at 21:31 -0800 David Ellement sent off: > For pgp5, the extract keys command was missing the -a option. Sorry, but have I missed anything? I can only find a Beta8 for Unix and a Beta11 for LinuX and at least this one hast expired for a long time. So why do you care about pgp5 support in Mutt? Will PGP5 ever be released in a final version for Unix? -bj -- e-mail: bjoern.jacke@stud.uni-karlsruhe.de URL(mit PGP-Key): http://b.jacke.home.pages.de From roessler@sobolev.rhein.de Sun Feb 1 18:16:07 1998 Return-Path: roessler@sobolev.rhein.de Received: from riemann.iam.uni-bonn.de (root@riemann.iam.uni-bonn.de [131.220.223.83]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA27431 for ; Sun, 1 Feb 1998 18:16:04 -0800 (PST) Received: (from uucp@localhost) by riemann.iam.uni-bonn.de (8.8.5/8.8.5) with UUCP id DAA28421 for mutt-users@cs.hmc.edu; Mon, 2 Feb 1998 03:09:40 +0100 Received: (from roessler@localhost) by sobolev.rhein.de (8.8.8/8.8.8) id OAA22193 ; Sun, 1 Feb 1998 14:22:05 +0100 Message-ID: <19980201142205.30780@sobolev.rhein.de> Date: Sun, 1 Feb 1998 14:22:05 +0100 From: Thomas Roessler To: MUTT Users Subject: Re: [0.89i] Bug fix: extract keys Mail-Followup-To: MUTT Users References: <19980131213139.49911@sdd.hp.com> <19980201133719.52099@c6.hadiko.de> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=9Ux+11Zm5mwPlX6n X-Mailer: Mutt 0.89.1i In-Reply-To: <19980201133719.52099@c6.hadiko.de> Content-Length: 1251 Lines: 39 --9Ux+11Zm5mwPlX6n Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On Sun, Feb 01, 1998 at 01:37:19PM +0100, Bjoern Jacke wrote: > Sorry, but have I missed anything? I can only find a Beta8 > for Unix and a Beta11 for LinuX and at least this one hast > expired for a long time. So why do you care about pgp5 > support in Mutt? For one, there is the US-only version of PGP 5.*. And then, the folks at pgpi.com are working on a final international version of PGP 5.* for Unix. See www.pgpi.com. tlr --=20 Thomas Roessler =B7 74a353cc0b19 =B7 dg1ktr =B7 http://home.pages.de/~roess= ler/ 2048/CE6AC6C1 =B7 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1 --9Ux+11Zm5mwPlX6n Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3in iQEVAwUBNNR2+9ImKUTOasbBAQGKNggAiaayfbBduqoZ8cc6jyfhzejOtC80Sbjl TI8xx0pdDqupKFDYi9R1afop+hrS9ZzrsaQk21A1eo0mZg/w13K2yhI0wRb01G4p ORLzvNaMVWS9FNHaE0BN0MvuQhZ35VGSc+JAdGFI8cWDG31sG04cqKea2Mu0/AYm Nz+xzNvZxpbde55qDGl/EYzYHNbgghZvlP0PdUZaJ3bASz2LCmhbwzdookH4wuMX Ap4nXoHbJKDJHOkGfSMVcPGTsjeid5ALuM0fyx4S1/pCo8OVDZ4t/Z58V34iyCW9 mJ7ROlYzCm5nfbzN2eDSGisuY/7tbMVDlBjC/kM6zcqyovAUhbfRQA== =QeQX -----END PGP SIGNATURE----- --9Ux+11Zm5mwPlX6n-- From fredr@joshua.rivertown.net Sun Feb 1 07:20:28 1998 Return-Path: fredr@joshua.rivertown.net Received: from joshua.rivertown.net (qmailr@joshua.rivertown.net [204.141.41.5]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id HAA26303 for ; Sun, 1 Feb 1998 07:20:26 -0800 (PST) Received: (qmail 13888 invoked by uid 500); 1 Feb 1998 15:22:50 -0000 Message-ID: <19980201102250.07918@joshua.rivertown.net> Date: Sun, 1 Feb 1998 10:22:50 -0500 From: "Fred B. Ringel" To: Bjoern Jacke Cc: Mutt Users List Subject: Re: [0.89i] Bug fix: extract keys Reply-To: fredr@joshua.rivertown.net References: <19980131213139.49911@sdd.hp.com> <19980201133719.52099@c6.hadiko.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980201133719.52099@c6.hadiko.de>; from Bjoern Jacke on Sun, Feb 01, 1998 at 01:37:19PM +0100 Organization: Rivertown.Net Content-Length: 988 Lines: 22 Recently, Bjoern Jacke had the following to say about Re: [0.89i] Bug fix: extract keys: > On 31.01. at 21:31 -0800 David Ellement sent off: > > For pgp5, the extract keys command was missing the -a option. > > Sorry, but have I missed anything? I can only find a Beta8 for Unix and a > Beta11 for LinuX and at least this one hast expired for a long time. So why > do you care about pgp5 support in Mutt? > > Will PGP5 ever be released in a final version for Unix? > Sure. I've had it for several months now. Check out PGP Inc.'s web site (http://www.pgp.com). It comes in several Unix flavors. Also check out the MIT freeware site. Don't recall the URL, but its somewhere on my PGP Users Home Page (http://pgp.rivertown.net). Fred -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Fred B. Ringel -- Rivertown.Net Internet Access Systems Administrator -- Voice/Fax/Support: +1.914.478.2885 "You tweachewous miscweant!" -- Elmer Fudd From steve@tightrope.demon.co.uk Mon Feb 2 03:22:58 1998 Return-Path: steve@tightrope.demon.co.uk Received: from bbcgate.bbc.co.uk (gatea.bbc.co.uk [132.185.132.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id DAA24871 for ; Mon, 2 Feb 1998 03:22:55 -0800 (PST) Received: from strychnine.bbc.co.uk ([10.199.4.205]) by bbcgate.bbc.co.uk (8.8.8/8.7.2) with ESMTP id LAA27007 for ; Mon, 2 Feb 1998 11:22:47 GMT Received: (from steve@localhost) by strychnine.bbc.co.uk (8.7.6/8.7.3) id KAA21569; Mon, 2 Feb 1998 10:44:53 GMT X-Authentication-Warning: strychnine.bbc.co.uk: steve set sender to steve@tightrope.demon.co.uk using -f Message-ID: <19980202104453.59508@tightrope.demon.co.uk> Date: Mon, 2 Feb 1998 10:44:53 +0000 From: Steve Mynott To: fredr@joshua.rivertown.net, Bjoern Jacke Cc: Mutt Users List Subject: Re: [0.89i] Bug fix: extract keys Mail-Followup-To: fredr@joshua.rivertown.net, Bjoern Jacke , Mutt Users List References: <19980131213139.49911@sdd.hp.com> <19980201133719.52099@c6.hadiko.de> <19980201102250.07918@joshua.rivertown.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980201102250.07918@joshua.rivertown.net>; from Fred B. Ringel on Sun, Feb 01, 1998 at 10:22:50AM -0500 X-Operating-System: Linux strychnine 2.0.18 Content-Length: 821 Lines: 21 On Sun, Feb 01, 1998 at 10:22:50AM -0500, Fred B. Ringel wrote: > > On 31.01. at 21:31 -0800 David Ellement sent off: > > Sorry, but have I missed anything? I can only find a Beta8 for Unix and a > > Beta11 for LinuX and at least this one hast expired for a long time. So why > > do you care about pgp5 support in Mutt? > > > > Will PGP5 ever be released in a final version for Unix? > > > Sure. I've had it for several months now. Check out PGP Inc.'s web > site (http://www.pgp.com). It comes in several Unix flavors. Also check out AFAIK the only source version of PGP 5.0i is the beta5 which is really buggy. The non-US export Linux binary is better, but there is no source available. PGP 5 generates non pgp 2.6 compatable keys and is not compatable with pgp 2.6 at the command line level. -- Steve Mynott From tim@shell.futuresouth.com Mon Feb 2 05:10:41 1998 Return-Path: tim@shell.futuresouth.com Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id FAA21472 for ; Mon, 2 Feb 1998 05:10:39 -0800 (PST) Received: (from tim@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id HAA16175; Mon, 2 Feb 1998 07:10:36 -0600 (CST) Message-ID: <19980202071036.42510@futuresouth.com> Date: Mon, 2 Feb 1998 07:10:36 -0600 From: Tim Tsai To: Mutt Users List Subject: sendmail voyeur mode References: <19980131213139.49911@sdd.hp.com> <19980201133719.52099@c6.hadiko.de> <19980201102250.07918@joshua.rivertown.net> <19980202104453.59508@tightrope.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Content-Length: 203 Lines: 8 How can I turn on sendmail's voyeur mode from within mutt? I would like to be able to do this on demand, instead of turning it on automatically. With BSD Mail, I just type "Mail -v ...". Thanks, Tim From maccy@c6.hadiko.de Sun Feb 1 06:47:40 1998 Return-Path: maccy@c6.hadiko.de Received: from nz15.rz.uni-karlsruhe.de (nz15.rz.uni-karlsruhe.de [129.13.64.15]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id GAA24243; Sun, 1 Feb 1998 06:47:38 -0800 (PST) Received: from hadic006.hadiko.uni-karlsruhe.de (c6.hadiko.de) [129.13.244.111] (maccy) by nz15.rz.uni-karlsruhe.de with esmtp (Exim 1.80 #4) id 0xz0fr-0004JE-00; Sun, 1 Feb 1998 15:47:07 +0100 Received: (from maccy@localhost) by c6.hadiko.de (8.8.5/8.8.5) id PAA00565; Sun, 1 Feb 1998 15:46:51 +0100 Message-ID: <19980201154651.38929@c6.hadiko.de> Date: Sun, 1 Feb 1998 15:46:51 +0100 From: Bjoern Jacke To: MUTT Users Cc: Michael Elkins Subject: attachment feature request Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=rl02BVI9TCfPar48 X-Mailer: Mutt 0.89i Content-Length: 879 Lines: 34 --rl02BVI9TCfPar48 Content-Type: text/plain; charset=us-ascii Hi! I just wanted to attach a whole directory to a mail. I climbed up to the directory with the TAB-key and thought: 'what a cool mailer mutt is'. Then I only wanted to say /bla/bla/bla/* and mutt told me: /bla/bla/bla/*: No such file or directory (errno = 2) _Why can't mutt accept wildcards?!?_ Is there a trick to attach a whole directory? -- e-mail: bjoern.jacke@stud.uni-karlsruhe.de URL(mit PGP-Key): http://b.jacke.home.pages.de --rl02BVI9TCfPar48 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3i iQCVAwUBNNSK2qdtf/tbTq/xAQEh+wP/Z6qFXkJNkFBOTG/I03Gv82BS5Mb2VifL LNO2xffAdNfLYqdGHfcazMo9+3ziftpl/LBnatTkHfHxSJGYMq6j6b6kzeAUObZ1 TxMsZeIsgw4QxWzw0V/2Ykivow3AZLWSSHdWEeiipolxpZFl3bUoiFGZc8yW3qxQ UyJQ/dfqxhg= =Ke3c -----END PGP SIGNATURE----- --rl02BVI9TCfPar48-- From bonkey@matylda.silesia.linux.org.pl Sun Feb 1 12:07:18 1998 Return-Path: bonkey@matylda.silesia.linux.org.pl Received: from pikus.wnaft.agh.edu.pl (uucp@pikus.wnaft.agh.edu.pl [149.156.117.124]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA15056 for ; Sun, 1 Feb 1998 12:07:11 -0800 (PST) Received: from matylda.UUCP (uucp@localhost) by pikus.wnaft.agh.edu.pl (8.8.8/8.8.8) with bsmtp id VAA15478 for mutt-users@cs.hmc.edu; Sun, 1 Feb 1998 21:11:13 +0100 Received: from localhost (bonkey@localhost) by matylda.silesia.linux.org.pl (8.8.5/8.8.7) with SMTP id UAA01545 for ; Sun, 1 Feb 1998 20:56:41 +0100 Date: Sun, 1 Feb 1998 20:56:39 +0100 (MET) From: Daniel Bauke To: Mutt mail list Subject: Segmentation fault while sending a message Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-1612769306-886362999=:720" Content-Length: 4782 Lines: 93 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --8323328-1612769306-886362999=:720 Content-Type: TEXT/PLAIN; charset=US-ASCII Hii, I've got a problem with mutt... Sounds silly to me because I never expected that I would have to say it ;). It happens when I try to send any message -- mutt exits with a segmentation fault. Few days ago I've upgraded my mutt from 0.88 into 0.89 and the day after into 0.89i. I was working on the kernel 2.0.32 that time but about dwo days ago I patched it into a 2.0.33 with some patches from Linux Mama (ext2 compression, AMD K5 cleanup, Joilet and few cosmetic changes). I'm sure that mutt 0.89 worked on the 2.0.32 and I think that the problem might be in that 2.0.33, but when I tried to run mutt on a kernel 2.0.32 which I got straight from the Red Hat distribution (I've got 4.2) the error occured also. I've tried many configurations eg. pure 0.89 on the redhat kernel, patch into 0.89.1i with my 2.0.33 patched kernel, I also tried to add as many patches I could find and... nothing. Always the same error message. I attached the `logfile' from gdb, but I'm not a programmer, so I don't even understand it ;). Well, I hope it isn't a big problem. I hope because pine is terrible to me after I got used to using mutt :). Daniel `bonkey' Bauke -- Please be indulgent -- English is NOT my native language. --8323328-1612769306-886362999=:720 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=log-error Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: TXV0dCAwLjg5aSwgQ29weXJpZ2h0IChDKSAxOTk2LTggTWljaGFlbCBSLiBF bGtpbnMgPG1lQGNzLmhtYy5lZHU+DQpNdXR0IGNvbWVzIHdpdGggQUJTT0xV VEVMWSBOTyBXQVJSQU5UWTsgZm9yIGRldGFpbHMgdHlwZSBgbXV0dCAtdnYn Lg0KTXV0dCBpcyBmcmVlIHNvZnR3YXJlLCBhbmQgeW91IGFyZSB3ZWxjb21l IHRvIHJlZGlzdHJpYnV0ZSBpdA0KdW5kZXIgY2VydGFpbiBjb25kaXRpb25z OyB0eXBlIGBtdXR0IC12dicgZm9yIGRldGFpbHMuDQoNClN5c3RlbSBpbmZv OiBMaW51eCAyLjAuMzMgW3VzaW5nIHNsYW5nIDk5MzhdDQoNCkNvbXBpbGUg dGltZSBkZWZpbml0aW9uczoNCi1ET01BSU4NCi1ISURERU5fSE9TVCAgLUhP TUVTUE9PTCAgK1VTRV9TRVRHSUQgICtVU0VfRE9UTE9DSyAgK1VTRV9GQ05U TCAgLVVTRV9GTE9DSw0KK1VTRV9QT1AgICtIQVZFX1JFR0NPTVAgIC1VU0Vf R05VX1JYICArSEFWRV9DT0xPUiAgLUJVRkZZX1NJWkUNClNFTkRNQUlMPSIv dXNyL3NiaW4vc2VuZG1haWwiDQpNQUlMUEFUSD0iL3Zhci9zcG9vbC9tYWls Ig0KU0hBUkVESVI9Ii91c3IvbG9jYWwvc2hhcmUiDQpJU1BFTEw9Ii91c3Iv YmluL2lzcGVsbCINCl9QR1BQQVRIPSIvdXNyL2Jpbi9wZ3AiDQpGZWF0dXJl IHBhdGNoOiBxdW90ZV9zaWcgMC44OCBieSBEdW5jYW4gU2FyZ2VhbnQNCkZl YXR1cmUgcGF0Y2g6IGNvbG9yX2F0dHIgMC44OC4xNSBieSBTdGVmYW4gYFNl Y2AgWmVobA0KRmVhdHVyZSBwYXRjaDogY29uZGVuc2VfcGdwIDAuODguMTUg YnkgU3RlZmFuIGBTZWNgIFplaGwNCkZlYXR1cmUgcGF0Y2g6IGJvbGRfdW5k ZXJsaW5lIDAuODguMTIgYnkgQnlyaWFsIEplbnNlbg0KDQoqIHdpdGhvdXQg c3ViamVjdDoNCg0KU2VuZGluZyBtZXNzYWdlLi4uDQpQcm9ncmFtIHJlY2Vp dmVkIHNpZ25hbCBTSUdTRUdWLCBTZWdtZW50YXRpb24gZmF1bHQuDQoweDgw NWFmNjggaW4gbXV0dF9pc19tYWlsX2xpc3QgKGFkZHI9MHg4MGY0YTU4KSBh dCBoZHJsaW5lLmM6MzgNCjM4ICAgICAgICAgIGlmIChzdHJuY2FzZWNtcCAo YWRkci0+bWFpbGJveCwgcC0+ZGF0YSwgc3RybGVuIChwLT5kYXRhKSkgPT0g MCkNCihnZGIpDQoNCiogd2l0aCBzdWJqZWN0Og0KDQpTZW5kaW5nIG1lc3Nh Z2UuLi4NClByb2dyYW0gcmVjZWl2ZWQgc2lnbmFsIFNJR1NFR1YsIFNlZ21l bnRhdGlvbiBmYXVsdC4NCjB4ODA1YWY2OCBpbiBtdXR0X2lzX21haWxfbGlz dCAoYWRkcj0weDgwZjRhNTgpIGF0IGhkcmxpbmUuYzozOA0KaGRybGluZS5j OjM4OiBObyBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5Lg0KKGdkYikNCg0KPT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT0NCk11dHQgMC44OSwgQ29weXJpZ2h0IChDKSAxOTk2LTggTWljaGFl bCBSLiBFbGtpbnMgPG1lQGNzLmhtYy5lZHU+DQpNdXR0IGNvbWVzIHdpdGgg QUJTT0xVVEVMWSBOTyBXQVJSQU5UWTsgZm9yIGRldGFpbHMgdHlwZSBgbXV0 dCAtdnYnLg0KTXV0dCBpcyBmcmVlIHNvZnR3YXJlLCBhbmQgeW91IGFyZSB3 ZWxjb21lIHRvIHJlZGlzdHJpYnV0ZSBpdA0KdW5kZXIgY2VydGFpbiBjb25k aXRpb25zOyB0eXBlIGBtdXR0IC12dicgZm9yIGRldGFpbHMuDQoNClN5c3Rl bSBpbmZvOiBMaW51eCAyLjAuMzMgW3VzaW5nIHNsYW5nIDk5MzhdDQoNCkNv bXBpbGUgdGltZSBkZWZpbml0aW9uczoNCi1ET01BSU4NCi1ISURERU5fSE9T VCAgLUhPTUVTUE9PTCAgK1VTRV9TRVRHSUQgICtVU0VfRE9UTE9DSyAgK1VT RV9GQ05UTCAgLVVTRV9GTE9DSw0KK1VTRV9QT1AgICtIQVZFX1JFR0NPTVAg IC1VU0VfR05VX1JYICArSEFWRV9DT0xPUiAgLUJVRkZZX1NJWkUNClNFTkRN QUlMPSIvdXNyL3NiaW4vc2VuZG1haWwiDQpNQUlMUEFUSD0iL3Zhci9zcG9v bC9tYWlsIg0KU0hBUkVESVI9Ii91c3IvbG9jYWwvc2hhcmUiDQpJU1BFTEw9 Ii91c3IvYmluL2lzcGVsbCINCg0KDQpQcm9ncmFtIHJlY2VpdmVkIHNpZ25h bCBTSUdTRUdWLCBTZWdtZW50YXRpb24gZmF1bHQuDQoweDgwNWE1MGMgaW4g bXV0dF9pc19tYWlsX2xpc3QgKGFkZHI9MHg4MGViMmM4KSBhdCBoZHJsaW5l LmM6MzUNCjM1ICAgICAgICAgIGlmIChzdHJuY2FzZWNtcCAoYWRkci0+bWFp bGJveCwgcC0+ZGF0YSwgc3RybGVuIChwLT5kYXRhKSkgPT0gMCkNCihnZGIp DQo= --8323328-1612769306-886362999=:720-- From byrial@post3.tele.dk Sun Feb 1 16:05:05 1998 Return-Path: byrial@post3.tele.dk Received: from mail-in1.inet.tele.dk (mail-in1.inet.tele.dk [194.182.148.158]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id QAA23542 for ; Sun, 1 Feb 1998 16:05:01 -0800 (PST) Received: (qmail 26716 invoked from network); 2 Feb 1998 00:04:54 -0000 Received: from post3.tele.dk (194.239.134.166) by mail-in1.inet.tele.dk with SMTP; 2 Feb 1998 00:04:54 -0000 Received: from ask.ask ([194.239.129.22]) by post3.tele.dk (Netscape Mail Server v2.02) with ESMTP id AAB60998 for ; Mon, 2 Feb 1998 01:04:52 +0100 Received: (qmail 546 invoked by uid 500); 2 Feb 1998 00:01:05 -0000 Message-ID: <19980202010105.47002@ask.tele.dk> Date: Mon, 2 Feb 1998 01:01:05 +0100 From: Byrial Jensen To: Daniel Bauke , Mutt mail list Cc: Byrial Jensen Subject: Re: Segmentation fault while sending a message Mail-Followup-To: Daniel Bauke , Mutt mail list References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Daniel Bauke on Sun, Feb 01, 1998 at 08:56:39PM +0100 Content-Length: 1362 Lines: 37 On Sun, Feb 01, 1998 at 08:56:39PM +0100, Daniel Bauke wrote: > Hii, > > I've got a problem with mutt... Sounds silly to me because I never > expected that I would have to say it ;). It happens when I try to send > any message -- mutt exits with a segmentation fault. > I've tried many configurations eg. pure 0.89 on the redhat kernel, > patch into 0.89.1i with my 2.0.33 patched kernel, I also tried to add > as many patches I could find and... nothing. Always the same error > message. I attached the `logfile' from gdb, but I'm not a programmer, > so I don't even understand it ;). > Sending message... > Program received signal SIGSEGV, Segmentation fault. > 0x805af68 in mutt_is_mail_list (addr=0x80f4a58) at hdrline.c:38 > 38 if (strncasecmp (addr->mailbox, p->data, strlen (p->data)) == 0) > (gdb) This code should not be able to give a segmentation fault as far as I can see. Maybe some of the source files are not properly recompiled after applying a patch. That can happen because not all dependecies are stated in the Makefile. So if you don't already have tried it, do a "make clean; make", and see if this helps. If this does not help, then it may be neccesary with more information from gdb. Try to send the output of these commands at gdb prompt after seg fault: bt print *addr print *p Best regards - Byrial From bonkey@matylda.silesia.linux.org.pl Mon Feb 2 00:29:25 1998 Return-Path: bonkey@matylda.silesia.linux.org.pl Received: from pikus.wnaft.agh.edu.pl (uucp@pikus.wnaft.agh.edu.pl [149.156.117.124]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA10006 for ; Mon, 2 Feb 1998 00:29:18 -0800 (PST) Received: from matylda.UUCP (uucp@localhost) by pikus.wnaft.agh.edu.pl (8.8.8/8.8.8) with bsmtp id JAA10428; Mon, 2 Feb 1998 09:33:17 +0100 Received: from localhost (bonkey@localhost) by matylda.silesia.linux.org.pl (8.8.5/8.8.7) with SMTP id JAA06800; Mon, 2 Feb 1998 09:21:39 +0100 Date: Mon, 2 Feb 1998 09:21:37 +0100 (MET) From: Daniel Bauke To: Byrial Jensen cc: Mutt mail list Subject: Re: Segmentation fault while sending a message In-Reply-To: <19980202010105.47002@ask.tele.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Length: 4307 Lines: 106 On Mon, 2 Feb 1998, Byrial Jensen wrote: > Maybe some of the source files are not properly recompiled after > applying a patch. That can happen because not all dependecies are > stated in the Makefile. So if you don't already have tried it, do a > "make clean; make", and see if this helps. Unfortunately... I unpacked archive with mutt-0.89, patched it into 0.89i, next into 0.89.1i and then added some nice patches from Stefan `Sec` Zehl and than those from David Eisenbud. After it I run =2E/configure with slang, pop and locales `support'. and then `make install'. And the same: Sending message... Program received signal SIGSEGV, Segmentation fault. 0x805aea4 in mutt_is_mail_list (addr=3D0x80f8858) at hdrline.c:38 38 if (strncasecmp (addr->mailbox, p->data, strlen (p->data)) =3D= =3D 0) (gdb) bt #0 0x805aea4 in mutt_is_mail_list (addr=3D0x80f8858) at hdrline.c:38 #1 0x8070b7e in mutt_is_list_recipient (a=3D0x80f8858) at send.c:761 #2 0x8070bb5 in mutt_set_followup_to (e=3D0x80f8788) at send.c:770 #3 0x80715d4 in ci_send_message (flags=3D0, msg=3D0x80f84c0, tempfile=3D0x= 0, cur=3D0x0) at send.c:1159 #4 0x8053c66 in mutt_index_menu () at curs_main.c:1317 #5 0x805f578 in main (argc=3D1, argv=3D0xbffffa64) at main.c:611 #6 0x804951b in _start () (gdb) print *addr $1 =3D {mailbox =3D 0x80f8880 "bonkey", adl =3D 0x0, host =3D 0x80f8648 "ma= tylda.silesia.linux.org.pl", personal =3D 0x80f8630 "Daniel Bauke", next =3D 0x0} (gdb) print *p $2 =3D {data =3D 0x0, next =3D 0x0} mutt -v: Mutt 0.89.1i, Copyright (C) 1996-8 Michael R. Elkins Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System info: Linux 2.0.33 [using slang 9938] Compile time definitions: -DOMAIN -HIDDEN_HOST -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR -BUFFY_SIZE SENDMAIL=3D"/usr/sbin/sendmail" MAILPATH=3D"/var/spool/mail" SHAREDIR=3D"/usr/local/share" ISPELL=3D"/usr/bin/ispell" _PGPPATH=3D"/usr/bin/pgp" Feature patch: quote_sig 0.88 by Duncan Sargeant Feature patch: color_attr 0.88.15 by Stefan `Sec` Zehl Feature patch: condense_pgp 0.88.15 by Stefan `Sec` Zehl Feature patch: bold_underline 0.88.12 by Byrial Jensen BUT, I noticed another two strange things. First, when I try to save a message, mutt also fall down with similar error: Program received signal SIGSEGV, Segmentation fault. 0x805aea4 in mutt_is_mail_list (addr=3D0x810b1d8) at hdrline.c:38 38 if (strncasecmp (addr->mailbox, p->data, strlen (p->data)) =3D= =3D 0) (gdb) bt #0 0x805aea4 in mutt_is_mail_list (addr=3D0x810b1d8) at hdrline.c:38 #1 0x805ccee in mutt_default_save (path=3D0xbfffee78 "=A0=EF=FF=BF=CA=FE",= pathlen=3D255, env=3D0x810ae70) at hook.c:215 #2 0x804e56c in mutt_save_message (h=3D0x810ae28, delete=3D1, decode=3D0, = redraw=3D0x80f4d9c) at commands.c:511 #3 0x8052f14 in mutt_index_menu () at curs_main.c:905 #4 0x805f578 in main (argc=3D1, argv=3D0xbffffa64) at main.c:611 #5 0x804951b in _start () (gdb) print *addr $1 =3D {mailbox =3D 0x810b210 "pso-l", adl =3D 0x0, host =3D 0x810b1f0 "lis= ts.hep.utexas.edu", personal =3D 0x0, next =3D 0x0} (gdb) print *p $2 =3D {data =3D 0x0, next =3D 0x0} Next is (or rather `was'): when I tried to send an email as a root... It worked perfectly. So, I changed his .muttrc file into my personal and then mutt crashed with this `funny' message. Now I know where I should find the reasons of his `illness'. Thanks for the advice. I'll send a report, as soon as I find a bug. Daniel `bonkey' Bauke PS. While ago I tried to run `make dep' and there were a lot of messages looking like this: In file included from mutt_menu.h:23, from ./recvattach.c:21: keymap.h:88: keymap_defs.h: No such file or directory So, I changed configuration into ncurses (I thought that slang might have been the reason, but don't laugh at me if I did something stupid -- I'm not a programmer ;) and the error occured also. And then I tried it on the `pure' 0.89 and there was the same problem. Is it normal? From mutt-users-request@cs.hmc.edu Mon Feb 2 10:10:51 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id KAA11321 for me@cs.hmc.edu; Mon, 2 Feb 1998 10:10:50 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 10:10:50 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: bonkey@matylda.silesia.linux.org.pl Message-ID: <19980202180957.07938@matylda.silesia.linux.org.pl> Date: Mon, 2 Feb 1998 18:09:57 +0100 From: Daniel Bauke To: Mutt User List Cc: Byrial Jensen Subject: Segmentation fault while sending a message Mail-Followup-To: Mutt User List , Byrial Jensen References: <19980202010105.47002@ask.tele.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Daniel Bauke on Mon, Feb 02, 1998 at 09:21:37AM +0100 X-Operating-System: Linux 2.0.33 i586 X-Writing-Started: Mon Feb 2 17:50:34 MET 1998 Resent-Message-ID: <"M_m7RB.A.-1G.6Hg10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu Content-Length: 1116 Lines: 30 02 Feb 98 (Monday), 09:21:37AM +0100, Daniel Bauke: > Next is (or rather `was'): when I tried to send an email as a > root... It worked perfectly. So, I changed his .muttrc file into my > personal and then mutt crashed with this `funny' message. Now I know > where I should find the reasons of his `illness'. > > I'll send a report, as soon as I find a bug. Well... I don't know how to say it... My fault. I tried to improve mutt's great advantages and set: lists $mailboxes Because I was to lazy (or maybe to smart ;) to rewrite it. Now everything is OK. Sorry for bothering you with this stupid problem. Despite this error I'm still thinking about similar solution. I want to join $lists, $mailboxes and filters from my procmail in one utility. I don't like to change same things in three places. And it would be good if mutt be able to show how many new messages are in the mailboxes. And #2: what do you think about score file? My friend told me that it could make him change emacs into mutt. ;) Any suggestions? Daniel `bonkey' Bauke From Ulli.Horlacher@RUS.Uni-Stuttgart.DE Sun Feb 1 12:04:47 1998 Return-Path: Ulli.Horlacher@RUS.Uni-Stuttgart.DE Received: from noc.belwue.de (root@noc.BelWue.DE [129.143.2.1]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA14899 for ; Sun, 1 Feb 1998 12:04:45 -0800 (PST) Received: from bofh.belwue.de (bofh.BelWue.DE [129.143.2.24]) by noc.belwue.de (8.8.8/8.8.8) with ESMTP id VAA20958 for ; Sun, 1 Feb 1998 21:04:19 +0100 (MET) env-from (framstag@bofh.belwue.de) Received: (from framstag@localhost) by bofh.belwue.de (8.8.8/8.8.7) id VAA14988; Sun, 1 Feb 1998 21:04:18 +0100 (MET) Message-ID: <19980201210418.38528@bofh.belwue.de> Date: Sun, 1 Feb 1998 21:04:18 +0100 From: Ulli Horlacher To: mutt-users@turing.cs.hmc.edu Subject: [0.89i] empty_lines feature-patch Mail-Followup-To: mutt-users@turing.cs.hmc.edu Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=1yeeQ81UyVL57Vl7 X-Mailer: Mutt 0.89i Content-Length: 2576 Lines: 75 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii I have a lot of hardcore elm users, which refuse to upgrade to mutt mainly because of one reason: the index does not look like elm, there are too few empty lines before. Call it stupid (I do so), but they will not use mutt and stick with their ancient versions of elm which cannot even use MIME, Umlauts or pgp. So I wrote a little patch to offer a new variable : set empty_lines=2 and they are happy :-) Don't get confused with the 0.89f version name in the patch below. I use it only for internal reasons. This patch will apply to 0.89i and 0.89.1i. -- \ Ulli 'Framstag' Horlacher \ BelWue-Koordination \ framstag@belwue.de \ \ Universitaet Stuttgart \ Allmandring 30 \ D-70550 Stuttgart \ Germany \ \ SAFT://saft.belwue.de/framstag \ HTTP://www.belwue.de/ \ \ "X.500: Security through Complexity" - Juergen G. \ --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mutt-0.89i-empty_lines.patch" --- /tmp/mutt-0.89f/globals.h Fri Jan 23 08:08:55 1998 +++ globals.h Sat Jan 31 10:31:03 1998 @@ -99,6 +99,7 @@ WHERE char EscChar[2] INITVAL ("~"); /* $escape, used for $editor=builtin */ WHERE unsigned short Counter INITVAL (0); +WHERE short Empty_Lines INITVAL (0); WHERE short HistSize INITVAL (10); WHERE short PagerContext INITVAL (0); WHERE short PagerIndexLines INITVAL (0); --- /tmp/mutt-0.89f/init.h Wed Jan 28 16:27:54 1998 +++ init.h Sat Jan 31 10:31:03 1998 @@ -81,6 +81,7 @@ { "edit_forward", DT_QUAD, R_NONE, (void *) OPT_EDITFORWARD, 0 }, { "edit_hdrs", DT_BOOL, R_NONE, (void *) OPTEDITHDRS, 0 }, { "editor", DT_PATH, R_NONE, S_DECL(Editor) }, + { "empty_lines", DT_NUM, R_NONE, &Empty_Lines }, { "escape", DT_STR, R_NONE, S_DECL(EscChar) }, { "fast_reply", DT_BOOL, R_NONE, (void *) OPTFASTREPLY, 0 }, { "fcc_attach", DT_BOOL, R_NONE, (void *) OPTFCCATTACH, 0 }, --- /tmp/mutt-0.89f/menu.c Fri Jan 23 08:08:56 1998 +++ menu.c Sat Jan 31 10:36:49 1998 @@ -104,7 +104,7 @@ /* clear() doesn't optimize screen redraws */ move (0, 0); clrtobot (); - + if (option (OPTHELP)) { SETCOLOR (MT_COLOR_STATUS); @@ -118,7 +118,13 @@ menu->offset = option (OPTSTATUSONTOP) ? 1 : 0; menu->pagelen = LINES - 2; } - + + if (Empty_Lines > 0 && Empty_Lines < 5) + { + menu->offset += Empty_Lines; + menu->pagelen -= 2*Empty_Lines; + } + mutt_show_error (); menu->redraw = REDRAW_INDEX | REDRAW_STATUS; --1yeeQ81UyVL57Vl7-- From eisenbud@allspice.cs.swarthmore.edu Sun Feb 1 13:52:41 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA25263 for ; Sun, 1 Feb 1998 13:52:39 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id QAA08065; Sun, 1 Feb 1998 16:52:38 -0500 (EST) Message-ID: <19980201165238.15881@cs.swarthmore.edu> Date: Sun, 1 Feb 1998 16:52:38 -0500 From: Daniel Eisenbud To: Mutt Users List Subject: [0.89*] bugfix: memory leak of "Mail-Followup-To:" addresses Mail-Followup-To: Mutt Users List Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=r5Pyd7+fXNt84Ff3 X-Mailer: Mutt 0.89.1i Content-Length: 1178 Lines: 33 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Mutt was leaking potentially a lot of memory by failing to deallocate the addresses it read in Mail-Followup-To headers - whoever added recognition of this header forgot to deallocate them at the end. It was leaking about 80k each time I changed out of my =mutt mailbox (which is admittedly about 8 megabytes...) This patch fixes that. It should apply to any variant of 0.89 or 0.89.1. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.de.mail_followup_to-leak.1" diff -durp mutt-0.89.1i/lib.c mutt-0.89.1i.new/lib.c --- mutt-0.89.1i/lib.c Fri Jan 23 02:08:55 1998 +++ mutt-0.89.1i.new/lib.c Sun Feb 1 16:17:47 1998 @@ -448,6 +448,7 @@ void mutt_free_envelope (ENVELOPE **p) mutt_free_address (&(*p)->sender); mutt_free_address (&(*p)->from); mutt_free_address (&(*p)->reply_to); + mutt_free_address (&(*p)->mail_followup_to); safe_free ((void **) &(*p)->subject); safe_free ((void **) &(*p)->message_id); mutt_free_list (&(*p)->references); --r5Pyd7+fXNt84Ff3-- From eisenbud@allspice.cs.swarthmore.edu Sun Feb 1 18:35:06 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA02839 for ; Sun, 1 Feb 1998 18:34:58 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id VAA22665; Sun, 1 Feb 1998 21:34:44 -0500 (EST) Message-ID: <19980201213444.19525@cs.swarthmore.edu> Date: Sun, 1 Feb 1998 21:34:44 -0500 From: Daniel Eisenbud To: Mutt Users List Subject: Re: [0.89*] bugfix: memory leak of regular expressions from pattern.c Mail-Followup-To: Mutt Users List References: <19980201165238.15881@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=ReaqsoxgOBHFXBhH X-Mailer: Mutt 0.89.1i In-Reply-To: <19980201165238.15881@cs.swarthmore.edu>; from Daniel Eisenbud on Sun, Feb 01, 1998 at 04:52:38PM -0500 Content-Length: 2786 Lines: 85 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Here's a patch for another memory leak. The code in pattern.c was failing to free regular expressions it compiled. This one leaked a much smaller amount of memory, but it could still be significant if you did a lot of limiting and searching. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.de.pattern-regexp-leak.1" Only in mutt-0.89.1i: .pure diff -durp mutt-0.89.1i.orig/pattern.c mutt-0.89.1i/pattern.c --- mutt-0.89.1i.orig/pattern.c Tue Jan 27 04:04:34 1998 +++ mutt-0.89.1i/pattern.c Sun Feb 1 21:30:32 1998 @@ -48,7 +48,7 @@ typedef struct pattern_t int maxmsg; struct pattern_t *next; struct pattern_t *child; /* arguments to logical op */ - regex_t rx; + regex_t *rx; } pattern_t; static const char *eat_regexp (pattern_t *pat, const char *s, char *, size_t); @@ -217,11 +217,13 @@ eat_regexp (pattern_t *pat, const char * ps = mutt_extract_token (buf, sizeof (buf), s, expn, sizeof (expn), M_PATTERN | M_COMMENT | M_NULL); - - if ((r = REGCOMP (&pat->rx, buf, REG_NEWLINE | REG_NOSUB | mutt_which_case (buf))) != 0) + + pat->rx = safe_malloc (sizeof (regex_t)); + if ((r = REGCOMP (pat->rx, buf, REG_NEWLINE | REG_NOSUB | mutt_which_case (buf))) != 0) { - regerror (r, &pat->rx, err, errlen); - regfree (&pat->rx); + regerror (r, pat->rx, err, errlen); + regfree (pat->rx); + safe_free ((void **) &pat->rx); return NULL; } @@ -413,6 +415,11 @@ static void mutt_pattern_free (pattern_t tmp = *pat; *pat = (*pat)->next; + if (tmp->rx) + { + regfree (tmp->rx); + safe_free ((void **) &tmp->rx); + } if (tmp->child) mutt_pattern_free (&tmp->child); safe_free ((void **) &tmp); @@ -611,9 +618,9 @@ static int mutt_pattern_exec (struct pat case M_DATE_RECEIVED: return (pat->not ^ (h->received >= pat->notbefore && h->received <= pat->notafter)); case M_BODY: - return (pat->not ^ msg_search (&pat->rx, buf, sizeof (buf), 0, h->msgno)); + return (pat->not ^ msg_search (pat->rx, buf, sizeof (buf), 0, h->msgno)); case M_HEADER: - return (pat->not ^ msg_search (&pat->rx, buf, sizeof (buf), 1, h->msgno)); + return (pat->not ^ msg_search (pat->rx, buf, sizeof (buf), 1, h->msgno)); default: buf[0] = 0; switch (pat->op) @@ -643,7 +650,7 @@ static int mutt_pattern_exec (struct pat pat->op); return (-1); } - return ((regexec (&pat->rx, buf, 0, NULL, 0) == 0) ^ pat->not); + return ((regexec (pat->rx, buf, 0, NULL, 0) == 0) ^ pat->not); } /* not reached */ --ReaqsoxgOBHFXBhH-- From eisenbud@allspice.cs.swarthmore.edu Sun Feb 1 22:01:30 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id WAA29958 for ; Sun, 1 Feb 1998 22:01:24 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id BAA26784; Mon, 2 Feb 1998 01:01:23 -0500 (EST) Message-ID: <19980202010122.31159@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 01:01:22 -0500 From: Daniel Eisenbud To: Mutt Users List Subject: Re: [0.89*] bugfix: memory leak of mailing list addresses Mail-Followup-To: Mutt Users List References: <19980201165238.15881@cs.swarthmore.edu> <19980201213444.19525@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=r5Pyd7+fXNt84Ff3 X-Mailer: Mutt 0.89.1i In-Reply-To: <19980201213444.19525@cs.swarthmore.edu>; from Daniel Eisenbud on Sun, Feb 01, 1998 at 09:34:44PM -0500 Content-Length: 874 Lines: 32 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii When one does list-reply, there is a small memory leak. Try the attached patch. -Daniel --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.de.list-reply-leak.1" --- mutt-0.89.1i.orig/send.c Sat Jan 31 08:13:06 1998 +++ mutt-0.89.1i/send.c Mon Feb 2 00:53:23 1998 @@ -520,8 +520,13 @@ static int default_to (ADDRESS **to, ENV static int fetch_recips (ENVELOPE *out, ENVELOPE *in, int flags) { + ADDRESS *tmp; if (flags & SENDLISTREPLY) - rfc822_append (&out->to, find_mailing_lists (in->to, in->cc)); + { + tmp = find_mailing_lists (in->to, in->cc); + rfc822_append (&out->to, tmp); + mutt_free_address (&tmp); + } else { if (default_to (&out->to, in, flags & SENDGROUPREPLY) == -1) --r5Pyd7+fXNt84Ff3-- From eisenbud@allspice.cs.swarthmore.edu Sun Feb 1 22:30:21 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id WAA08102 for ; Sun, 1 Feb 1998 22:30:19 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id BAA27048; Mon, 2 Feb 1998 01:28:51 -0500 (EST) Message-ID: <19980202012851.09614@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 01:28:51 -0500 From: Daniel Eisenbud To: Mutt Users List Subject: Re: [0.89*] bugfix: memory leak in send menu Mail-Followup-To: Mutt Users List References: <19980201165238.15881@cs.swarthmore.edu> <19980201213444.19525@cs.swarthmore.edu> <19980202010122.31159@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=XsQoSWH+UP9D9v3l X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202010122.31159@cs.swarthmore.edu>; from Daniel Eisenbud on Mon, Feb 02, 1998 at 01:01:23AM -0500 Content-Length: 832 Lines: 36 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii The attached patch fixes a memory leak in the send menu. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.de.send-menu-leak.1" --- mutt-0.89.1i.orig/compose.c Fri Jan 23 02:08:55 1998 +++ mutt-0.89.1i/compose.c Mon Feb 2 01:15:40 1998 @@ -795,13 +795,13 @@ int mutt_send_menu (HEADER *msg, /* st idx[i]->content->next = idx[i + 1]->content; idx[i]->content->next = NULL; msg->content = idx[0]->content; + for (i = 0; i < idxlen; i++) + safe_free ((void **) &idx[i]); } else msg->content = NULL; safe_free ((void **) &idx); - idxlen = 0; - idxmax = 0; return (r); } --XsQoSWH+UP9D9v3l-- From eisenbud@allspice.cs.swarthmore.edu Sun Feb 1 23:48:24 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id XAA29005 for ; Sun, 1 Feb 1998 23:48:20 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id CAA28071; Mon, 2 Feb 1998 02:46:46 -0500 (EST) Message-ID: <19980202024646.61427@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 02:46:46 -0500 From: Daniel Eisenbud To: Mutt Users List Subject: Re: [0.89*] bugfix: memory leak and bug in remove_user() Mail-Followup-To: Mutt Users List References: <19980201165238.15881@cs.swarthmore.edu> <19980201213444.19525@cs.swarthmore.edu> <19980202010122.31159@cs.swarthmore.edu> <19980202012851.09614@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=liOOAslEiF7prFVr X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202012851.09614@cs.swarthmore.edu>; from Daniel Eisenbud on Mon, Feb 02, 1998 at 01:28:51AM -0500 Content-Length: 1200 Lines: 52 --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Mutt would not correctly make the default reply address to a message from and to you be you. This patch fixes that, and fixes a related memory leak. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.de.remove_user.1" --- mutt-0.89.1i.orig/send.c Sat Jan 31 08:13:06 1998 +++ mutt-0.89.1i/send.c Mon Feb 2 02:42:10 1998 @@ -160,7 +160,7 @@ static ADDRESS *mutt_remove_xrefs (ADDRE */ static ADDRESS *remove_user (ADDRESS *a, int leave_only) { - ADDRESS *top = NULL, *last = NULL; + ADDRESS *top = NULL, *last = NULL, *tmp = NULL; while (a) { @@ -178,17 +178,16 @@ static ADDRESS *remove_user (ADDRESS *a, } else { - ADDRESS *tmp = a; - + tmp = a; a = a->next; - if (!leave_only || (a && a->next) || last) + if (!leave_only || a || last) { tmp->next = NULL; mutt_free_address (&tmp); } } } - return top; + return top ? top : tmp; } static ADDRESS *find_mailing_lists (ADDRESS *t, ADDRESS *c) --liOOAslEiF7prFVr-- From news@bogon.com Sun Feb 1 14:15:39 1998 Return-Path: news@bogon.com Received: from wu.bogon.com (exim@wu.bogon.com [207.6.172.33]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id OAA27313 for ; Sun, 1 Feb 1998 14:15:37 -0800 (PST) Received: from news by wu.bogon.com with local (Exim 1.80 #6) id 0xz7fr-0002ef-00; Sun, 1 Feb 1998 14:15:35 -0800 To: mutt-users@cs.hmc.edu Path: not-for-mail From: jhenders@bogon.com (John Henders) Newsgroups: local.mutt-users Subject: 0.89.1 - long pause when syncing folders? Date: 1 Feb 1998 22:15:35 GMT Organization: Bogon Research Message-ID: <6b2s67$9v0$1@wu.bogon.com> Reply-To: jhenders@bogon.com (John Henders) NNTP-Posting-Host: stdismas.bogon.com X-Newsreader: NN version 6.5.1 (NOV) Sender: Usenet News Owner Content-Length: 349 Lines: 11 Compared to 0.88, 0.89.1 seems has quite a noticable pause before rewriting the mailbox when I sync it up with $ after marking one or more messages for deletion. -- Artificial Intelligence stands no chance against Natural Stupidity. GAT d- -p+(--) c++++ l++ u++ t- m--- W--- !v b+++ e* s-/+ n-(?) h++ f+g+ w+++ y* From kreed@telesys.tnet.com Sun Feb 1 15:10:15 1998 Return-Path: kreed@telesys.tnet.com Received: from telesys.tnet.com (telesys.tnet.com [192.150.127.65]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id PAA08386 for ; Sun, 1 Feb 1998 15:10:12 -0800 (PST) Received: from localhost (2207 bytes) by telesys.tnet.com via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Sun, 1 Feb 1998 16:09:07 -0700 (MST) (Smail-3.2.0.97 1997-Aug-19 #8 built 1997-Sep-24) Message-ID: <19980201160907.51376@telesys.tnet.com> Date: Sun, 1 Feb 1998 16:09:07 -0700 From: "Kevin W. Reed" To: MUTT Mailing List Cc: kreed@tnet.com Subject: [0.89.1i] Editor hanging Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: TNET Services X-Mailer-Info: http://www.tnet.com Content-Length: 1771 Lines: 45 I'm in the process of upgrading (finally) from 0.65 which has worked for me very well, the the current release 0.891i. I'm having a problem with Mutt after composing a message in the editor (I'm using Epsilon, a commercial Emacs editor, but vi does the same thing) After you leave the editor with the message you want to send, the system hangs. A check of ps -ef shows a process. It will sit there forever, until you hit intr (DEL on my system). Then you are returned to the Compose menu. Any ideas what is causing this problem?? This is Elm 0.891i compiled on an SCO Unix 3.2v4.2 platform: Mutt 0.89.1i, Copyright (C) 1996-8 Michael R. Elkins Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System info: SCO 3.2 Compile time definitions: -DOMAIN -HIDDEN_HOST -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_POP -HAVE_REGCOMP +USE_GNU_RX +HAVE_COLOR -BUFFY_SIZE SENDMAIL="/usr/lib/sendmail" MAILPATH="/usr/spool/mail" SHAREDIR="/usr/local/share" ISPELL="/usr/local/bin/ispell" _PGPPATH="/usr/local/bin/pgp" BTW: I thought is was pretty cute to have a sample send-hook in the sample.muttrc file. I almost didn't catch it :-) #send-hook mutt- 'my_hdr From: Michael Elkins ' This should be set to a non-valid address, certainly not Michael's addr... -- -------------------------------------------------------------------------- Kevin W. Reed (KWR10) - kreed@tnet.com * TNET Services * Mesa Arizona Voice/FAX: 602-668-9829 Disability Systems & Software Development WEB: http://www.tnet.com MAILBOT.COM - TNET.COM - DIMENET From eisenbud@allspice.cs.swarthmore.edu Sun Feb 1 17:18:12 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA12404 for ; Sun, 1 Feb 1998 17:18:09 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id UAA20472; Sun, 1 Feb 1998 20:18:09 -0500 (EST) Message-ID: <19980201201808.34760@cs.swarthmore.edu> Date: Sun, 1 Feb 1998 20:18:08 -0500 From: Daniel Eisenbud To: Mutt Users List Subject: [0.89.1, 0.89.1i] My feature patches Mail-Followup-To: Mutt Users List Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=AqsLC8rIMeq19msA X-Mailer: Mutt 0.89.1i Content-Length: 11950 Lines: 198 --AqsLC8rIMeq19msA Content-Type: text/plain; charset=us-ascii Here are my patches for mutt-0.89.1i and mutt-0.89.1. beep_new and narrow_tree are updated to apply over the new version. fcc-save-hook and index-percentage are unchanged. To quickly recap: beep_new adds a variable of the same name that makes mutt beep when there's new mail. narrow_tree adds a variable of the same name that makes the tree narrower, useful for long threads on 80 column screens. fcc-save-hook adds a command by the same name, which acts as a combination fcc-hook and save-hook. index-percentage adds a format specifier (%P) for the status line, which tells you how far through the index you are. This is particularly useful when in a limited display, when there's no other way to tell. This also adds %P to the right hand of the default status line. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu --AqsLC8rIMeq19msA Content-Type: application/x-gunzip Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="patch-0.89.1i.de.beep_new.1.gz" H4sICAcd1TQCA3BhdGNoLTAuODkuMWkuZGUuYmVlcF9uZXcuMQCVV3tv2kgQ/xs+xRynqyAY wqN5EqISME3ueOQwNK2qk7XYC1g1XmSvS7k03/1m1phXgPSiCMO8d+Y3M2vbGY0gZ4f+DKah lLlC/vIqX3TywnfGp8NwNFrkrS1OTEzmcrnDKgmDSfiTeVAuQuHyuli+LpxD8erqMpnNZvfa SxihB00+BCii4PXZ1XXxItL48AFy5fcX2gVkowcSHE8qK6bSNq0Jt75B+rtw7EwSAHwuQ9+L JEbCt/imXDpTScJLEpI5kt804wnpjBaxneyOk20uPJOju0Gz+QVO5HRWoZ/WhPkwY3Ly1Xzs Gg+fzcda/95s1z7/U4mOcV7WigU8Bz2LdJDjIUBCsaY8CNiYQzrV4XOYMsfFBMAfQT6lKW90 oATGkLtV6g63oQpFIt6R0Y6ymctVkrlElJlKMrv8BuliRoVOfy/J9eMlmV3lMV2IUwanJ5C0 j2HGCv3AxBC9XdxsMA5gZ0Pif+BnS2uNoVLhulBCxTWGShdlwhA9dnPveDb/gWn2wnXmnRGk HahWoW329O6j3tEbRIZIg/u+8LEgbSzGUPyAOQuA/5Dc95jrLmAqbFWHPEDTZeMAi7aAIYe5 L7xxPqUKxt2AYx2e10b311lOnED9QD9KNYvyFJ2YSUdgdbqP/Ttdf+zoT5mMYgK64jNIK1ks WwKrxtRp5YRD7GXIHW8M4jv3574jJfdgiDESYODkFJVssY3JKhQw7CiVl1cqlVcKzm+lkv4o 3rTH55YIsauqe5o3k4HfqiBcW4lkYkySpdytz22fzeFnFXp6o1d7Mo1+rT8wKmvjO9Fmkrml /uveorQQ6zl6RPr75ODdOziQ5HWCNxpHVXQZ9+vsUUMe7x1bWKdT5oXMzQfjqbuN8x3mgR7a kdrto9L12aE+eqV5bB6Xiu/PtXNEAD2LZwSBBh+x0JXXEHBJk+JpwpfY/c58hw1dDvgdmZry C3PHdSOczkkSY4x6SljU0Xk0kb0JuCVLtyT0zhXzIfMrCKEblw05doZdTSnomEhL3aL0DD/6 ixkiWwiXM+8GGa7jcSSvggs9Ci+bzGJ4vx4dxyYBR8LMx50QAMPY4i6KykudtBAhiBF4y9bF 1u+TffrHnphx/EDoowQ2YTKLrqTqP/Ubbnw+Ukcinynw2JQvv9+uIsxj3LDMCW0aNLGVC0XB TABlAigTWAyJIY/XmTiKP8dzZH6yDYuIdgBtETPR9B0FslIZcOYizs7ODoBsqXAUW+eXhCz8 VJseDxBactmGpoQ2mvuEJ/36D7aU2sHPkGKhFNx2ZEpLJBp9867bbWnQMzvdjq5FYwhOMoAt XBv0u3rjoa8lCvCibWibko1/Sbtf+7ilrGr0liJNjqVWdqWlcPsrmjhztlzGlY50jX5PS6x0 DbOh11vpeiSS2VSKW0U77rF+r9f/euVSeCPHn7IZwfhNC91O86HXrj3i0mxooMwcxR1RdnEX 0Q7gLmLuGW4XB3AXKxydaeWSGmn4UMjDxTOl4+OJBoZ+effQbz+0dW1JanZ7T5jqbmOL8veg 29dVkTdqt+S39c7AqPe6rZZGCzmwfIEzRm1KxwskZzYNA2c6cx0LZ42H14ncjEYMbePYQ13v 6c2ebtwrG+lZwENbZPCiNvJ5MAEcVB5glmmyTBl6CNbarW691tINRM2mJqKE9l8Y4ISbMBqH LhbSFRbDkWjzEXUsLUA0c7SGM19IEexWMaYeqGPM3jNBDq2plcpbM+RCzZDznUs2HuybGThj vKYFywsKruUDAmawwLpM98rhJQVfK1Y3tnu91tB7cKJBrdHA+hjYC9sK6mKVVm8IxDr+8rGl auEy8+Mb5x62z5nkJtYNy5fWO5/0Fl5XI/+/q6sRVZHbaUSxabRqnY9mfdAzdCMDP39CzLyv fdIV3TT0Pl5xKIvF8nvqiGK5vPPWpXyZlkCscsnjU2kQOP9yk+5uG5KYUJR0KXaijsaa4g7H FN9azluY3/jCxEmMswY3Y0hmBfYFrFJ27K2vcvx1bVPZYp5pc0vY6OGu2/iyYxvdeWNujvDa vllW5O+I0TzlHtqhZtuN9T8kMFrjWA8AAA== --AqsLC8rIMeq19msA Content-Type: application/x-gunzip Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="patch-0.89.1i.de.narrow_tree.1.gz" H4sICP8Z1TQCA3BhdGNoLTAuODkuMWkuZGUubmFycm93X3RyZWUuMQCVV/tz2kYQ/ln6K7bM OAYkMBDj2Dh24wQ5dcaAC7YznbajEdIB1wiJ3h0mqcf/e3fvJB5+kGQGkG5vv31+9yDioxFU ormYwXSuVKVWPTyq1nk1FXy8F6Xh3jRI5kFcleNpvKHxeNKuVCrfN2ENAgWfggRe16F22Ko3 Ws0DqB8dHdqO42y1bw3mCZyzIUAdAa3mfqvWNMh376DSOKg13QNw9LPeBJQlwZSdFAKlgnAy ZYkqnAI+5jBKBaykEmw4JwmM5nEMMZeKJ2NIRxCxEU9YBEyGwYyBZP/OWRIyiW8M1IQkoeJp Avh5K9jIBh6dFCaR8NHDNFCFLAKUvIrTxTAQx9nEadUG23lL+MZpEgiRLnINJRh7GwdDFmtr ZtInaeEUITP8uf42Yy0YpmnMguRtwhYxhonyNhsF81i1YJ5IpmwHNSdcwl0geDCMGYRpokQa Sx37gkdqQlnSQE0ECyIgL7CYsARkKnQVht+yOVm1nc96hikXuIJp8IUZSxoVzGYi/coxORYj ZsFDlEkw4bugUghizBCmqWAg0nRqOytsEmFjpAzGWNL58B+siqwC6ODxM5cMO0NFNtZAhohK KCIbshrOECvWyqbHWDCggoEpmFQCU1rVK9pGfOwZaVXDTUouxS+QfTn/DM3fvEDzNcwmwZut +sGK4PX9I+I3PXDFoESqQPEQeKKoRMLn0hcs5DOOpIai1731LntXHpRtABBMzUUCxVrp2IYH It9eGaLUz8qdzZt+zlI0yQQ1Gas/5nfYdVoyulf4zDF8ZDtQ1hDB5IzWwh0qJCxj1ZTg2HWz VDKQmmBdEsYiSZwYMm1iJshjhD1PUVcsuGSaY2GKyZigNL9QD/mVNZISRwtzEwVxaJVEoKok 3bOdcBIIKK9lWjSSbOiCGVJuri7lKA7GMhejdRck/4/5ijzRWwlrd4/GM41IqmMa0ZePoKjh 8Ao6/nXf80ok1tpmNp3p/aLYu7runvX7vc9aqWQUMj0AtAkn5O84l+TPxYTjOi5mocAp1Ev5 FKKtskHqbBBrZXqVCg1wznHohQL5pVgu6n46aIICsACGuM6/kIKZOIHG0v9D/kLYDFlBJJyc wO5ftXptl0yUi+S/Ag2UZ+InGWzW6LzX/+ANbt5/IrhMNA9QAc24eb1dKOzIgrsk0K/LtxYU CqWlAxZLtipBbSnPmY/mcuUsG0JsiWejJavYNCXWY9PRGf58L8btsTzWIptGTSstw81sZyHm 2rn0ONddox76+7P291pZngSCHh5oO92j3aIMOwEqB1GE61rSag7mapIKMxXilGYfyvNdmyd4 Uigm9Ua1X6+7jQY4+wd195A2Kp+2O58ODD9butkijBg1OltfEbPBCgNMclfutnCLAmu97qNp ppqaQYmKv7MjqfozPHz5V8ykYj2/Ckl+r3+3MNBM52qPet5YOadRadV63L4rp7r/iLQsPWTJ XeV0xYansowXz7ra8ISOdObaaQ54yJ66zT9uYxlpZsiYWRrJM/+uIcrT+PzpZB/0ThPOkEPr e/ITzHpZ8y35mS4Qea0fST2c0cG32uRgybUBcm3rTYAnXFUnm0e2kb1wBzCT1rng+gLQeA21 RgvvAM3mCxeADLD1eluvN/Tpj4835vAXc6ycOVBw9XTQ4G0g5J+0zO/pyL+HwpRPmT9aRAXX strX/vte79KFvt/tdT0Xincpj6BcAjyMOhcd7/xz27Vq8ODm4PSOZcDfb87azwP9Tu/W24TJ cX79dQk7uO671hI78Nveh8tiR47PcQkTytGo9Wuuux7r+971b5suVwenC2t+zY3PxHt1RqBH Pq9IofQI4NOdmH3NYu3edNZifaURH4zCY9xzKV6dffT6m/7yLLcyjCSPGWZkLzDMTP7EFTMH bP0D1TjQ/5/woRmG/5SmlDKW/OJjt9f3Li8wUe/q8o/rnptNDM5uvbN2u+8NBkvRzeDK67Z1 Yze7lSv0+jjMRzcDr93rnF101wTn/V7Htf8Hp1Rt+ZgOAAA= --AqsLC8rIMeq19msA Content-Type: application/x-gunzip Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="patch-0.89i.de.fcc-save-hook.1.gz" H4sICGJ+zjQCA3BhdGNoLTAuODlpLmRlLmZjYy1zYXZlLWhvb2suMQCtWHtT20gS/9v6FL25 LWIjyQ9IeAVYHOIs2SWwhcnVVmX3fGNphLXoldGIxyX73a97HrZsDCEbqijJ09Pd0/3rx7QI 4ygCP6xEAWklpd9tb23H7VzEF50wDzopyyqWtMuLNKntL245vu9/TbxxXnH4hWWwtgndFzv4 1+tBb3t7y3Fd9wHddbne9s76+k53XcsdHIC/vbHpbYBLr/UeIKVkV9yf5PklpPygKSsRZxd/ /NFu/RSU+JqkAT55WP3o1DhZniA1yNMfwS0Lljqw27niYry/25FlIDjP9h1w3H5S5lByDnLC YVfwCOJw71kUBP5U1TPIWMoXifuAutGlsO24jrtb8kD29ocFD+LoFkIesSqR8DYIdiBlcTLO b+B6wjMSKvIS7d9N2Jgn09O0TlRU4ONDyS74DuxK2bF7HVhJyk/jVz+sCHrt8rQj+AW/KTpA v80ZHbLlfBKX1jjAn1XJQ5C5wgbySl7keLyyCuIM2NS+HCEQiAPL0AyLhOBBLkILwUqYJwkT rwx1vw3wHoOMADIRTHipUIyzWMYsgSQuJeSR46a8JIcApYqYZ7KEKBeKNYoF8qRMBhOyqe4V GY+WlwvuMX3GMoDRmHcRZLnWR55HeYVaiN+acB0nCYy5wiJ0XETlkZ5ODyGEBzcsLZKFCFHG Ub5ZSZ12KReliQoHNs6vjA0qGAzDVNwiRsCQZGwsQQcIbSPLjVYIc7QgQypajeT/TrU/nwZw PE08hOJRie24tdTmWfgNqa0ciOKEkwYVraVJzzAFsoAvZHvtrOUpP2X4jrxnUE5yIYNKesA/ VfEVQ2Ml4RoqgMeY8Mg0h81ivVsb2Tiss97pDfW+cB2j3hiznImLKqV8JxzB4HiI9YWJWHIp 0YgSxozKsyryDGp1EutCqcFWhwwIMqhB9li4DDod3Wa3try1Hri9bm8d+y312fgiY9he+ZxZ lEAzk9p4+jjqnOSS73TU3vTw5+QytpgsuQV+wxF4VHF6cjgAFklsLRfa53qTcGyXqJ+AyRuG xMhmVKNC8CK5pS1sIDyMrTpnvsBPTs8hYNg9MC9vZ/ZR6LH2rWltx3f8p2rcPoXE/47GjbY8 QeP2n7Jx+0/YuP0nbdz+P2nciPA3N24Vladq3P4jGjfOJLZTmCK45JTCnyqObbS0ypE4zpkI YVxFERe1nCyqcmJbRHj/HEiOt4P6iKYpS6c+vdV4K2I9tK1Dd22nu7Xz8uXSYc+wPzjjbfS8 TXDVE5cxFjgpGBVMlHykotIM8gxzLJgwAaulB1d5HDoA8DdBBFDCnhbhN1KwQI5kfoll2jT1 42Ez+x/HAFlCCyl4D9wU2WyLVi3P8RuNBkBT3hYc9vbg/ejt6fGbwdnR6emv8OULzOjDwckb orbgJ8etCa1Ac16ozkvMoJmR+lsf2yHtv+4f/jo87g+PWrAD3dYr7VWMVv2wak1WSG1ueNvg quc3IgVYuNjNERS/Rwdo7Hx9yte9ff/69HflgePWRJb5OuVs6WNNXAr0Ae3E27CJT2zfNegN oYV23THIqlsAv//vwV3q28PDe2ycaZkTrsnca+29OWTD1FlFtHmgbpSUXWJbwkuTOrBUbdl0 RRWcMOdl9hzpieAspIuRuuuquYLXqArU85tjCzBGjZf3x9Vm4PfBONPyFRijhOE482UPzgY/ j94d9ocDA5a4wVItWcRHKXbLPICmhVVdGSNJsBIavbUNgkO/kEC+akCiPAm5sIgoLChS6mS1 5EJ8HB6dnp2Phudn705+/tOcTfdV8xXItFAPNASf/n6GTaNFiBlvibasIBQeizwrCyzK+882 KMSrHeOBkRI3bXHjAVnsQdeDkw/Hx/ijRafh8z9gubJctqyezxqSFy8VJOqFBO27xiTGfNWI UOKQaR7YbCEtKlCr2usj5Cv/OSb0vgcLvXUXg/sgWIIAtkfbqBSzrTaTFfqq6Nm7YpYVNNgZ BPpv3pwNhkNYZWEoWjPvabfutuK2cKgC1U+k0esOCpq45AaYgVFjWZnjMGCocwuyCw+h1yso ai8kqrc9ehp+aODd/rH7JzJ0DRJbuj62TH2Uksk4mLUNUnOnRrCJkc4pQPrsJ4NkITPmwKil xlPB8MBEQ9Nre1KfQzRl6USjtx490Rj2ByeatfVt+q8VvUx0RBVIO8+PJBzqX+VH8kXVymd4 FuRJLp55jUat8Sua16Aigb89B/6FeR5HRmD6zTEvQySv0VTFsdqadWdS4E4FZ5+p3gPCzZl0 vem3lDFal+rHX9c0NylMpSeYpjibc/Jbi9EXB/qzcoRXJBentHdM1+RUBD9Mc8HJZy2g17i0 ID2QGLSeTwxNWZoYemtJYmwsTQzD/mBibK57PSxb/To4wHjisB9nXKFzdjgYfnj9S6PZ293F foiDRSFUO6cP62r8F34JAL/CwRarK5YQxiENE4H+JwJOETVl52eDQUMp6ilFoWDXSo+c0OgB UnAt4ri4S8Wpv+ds71DBa7aIxa2baAPY6NXpdrwyB9a3bAtUW2tzWyav1M76vJDJMrX1okX/ MeFZlTpYKb4auB40GFnmcm0Pep4mWr1mac22u8ZUszTm4cpMeWke1g+9ivn1CCdXFkzoHzu1 s3Ho+XDcP1PFNl1pM0Cd2393fNj/zaz6w9H54PdzXDn/B/r2XuysFwAA --AqsLC8rIMeq19msA Content-Type: application/x-gunzip Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="patch-0.89i.de.index-percentage.1.gz" H4sICDOEzjQCA3BhdGNoLTAuODlpLmRlLmluZGV4LXBlcmNlbnRhZ2UuMQDNWetz2kgS/wx/ RYc9JchC5uUXZG3WZzsb3xnswqTurnJbKiENoIqQdNIQ4svjb7/uGT1BYOc+bSplSTO/7pnp dw+2M5uBbq/CAJYrzvXW4VnPOfRDZ960VmFkLE3HO7Ryc/nhqq7r+8gq70IH/mZ60OlCq9Nv nfWPj6Hd651VNU3bwbMyWTFJc4rQ/vFZv3smaX77DfRO76jR6YFGz24XcOiz79iCleF4Nvti LJm3gjqNqlWQ/8RstPDXBgtDP4S6+lZOfa9CVacXZwZ1ItQvQmaH5hpew/jmenz5D+Nxcjn5 8KhK2Ff5SDhyk68iw3U8BvXpataAyPkv82fiQ23Ao5jHtWKiq7uby/Hd7egG6n7AHd+D+v3D RC5wP5rcP6gwgBb0gTCPeiejfLyZXN3f3Y+hPpwY4i3ZVwoJQsfja6jXFP3g8CCqNQBxj8lf 2tA+bqP78fDyLoMUZXEOPwrSiGHfq7oUYyY9IfzzcxjejD4Yw8vbUayDr4kqCHrle5x94al6 cLJChIa1YNYnI2QWQ0AoeZKqqnplS0G4SLyn29H1zT/VqlbZrcQUQkvJ0xkSI40mXUqrbJz9 2zlsHF2roNVUmBuxMqupx+jh/eT2fmSMbx7/Nbp6D9+gMK6qW/tY+tIi4o3oO1bIjn31YTy+ GU3oVLs2s4ncXBO9LkRRZ4KG2Cu0qgbwIr+ABPkV9yF4P+cVBMr5hlb5P9xCq+zzCK3yEmco 5ZH6gTzMPhfQMmFBidOcQ+ttccJ37UTg5/FQ/E0mbu+Ow7ZvNZemtzLdw2i+dPNxc2OqNB5v YPLxtXXUx//tdmlM3kOHcfnopC9e4rjc7XTPGiegiecpxeWI/WfFPItF/SoowwpfMPBWyyn6 NdrCkkWROWcRUFRGhTuH7LAB64VjLWBpcvxL+ERcrrN0uAoHyMirZEw8ts4YOZ4gwRziTv0v AhvksIEf8cD3mJ1RHFQ15aESsJDCDY4QjFiszSd8hv5qLnchIgSyCytLH7XkMLsZMtPWfc99 aq597w3X16HDBdCxTO6HDTAtyw9tx5sD9+EvsUtYCzOMkFFUSQ4W+SEnEDJmOMFzG8YdzYu7 3WMhjufwYpKWI6X2IKdenJpj+F7tt7snLdS6Fj83srKDEcah035yAiN6iozQErE/8oSfYmR4 dOYeiihkWbBIhzBk1JSoeRglA+jN7/0ls51QhqyIhzMreCKSZeCyR2aG1gKJfsxQ1Bh5f0T4 rOU5ZzB1kwW/IiUhtX6g5GnkuCozZA5OiiW0EupDPG0flBl8HEbzqK8MhgNl2BwoS2XgDWDE 1n3FGygDewDXzO0rNr6/G8A715z3lXf4wQcwoXeO78EAHtBi+0qAH9MB3HpWX8Gn4v6BKq0r kap80wv7E+FUFWHpz7A9XbnA54OKn6XbhGqcXeoBRsM548z7jPF6Mny4vh3XVBVencPow91d XCSkR5qwZYCab0CQcY3HiO0eH6GIW/QROVLqI3KqxEdOSn0khud8pNPqt7r99lGucm33yEXk I/WQkgpg+GEyofoJDkRarj5bswnAX//++zWCdsx/J7Pdzk/adqW3keVEiby917Ry2NysOOmR POnRrpPuoP5znXSzGN086T5To7gnbGJRsJJsuNzosvmXW16OZm+IPu1Rej7dUkmsC4P7Qf6M JMxt0NKxbZc9j5v6nPvLPbidsqUIluEKtSSlTziQbm/wBmREDbB8L+IgETK65NRFIsJaId8Z prtJxHfNMMT4T/mtHOyPJwGm5bAYUOKhUuXGcy9WbILfn3ePTk5F3pVPHBIHErQosJxQpqbn sTATVFKaNg9k5wj+imfVDkjBw5RIm/nebWGH8Po1PNAKtwS9Q91EuVZOr5T2xjNaXAbs+FMt NAGlrUMpkdhgjhbyDYSY9GeziHHQkn5iRzshwS7zQIe2KpLS840D7SHXKO2zj9DnflSMAMlY uYXEky83kYRgv43IvEOPk2JlFi2Y6xosssyAlflF/sakZJbqMTcu78qmqcoyTNsOsYTd9t7L 62tsjh+Fu+o5sn0ev+nlGRk3pxGGMCMKTOw4EspNzNxAuzBmWNKIgpRsiRcxK2/q+hia5OGi 9GB79Cx3XAwEyVipnpPJF+s5Jdiv51MK8G0ZB9BCD5pAcfAXx7Pclc2gRhwPF7WqVhyKs0dt E0rBPGLRxgx1LGJIdn3Houc7SdfETg/z7e4+77MTrrjpJuOo0RXGnvUCnVA0edgMqfBRuu0f kqFXYFjo+YrAoAAsafhSuEbwB4THzR/h811f3PERKkQUdXtJs8dFq9dE+/KoPSNbksAIgVtt HeML35bz1PT/UtbYpbsigR6dNtpnoGHl1O4lIsV/yuDXmR9iYyx6yIvBr5IG3Q+zFq50MRAK p5uyva6UXscYnIIZxr6iUwXqM9m3jEGxMNpiKO/+5KcVvM0+1gEn6SKbbJAvg4+P7+/HEyzL xrej3/8QlVsy1dmcS8iCkM2cL7tmZ0u+awrlKCW4C2AtxDtlyDWliuRaR6TMWAlyUJeDaIEG 2Z7YOA0IE09pkEfc/Ejx6fpbysGR+ZlB6GPNhHoWeZiHpuOSEf27RZqVkbwrI/nJZo+9X1Pi 3o+S9yuhjwpZ1BSN+pNYemraII1LWFCFDo4nOgg0TcwHOE8sTYtKNYTolbL7b1RP1pHhB2bq IHeh+ixY2k4gsjCAFDVlXUzOa5mjUVH0IvAStV44VI3S6AW05NG+SlH1uo12G2XVO2n0fk5W mbQS/SaMdSE5QULgj8doJ3osz+wuA60tOxt+iPsLRYmomJB2Kq53018RcIzzJ4MooE5/M2p6 Inl8X45lS/ymXwh0H8+csMrWL5FtuqVYIWUrk3sV6DrPrqy9cGXBTGrsu/ib3le/Shb49g1e FZZI7LToY6K77J412ph1Ot1eo9v6ad1aJq79JnjTFz8rQOqvdCcrGoX4W+aOenxMmad2Qnaa zEuNw942juflmuzjJ1QhzpHqQi/oImUnuGXjkqZUHzQmIwlKU4tl+4Cy1SqCSfbzAbWXWtyC U3sifDa5Bl+aX9T4CFaQXo4TyQBqzLNraHA103Vrb9OtiZevCVGsnXq7hcFyz5KqCs1szVKx bTtBTbEVugtMZBdf/Mt/Yr8ElMy+i78/GQyKJDtVl4TTWOC4jdScQ2HOiRWmv6+JEq11TEmj 22n9bNKA9CfSXP+XGXhZo1ey9zTD7mjzdqaCPGFhC3WZHPLpQM01oP8DXdlhMdEeAAA= --AqsLC8rIMeq19msA-- From kreed@telesys.tnet.com Sun Feb 1 17:59:31 1998 Return-Path: kreed@telesys.tnet.com Received: from telesys.tnet.com (telesys.tnet.com [192.150.127.65]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id RAA22973 for ; Sun, 1 Feb 1998 17:59:28 -0800 (PST) Received: from localhost (1446 bytes) by telesys.tnet.com via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Sun, 1 Feb 1998 18:58:38 -0700 (MST) (Smail-3.2.0.97 1997-Aug-19 #8 built 1997-Sep-24) Message-ID: <19980201185837.43437@telesys.tnet.com> Date: Sun, 1 Feb 1998 18:58:37 -0700 From: "Kevin W. Reed" To: MUTT Mailing List Subject: Re: [0.89.1i] Editor Hanging Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: TNET Services X-Mailer-Info: http://www.tnet.com Content-Length: 1025 Lines: 20 > I'm having a problem with Mutt after composing a message in the editor > (I'm using Epsilon, a commercial Emacs editor, but vi does the same thing) > > After you leave the editor with the message you want to send, the system > hangs. A check of ps -ef shows a process. It will sit there > forever, until you hit intr (DEL on my system). Then you are returned > to the Compose menu. I have just found out that this occurs when accessing any outside program from mutt. Ispell does the same thing. I suspect it has something to do with forking but have not been able to find the code that is actually doing the calls yet... Might give someone more familiar with the code an idea where I might look.. -- -------------------------------------------------------------------------- Kevin W. Reed (KWR10) - kreed@tnet.com * TNET Services * Mesa Arizona Voice/FAX: 602-668-9829 Disability Systems & Software Development WEB: http://www.tnet.com MAILBOT.COM - TNET.COM - DIMENET From eisenbud@allspice.cs.swarthmore.edu Sun Feb 1 18:38:19 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA03594 for ; Sun, 1 Feb 1998 18:38:15 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id VAA22799; Sun, 1 Feb 1998 21:38:11 -0500 (EST) Message-ID: <19980201213810.18760@cs.swarthmore.edu> Date: Sun, 1 Feb 1998 21:38:10 -0500 From: Daniel Eisenbud To: MUTT Mailing List Subject: Re: [0.89.1i] Editor Hanging Mail-Followup-To: MUTT Mailing List References: <19980201185837.43437@telesys.tnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980201185837.43437@telesys.tnet.com>; from Kevin W. Reed on Sun, Feb 01, 1998 at 06:58:37PM -0700 Content-Length: 956 Lines: 22 On Sun, Feb 01, 1998 at 06:58:37PM -0700, Kevin W. Reed wrote: > > I'm having a problem with Mutt after composing a message in the editor > > (I'm using Epsilon, a commercial Emacs editor, but vi does the same thing) > > > > After you leave the editor with the message you want to send, the system > > hangs. A check of ps -ef shows a process. It will sit there > > forever, until you hit intr (DEL on my system). Then you are returned > > to the Compose menu. > > I have just found out that this occurs when accessing any outside > program from mutt. Ispell does the same thing. I suspect it has something > to do with forking but have not been able to find the code that is actually > doing the calls yet... > > Might give someone more familiar with the code an idea where I might look.. Look at _mutt_system (mutt_system is a macro which calls this.) -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From olsenc@ichips.intel.com Sun Feb 1 18:42:51 1998 Return-Path: olsenc@ichips.intel.com Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA04973 for ; Sun, 1 Feb 1998 18:42:49 -0800 (PST) Received: from ichips-jf.jf.intel.com (ichips-jf.jf.intel.com [134.134.50.200]) by ganymede.or.intel.com (8.8.6/8.8.5) with ESMTP id SAA20395 for ; Sun, 1 Feb 1998 18:46:17 -0800 (PST) Received: from dtthp169 (olsenc@dtthp169.jf.intel.com [134.134.102.22]) by ichips-jf.jf.intel.com (8.8.8/8.8.7) with ESMTP id SAA16102 for ; Sun, 1 Feb 1998 18:42:48 -0800 (PST) Received: by dtthp169 (8.8.8/WW2.1) id SAA24380; Sun, 1 Feb 1998 18:42:48 -0800 (PST) Message-ID: <19980201184248.45132@dtthp169.jf.intel.com> Date: Sun, 1 Feb 1998 18:42:48 -0800 From: Clint Olsen To: MUTT Mailing List Subject: Re: [0.89.1i] Editor Hanging Mail-Followup-To: MUTT Mailing List References: <19980201185837.43437@telesys.tnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980201185837.43437@telesys.tnet.com>; from Kevin W. Reed on Sun, Feb 01, 1998 at 06:58:37PM -0700 Organization: Intel Corporation, Hillsboro, OR X-Disclaimer: Mutt Bites! Content-Length: 329 Lines: 10 On Feb 01, Kevin W. Reed wrote: > > I have just found out that this occurs when accessing any outside > program from mutt. Ispell does the same thing. I suspect it has something > to do with forking but have not been able to find the code that is actually > doing the calls yet... Hmm, I don't see any problem here. -Clint From kreed@telesys.tnet.com Mon Feb 2 00:07:40 1998 Return-Path: kreed@telesys.tnet.com Received: from telesys.tnet.com (telesys.tnet.com [192.150.127.65]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id AAA04162 for ; Mon, 2 Feb 1998 00:07:38 -0800 (PST) Received: from localhost (1953 bytes) by telesys.tnet.com via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Mon, 2 Feb 1998 01:06:24 -0700 (MST) (Smail-3.2.0.97 1997-Aug-19 #8 built 1997-Sep-24) Message-ID: <19980202010623.50287@telesys.tnet.com> Date: Mon, 2 Feb 1998 01:06:23 -0700 From: "Kevin W. Reed" To: MUTT Mailing List Cc: Clint Olsen Subject: Re: [0.89.1i] Editor Hanging Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: TNET Services X-Mailer-Info: http://www.tnet.com Content-Length: 1490 Lines: 35 On Feb 01, Clint Olsen wrote: > > On Feb 01, Kevin W. Reed wrote: > > > > I have just found out that this occurs when accessing any outside > > program from mutt. Ispell does the same thing. I suspect it has something > > to do with forking but have not been able to find the code that is actually > > doing the calls yet... > > Hmm, I don't see any problem here. I barely know what I'm doing in this area as I don't write fork functions very often. The first thing that I tried was replace the actual fork function itself with a system(xx) call. I thought perhaps the forking function itself was the possible problem. The results were the same. Next, I assumed that one of the sigaction statements was causing the problem so I commented out all the SIGCHLD ones first (both sigaction an sigaddset). This worked without any problems. After editing in the editor, it returned like it should with no halting. Perhaps the SCO version of that signal is screwed up?? I'm not really sure what it does in anycase. BTW: a compilation of the same source (original that is) on Linux Redhat worked just fine... Just the SCO one is hanging on the forks. -- -------------------------------------------------------------------------- Kevin W. Reed (KWR10) - kreed@tnet.com * TNET Services * Mesa Arizona Voice/FAX: 602-668-9829 Disability Systems & Software Development WEB: http://www.tnet.com MAILBOT.COM - TNET.COM - DIMENET From olsenc@ichips.intel.com Mon Feb 2 00:34:55 1998 Return-Path: olsenc@ichips.intel.com Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA11804 for ; Mon, 2 Feb 1998 00:34:53 -0800 (PST) Received: from ichips-jf.jf.intel.com (ichips-jf.jf.intel.com [134.134.50.200]) by ganymede.or.intel.com (8.8.6/8.8.5) with ESMTP id AAA13073 for ; Mon, 2 Feb 1998 00:38:19 -0800 (PST) Received: from dtthp169 (olsenc@dtthp169.jf.intel.com [134.134.102.22]) by ichips-jf.jf.intel.com (8.8.8/8.8.7) with ESMTP id AAA27551 for ; Mon, 2 Feb 1998 00:34:48 -0800 (PST) Received: by dtthp169 (8.8.8/WW2.1) id AAA26035; Mon, 2 Feb 1998 00:34:48 -0800 (PST) Message-ID: <19980202003448.33904@dtthp169.jf.intel.com> Date: Mon, 2 Feb 1998 00:34:48 -0800 From: Clint Olsen To: MUTT Mailing List Subject: Re: [0.89.1i] Editor Hanging Mail-Followup-To: MUTT Mailing List References: <19980202010623.50287@telesys.tnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202010623.50287@telesys.tnet.com>; from Kevin W. Reed on Mon, Feb 02, 1998 at 01:06:23AM -0700 Organization: Intel Corporation, Hillsboro, OR X-Disclaimer: Mutt Bites! Content-Length: 385 Lines: 10 On Feb 02, Kevin W. Reed wrote: > > The first thing that I tried was replace the actual fork function itself > with a system(xx) call. I thought perhaps the forking function itself > was the possible problem. The results were the same. Are you using mutt_system()? This was written specifically because developers had problems in the past with cross-platform portability. -Clint From mutt-users-request@cs.hmc.edu Mon Feb 2 06:43:57 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id GAA14826 for me@cs.hmc.edu; Mon, 2 Feb 1998 06:43:56 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 06:43:56 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: fabrice@math.Princeton.EDU Message-ID: <19980202085536.58895@math.princeton.edu> Date: Mon, 2 Feb 1998 08:55:36 -0500 From: Fabrice Planchon To: mutt-users@cs.hmc.edu Subject: filter-entry and encoding Mail-Followup-To: mutt-users@cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Organization: Princeton University X-http: //www.math.princeton.edu/~fabrice/ Resent-Message-ID: <"9QFReB.A.yo.bBd10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu Content-Length: 600 Lines: 18 Hello, with mutt-0.88, I used to have the following macro: macro compose \Co |isoascii\ny where isoascii does what you think, that is gets rid of all 8bit characters. When I was applying this to an attachment, the content type was correctly changed from 8bit to 7bit. Now with 0.89(i), the content type stays 8bit (and I had to replace the | by the F command). Is there any reason for that ? (other than a bug...) F. -- Fabrice Planchon (ph) 609/258-6495 Applied Math Program, 210 Fine Hall (fax) 609/258-1735 From mutt-users-request@cs.hmc.edu Mon Feb 2 09:45:28 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id JAA03418 for me@cs.hmc.edu; Mon, 2 Feb 1998 09:45:27 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 09:45:27 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: sec@matrix.42.org Message-ID: <19980202180451.41363@matrix.42.org> Date: Mon, 2 Feb 1998 18:04:51 +0100 From: Stefan `Sec` Zehl To: mutt-users@cs.hmc.edu Subject: Re: filter-entry and encoding Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202085536.58895@math.princeton.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202085536.58895@math.princeton.edu>; from Fabrice Planchon on Mon, Feb 02, 1998 at 08:55:36AM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ Resent-Message-ID: <"xXcKoB.A.8UF.Bzf10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu Content-Length: 452 Lines: 13 On Mon, Feb 02, 1998 at 08:55:36AM -0500, Fabrice Planchon wrote: > Now with 0.89(i), the content type stays 8bit (and I had to replace the > | by the F command). Is there any reason for that ? (other than a bug...) No bug. The default mapping simply changed that "Filter" function from | to F. so its logically that you have to change your macro. CU, Sec -- You haven't seen _multitasking_ until you have seen Doom and Quake run side by side. From fox@fuzzy.rsn.hp.com Mon Feb 2 09:47:01 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id JAA03787 for ; Mon, 2 Feb 1998 09:46:59 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id JAA29577 for ; Mon, 2 Feb 1998 09:46:55 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id LAA00321; Mon, 2 Feb 1998 11:46:54 -0600 (CST) Message-ID: <19980202114653.35586@rsn.hp.com> Date: Mon, 2 Feb 1998 11:46:53 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: filter-entry and encoding Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202085536.58895@math.princeton.edu> <19980202180451.41363@matrix.42.org> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=4qYPpj5QlsIQJ0KB X-Mailer: Mutt 0.89i In-Reply-To: <19980202180451.41363@matrix.42.org>; from Stefan `Sec` Zehl on Mon, Feb 02, 1998 at 06:04:51PM +0100 Content-Length: 1588 Lines: 42 --4qYPpj5QlsIQJ0KB Content-Type: text/plain; charset=us-ascii Stefan `Sec` Zehl wrote: > > On Mon, Feb 02, 1998 at 08:55:36AM -0500, Fabrice Planchon wrote: > > Now with 0.89(i), the content type stays 8bit (and I had to replace the > > | by the F command). Is there any reason for that ? (other than a bug...) > > No bug. The default mapping simply changed that "Filter" function from | > to F. so its logically that you have to change your macro. I think the bug he's referring to is the fact that Mutt doesn't re-evaluate its choice of content-encoding if you filter the text. I tried it myself. If I put an 8-bit character in my message, the content-encoding is set to "8bit". If I edit and remove the character, the encoding changes to "7bit". It goes back to "8bit" if I put the character back. BUT, if I use "F" to filter the message through a pipe which ends up removing the 8-bit character, the encoding does not change, and remains at "8bit". -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --4qYPpj5QlsIQJ0KB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNYGig0lGhIp2tThAQGpTQL/RkSKC+oBTpvKEnQvhIMwVNll2UVFAo9E KHlWUdg7XVGcOn0oDbpyPO2lOtiYXjGzPzPV3ZpmDidjqBOLfI31dzceyYBz1axb EAuJzI9qi4a4nmHjtCymdiQlgMOgBGkO =fSy8 -----END PGP SIGNATURE----- --4qYPpj5QlsIQJ0KB-- From fabrice@math.Princeton.EDU Mon Feb 2 10:07:49 1998 Return-Path: fabrice@math.Princeton.EDU Received: from and.Princeton.EDU (root@and.Princeton.EDU [128.112.16.144]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA10282 for ; Mon, 2 Feb 1998 10:07:47 -0800 (PST) Received: from eurydice.Princeton.EDU (eurydice.Princeton.EDU [128.112.16.153]) by and.Princeton.EDU (8.8.8/8.8.3) with ESMTP id NAA24140 for ; Mon, 2 Feb 1998 13:07:46 -0500 (EST) Received: (fabrice@localhost) by eurydice.Princeton.EDU (950413.SGI.8.6.12/8.6.12) id NAA03104; Mon, 2 Feb 1998 13:07:45 -0500 Message-ID: <19980202130745.35829@math.princeton.edu> Date: Mon, 2 Feb 1998 13:07:45 -0500 From: Fabrice Planchon To: mutt-users@cs.hmc.edu Subject: Re: filter-entry and encoding Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202085536.58895@math.princeton.edu> <19980202180451.41363@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980202180451.41363@matrix.42.org>; from Stefan `Sec` Zehl on Mon, Feb 02, 1998 at 06:04:51PM +0100 Organization: Princeton University X-http: //www.math.princeton.edu/~fabrice/ Content-Length: 1725 Lines: 41 On Mon Feb 02 1998 at 06:04:51PM +0100, Stefan `Sec` Zehl wrote: > On Mon, Feb 02, 1998 at 08:55:36AM -0500, Fabrice Planchon wrote: > > Now with 0.89(i), the content type stays 8bit (and I had to replace the > > | by the F command). Is there any reason for that ? (other than a bug...) > > No bug. The default mapping simply changed that "Filter" function from | > to F. so its logically that you have to change your macro. I tried to carefully word my question in order to avoid exactly this answer, but no luck ;-) Ok, I understand that there are now 2 different things, filter, mapped to F, and pipe, mapped to |. So I changed my macro, of course. The problem isn't that, the problem is not even what I though it was first, that the Content-Transfer-Encoding is not updated, actually it is. What is not updated is the display: ===== Attachments ===== -> - 1 [text/plain, 8bit, 0.1K] /tmp/mutt-*************** Hop, I filter, and it stays ===== Attachments ===== -> - 1 [text/plain, 8bit, 0.1K] /tmp/mutt-*************** whereas before 0.89 it was (correctly) updated to ===== Attachments ===== -> - 1 [text/plain, 7bit, 0.1K] /tmp/mutt-*************** If (after filtering), I edit the content-transfer-encoding, it shows up at 7 bit. So it's only a question of displaying the correct thing, and at that point I am clueless at where to look in the code. Still, it's a real problem as the only way to know that my filter did what it's supposed to do is to see this field changed on my screen. F. -- Fabrice Planchon (ph) 609/258-6495 Applied Math Program, 210 Fine Hall (fax) 609/258-1735 From mutt-users-request@cs.hmc.edu Mon Feb 2 08:41:51 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id IAA15149 for me@cs.hmc.edu; Mon, 2 Feb 1998 08:41:50 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 08:41:50 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: rnapier@cisco.com Message-ID: <19980202105801.08912@cisco.com> Date: Mon, 2 Feb 1998 10:58:01 -0500 From: Robert Napier To: Mutt Users List Subject: tag-subthread; user input on macros Mail-Followup-To: Mutt Users List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Resent-Message-ID: <"paq72C.A.Mu.v0e10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu Content-Length: 1872 Lines: 42 I'm looking for a tag-subthread function, which seems to be missing, to parallel delete-subthread. Am I just missing it, or has it not been implemented? Is this something I should try implementing myself (as a somewhat experienced C-programmer, but a novice mutt-hacker)? If I do need to start mutt-hacking, is there a mutt-hacking FAQ (is joining the mutt-dev list a "real good idea"?) I'm also looking for a way to put user input into a macro. For example, I want a macro that tags a user-supplied RE and saves it (\et;s=.trashcan). Is it a better idea to create a save-pattern function? Should I take this discussion to the dev list (I just hate subscribing to *another* list. My mailbox is going to explode...) The goal of all this is to override all of the delete commands to save stuff in a =.trashcan mailbox. I don't want to actually sift this stuff into mailboxes, but I hate actually throwing anything away... I've already overridden the normal delete keys: macro index d s=.trashcan^M macro pager d s=.trashcan^M macro index \CD \et;s=.trashcan^M macro pager \CD \et;s=.trashcan^M but I'm stuck at delete-subthread and delete-pattern. BTW, is there an easier way to do the "macro index foo; macro pager foo; macro index bar; macro pager bar; ..." Is there an easier way to do this whole thing (ie. save stuff in =.trashcan?) Thanks, Rob -- Rob Napier | 7025 Kit Creek Road | Check out Triangle Ascension: rnapier@cisco.com | PO Box 14987 | http://www.serve.com/napier/mage 919/472-3941 | RTP, NC 27709 | +===========================================================================+ | Imagine what my body would sound like / Slamming against those rocks | | When it lands / Will my eyes / Be closed or open? -- Bjork "Hyper Ballad" | +===========================================================================+ From mutt-users-request@cs.hmc.edu Mon Feb 2 09:47:35 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id JAA03997 for me@cs.hmc.edu; Mon, 2 Feb 1998 09:47:34 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 09:47:34 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: vikasa@att.com Message-ID: <19980202120927.45543@att.com> Date: Mon, 2 Feb 1998 12:09:27 -0500 From: Vikas Agnihotri To: Mutt Users List Subject: Re: tag-subthread; user input on macros Mail-Followup-To: Mutt Users List References: <19980202105801.08912@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 In-Reply-To: <19980202105801.08912@cisco.com>; from Robert Napier on Mon, Feb 02, 1998 at 10:58:01AM -0500 Resent-Message-ID: <"yMoFHB.A.KwF.W5f10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu Content-Length: 1253 Lines: 36 On Mon, Feb 02, 1998 at 10:58:01AM -0500, Robert Napier wrote: > I'm also looking for a way to put user input into a macro. For IIRC, this has been on the wish list for some time. Quite difficult to implement, as I understand it. > macro index d s=.trashcan^M > macro pager d s=.trashcan^M > macro index \CD \et;s=.trashcan^M > macro pager \CD \et;s=.trashcan^M I have the same macros too, > but I'm stuck at delete-subthread and delete-pattern. BTW, is there an but I still think the delete-pattern (D) command is nice because it lets me bypass my own macros to zap any messages that I ABSOLUTELY dont want, period. I dont want them to scratch any more of my disk by saving them to =trash-can and then take the effort to go there and delete them! > easier way to do the "macro index foo; macro pager foo; macro index > bar; macro pager bar; ..." Look up help for the 'generic' mapping, but I think it is a short-cut to 'all contexts EXCEPT index and pager', so for index/pager, one would _have_ to do this 'macro index foo; macro pager foo' business. Quite a chore. Why doesnt 'generic' refer to all the contexts, BTW? > Is there an easier way to do this whole thing (ie. save stuff in > =.trashcan?) Dunno. Looking for one myself. Vikas From eisenbud@allspice.cs.swarthmore.edu Mon Feb 2 09:14:39 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id JAA24484 for ; Mon, 2 Feb 1998 09:14:34 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id MAA05392; Mon, 2 Feb 1998 12:14:32 -0500 (EST) Message-ID: <19980202121432.37881@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 12:14:32 -0500 From: Daniel Eisenbud To: Mutt Users List Subject: [0.89.1i] feature: tag-subthread Mail-Followup-To: Mutt Users List References: <19980202105801.08912@cisco.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=C7zPtVaVf+AK4Oqc X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202105801.08912@cisco.com>; from Robert Napier on Mon, Feb 02, 1998 at 10:58:01AM -0500 Content-Length: 5354 Lines: 134 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii On Mon, Feb 02, 1998 at 10:58:01AM -0500, Robert Napier wrote: > I'm looking for a tag-subthread function, which seems to be missing, > to parallel delete-subthread. Am I just missing it, or has it not been > implemented? Good point. The attached patch implements it. It's unbound by default. (Do a 'make clean' and "rm keymap_defs.h" before rebuilding.) > Is this something I should try implementing myself (as a > somewhat experienced C-programmer, but a novice mutt-hacker)? Well, I guess I beat you to it this time, but you should feel free to join in. > If I do > need to start mutt-hacking, is there a mutt-hacking FAQ (is joining > the mutt-dev list a "real good idea"?) Yeah. mutt-dev is where you should send patches, unless they're for the current public release, and you're pretty sure that they'll work correctly, in which case mutt-users is appropriate. > I'm also looking for a way to put user input into a macro. For > example, I want a macro that tags a user-supplied RE and saves it > (\et;s=.trashcan). Is it a better idea to create a > save-pattern function? Should I take this discussion to the dev list > (I just hate subscribing to *another* list. My mailbox is going to > explode...) > > The goal of all this is to override all of the delete commands to save > stuff in a =.trashcan mailbox. I don't want to actually sift this > stuff into mailboxes, but I hate actually throwing anything away... > I've already overridden the normal delete keys: > > macro index d s=.trashcan^M > macro pager d s=.trashcan^M > macro index \CD \et;s=.trashcan^M > macro pager \CD \et;s=.trashcan^M > > but I'm stuck at delete-subthread and delete-pattern. BTW, is there an > easier way to do the "macro index foo; macro pager foo; macro index > bar; macro pager bar; ..." > > Is there an easier way to do this whole thing (ie. save stuff in > =.trashcan?) This is a feature that I'd really like. Actually, what I'd like the most is what I used to have with MH: you can customize your delete command there, so mine, instead of putting those annoying commas before filenames, would move the message into the DELETE subdirectory of the current mailbox. I had a cron script to clean up deleted messages four days later. This saved me from deleting something important on a fairly regular basis. So the features I'd like (and may add tomorrow) are the following: 1. Have an option to urn off the annoying commas when deleting MH messages. 2. Being able to specify a mailbox to save messages to when deleting them. 3. Having a shortcut for the current mailbox, so I could do curr-DELETE for my delete mailbox in #2 (it can't be a subdirectory in general), where curr would be replaced by some token that would expand to the path of the current folder. Maybe "$" could be the token? The first of these should be easy, the second pretty easy, and I don't know about the third. Thoughts? In the meantime, you can get by with tag-subthread and tag-pattern, I guess, and have a macro that will delete the tagged messages by saving them to .trashcan. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.de.tag-subthread.1" diff -durp mutt-0.89.1i.orig/OPS mutt-0.89.1i/OPS --- mutt-0.89.1i.orig/OPS Fri Dec 19 06:01:15 1997 +++ mutt-0.89.1i/OPS Mon Feb 2 11:49:02 1998 @@ -121,12 +121,13 @@ OP_SORT "sort messages" OP_SORT_REVERSE "sort messages in reverse order" OP_TAG "tag the current entry" OP_TAG_PREFIX "apply next function to tagged messages" +OP_TAG_SUBTHREAD "tag the current subthread" OP_TAG_THREAD "tag the current thread" OP_TOGGLE_NEW "toggle a message's 'new' flag" OP_TOGGLE_WRITE "toggle whether the mailbox will be rewritten" OP_TOP_PAGE "move to the top of the page" OP_UNDELETE "undelete the current entry" OP_UNDELETE_THREAD "undelete all messages in thread" -OP_UNDELETE_SUBTHREAD "undelete all messages in thread" +OP_UNDELETE_SUBTHREAD "undelete all messages in subthread" OP_VERSION "show the Mutt version number and date" OP_VIEW_ATTACHMENTS "show MIME attachments" diff -durp mutt-0.89.1i.orig/curs_main.c mutt-0.89.1i/curs_main.c --- mutt-0.89.1i.orig/curs_main.c Sat Jan 31 08:13:06 1998 +++ mutt-0.89.1i/curs_main.c Mon Feb 2 11:50:35 1998 @@ -1314,9 +1314,11 @@ void mutt_index_menu (void) break; case OP_TAG_THREAD: + case OP_TAG_SUBTHREAD: CHECK_MSGCOUNT; - rc = mutt_thread_set_flag (CURHDR, M_TAG, !CURHDR->tagged, 0); + rc = mutt_thread_set_flag (CURHDR, M_TAG, !CURHDR->tagged, + op == OP_TAG_THREAD ? 0 : 1); if (rc != -1) { diff -durp mutt-0.89.1i.orig/functions.h mutt-0.89.1i/functions.h --- mutt-0.89.1i.orig/functions.h Tue Jan 27 04:04:12 1998 +++ mutt-0.89.1i/functions.h Mon Feb 2 11:56:11 1998 @@ -99,6 +99,7 @@ struct binding_t OpMain[] = { { "read-subthread", OP_MAIN_READ_SUBTHREAD, "\033r" }, { "save-message", OP_SAVE, "s" }, { "tag-pattern", OP_MAIN_TAG_PATTERN, "T" }, + { "tag-subthread", OP_TAG_SUBTHREAD, NULL }, { "tag-thread", OP_TAG_THREAD, "\033t" }, { "untag-pattern", OP_MAIN_UNTAG_PATTERN, "\024" }, { "undelete-message", OP_UNDELETE, "u" }, --C7zPtVaVf+AK4Oqc-- From mutt-users-request@cs.hmc.edu Mon Feb 2 08:59:09 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id IAA19986 for me@cs.hmc.edu; Mon, 2 Feb 1998 08:59:08 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 08:59:08 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: vikasa@att.com Message-ID: <19980202111333.01745@att.com> Date: Mon, 2 Feb 1998 11:13:33 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: [0.89 core dump] mutt_buffy ? Mail-Followup-To: Mutt users mailing list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 Resent-Message-ID: <"ZNIpfB.A.0vB.bEf10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu Content-Length: 1291 Lines: 33 I have the following macro: macro index ,e "!vim $HOME/.muttrc\n:source ~/.muttrc\n\cl" macro pager ,e "!vim $HOME/.muttrc\n:source ~/.muttrc\n\cl" This has been working fine forever. Today, when I exited Vim, I got a core dump. Guess, a mail just happened to come in when I exited from the editor? Still, it has never dumped core on me before. Thanks, Vikas $ gdb ~/bin/mutt ~/mail/core GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (sparc-sun-solaris2.5.1), Copyright 1996 Free Software Foundation, Inc... warning: core file may not match specified executable file. Core was generated by `/export/home/vikas/bin/mutt'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libc.so.1...done. Reading symbols from /usr/lib/libdl.so.1...done. Reading symbols from /usr/platform/SUNW,Ultra-2/lib/libc_psr.so.1...done. #0 mutt_buffy (s=0xeffff000 "") at buffy.c:385 buffy.c:385: No such file or directory. (gdb) where #0 mutt_buffy (s=0xeffff000 "") at buffy.c:385 #1 0x21608 in mutt_index_menu () at curs_main.c:693 #2 0x2f664 in main (argc=1, argv=0xeffffa74) at main.c:608 From mutt-users-request@cs.hmc.edu Mon Feb 2 09:13:38 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id JAA24260 for me@cs.hmc.edu; Mon, 2 Feb 1998 09:13:37 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 09:13:37 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: nazario@doit.wisc.edu Sender: nazario@guernsey.doit.wisc.edu Message-ID: <34D5F566.7CD8F64A@doit.wisc.edu> Date: Mon, 02 Feb 1998 10:33:42 -0600 From: "Paul S. Nazario" Organization: UW Division of Information Technology X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.5 sun4c) MIME-Version: 1.0 To: mutt-users@turing.cs.hmc.edu Subject: Pine feature emulation in Mutt? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"R9ApiB.A.rPD.9Vf10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu Content-Length: 806 Lines: 22 Hi Mutt users, I've been a Pine user for some time and really like the feature in Pine that moves your read mail to the 'saved messsages' folder when you exit Pine. Is there a way to make Mutt behave the same way? Please reply directly to me since I'm not subscribed to this list. thanks paul -- //----------------------------------------------------------\\ | Paul Nazario nazario@doit.wisc.edu | | University of Wisconsin phone: 608-262-2595 | | Division of Information Technology fax: 608-262-9030 | | Network Engineering Technology | | 1210 W. Dayton Street | | Madison, WI 53706 | \\----------------------------------------------------------// From mutt-users-request@cs.hmc.edu Mon Feb 2 09:44:06 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id JAA03066 for me@cs.hmc.edu; Mon, 2 Feb 1998 09:44:05 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 09:44:05 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: sec@matrix.42.org Message-ID: <19980202180727.18536@matrix.42.org> Date: Mon, 2 Feb 1998 18:07:27 +0100 From: Stefan `Sec` Zehl To: "Paul S. Nazario" , mutt-users@turing.cs.hmc.edu Subject: Re: Pine feature emulation in Mutt? Mail-Followup-To: "Paul S. Nazario" , mutt-users@turing.cs.hmc.edu References: <34D5F566.7CD8F64A@doit.wisc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.89.1i In-Reply-To: <34D5F566.7CD8F64A@doit.wisc.edu>; from Paul S. Nazario on Mon, Feb 02, 1998 at 10:33:42AM -0600 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ Resent-Message-ID: <"D4qU5C.A.4eF.t1f10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu Content-Length: 417 Lines: 16 On Mon, Feb 02, 1998 at 10:33:42AM -0600, Paul S. Nazario wrote: > I've been a Pine user for some time and really like the feature in Pine > that moves your read mail to the 'saved messsages' folder when you exit > Pine. > > Is there a way to make Mutt behave the same way? Yes there is, look into the manual for this. CU, Sec P.S.: search for "move" -- Die kürzesten Computerwitze: 2) Ich hab nix gemacht. From mutt-users-request@cs.hmc.edu Mon Feb 2 10:28:21 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id KAA16094 for me@cs.hmc.edu; Mon, 2 Feb 1998 10:28:20 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 10:28:20 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: fox@fuzzy.rsn.hp.com Message-ID: <19980202114653.35586@rsn.hp.com> Date: Mon, 2 Feb 1998 11:46:53 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: filter-entry and encoding Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202085536.58895@math.princeton.edu> <19980202180451.41363@matrix.42.org> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=4qYPpj5QlsIQJ0KB X-Mailer: Mutt 0.89i In-Reply-To: <19980202180451.41363@matrix.42.org>; from Stefan `Sec` Zehl on Mon, Feb 02, 1998 at 06:04:51PM +0100 Resent-Message-ID: <"f75OPD.A.d7.Vag10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu --4qYPpj5QlsIQJ0KB Content-Type: text/plain; charset=us-ascii Stefan `Sec` Zehl wrote: > > On Mon, Feb 02, 1998 at 08:55:36AM -0500, Fabrice Planchon wrote: > > Now with 0.89(i), the content type stays 8bit (and I had to replace the > > | by the F command). Is there any reason for that ? (other than a bug...) > > No bug. The default mapping simply changed that "Filter" function from | > to F. so its logically that you have to change your macro. I think the bug he's referring to is the fact that Mutt doesn't re-evaluate its choice of content-encoding if you filter the text. I tried it myself. If I put an 8-bit character in my message, the content-encoding is set to "8bit". If I edit and remove the character, the encoding changes to "7bit". It goes back to "8bit" if I put the character back. BUT, if I use "F" to filter the message through a pipe which ends up removing the 8-bit character, the encoding does not change, and remains at "8bit". -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --4qYPpj5QlsIQJ0KB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNYGig0lGhIp2tThAQGpTQL/RkSKC+oBTpvKEnQvhIMwVNll2UVFAo9E KHlWUdg7XVGcOn0oDbpyPO2lOtiYXjGzPzPV3ZpmDidjqBOLfI31dzceyYBz1axb EAuJzI9qi4a4nmHjtCymdiQlgMOgBGkO =fSy8 -----END PGP SIGNATURE----- --4qYPpj5QlsIQJ0KB-- From eisenbud@allspice.cs.swarthmore.edu Mon Feb 2 10:32:37 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA17228 for ; Mon, 2 Feb 1998 10:32:35 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id NAA07720; Mon, 2 Feb 1998 13:32:33 -0500 (EST) Message-ID: <19980202133233.45583@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 13:32:33 -0500 From: Daniel Eisenbud To: Mutt users mailing list Subject: [0.89.1i] bugfix: buffy sanity checks Mail-Followup-To: Mutt users mailing list References: <19980202111333.01745@att.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="bRzO86E/ozDv8r1Q" X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202111333.01745@att.com>; from Vikas Agnihotri on Mon, Feb 02, 1998 at 11:13:33AM -0500 --bRzO86E/ozDv8r1Q Content-Type: text/plain; charset=us-ascii On Mon, Feb 02, 1998 at 11:13:33AM -0500, Vikas Agnihotri wrote: > I have the following macro: > > macro index ,e "!vim $HOME/.muttrc\n:source ~/.muttrc\n\cl" > macro pager ,e "!vim $HOME/.muttrc\n:source ~/.muttrc\n\cl" > > This has been working fine forever. Today, when I exited Vim, I got a core > dump. > > Guess, a mail just happened to come in when I exited from the editor? > Still, it has never dumped core on me before. Hmm, I guess that mutt_buffy_check() returned 1, but there were no mailboxes flagged as "new". Which can happen easily if buffy is 2 seconds stale, or if there's some other bug in mutt_buffy_check() that I haven't found. The attached patch adds a bunch of sanity checks to buffy.c that should help prevent this kind of thing (including a possible infinite loop.) It also fixes the minor problem of buffy sometimes checking twice in a row after opening a mailbox. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu --bRzO86E/ozDv8r1Q Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="patch-0.89.1i.de.buffy_sanity.1" --- mutt-0.89.1i.orig/buffy.c Sat Jan 31 08:13:06 1998 +++ mutt-0.89.1i/buffy.c Mon Feb 2 13:26:34 1998 @@ -219,6 +219,9 @@ int mutt_force_buffy_check(void) char path[_POSIX_PATH_MAX]; struct stat contex_sb; =20 + /* update time of last check */ + BuffyTime =3D time (NULL); + =20 /* fastest return if there are no mailboxes */ if (!Incoming) return 0; @@ -333,7 +336,7 @@ int mutt_force_buffy_check(void) return (BuffyCount); } =20 -/* this only checks for new mail each three seconds */ +/* this only checks for new mail each BuffyTimeout (def. 3) seconds */ int mutt_buffy_check (void) { time_t t; @@ -343,7 +346,6 @@ int mutt_buffy_check (void) t =3D time (NULL); if ((t - BuffyTime) < BuffyTimeout) return BuffyCount; - BuffyTime =3D t; return mutt_force_buffy_check(); } =20 @@ -366,6 +368,10 @@ void mutt_buffy_notify (void) return; } } + /* there were no mailboxes needing to be notified, so clean up since= =20 + * BuffyNotify has somehow gottten out of sync + */ + BuffyNotify =3D 0; } } =20 @@ -390,26 +396,39 @@ void mutt_buffy (char *s) =20 case 1: =20 - while (!tmp->new) + while (tmp && !tmp->new) tmp =3D tmp->next; + if (!tmp) + { + s =3D '\0'; + mutt_force_buffy_check (); /* buffy was wrong - resync things */ + break; + } strcpy (s, tmp->path); mutt_pretty_mailbox (s); break; =20 default: - - FOREVER + =20 + count =3D 0; + while (count < 3) { if (strcmp (s, tmp->path) =3D=3D 0) - count =3D 0; - else if (count =3D=3D 0 && tmp->new) + count++; + else if (count && tmp->new) break; tmp =3D tmp->next; - if (tmp =3D=3D NULL) + if (!tmp) { tmp =3D Incoming; - count =3D 0; + count++; } + } + if (count >=3D 3) + { + s =3D '\0'; + mutt_force_buffy_check (); /* buffy was wrong - resync things */ + break; } strcpy (s, tmp->path); mutt_pretty_mailbox (s); =1B[43;1H=1B[K --bRzO86E/ozDv8r1Q-- From smcpeek@td2cad.intel.com Mon Feb 2 10:44:05 1998 Return-Path: smcpeek@td2cad.intel.com Received: from crotus.sc.intel.com (root@crotus.sc.intel.com [143.183.152.26]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA20059 for ; Mon, 2 Feb 1998 10:44:03 -0800 (PST) Received: from td2cad.intel.com (td2cad-seg48.intel.com [143.183.48.44]) by crotus.sc.intel.com (8.8.6/8.8.5) with ESMTP id KAA19072 for ; Mon, 2 Feb 1998 10:43:24 -0800 (PST) Received: from ctdws66.sc.intel.com (ctdws66.sc.intel.com [143.183.37.136]) by td2cad.intel.com (8.8.5/8.7.3) with SMTP id KAA27438 for ; Mon, 2 Feb 1998 10:43:24 -0800 (PST) Received: by ctdws66.sc.intel.com (AIX 4.1/UCB 5.64/ICES-RS6000) id AA36950; Mon, 2 Feb 1998 10:43:24 -0800 Message-Id: <19980202104324.60584@td2cad.intel.com> Date: Mon, 2 Feb 1998 10:43:24 -0800 From: "Shawn D. McPeek" To: mutt-users@cs.hmc.edu Subject: e-mail/HTML enhancement? - Nope Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85 It sounds like Microsoft, Qualcomm, and Lotus are proposing an addition to HTML that would "enhance" the display of email messages and their multiple replies. Check out the article here: http://www.wired.com/news/news/technology/story/9988.html Here is my favorite sentence from the article: "The proposal would also allow viewing of messages by different ordering schemes - such as by date or by author." Shawn -- Never be led astray onto the path of virtue. From mutt-users-request@cs.hmc.edu Mon Feb 2 10:49:46 1998 Return-Path: mutt-users-request@cs.hmc.edu Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id KAA21527 for me@cs.hmc.edu; Mon, 2 Feb 1998 10:49:45 -0800 (PST) Resent-Date: Mon, 2 Feb 1998 10:49:45 -0800 (PST) X-Authentication-Warning: turing.cs.hmc.edu: me set sender to mutt-users-request@cs.hmc.edu using -f Old-Return-Path: fabrice@math.Princeton.EDU Message-ID: <19980202130745.35829@math.princeton.edu> Date: Mon, 2 Feb 1998 13:07:45 -0500 From: Fabrice Planchon To: mutt-users@cs.hmc.edu Subject: Re: filter-entry and encoding Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202085536.58895@math.princeton.edu> <19980202180451.41363@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980202180451.41363@matrix.42.org>; from Stefan `Sec` Zehl on Mon, Feb 02, 1998 at 06:04:51PM +0100 Organization: Princeton University X-http: //www.math.princeton.edu/~fabrice/ Resent-Message-ID: <"BpkrJB.A.5gC.1tg10"@turing> Resent-From: mutt-users@cs.hmc.edu X-Mailing-List: X-Loop: mutt-users@cs.hmc.edu Precedence: list Resent-Sender: mutt-users-request@cs.hmc.edu On Mon Feb 02 1998 at 06:04:51PM +0100, Stefan `Sec` Zehl wrote: > On Mon, Feb 02, 1998 at 08:55:36AM -0500, Fabrice Planchon wrote: > > Now with 0.89(i), the content type stays 8bit (and I had to replace the > > | by the F command). Is there any reason for that ? (other than a bug...) > > No bug. The default mapping simply changed that "Filter" function from | > to F. so its logically that you have to change your macro. I tried to carefully word my question in order to avoid exactly this answer, but no luck ;-) Ok, I understand that there are now 2 different things, filter, mapped to F, and pipe, mapped to |. So I changed my macro, of course. The problem isn't that, the problem is not even what I though it was first, that the Content-Transfer-Encoding is not updated, actually it is. What is not updated is the display: ===== Attachments ===== -> - 1 [text/plain, 8bit, 0.1K] /tmp/mutt-*************** Hop, I filter, and it stays ===== Attachments ===== -> - 1 [text/plain, 8bit, 0.1K] /tmp/mutt-*************** whereas before 0.89 it was (correctly) updated to ===== Attachments ===== -> - 1 [text/plain, 7bit, 0.1K] /tmp/mutt-*************** If (after filtering), I edit the content-transfer-encoding, it shows up at 7 bit. So it's only a question of displaying the correct thing, and at that point I am clueless at where to look in the code. Still, it's a real problem as the only way to know that my filter did what it's supposed to do is to see this field changed on my screen. F. -- Fabrice Planchon (ph) 609/258-6495 Applied Math Program, 210 Fine Hall (fax) 609/258-1735 From shaug@callamer.com Mon Feb 2 10:56:24 1998 Return-Path: shaug@callamer.com Received: from gromit.callamer.com ([24.2.127.48]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id KAA23677 for ; Mon, 2 Feb 1998 10:56:22 -0800 (PST) Received: (qmail 13783 invoked by uid 3992); 2 Feb 1998 18:52:54 -0000 Message-ID: <19980202105253.17636@callamer.com> Date: Mon, 2 Feb 1998 10:52:53 -0800 From: "O'Shaughnessy Evans" To: mutt-users@cs.hmc.edu Subject: Re: Getting out of 'limit' Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980128160230.19141@ipk.fhg.de> <19980128171715.14681@matrix.42.org> <19980128173548.40264@matrix.42.org> <19980128132518.56886@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980128132518.56886@cs.swarthmore.edu>; from Daniel Eisenbud on Wed, Jan 28, 1998 at 01:25:18PM -0500 Organization: GST Call America, Inc. Daniel Eisenbud's keyboard spewed forth thus, on Wed, Jan 28, 1998: >>> On Wed, Jan 28, 1998 at 04:02:30PM +0100, Tobias Richter wrote: >>>> I would prefer 'l' to see all messages again. > > I think that this is a bad idea. I like to be able to abort limiting by > hitting return, just like I can abort most prompts if I leave them > blank. Since the macro solution works so well, I don't really think > that this problem needs a code change. > > -Daniel I'm putting in my vote for "please don't hard-code a change". I agree with Daniel that consistency of usage is far more important than a solution that's fixable with a macro anyway. -- - O'Shaughnessy Evans - San Luis Obispo, California From sec@matrix.42.org Mon Feb 2 11:03:31 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA25769 for ; Mon, 2 Feb 1998 11:03:27 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id UAA29234 (sender ); Mon, 2 Feb 1998 20:03:15 +0100 (CET) Message-ID: <19980202200313.28477@matrix.42.org> Date: Mon, 2 Feb 1998 20:03:14 +0100 From: Stefan `Sec` Zehl To: mutt-users@cs.hmc.edu Subject: Re: filter-entry and encoding Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202085536.58895@math.princeton.edu> <19980202180451.41363@matrix.42.org> <19980202114653.35586@rsn.hp.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=HlL+5n6rz5pIUxbD X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202114653.35586@rsn.hp.com>; from David DeSimone on Mon, Feb 02, 1998 at 11:46:53AM -0600 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii On Mon, Feb 02, 1998 at 11:46:53AM -0600, David DeSimone wrote: > I think the bug he's referring to is the fact that Mutt doesn't > re-evaluate its choice of content-encoding if you filter the text. Whoops, i stand corrected. I didn't parse the message correctly. Maybe I should get something to eat first, before continuning to answer mail. CU, Sec -- Programs that make a computer worth to use: FreeBSD, zsh, mutt, wmx, procmail, vim, perl, less, LaTeX, fetch, slrn, screen, ssh, pgp, ircII, sendfile --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3i iQEVAwUBNNYYap5z6wpNWO5RAQF9Bgf/YECQR5Zk7pmfuwy4evXNfv4wfgYQaTeQ rQDJwTP/m1hUd1xHTlDCPQ3mmAunIVzakDq/6kZGwTjPbHRcmGNpVZAtgigeeGdV GYzKeOX3ZYOTnUmz2DKiueq4qZJw+LcQQcYFJYgC1eXYp12sjyHf5MNsvl1TfXPK u9Fd37rwBRFvgXHvbbgEDJbikOOQvW93L1Ro2jU71xnxc0kQUuEmxqk22ZvnMB5L 4m9ccJrz8lqwjjHZ8wfNrJuv6fAgeWh4PzpsDSL2tGjBtLNoOEL9Pfg5D+Sg6nt9 NYb0lAs1Q0c/4GwfCHKMVR7i7Jw8V7f+vWkwIlwbtEPsSCW4fdEZTQ== =x4wK -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- From eisenbud@allspice.cs.swarthmore.edu Mon Feb 2 11:09:43 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA27600 for ; Mon, 2 Feb 1998 11:09:40 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id OAA08443; Mon, 2 Feb 1998 14:09:33 -0500 (EST) Message-ID: <19980202140932.47994@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 14:09:32 -0500 From: Daniel Eisenbud To: Mutt users mailing list Subject: Repost: [0.89.1i] bugfix: buffy sanity checks Mail-Followup-To: Mutt users mailing list References: <19980202111333.01745@att.com> <19980202133233.45583@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="bp/iNruPH9dso1Pn" X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202133233.45583@cs.swarthmore.edu>; from Daniel Eisenbud on Mon, Feb 02, 1998 at 01:32:33PM -0500 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii On Mon, Feb 02, 1998 at 01:32:33PM -0500, Daniel Eisenbud wrote: > Hmm, I guess that mutt_buffy_check() returned 1, but there were no > mailboxes flagged as "new". Which can happen easily if buffy is 2 > seconds stale, or if there's some other bug in mutt_buffy_check() that I > haven't found. The attached patch adds a bunch of sanity checks to > buffy.c that should help prevent this kind of thing (including a > possible infinite loop.) It also fixes the minor problem of buffy > sometimes checking twice in a row after opening a mailbox. Hmm, that patch had garbage at the end. I'm not sure how it got there, and the rest of the patch is probably OK, but here's a fresh version. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.de.buffy_sanity.1" --- buffy.c Mon Feb 2 13:26:34 1998 +++ ../mutt-0.89.1i.orig/buffy.c Sat Jan 31 08:13:06 1998 @@ -219,9 +219,6 @@ int mutt_force_buffy_check(void) char path[_POSIX_PATH_MAX]; struct stat contex_sb; - /* update time of last check */ - BuffyTime = time (NULL); - /* fastest return if there are no mailboxes */ if (!Incoming) return 0; @@ -336,7 +333,7 @@ int mutt_force_buffy_check(void) return (BuffyCount); } -/* this only checks for new mail each BuffyTimeout (def. 3) seconds */ +/* this only checks for new mail each three seconds */ int mutt_buffy_check (void) { time_t t; @@ -346,6 +343,7 @@ int mutt_buffy_check (void) t = time (NULL); if ((t - BuffyTime) < BuffyTimeout) return BuffyCount; + BuffyTime = t; return mutt_force_buffy_check(); } @@ -368,10 +366,6 @@ void mutt_buffy_notify (void) return; } } - /* there were no mailboxes needing to be notified, so clean up since - * BuffyNotify has somehow gottten out of sync - */ - BuffyNotify = 0; } } @@ -396,39 +390,26 @@ void mutt_buffy (char *s) case 1: - while (tmp && !tmp->new) + while (!tmp->new) tmp = tmp->next; - if (!tmp) - { - s = '\0'; - mutt_force_buffy_check (); /* buffy was wrong - resync things */ - break; - } strcpy (s, tmp->path); mutt_pretty_mailbox (s); break; default: - - count = 0; - while (count < 3) + + FOREVER { if (strcmp (s, tmp->path) == 0) - count++; - else if (count && tmp->new) + count = 0; + else if (count == 0 && tmp->new) break; tmp = tmp->next; - if (!tmp) + if (tmp == NULL) { tmp = Incoming; - count++; + count = 0; } - } - if (count >= 3) - { - s = '\0'; - mutt_force_buffy_check (); /* buffy was wrong - resync things */ - break; } strcpy (s, tmp->path); mutt_pretty_mailbox (s); --bp/iNruPH9dso1Pn-- From hazmat@unixshell.com Mon Feb 2 11:33:20 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (hazmat@unixshell.com [204.170.16.210]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA04335 for ; Mon, 2 Feb 1998 11:33:15 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id OAA01372; Mon, 2 Feb 1998 14:33:35 -0500 (EST) Message-ID: <19980202143335.24929@unixshell.com> Date: Mon, 2 Feb 1998 14:33:35 -0500 From: Ken W To: mutt Subject: status_on_top modification? Mail-Followup-To: mutt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X I apologize if this is possible, but I set status_on_top and unset help. In 0.88 the index status bar stayed on top, but the pager status line stayed on the bottom, and I really liked it. In 0.89, both are on the bottom with this setting. I suppose that it is actually fixed this way, but is there any way to go back to this? Thanks. -Ken -- hazmat@unixshell.com hazmat@shore.net http://www.shore.net/~hazmat From eisenbud@allspice.cs.swarthmore.edu Mon Feb 2 11:39:50 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA06284 for ; Mon, 2 Feb 1998 11:39:45 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id OAA10153; Mon, 2 Feb 1998 14:39:11 -0500 (EST) Message-ID: <19980202143910.07611@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 14:39:10 -0500 From: Daniel Eisenbud To: Mutt users mailing list Subject: Re: [0.89.1i] bugfix: buffy sanity checks Mail-Followup-To: Mutt users mailing list References: <19980202111333.01745@att.com> <19980202133233.45583@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202133233.45583@cs.swarthmore.edu>; from Daniel Eisenbud on Mon, Feb 02, 1998 at 01:32:33PM -0500 On Mon, Feb 02, 1998 at 01:32:33PM -0500, Daniel Eisenbud wrote: > On Mon, Feb 02, 1998 at 11:13:33AM -0500, Vikas Agnihotri wrote: > > I have the following macro: > > > > macro index ,e "!vim $HOME/.muttrc\n:source ~/.muttrc\n\cl" > > macro pager ,e "!vim $HOME/.muttrc\n:source ~/.muttrc\n\cl" > > > > This has been working fine forever. Today, when I exited Vim, I got a core > > dump. > > > > Guess, a mail just happened to come in when I exited from the editor? > > Still, it has never dumped core on me before. > > Hmm, I guess that mutt_buffy_check() returned 1, but there were no > mailboxes flagged as "new". Which can happen easily if buffy is 2 > seconds stale, or if there's some other bug in mutt_buffy_check() that I > haven't found. The attached patch adds a bunch of sanity checks to > buffy.c that should help prevent this kind of thing (including a > possible infinite loop.) It also fixes the minor problem of buffy > sometimes checking twice in a row after opening a mailbox. Some day's I can't get anything right. That patch was reversed; you'll need to apply it with '-R'. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From hazmat@unixshell.com Mon Feb 2 11:43:17 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (hazmat@unixshell.com [204.170.16.210]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA07363 for ; Mon, 2 Feb 1998 11:43:11 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id OAA01655; Mon, 2 Feb 1998 14:43:30 -0500 (EST) Message-ID: <19980202144329.15940@unixshell.com> Date: Mon, 2 Feb 1998 14:43:29 -0500 From: Ken W To: mutt Subject: the FreeBSD 'make install' error Mail-Followup-To: mutt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X Where exactly can I disable setgid? In config.h that gets made after configure, I tried commenting it out and #undef and even commenting out every instance of chown and chgrp and still make install craps out. I would just like it to complete. Thanks. -Ken -- hazmat@unixshell.com hazmat@shore.net http://www.shore.net/~hazmat From rnapier@cisco.com Mon Feb 2 11:52:03 1998 Return-Path: rnapier@cisco.com Received: from claret.cisco.com (claret.cisco.com [171.69.160.39]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA09563 for ; Mon, 2 Feb 1998 11:52:01 -0800 (PST) Received: (rnapier@localhost) by claret.cisco.com (8.8.4-Cisco.1/8.6.5) id OAA19510; Mon, 2 Feb 1998 14:51:30 -0500 (EST) Message-ID: <19980202145130.58289@cisco.com> Date: Mon, 2 Feb 1998 14:51:30 -0500 From: Robert Napier To: Mutt Users List Subject: Re: tag-subthread; user input on macros Mail-Followup-To: Mutt Users List References: <19980202105801.08912@cisco.com> <19980202120927.45543@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980202120927.45543@att.com>; from Vikas Agnihotri on Mon, Feb 02, 1998 at 12:09:27PM -0500 On Mon, Feb 02, 1998 at 12:09:27PM -0500, Vikas Agnihotri wrote: > On Mon, Feb 02, 1998 at 10:58:01AM -0500, Robert Napier wrote: > > I'm also looking for a way to put user input into a macro. For > > IIRC, this has been on the wish list for some time. Quite difficult to IIRC? I suddenly feel like a newbie. > implement, as I understand it. > > > macro index d s=.trashcan^M > > macro pager d s=.trashcan^M > > macro index \CD \et;s=.trashcan^M > > macro pager \CD \et;s=.trashcan^M > > I have the same macros too, BTW, I just figured out that the last one doesn't work. Apparently, delete-thread isn't implemented in the pager. Was that just an oversight, or is that hard to do? Rob -- Rob Napier | 7025 Kit Creek Road | Check out Triangle Ascension: rnapier@cisco.com | PO Box 14987 | http://www.serve.com/napier/mage 919/472-3941 | RTP, NC 27709 | +===========================================================================+ | Imagine what my body would sound like / Slamming against those rocks | | When it lands / Will my eyes / Be closed or open? -- Bjork "Hyper Ballad" | +===========================================================================+ From eisenbud@allspice.cs.swarthmore.edu Mon Feb 2 11:53:28 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA10084 for ; Mon, 2 Feb 1998 11:53:25 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id OAA10509; Mon, 2 Feb 1998 14:53:11 -0500 (EST) Message-ID: <19980202145311.19776@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 14:53:11 -0500 From: Daniel Eisenbud To: Mutt User List Subject: Re: Segmentation fault while sending a message Mail-Followup-To: Mutt User List References: <19980202010105.47002@ask.tele.dk> <19980202180957.07938@matylda.silesia.linux.org.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202180957.07938@matylda.silesia.linux.org.pl>; from Daniel Bauke on Mon, Feb 02, 1998 at 06:09:57PM +0100 On Mon, Feb 02, 1998 at 06:09:57PM +0100, Daniel Bauke wrote: > 02 Feb 98 (Monday), 09:21:37AM +0100, Daniel Bauke: > > > Next is (or rather `was'): when I tried to send an email as a > > root... It worked perfectly. So, I changed his .muttrc file into my > > personal and then mutt crashed with this `funny' message. Now I know > > where I should find the reasons of his `illness'. > > > > I'll send a report, as soon as I find a bug. > > Well... I don't know how to say it... My fault. I tried to improve > mutt's great advantages and set: > > lists $mailboxes > > Because I was to lazy (or maybe to smart ;) to rewrite it. Now > everything is OK. Sorry for bothering you with this stupid problem. It's still an annoying bug, and should be fixed. I see how to quickly and superficially fix one aspect, checking whether a pointer is null when checking for mailing list recipients, but that null pointer shouldn't get into the list of mailing lists in the first place. The problem is in how mutt expands environment variables (it looks for the environment variable $mailboxes above,) so a fix will have to wait until I or someone else looks into that. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From vaxerdec@vaxerdec.dyn.ml.org Mon Feb 2 12:01:53 1998 Return-Path: vaxerdec@vaxerdec.dyn.ml.org Received: from node21.frontiernet.net (root@node21.frontiernet.net [205.232.174.29]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA12342 for ; Mon, 2 Feb 1998 12:01:48 -0800 (PST) Received: from vaxerdec.dyn.ml.org (as5200-10-1.roc.ny.frontiernet.net [209.130.148.103]) by node21.frontiernet.net (8.8.8/8.8.6) with ESMTP id PAA05558 for ; Mon, 2 Feb 1998 15:01:45 -0500 Received: (from vaxerdec@localhost) by vaxerdec.dyn.ml.org (8.8.8/8.8.8) id OAA02593; Mon, 2 Feb 1998 14:58:49 -0500 Message-ID: <19980202145849.47283@dyn.ml.org> Date: Mon, 2 Feb 1998 14:58:49 -0500 From: Scott McDermott To: mutt-users@cs.hmc.edu Subject: Re: e-mail/HTML enhancement? - Nope Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202104324.60584@td2cad.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 In-Reply-To: <19980202104324.60584@td2cad.intel.com>; from Shawn D. McPeek on Mon, Feb 02, 1998 at 10:43:24AM -0800 On Mon, Feb 02, 1998 at 10:43:24AM -0800, Shawn D. McPeek wrote: > It sounds like Microsoft, Qualcomm, and Lotus are proposing an addition to > HTML that would "enhance" the display of email messages and their multiple > replies. Check out the article here: Sigh, just read it. Unfortunately, idiocy proliferates and there is nothing that we can do about it. It may be the case that this stuff will be a godsend to many people, however ridiculous that may seem to more `proficient' users. What amazes me is that people can't figure out that they should delete irrelevant portions or quotes themselves so that they don't accumulate like the article complains about. It seems that the hand-holding must extend even here. > "The proposal would also allow viewing of messages by different > ordering schemes - such as by date or by author." > Never be led astray onto the path of virtue. Do you mean `from' the path of virtue? Or that virtuism may sometimes interfere with what you should do? I believe it was herbert that said something along the lines of "You should never let your morals interfere with What's Right." Scott From dannyman@arh0300.urh.uiuc.edu Mon Feb 2 12:33:27 1998 Return-Path: dannyman@arh0300.urh.uiuc.edu Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA21351 for ; Mon, 2 Feb 1998 12:33:23 -0800 (PST) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id OAA22080; Mon, 2 Feb 1998 14:33:15 -0600 (CST) Message-ID: <19980202143314.32624@urh.uiuc.edu> Date: Mon, 2 Feb 1998 14:33:14 -0600 From: dannyman To: "Shawn D. McPeek" , mutt-users@cs.hmc.edu Subject: Re: e-mail/HTML enhancement? - Nope References: <19980202104324.60584@td2cad.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980202104324.60584@td2cad.intel.com>; from Shawn D. McPeek on Mon, Feb 02, 1998 at 10:43:24AM -0800 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ On Mon, Feb 02, 1998 at 10:43:24AM -0800, Shawn D. McPeek wrote: > "The proposal would also allow viewing of messages by different > ordering schemes - such as by date or by author." I've heard it through the grape vine that Microsoft is planning to introduce a new form of "wheel" that will bring transportation up from the stone-age too. dammit, this plain text works awful nice for me. i hope someone in that coalition will read an RFC sometime ... -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement From eisenbud@allspice.cs.swarthmore.edu Mon Feb 2 12:38:06 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA22499 for ; Mon, 2 Feb 1998 12:38:04 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id PAA12587; Mon, 2 Feb 1998 15:38:01 -0500 (EST) Message-ID: <19980202153801.27064@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 15:38:01 -0500 From: Daniel Eisenbud To: Mutt Users List Subject: Re: tag-subthread; user input on macros Mail-Followup-To: Mutt Users List References: <19980202105801.08912@cisco.com> <19980202120927.45543@att.com> <19980202145130.58289@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202145130.58289@cisco.com>; from Robert Napier on Mon, Feb 02, 1998 at 02:51:30PM -0500 On Mon, Feb 02, 1998 at 02:51:30PM -0500, Robert Napier wrote: > On Mon, Feb 02, 1998 at 12:09:27PM -0500, Vikas Agnihotri wrote: > > On Mon, Feb 02, 1998 at 10:58:01AM -0500, Robert Napier wrote: > > > I'm also looking for a way to put user input into a macro. For > > > > IIRC, this has been on the wish list for some time. Quite difficult to > > IIRC? I suddenly feel like a newbie. If I recall correctly. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From shaug@callamer.com Mon Feb 2 12:46:52 1998 Return-Path: shaug@callamer.com Received: from gromit.callamer.com ([24.2.127.48]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id MAA25098 for ; Mon, 2 Feb 1998 12:46:49 -0800 (PST) Received: (qmail 13990 invoked by uid 3992); 2 Feb 1998 19:41:17 -0000 Message-ID: <19980202114117.64871@callamer.com> Date: Mon, 2 Feb 1998 11:41:17 -0800 From: "O'Shaughnessy Evans" To: mutt Subject: Re: $point_new variable Mail-Followup-To: mutt References: <19980131163051.62151@unixshell.com> <19980131175703.59924@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980131175703.59924@att.com>; from Vikas Agnihotri on Sat, Jan 31, 1998 at 05:57:03PM -0500 Organization: GST Call America, Inc. Vikas Agnihotri's keyboard spewed forth thus, on Sat, Jan 31, 1998: > On Sat, Jan 31, 1998 at 04:30:51PM -0500, Ken W wrote: > > I always used the $point_new variable and its equivalent in Elm and > > would really like it back. Is there at least a patch for this? Why > > folder-hook . "push \t" > ought to do it where TAB (\t) takes you to the first new message > > > was it taken out anyyway? > > Dunno. >From the NEWS file for mutt-0.89i: - removed the $point_new variable. the pointer is now always position on the first new message (if it exists) -- - O'Shaughnessy Evans - http://www.callamerica.net/shaug/ From sec@matrix.42.org Mon Feb 2 12:47:58 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA25362 for ; Mon, 2 Feb 1998 12:47:54 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id VAA00407 (sender ); Mon, 2 Feb 1998 21:47:41 +0100 (CET) Message-ID: <19980202214739.48434@matrix.42.org> Date: Mon, 2 Feb 1998 21:47:39 +0100 From: Stefan `Sec` Zehl To: mutt Subject: Re: status_on_top modification? Mail-Followup-To: mutt References: <19980202143335.24929@unixshell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202143335.24929@unixshell.com>; from Ken W on Mon, Feb 02, 1998 at 02:33:35PM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Mon, Feb 02, 1998 at 02:33:35PM -0500, Ken W wrote: > I apologize if this is possible, but I set status_on_top and unset > help. In 0.88 the index status bar stayed on top, but the pager > status line stayed on the bottom, and I really liked it. In 0.89, > both are on the bottom with this setting. I suppose that it is > actually fixed this way, but is there any way to go back to this? I think you might have applied my pager_status_on_top patch for .88 which lets you control the postion of both status lines independently. You can get the updated version of my patch from my webpage (see header) CU, Sec -- Die Zahl 42 kommt erstaunlich oft vor, dafuer das sie so ungebraeuchlich ist. am 20.8.97 From sec@matrix.42.org Mon Feb 2 12:49:36 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA25993 for ; Mon, 2 Feb 1998 12:49:30 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id VAA00442 (sender ); Mon, 2 Feb 1998 21:49:23 +0100 (CET) Message-ID: <19980202214923.64572@matrix.42.org> Date: Mon, 2 Feb 1998 21:49:23 +0100 From: Stefan `Sec` Zehl To: mutt Subject: Re: the FreeBSD 'make install' error Mail-Followup-To: mutt References: <19980202144329.15940@unixshell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202144329.15940@unixshell.com>; from Ken W on Mon, Feb 02, 1998 at 02:43:29PM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Mon, Feb 02, 1998 at 02:43:29PM -0500, Ken W wrote: > Where exactly can I disable setgid? In config.h that gets made after > configure, I tried commenting it out and #undef and even commenting > out every instance of chown and chgrp and still make install craps > out. I would just like it to complete. I'm doing this for quite a while now, its fairly easy: run ./configure edit config.h and remove the two lines containing: USE_SETGID and USE_DOTLOCK then compile mutt with "make" CU, Sec -- Die kürzesten Computerwitze: 1) Müßte laufen. From eisenbud@allspice.cs.swarthmore.edu Mon Feb 2 12:57:49 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA28479 for ; Mon, 2 Feb 1998 12:57:42 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id PAA13157; Mon, 2 Feb 1998 15:57:39 -0500 (EST) Message-ID: <19980202155739.46242@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 15:57:39 -0500 From: Daniel Eisenbud To: Mutt users mailing list Subject: Re: [0.89.1i] bugfix: buffy sanity checks Mail-Followup-To: Mutt users mailing list References: <19980202111333.01745@att.com> <19980202133233.45583@cs.swarthmore.edu> <19980202143910.07611@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202143910.07611@cs.swarthmore.edu>; from Daniel Eisenbud on Mon, Feb 02, 1998 at 02:39:10PM -0500 On Mon, Feb 02, 1998 at 02:39:10PM -0500, Daniel Eisenbud wrote: > Some day's I can't get anything right. That patch was reversed; you'll > need to apply it with '-R'. . That was unclear and misleading, given which message it was in reply to. My first version of the patch had garbage at the end, but was not reversed. The recommended way of applying the patch is to apply the second one I posted with '-R'. Sorry for the confusion, folks. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From rsk@gsp.org Mon Feb 2 13:37:45 1998 Return-Path: rsk@gsp.org Received: from gsp.org (rsk.itw.com [208.211.3.21]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA10276 for ; Mon, 2 Feb 1998 13:37:42 -0800 (PST) Received: (from rsk@localhost) by gsp.org (8.8.8/8.8.8) id QAA09687; Mon, 2 Feb 1998 16:38:20 -0500 (EST) Message-ID: <19980202163819.25476@wombat> Date: Mon, 2 Feb 1998 16:38:19 -0500 From: Rich Kulawiec To: dannyman Cc: mutt-users@cs.hmc.edu Subject: Re: e-mail/HTML enhancement? - Nope References: <19980202104324.60584@td2cad.intel.com> <19980202143314.32624@urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980202143314.32624@urh.uiuc.edu>; from dannyman on Mon, Feb 02, 1998 at 02:33:14PM -0600 On Mon, Feb 02, 1998 at 02:33:14PM -0600, dannyman wrote: > dammit, this plain text works awful nice for me. i hope someone in that > coalition will read an RFC sometime ... Oh, you just *don't* understand! Here, read this excerpt from the forthcoming FAQ from Miss Mailers: > Q. Should I format my messages with HTML? > > A. Absolutely. HTML isn't just intended for the web, you know; in fact, > it makes complete sense to send *all* of your messages in HTML, because > your deathless prose will make an even bigger impression if you surround > it with HTML tags. Think of how much better Henry V's speech > before the battle of Agincourt would read if Shakespeare had access to HTML: > > 
> 	If we are mark'd to die, we are enow
> 	To do our country loss; and if to live,
> 	The fewer men, the greater share of honour.
> 	God's will! I pray thee, wish not one man more.
> 	
> 	By Jove, I am not covetous for gold,
> 	Nor care I who doth feed upon my cost;
> 	It yearns me not if men my garments wear;
> 	Such outward things dwell not in my desires:
> 	But if it be a sin to covet honour,
> 	I am the most offending soul alive.
>
> > So don't bother with a spell checker; don't waste your time trying > to edit your comments into comprehensible prose; just trot out those > HTML tags and go to it! :-) Cheers, Rich From eisenbud@allspice.cs.swarthmore.edu Mon Feb 2 13:41:28 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA11530 for ; Mon, 2 Feb 1998 13:41:26 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id QAA15472; Mon, 2 Feb 1998 16:41:13 -0500 (EST) Message-ID: <19980202164113.26024@cs.swarthmore.edu> Date: Mon, 2 Feb 1998 16:41:13 -0500 From: Daniel Eisenbud To: mutt Subject: Re: the FreeBSD 'make install' error Mail-Followup-To: mutt References: <19980202144329.15940@unixshell.com> <19980202214923.64572@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202214923.64572@matrix.42.org>; from Stefan `Sec` Zehl on Mon, Feb 02, 1998 at 09:49:23PM +0100 On Mon, Feb 02, 1998 at 09:49:23PM +0100, Stefan `Sec` Zehl wrote: > On Mon, Feb 02, 1998 at 02:43:29PM -0500, Ken W wrote: > > Where exactly can I disable setgid? In config.h that gets made after > > configure, I tried commenting it out and #undef and even commenting > > out every instance of chown and chgrp and still make install craps > > out. I would just like it to complete. > > I'm doing this for quite a while now, its fairly easy: > > run ./configure > > edit config.h and remove the two lines containing: > USE_SETGID and > USE_DOTLOCK > > then compile mutt with "make" make install may also give you problems, but if worst comes to worst you can just do "make -k install" and then copy the mutt binary by hand. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From elb@chaos.com Mon Feb 2 13:43:15 1998 Return-Path: elb@chaos.com Received: from chaos.com (elb@ppp155.day-oh.siscom.net [206.244.171.155]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA12763 for ; Mon, 2 Feb 1998 13:43:11 -0800 (PST) Received: (from elb@localhost) by chaos.com (8.7.6/8.6.12) id QAA10744; Mon, 2 Feb 1998 16:47:32 -0500 Message-ID: <19980202164732.07832@trc-inc.com> Date: Mon, 2 Feb 1998 16:47:32 -0500 From: Ethan Blanton To: mutt-users@cs.hmc.edu Subject: Configuration files Mail-Followup-To: mutt-users@cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Operating-System: Linux I am reasonably new to the "mutt scene", but I have a couple of questions/suggestions to make... If any of them are stupid, please let me know in a nice sort of way. :-) I'm not much of a programmer, so I may not know what is reasonable and what is not. Is it possible to implement an s-lang configuration file? (ala JED) I know that mutt includes support for the s-lang screen libraries (which I use, as they seem to work better than ncurses), but I have no idea how difficult it would be to put in an s-lang interpreter... It seems to me (from way up here in non-coder land!) that the mutt config files are a weak point... (From looking at the number of times my config file "breaks" from ver. to ver. due to changes, and the sometimes unfriendly syntax) I am personally familiar enough with computers/configs in general that I had little trouble, but I can see where a newbie would fall down here. Failing this, what about conditionals? I would like to be able to set variables to control flow of the file... If nothing else something such as #define, #ifdef, etc. Like I stated before, let me know nicely if this is already done/impossible. Thanks, Ethan Blanton From sec@matrix.42.org Mon Feb 2 14:06:54 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id OAA25278 for ; Mon, 2 Feb 1998 14:06:45 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id XAA01214 (sender ); Mon, 2 Feb 1998 23:06:42 +0100 (CET) Message-ID: <19980202230641.38572@matrix.42.org> Date: Mon, 2 Feb 1998 23:06:41 +0100 From: Stefan `Sec` Zehl To: mutt-users@cs.hmc.edu Subject: Re: Configuration files Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202164732.07832@trc-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202164732.07832@trc-inc.com>; from Ethan Blanton on Mon, Feb 02, 1998 at 04:47:32PM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Mon, Feb 02, 1998 at 04:47:32PM -0500, Ethan Blanton wrote: > Is it possible to implement an s-lang configuration file? (ala JED) I know > that mutt includes support for the s-lang screen libraries (which I use, as > they seem to work better than ncurses), but I have no idea how difficult it > would be to put in an s-lang interpreter... Mutt uses only the curses-emulation mode of s-lang. As it was already discussed on this list (many moons ago :) mutt will probably never add support for the s-lang interpreter, as it would be far to much work, and would render it incompatible with ncurses (which i prefer over s-lang ) CU, Sec -- So viel ist in so kurzer Zeit zu tun. From blong@shell9.ba.best.com Mon Feb 2 14:33:44 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id OAA05722 for ; Mon, 2 Feb 1998 14:33:42 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id OAA19799; Mon, 2 Feb 1998 14:32:55 -0800 (PST) Message-ID: <19980202143255.27286@shell9.ba.best.com> Date: Mon, 2 Feb 1998 14:32:55 -0800 From: Brandon Long To: mutt-users@cs.hmc.edu Subject: Re: Configuration files Reply-To: blong@fiction.net Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202164732.07832@trc-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980202164732.07832@trc-inc.com>; from Ethan Blanton on Mon, Feb 02, 1998 at 04:47:32PM -0500 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/02/98 Ethan Blanton uttered the following other thing: > Is it possible to implement an s-lang configuration file? (ala JED) I know > that mutt includes support for the s-lang screen libraries (which I use, as > they seem to work better than ncurses), but I have no idea how difficult it > would be to put in an s-lang interpreter... It seems to me (from way up > here in non-coder land!) that the mutt config files are a weak point... > (From looking at the number of times my config file "breaks" from ver. to > ver. due to changes, and the sometimes unfriendly syntax) I am personally > familiar enough with computers/configs in general that I had little trouble, > but I can see where a newbie would fall down here. We use slang merely for the curses emulation. There has been no intention to use any of the other stuff that slang comes with. The syntax of the config file works just fine, and moving to a slang based one would merely make for different problems (you are proposing one set of esoteric commands over another, because you have spent the time to learn one. Others who have not learned that one aren't going to be helped by it). In addition, mutt has never proposed to be the mailer for newbies. Its syntax is designed to do what expert users want to do. > Failing this, what about conditionals? I would like to be able to set > variables to control flow of the file... If nothing else something such as > #define, #ifdef, etc. hooks are conditionals, based on the various conditions one could expect in an mua. send-hook, folder-hook, etc, what other conditions do you want? Brandon -- Brandon Long "A fool: anyone who thinks he sees what God is doing." MD6 Crash Test Dummy -- Kurt Vonnegut, Jr. Intel Corporation I'm too low on the totem pole to speak for Intel. http://www.fiction.net/blong/ From byrial@post3.tele.dk Mon Feb 2 16:19:56 1998 Return-Path: byrial@post3.tele.dk Received: from cgi.inet.tele.dk (cgi.inet.tele.dk [194.182.149.95]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id QAA15283 for ; Mon, 2 Feb 1998 16:19:50 -0800 (PST) Received: (qmail 35412 invoked from network); 3 Feb 1998 00:19:40 -0000 Received: from post3.tele.dk (194.239.134.166) by cgi.inet.tele.dk with SMTP; 3 Feb 1998 00:19:40 -0000 Received: from ask.ask ([194.239.129.77]) by post3.tele.dk (Netscape Mail Server v2.02) with ESMTP id AAB70950 for ; Tue, 3 Feb 1998 01:19:37 +0100 Received: (qmail 731 invoked by uid 500); 2 Feb 1998 23:49:08 -0000 Message-ID: <19980203004907.02831@ask.tele.dk> Date: Tue, 3 Feb 1998 00:49:07 +0100 From: Byrial Jensen To: Mutt users mailing list Cc: Byrial Jensen Subject: Re: Repost: [0.89.1i] bugfix: buffy sanity checks Mail-Followup-To: Mutt users mailing list References: <19980202111333.01745@att.com> <19980202133233.45583@cs.swarthmore.edu> <19980202140932.47994@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=iS0Q5IWpPtfppvPm X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202140932.47994@cs.swarthmore.edu>; from Daniel Eisenbud on Mon, Feb 02, 1998 at 02:09:32PM -0500 --iS0Q5IWpPtfppvPm Content-Type: text/plain; charset=us-ascii On Mon, Feb 02, 1998 at 02:09:32PM -0500, Daniel Eisenbud wrote: > On Mon, Feb 02, 1998 at 01:32:33PM -0500, Daniel Eisenbud wrote: > > The attached patch adds a bunch of sanity checks to > > buffy.c that should help prevent this kind of thing (including a > > possible infinite loop.) It also fixes the minor problem of buffy > > sometimes checking twice in a row after opening a mailbox. Here is second version of this patch which furthermore removes some superfluous assignments. Best regards - Byrial --iS0Q5IWpPtfppvPm Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.de-bj.buffy_sanity.1-2" --- buffy.c~ Tue Feb 3 00:32:55 1998 +++ buffy.c Tue Feb 3 00:34:42 1998 @@ -339,12 +339,10 @@ /* this only checks for new mail each BuffyTimeout (def. 3) seconds */ int mutt_buffy_check (void) { - time_t t; /* fastest return if there are no mailboxes */ if (!Incoming) return 0; - t = time (NULL); - if ((t - BuffyTime) < BuffyTimeout) + if ((time (NULL) - BuffyTime) < BuffyTimeout) return BuffyCount; return mutt_force_buffy_check(); } @@ -383,11 +381,11 @@ */ void mutt_buffy (char *s) { - int count = 0; + int count; BUFFY *tmp = Incoming; mutt_expand_path (s, _POSIX_PATH_MAX); - switch (count = mutt_buffy_check ()) + switch (mutt_buffy_check ()) { case 0: --iS0Q5IWpPtfppvPm Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.de-bj.buffy_sanity.2" --- buffy.c.orig Tue Feb 3 00:32:31 1998 +++ buffy.c Tue Feb 3 00:34:42 1998 @@ -219,6 +219,9 @@ char path[_POSIX_PATH_MAX]; struct stat contex_sb; + /* update time of last check */ + BuffyTime = time (NULL); + /* fastest return if there are no mailboxes */ if (!Incoming) return 0; @@ -333,17 +336,14 @@ return (BuffyCount); } -/* this only checks for new mail each three seconds */ +/* this only checks for new mail each BuffyTimeout (def. 3) seconds */ int mutt_buffy_check (void) { - time_t t; /* fastest return if there are no mailboxes */ if (!Incoming) return 0; - t = time (NULL); - if ((t - BuffyTime) < BuffyTimeout) + if ((time (NULL) - BuffyTime) < BuffyTimeout) return BuffyCount; - BuffyTime = t; return mutt_force_buffy_check(); } @@ -366,6 +366,10 @@ return; } } + /* there were no mailboxes needing to be notified, so clean up since + * BuffyNotify has somehow gottten out of sync + */ + BuffyNotify = 0; } } @@ -377,11 +381,11 @@ */ void mutt_buffy (char *s) { - int count = 0; + int count; BUFFY *tmp = Incoming; mutt_expand_path (s, _POSIX_PATH_MAX); - switch (count = mutt_buffy_check ()) + switch (mutt_buffy_check ()) { case 0: @@ -390,26 +394,39 @@ case 1: - while (!tmp->new) + while (tmp && !tmp->new) tmp = tmp->next; + if (!tmp) + { + s = '\0'; + mutt_force_buffy_check (); /* buffy was wrong - resync things */ + break; + } strcpy (s, tmp->path); mutt_pretty_mailbox (s); break; default: - - FOREVER + + count = 0; + while (count < 3) { if (strcmp (s, tmp->path) == 0) - count = 0; - else if (count == 0 && tmp->new) + count++; + else if (count && tmp->new) break; tmp = tmp->next; - if (tmp == NULL) + if (!tmp) { tmp = Incoming; - count = 0; + count++; } + } + if (count >= 3) + { + s = '\0'; + mutt_force_buffy_check (); /* buffy was wrong - resync things */ + break; } strcpy (s, tmp->path); mutt_pretty_mailbox (s); --iS0Q5IWpPtfppvPm-- From blong@shell9.ba.best.com Mon Feb 2 16:30:05 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA18713 for ; Mon, 2 Feb 1998 16:30:02 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id QAA26218; Mon, 2 Feb 1998 16:29:32 -0800 (PST) Message-ID: <19980202162932.27341@shell9.ba.best.com> Date: Mon, 2 Feb 1998 16:29:32 -0800 From: Brandon Long To: MUTT Mailing List Subject: Re: [0.89.1i] Editor Hanging Reply-To: blong@fiction.net Mail-Followup-To: MUTT Mailing List References: <19980202010623.50287@telesys.tnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980202010623.50287@telesys.tnet.com>; from Kevin W. Reed on Mon, Feb 02, 1998 at 01:06:23AM -0700 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/02/98 Kevin W. Reed uttered the following other thing: > On Feb 01, Clint Olsen wrote: > > > > On Feb 01, Kevin W. Reed wrote: > > > > > > I have just found out that this occurs when accessing any outside > > > program from mutt. Ispell does the same thing. I suspect it has > > > something to do with forking but have not been able to find the > > > code that is actually doing the calls yet... > > > > Hmm, I don't see any problem here. > > I barely know what I'm doing in this area as I don't write fork > functions very often. > > The first thing that I tried was replace the actual fork function > itself with a system(xx) call. I thought perhaps the forking function > itself was the possible problem. The results were the same. > > Next, I assumed that one of the sigaction statements was causing the > problem so I commented out all the SIGCHLD ones first (both sigaction > an sigaddset). > > This worked without any problems. After editing in the editor, it > returned like it should with no halting. > > Perhaps the SCO version of that signal is screwed up?? I'm not really > sure what it does in anycase. > > BTW: a compilation of the same source (original that is) on Linux > Redhat worked just fine... Just the SCO one is hanging on the forks. Sounds like buggy signals, is this an old version of SCO? We'd need an expert on SCO to tell use what the correct fix is, so we can put the fix in the code (just commenting out all of the sigaction() commands is probably not the correct fix). Brandon -- Brandon Long God took 6 days to create the world, but the MD6 Crash Test Dummy first one was an allnighter. Intel Corporation - leibniz rumor I'm too low on the totem pole to speak for Intel. http://www.fiction.net/blong/ From Ulli.Horlacher@RUS.Uni-Stuttgart.DE Mon Feb 2 16:42:58 1998 Return-Path: Ulli.Horlacher@RUS.Uni-Stuttgart.DE Received: from noc.belwue.de (root@noc.BelWue.DE [129.143.2.1]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA23029 for ; Mon, 2 Feb 1998 16:42:55 -0800 (PST) Received: from bofh.belwue.de (bofh.BelWue.DE [129.143.2.24]) by noc.belwue.de (8.8.8/8.8.8) with ESMTP id BAA13095 for ; Tue, 3 Feb 1998 01:41:56 +0100 (MET) env-from (framstag@bofh.belwue.de) Received: (from framstag@localhost) by bofh.belwue.de (8.8.8/8.8.7) id BAA16824; Tue, 3 Feb 1998 01:41:56 +0100 (MET) Message-ID: <19980203014156.04108@bofh.belwue.de> Date: Tue, 3 Feb 1998 01:41:56 +0100 From: Ulli Horlacher To: mutt-users@cs.hmc.edu Subject: Re: Configuration files Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202164732.07832@trc-inc.com> <19980202143255.27286@shell9.ba.best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980202143255.27286@shell9.ba.best.com>; from Brandon Long on Mon, Feb 02, 1998 at 02:32:55PM -0800 On Mon 1998-02-02 (14:32), Brandon Long wrote: > > Failing this, what about conditionals? I would like to be able to set > > variables to control flow of the file... If nothing else something such as > > #define, #ifdef, etc. > > hooks are conditionals, based on the various conditions one could expect > in an mua. send-hook, folder-hook, etc, what other conditions do you > want? Something like: #if $DISPLAY == "*:0" #else #endif I miss this REALLY! -- \ Ulli 'Framstag' Horlacher \ BelWue-Koordination \ framstag@belwue.de \ \ Universitaet Stuttgart \ Allmandring 30 \ D-70550 Stuttgart \ Germany \ \ SAFT://saft.belwue.de/framstag \ HTTP://www.belwue.de/ \ \ "X.500: Security through Complexity" - Juergen G. \ From michael@tis.com Mon Feb 2 16:52:19 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA26423 for ; Mon, 2 Feb 1998 16:52:17 -0800 (PST) Received: by relay.la.tis.com; id RAA09841; Mon, 2 Feb 1998 17:03:18 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma009823; Mon, 2 Feb 98 17:02:56 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id QAA08986; Mon, 2 Feb 1998 16:49:15 -0800 (PST) Message-ID: <19980202164915.45279@la.tis.com> Date: Mon, 2 Feb 1998 16:49:15 -0800 From: Michael Elkins To: Mutt Users List Subject: Re: tag-subthread; user input on macros Mail-Followup-To: Mutt Users List References: <19980202105801.08912@cisco.com> <19980202120927.45543@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202120927.45543@att.com>; from Vikas Agnihotri on Mon, Feb 02, 1998 at 12:09:27PM -0500 On Mon, Feb 02, 1998 at 12:09:27PM -0500, Vikas Agnihotri wrote: > Look up help for the 'generic' mapping, but I think it is a short-cut to > 'all contexts EXCEPT index and pager', so for index/pager, one would _have_ > to do this 'macro index foo; macro pager foo' business. > > Quite a chore. Why doesnt 'generic' refer to all the contexts, BTW? Actually, generic does apply to `index' as well. The ones that are separate are `pager' and `editor'. The reason they are separate is that the `pager' works quite differently than all the rest of the `menus', so it doesn't really make sense for them to share the same keymap. me From Ulli.Horlacher@RUS.Uni-Stuttgart.DE Mon Feb 2 16:55:27 1998 Return-Path: Ulli.Horlacher@RUS.Uni-Stuttgart.DE Received: from noc.belwue.de (root@noc.BelWue.DE [129.143.2.1]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA27617 for ; Mon, 2 Feb 1998 16:55:23 -0800 (PST) Received: from bofh.belwue.de (bofh.BelWue.DE [129.143.2.24]) by noc.belwue.de (8.8.8/8.8.8) with ESMTP id BAA16515 for ; Tue, 3 Feb 1998 01:55:18 +0100 (MET) env-from (framstag@bofh.belwue.de) Received: (from framstag@localhost) by bofh.belwue.de (8.8.8/8.8.7) id BAA17025; Tue, 3 Feb 1998 01:55:17 +0100 (MET) Message-ID: <19980203015516.08273@bofh.belwue.de> Date: Tue, 3 Feb 1998 01:55:16 +0100 From: Ulli Horlacher To: mutt-users@turing.cs.hmc.edu Subject: collapse threads Mail-Followup-To: mutt-users@turing.cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Perhaps this has been discussed in the past: How about to "collapse" threads to single line like tin does it? This would produce a more readable index of folders with big discussions - like this mailinglist :-) -- \ Ulli 'Framstag' Horlacher \ BelWue-Koordination \ framstag@belwue.de \ \ Universitaet Stuttgart \ Allmandring 30 \ D-70550 Stuttgart \ Germany \ \ SAFT://saft.belwue.de/framstag \ HTTP://www.belwue.de/ \ \ "X.500: Security through Complexity" - Juergen G. \ From rjmill01@starbase.spd.louisville.edu Mon Feb 2 17:25:22 1998 Return-Path: rjmill01@starbase.spd.louisville.edu Received: from starbase.spd.louisville.edu (starbase.spd.louisville.edu [136.165.99.61]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA08233 for ; Mon, 2 Feb 1998 17:25:20 -0800 (PST) Received: from vulcan.spd.louisville.edu (rjmill01@vulcan.spd.louisville.edu [136.165.99.33]) by starbase.spd.louisville.edu (8.8.6/8.6.12) with ESMTP id UAA11304; Mon, 2 Feb 1998 20:25:14 -0500 (EST) Received: (from rjmill01@localhost) by vulcan.spd.louisville.edu (8.8.6/8.8.8) id UAA17820; Mon, 2 Feb 1998 20:25:13 -0500 (EST) Message-ID: <19980202202513.55561@starbase.spd.louisville.edu> Date: Mon, 2 Feb 1998 20:25:13 -0500 From: "Randall J. Million" To: Ulli Horlacher Cc: mutt-users@cs.hmc.edu Subject: Re: Configuration files References: <19980202164732.07832@trc-inc.com> <19980202143255.27286@shell9.ba.best.com> <19980203014156.04108@bofh.belwue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980203014156.04108@bofh.belwue.de>; from Ulli Horlacher on Tue, Feb 03, 1998 at 01:41:56AM +0100 X-Fraternity: /T\ Triangle - Engineering - Architects - Scientists X-Service-Fraternity: Alpha Phi Omega - Delta Theta Chapter : Something like: : : #if $DISPLAY == "*:0" : : #else : : #endif You can use somehting similar to: source ~/.mutt/TERM/rc-`echo $TERM` I know this works, but have never had occasion to use it. randy -- rjmill01@starbase.spd.louisville.edu http://www.spd.louisville.edu/~rjmill01/ Triangle Fraternity http://www.spd.louisville.edu/~triangle/ Alpha Phi Omega http://www.louisville.edu/rso/apo/ "I would rather have men ask why I have no statue than why I have one." - Marcus Porcius Cato From fox@fuzzy.rsn.hp.com Mon Feb 2 17:26:30 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA08818 for ; Mon, 2 Feb 1998 17:26:28 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id RAA17549 for ; Mon, 2 Feb 1998 17:26:27 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id TAA00606; Mon, 2 Feb 1998 19:26:26 -0600 (CST) Message-ID: <19980202192625.64011@rsn.hp.com> Date: Mon, 2 Feb 1998 19:26:25 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: e-mail/HTML enhancement? - Nope Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202104324.60584@td2cad.intel.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=OgqxwSJOaUobr8KG X-Mailer: Mutt 0.89i In-Reply-To: <19980202104324.60584@td2cad.intel.com>; from Shawn D. McPeek on Mon, Feb 02, 1998 at 10:43:24AM -0800 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Shawn D. McPeek wrote: > > Here is my favorite sentence from the article: > > "The proposal would also allow viewing of messages by different > ordering schemes - such as by date or by author." This statement is not as idiotic as it might seem. For instance, if I have a message/rfc822 document with 16 subdocuments within it, does Mutt let me sort those message by date or by author? No. It shows them in the order that they are attached, and only in that order. Is it desirable to sort it any other way? I dunno. I usually only read the first part anyway. :) -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNZyPg0lGhIp2tThAQEtaQMArbJ91Ti3TdGr0SLrx4wyAKvUTlWRv98p PJiYYo8A0xgbkp4X3gEOXaHbmJq1+J4r9HkGH/ao3F+yEJgoJIWj/4+fPgsIEwap 4Q0kA4gva3w3rDqTAUZyS1icb5lomNo7 =jLK4 -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG-- From elb@chaos.com Mon Feb 2 18:58:16 1998 Return-Path: elb@chaos.com Received: from chaos.com (elb@ppp166.day-oh.siscom.net [206.244.171.166]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA11358 for ; Mon, 2 Feb 1998 18:58:11 -0800 (PST) Received: (from elb@localhost) by chaos.com (8.7.6/8.6.12) id WAA00456; Mon, 2 Feb 1998 22:02:50 -0500 Message-ID: <19980202220250.47014@trc-inc.com> Date: Mon, 2 Feb 1998 22:02:50 -0500 From: Ethan Blanton To: mutt-users@cs.hmc.edu Subject: Re: Configuration files Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202164732.07832@trc-inc.com> <19980202143255.27286@shell9.ba.best.com> <19980203014156.04108@bofh.belwue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980203014156.04108@bofh.belwue.de>; from Ulli Horlacher on Tue, Feb 03, 1998 at 01:41:56AM +0100 X-Operating-System: Linux On Tue, Feb 03, 1998 at 01:41:56AM +0100, Ulli Horlacher wrote: > Something like: > > #if $DISPLAY == "*:0" > > #else > > #endif > > > I miss this REALLY! This is exactly what I had in mind; I was actually thinking of using it for connection info... (pop, mailboxes, etc.) This is the idea, though. Ethan From smcpeek@td2cad.intel.com Mon Feb 2 19:16:00 1998 Return-Path: smcpeek@td2cad.intel.com Received: from crotus.sc.intel.com (root@crotus.sc.intel.com [143.183.152.26]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id TAA17793 for ; Mon, 2 Feb 1998 19:15:56 -0800 (PST) Received: from td2cad.intel.com (td2cad-seg48.intel.com [143.183.48.44]) by crotus.sc.intel.com (8.8.6/8.8.5) with ESMTP id TAA22883; Mon, 2 Feb 1998 19:13:56 -0800 (PST) Received: from ctdws66.sc.intel.com (ctdws66.sc.intel.com [143.183.37.136]) by td2cad.intel.com (8.8.5/8.7.3) with SMTP id TAA11579; Mon, 2 Feb 1998 19:13:32 -0800 (PST) Received: by ctdws66.sc.intel.com (AIX 4.1/UCB 5.64/ICES-RS6000) id AA97944; Mon, 2 Feb 1998 19:12:38 -0800 Message-Id: <19980202191238.06359@td2cad.intel.com> Date: Mon, 2 Feb 1998 19:12:38 -0800 From: "Shawn D. McPeek" To: David DeSimone Cc: mutt-users@cs.hmc.edu Subject: Re: e-mail/HTML enhancement? - Nope References: <19980202104324.60584@td2cad.intel.com> <19980202192625.64011@rsn.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85 In-Reply-To: <19980202192625.64011@rsn.hp.com>; from David DeSimone on Mon, Feb 02, 1998 at 07:26:25PM -0600 Previously, David DeSimone wrote: :> Shawn D. McPeek wrote: :> > :> > Here is my favorite sentence from the article: :> > :> > "The proposal would also allow viewing of messages by different :> > ordering schemes - such as by date or by author." :> :> This statement is not as idiotic as it might seem. For instance, if I :> have a message/rfc822 document with 16 subdocuments within it, does Mutt :> let me sort those message by date or by author? No. It shows them in :> the order that they are attached, and only in that order. What you talk about is a single message with multiple attachments, not multiple messages. There is quite a difference, especially when you talk with people who use threads a lot. :> Is it desirable to sort it any other way? I dunno. I usually only read :> the first part anyway. :) If you're talking about messages with multiple attachments, I s'pose it depends on what exactly the attachments are. A thread could very well need to be sorted in multiple ways, but I don't really think that is what you're talking about. If you are though, procmail breaks up digests quite nicely. Shawn -- Labor, n.: One of the processes by which A acquires property for B. -- Ambrose Bierce, "The Devil's Dictionary" From vaxerdec@vaxerdec.dyn.ml.org Mon Feb 2 19:45:50 1998 Return-Path: vaxerdec@vaxerdec.dyn.ml.org Received: from node21.frontiernet.net (root@node21.frontiernet.net [205.232.174.29]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id TAA27725 for ; Mon, 2 Feb 1998 19:45:45 -0800 (PST) Received: from vaxerdec.dyn.ml.org (srv-16-27.roc.ny.frontiernet.net [209.130.133.84]) by node21.frontiernet.net (8.8.8/8.8.6) with ESMTP id WAA100720 for ; Mon, 2 Feb 1998 22:45:43 -0500 Received: (from vaxerdec@localhost) by vaxerdec.dyn.ml.org (8.8.8/8.8.8) id WAA09655; Mon, 2 Feb 1998 22:40:10 -0500 Message-ID: <19980202224010.05645@dyn.ml.org> Date: Mon, 2 Feb 1998 22:40:10 -0500 From: Scott McDermott To: mutt-users@cs.hmc.edu Subject: Re: e-mail/HTML enhancement? - Nope Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202104324.60584@td2cad.intel.com> <19980202192625.64011@rsn.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 In-Reply-To: <19980202192625.64011@rsn.hp.com>; from David DeSimone on Mon, Feb 02, 1998 at 07:26:25PM -0600 On Mon, Feb 02, 1998 at 07:26:25PM -0600, David DeSimone wrote: > This statement is not as idiotic as it might seem. For instance, if I > have a message/rfc822 document with 16 subdocuments within it, does Mutt > let me sort those message by date or by author? No. It shows them in > the order that they are attached, and only in that order. Isn't this the job of the MDA however? I don't see why it wouldn't be possible to make eg procmail rulesets to do this. Scott From roessler@sobolev.rhein.de Tue Feb 3 01:49:59 1998 Return-Path: roessler@sobolev.rhein.de Received: from riemann.iam.uni-bonn.de (root@riemann.iam.uni-bonn.de [131.220.223.83]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id BAA06216 for ; Tue, 3 Feb 1998 01:49:55 -0800 (PST) Received: (from uucp@localhost) by riemann.iam.uni-bonn.de (8.8.5/8.8.5) with UUCP id KAA00917 for mutt-users@cs.hmc.edu; Tue, 3 Feb 1998 10:40:51 +0100 Received: (from roessler@localhost) by sobolev.rhein.de (8.8.8/8.8.8) id JAA10952 ; Tue, 3 Feb 1998 09:57:44 +0100 Message-ID: <19980203095743.49291@sobolev.rhein.de> Date: Tue, 3 Feb 1998 09:57:43 +0100 From: Thomas Roessler To: "The mutt users' list" Subject: [0.89.1i] Extracting PGP keys Mail-Followup-To: The mutt users' list Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=wq9mPyueHGvFACwf X-Mailer: Mutt 0.89.1i --wq9mPyueHGvFACwf Content-Type: multipart/mixed; boundary="bp/iNruPH9dso1Pn" --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable When using the extract-keys function from the attachment menu (by default bound to C-K), there was some undefined behaviour with respect to the prefix component of some state structure. See the attached patch for a fix. tlr --=20 Thomas Roessler =B7 74a353cc0b19 =B7 dg1ktr =B7 http://home.pages.de/~roess= ler/ 2048/CE6AC6C1 =B7 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="patch-0.89.1i.tlr.pgp_extract.1" --- /var/tmp/mutt-0.89.1i/pgp.c Sat Jan 31 14:12:57 1998 +++ mutt-0.89.1i/pgp.c Tue Feb 3 09:53:46 1998 @@ -584,6 +584,8 @@ return; } =20 + memset(&s, 0, sizeof(STATE)); + =20 mutt_mktemp(tempfname); if(!(s.fpout =3D safe_fopen(tempfname, "w"))) { @@ -645,9 +647,12 @@ mutt_perror(tempfname); return; } + + memset(&s, 0, sizeof(STATE)); + =20 s.fpin =3D fp; s.fpout =3D tempfp; - + =20 mutt_body_handler(top, &s); =20 fclose(tempfp); --bp/iNruPH9dso1Pn-- --wq9mPyueHGvFACwf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3in iQEVAwUBNNbcBdImKUTOasbBAQFQBwf/dP7ReH3/I1WJ2+evVNgDRIa5veSeCmHx p8xbw9k26foIoGUUTRR5clngFgSkkWe3Nh/qAw4qX4lwmSH690kgzdc69zV/iyOI i7WYDBMhvR8AUg841X1iPm0FAeD9i6J4t47sQFsJYOZe1ycMaUKMo+VxeR2EsC16 iZkYvqLOH3+LWm1UNb5TeOczHOm3tWr/meMswkdobuLDZ4WDbZrLTe7ZjKt3jDNj R4m97BQt6axD8XKHrVp2sNypODAgQWNCvI3SXkssygDOUy2TkzTdR4nBMB+/PQ2W t8dFbedxdpRRzuKFo2Oi/mTA/bZRHVjaelZdj8dpaZ0N0tiTm/AyUw== =XV9v -----END PGP SIGNATURE----- --wq9mPyueHGvFACwf-- From roessler@sobolev.rhein.de Tue Feb 3 01:50:11 1998 Return-Path: roessler@sobolev.rhein.de Received: from riemann.iam.uni-bonn.de (root@riemann.iam.uni-bonn.de [131.220.223.83]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id BAA06276 for ; Tue, 3 Feb 1998 01:50:06 -0800 (PST) Received: (from uucp@localhost) by riemann.iam.uni-bonn.de (8.8.5/8.8.5) with UUCP id KAA00918 for mutt-users@cs.hmc.edu; Tue, 3 Feb 1998 10:40:51 +0100 Received: (from roessler@localhost) by sobolev.rhein.de (8.8.8/8.8.8) id KAA11387 ; Tue, 3 Feb 1998 10:12:13 +0100 Message-ID: <19980203101212.20909@sobolev.rhein.de> Date: Tue, 3 Feb 1998 10:12:12 +0100 From: Thomas Roessler To: "The mutt users' list" Subject: [0.89.1i] More pgp buglets Mail-Followup-To: The mutt users' list Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="JP+T4n/bALQSJXh8" X-Mailer: Mutt 0.89.1i --JP+T4n/bALQSJXh8 Content-Type: multipart/mixed; boundary="0OAP2g/MAC+5xKAE" --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable The attached patch fixes two problems: - When using the extract-keys function from the attachment menu, the DONTHANDLEPGPKEYS pseudo-option wouldn't be reset. - When going from the main index to the attachment menu, mutt wouldn't ask for your pass phrase. Note that this behaviour is not yet perfect, since only PGP attachments on the _first_ level are really taken into consideration. tlr --=20 Thomas Roessler =B7 74a353cc0b19 =B7 dg1ktr =B7 http://home.pages.de/~roess= ler/ 2048/CE6AC6C1 =B7 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="patch-0.89.1i.tlr.pgp_extract.1-2" --- /var/tmp/mutt-0.89.1i/pgp.c Tue Feb 3 10:02:14 1998 +++ mutt-0.89.1i/pgp.c Tue Feb 3 10:05:52 1998 @@ -681,10 +681,9 @@ pgp_extract_keys_from_attachment (fp, top); =20 if(!tag) - return; + break; } =20 - mutt_any_key_to_continue(NULL); unset_option(OPTDONTHANDLEPGPKEYS); } =20 --- /var/tmp/mutt-0.89.1i/recvattach.c Tue Jan 27 10:04:35 1998 +++ mutt-0.89.1i/recvattach.c Tue Feb 3 10:08:51 1998 @@ -456,6 +456,13 @@ return; =20 #ifdef _PGPPATH + =20 + if(hdr->pgp && !pgp_valid_passphrase()) + { + mx_close_message(&msg); + return; + } + =20 if (hdr->pgp =3D=3D PGPENCRYPT && hdr->content->type =3D=3D TYPEMULTIPAR= T) { STATE s; --0OAP2g/MAC+5xKAE-- --JP+T4n/bALQSJXh8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3in iQEVAwUBNNbfatImKUTOasbBAQGUIgf+It/wzKFG8I4OZvUb0CqlYr1A1mG+1xkm +Bj9C36sLRaYT+x0/XToGSfY19xoeyBWbfiBJiLE1r9VBI9J5Mn/3iK09Q7qXvP1 klK8K6dS9IwZDt+oOs3yUrZn5efA4MA9YHNK9CtD8uRfo446WsqJcipOTaf9Da9o v7EeIEXSWLFqOh4EIqEX4PzEsnWNbmcv+XdRmS/rWdKEHmumH1N5BR3NkP+6f11v 6sk1ldKCt0toPljSCq/RKn7GtXWa2UtviaAuuZHTIArcQhtNIHXZSkgJHbGuuwlZ /ZukNyPsgC5TiBPCYiYj8wFxPUvWJVuawIXKHVeFbs5Kj6sAwkaa/w== =yXNZ -----END PGP SIGNATURE----- --JP+T4n/bALQSJXh8-- From kaukasoi@elektroni.ee.tut.fi Tue Feb 3 02:18:40 1998 Return-Path: kaukasoi@elektroni.ee.tut.fi Received: from elektroni.ee.tut.fi (qmailr@elektroni.ee.tut.fi [130.230.131.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id CAA15649 for ; Tue, 3 Feb 1998 02:18:31 -0800 (PST) Received: (qmail 865 invoked by uid 5591); 3 Feb 1998 10:18:03 -0000 Message-ID: <19980203121802.51094@elektroni.ee.tut.fi> Date: Tue, 3 Feb 1998 12:18:02 +0200 From: Petri Kaukasoina To: mutt-users@cs.hmc.edu Subject: Re: Need mutt to read ELM format alias files Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980130103144.55388@dgii.com> <19980130123223.25580@mph124.rh.psu.edu> <19980130125249.11280@dgii.com> <19980130144632.09397@shell9.ba.best.com> <19980130161550.64490@dtthp169.jf.intel.com> <19980130190422.13604@rsn.hp.com> <19980130174747.35505@la.tis.com> <19980202110820.06302@rsn.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <19980202110820.06302@rsn.hp.com>; from David DeSimone on Mon, Feb 02, 1998 at 11:08:20AM -0600 On Mon, Feb 02, 1998 at 11:08:20AM -0600, David DeSimone wrote: > Haven't any of you folks used systems in which the MDA doesn't bother > with dot-locking? Our BSD systems here use only flock and fcntl > locking. So, if you turn on dot-locking and nothing else on those > systems, you would risk mailbox corruption. > > I'm just trying to debunk the notion that seems to be out there, that > there is one true locking method that is "always safe." There isn't. > > The only way to really know is to find out what the MDA's are going to > do for locking, and use the same methods. Unfortunately that is a > non-trivial process on some systems. Sigh. Yes. For example qmail's delivery agent qmail-local only uses flock. From bonkey@matylda.silesia.linux.org.pl Tue Feb 3 02:35:32 1998 Return-Path: bonkey@matylda.silesia.linux.org.pl Received: from pikus.wnaft.agh.edu.pl (uucp@pikus.wnaft.agh.edu.pl [149.156.117.124]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id CAA20550 for ; Tue, 3 Feb 1998 02:33:35 -0800 (PST) Received: from matylda.UUCP (uucp@localhost) by pikus.wnaft.agh.edu.pl (8.8.8/8.8.8) with bsmtp id LAA02667 for mutt-users@cs.hmc.edu; Tue, 3 Feb 1998 11:37:38 +0100 Received: (from bonkey@localhost) by matylda.silesia.linux.org.pl (8.8.5/8.8.7) id JAA06327; Tue, 3 Feb 1998 09:00:40 +0100 Message-ID: <19980203090039.45703@matylda.silesia.linux.org.pl> Date: Tue, 3 Feb 1998 09:00:39 +0100 From: Daniel Bauke To: Mutt User List Subject: compressed folders with fcc-save-hook Mail-Followup-To: Mutt User List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Operating-System: Linux 2.0.33 i586 X-Writing-Started: Tue Feb 3 08:46:23 MET 1998 Is it possible? I tried to patch the source code with the compressed-folders patch after fcc-save-hook but there was one rejection in mutt.h: ---[cut]--- *************** *** 81,86 **** M_MBOXHOOK, M_SENDHOOK, M_FCCHOOK, /* modes for mutt_view_attachment() */ M_REGULAR, --- 81,90 ---- M_MBOXHOOK, M_SENDHOOK, M_FCCHOOK, + M_OPENHOOK, + M_APPENDHOOK, + M_CLOSEHOOK, + /* modes for mutt_view_attachment() */ M_REGULAR, ---[cut]--- So, I tried to change it by hand and added those three lines in correct (?!) place. I compiled mutt without any errors and it understands all those *-hook commands but he can't use them. When I try to open any *.gz folder mutt says: /bin/gzip -c %t >> %f: unknown command /home/bonkey/Mail/mutt-users-old.gz is not a mailbox. Any ideas? I doesn't look like a conflict between these patches but who knows? I don't. ;) -- Daniel Bauke | bonkey@matylda.silesia.linux.org.pl vulgo bonkey | http://www.silesia.linux.org.pl/~bonkey/ & rat's all 4 U (2) know... From sweth@astaroth.nit.gwu.edu Tue Feb 3 07:46:12 1998 Return-Path: sweth@astaroth.nit.gwu.edu Received: from astaroth.nit.gwu.edu (astaroth.nit.gwu.edu [128.164.142.43]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id HAA26739 for ; Tue, 3 Feb 1998 07:46:10 -0800 (PST) Received: (from sweth@localhost) by astaroth.nit.gwu.edu (8.8.8/8.8.8) id KAA09283; Tue, 3 Feb 1998 10:46:30 -0500 (EST) Message-ID: <19980203104629.52778@astaroth.nit.gwu.edu> Date: Tue, 3 Feb 1998 10:46:29 -0500 From: Sweth Chandramouli To: Mutt Users Subject: urlview compile problem Mail-Followup-To: Mutt Users Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 i'm trying to get urlview to compile on a sun ultra-30 running solaris 2.5.1. after running configure --with-slang, i try to run make, and get the following errors: gcc -DPACKAGE=\"urlview\" -DVERSION=\"0.6\" -DUSE_SLANG=1 -DHAVE_REGEX_H=1 -DHAVE_STDARG_H=1 -DHAVE_VARARGS_H=1 -I. -I. -g -O2 -DURLVIEW -Dunix -c urlview.c gcc -DPACKAGE=\"urlview\" -DVERSION=\"0.6\" -DUSE_SLANG=1 -DHAVE_REGEX_H=1 -DHAVE_STDARG_H=1 -DHAVE_VARARGS_H=1 -I. -I. -g -O2 -DURLVIEW -Dunix -c enter.c gcc -DPACKAGE=\"urlview\" -DVERSION=\"0.6\" -DUSE_SLANG=1 -DHAVE_REGEX_H=1 -DHAVE_STDARG_H=1 -DHAVE_VARARGS_H=1 -I. -I. -g -O2 -DURLVIEW -Dunix -c dokey.c dokey.c: In function `km_dokey': dokey.c:38: `KEY_DC' undeclared (first use this function) dokey.c:38: (Each undeclared identifier is reported only once dokey.c:38: for each function it appears in.) *** Error code 1 make: Fatal error: Command failed for target `dokey.o' any suggestions? tia, sweth. -- "Countin' on a remedy I've counted on before Goin' with a cure that's never failed me What you call the disease I call the remedy" -- The Mighty Mighty Bosstones From azgoda@szmaragd.ii.uni.wroc.pl Tue Feb 3 08:00:54 1998 Return-Path: azgoda@szmaragd.ii.uni.wroc.pl Received: from pogwizd.ii.uni.wroc.pl (root@pogwizd.ii.uni.wroc.pl [156.17.4.6]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id IAA01254 for ; Tue, 3 Feb 1998 08:00:41 -0800 (PST) Received: from szmaragd.ii.uni.wroc.pl (azgoda@doktor1 [156.17.4.77]) by pogwizd.ii.uni.wroc.pl (8.8.5/8.8.5) with ESMTP id QAA07305 for ; Tue, 3 Feb 1998 16:58:47 +0100 (MET) Received: (from azgoda@localhost) by szmaragd.ii.uni.wroc.pl (8.8.7/8.8.7) id QAA00616; Tue, 3 Feb 1998 16:57:00 +0100 Message-ID: <19980203165659.55134@szmaragd.ii.uni.wroc.pl> Date: Tue, 3 Feb 1998 16:56:59 +0100 From: Artur Zgoda To: mutt-announce@cs.hmc.edu Subject: subscribe Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e I would like to subscribe. :-) From fabrice@math.Princeton.EDU Tue Feb 3 08:04:29 1998 Return-Path: fabrice@math.Princeton.EDU Received: from and.Princeton.EDU (root@and.Princeton.EDU [128.112.16.144]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id IAA02536 for ; Tue, 3 Feb 1998 08:04:28 -0800 (PST) Received: from eurydice.Princeton.EDU (eurydice.Princeton.EDU [128.112.16.153]) by and.Princeton.EDU (8.8.8/8.8.3) with ESMTP id LAA21429 for ; Tue, 3 Feb 1998 11:04:26 -0500 (EST) Received: (fabrice@localhost) by eurydice.Princeton.EDU (950413.SGI.8.6.12/8.6.12) id LAA06288; Tue, 3 Feb 1998 11:04:25 -0500 Message-ID: <19980203110425.09878@math.princeton.edu> Date: Tue, 3 Feb 1998 11:04:25 -0500 From: Fabrice Planchon To: mutt-users@cs.hmc.edu Subject: Re: filter-entry and encoding: patch Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202085536.58895@math.princeton.edu> <19980202180451.41363@matrix.42.org> <19980202114653.35586@rsn.hp.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=0eh6TmSyL6TZE2Uz X-Mailer: Mutt 0.89.1i In-Reply-To: <19980202114653.35586@rsn.hp.com>; from David DeSimone on Mon, Feb 02, 1998 at 11:46:53AM -0600 Organization: Princeton University X-http: //www.math.princeton.edu/~fabrice/ --0eh6TmSyL6TZE2Uz Content-Type: multipart/mixed; boundary=fdj2RfSjLxBAspz7 --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii On Mon Feb 02 1998 at 11:46:53AM -0600, David DeSimone wrote: > I think the bug he's referring to is the fact that Mutt doesn't > re-evaluate its choice of content-encoding if you filter the text. actually, as said in another message, it does reevaluate, but doesn't refresh the display. The following (one line...) patch fixes that. Dunno if it's the correct way, the code seems to have been reorganized a lot in this area... F. -- Fabrice Planchon (ph) 609/258-6495 Applied Math Program, 210 Fine Hall (fax) 609/258-1735 --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-0.89.1i.fp.filter.1" --- compose.c.orig Mon Feb 2 17:33:25 1998 +++ compose.c Tue Feb 3 10:55:48 1998 @@ -732,6 +732,7 @@ case OP_FILTER: CHECK_COUNT; mutt_pipe_attachment_list (NULL, menu->tagprefix, menu->tagprefix ? msg->content : idx[menu->current]->content, op == OP_FILTER); + menu->redraw = REDRAW_CURRENT; break; case OP_EXIT: --fdj2RfSjLxBAspz7-- --0eh6TmSyL6TZE2Uz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3a iQCVAwUBNNdACdX42EYNMIltAQEWIAP/bFSIIPS6M6zME2PntUpiou0HE7/pmXBR kdb3noTpOjYPjD+6il72sHYJTYTtZC/Hr5NVebrd1i7hQH4Y/Je/CMZv+WAVyFzo 507UXaN356SgojeblPGH6p3efsrF5qdcEzY2PGovqukn5uX0r8VT3wnl6FrTsLgr C5FyLh7zNdc= =o8KC -----END PGP SIGNATURE----- --0eh6TmSyL6TZE2Uz-- From fox@fuzzy.rsn.hp.com Tue Feb 3 10:21:31 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA17631 for ; Tue, 3 Feb 1998 10:20:56 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id IAA29454 for ; Tue, 3 Feb 1998 08:41:32 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id KAA00905; Tue, 3 Feb 1998 10:41:30 -0600 (CST) Message-ID: <19980203104130.53309@rsn.hp.com> Date: Tue, 3 Feb 1998 10:41:30 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: e-mail/HTML enhancement? - Nope Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980202104324.60584@td2cad.intel.com> <19980202192625.64011@rsn.hp.com> <19980202191238.06359@td2cad.intel.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=Dxnq1zWXvFF0Q93v X-Mailer: Mutt 0.89i In-Reply-To: <19980202191238.06359@td2cad.intel.com>; from Shawn D. McPeek on Mon, Feb 02, 1998 at 07:12:38PM -0800 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Shawn D. McPeek wrote: > > Previously, David DeSimone wrote: > :> > :> This statement is not as idiotic as it might seem. For instance, if I > :> have a message/rfc822 document with 16 subdocuments within it, does Mutt > :> let me sort those message by date or by author? No. It shows them in > :> the order that they are attached, and only in that order. > > What you talk about is a single message with multiple attachments, not > multiple messages. There is quite a difference, especially when you talk > with people who use threads a lot. It's not what I am talking about. That's what the original message was talking about, the HTML-enhancment article that spawned this thread. It talked about how HTML tags would be created so that each section of a single message would have information about how that text was quoted from a different message, and how it relates to the others. This is very similar to Mutt's handling of message/rfc822 messages, where each message is broken out and shown how it relates to the others, although that relation is only shown as a MIME-attaching relation, rather than some sort of threaded order, or date-order, or whatever. Though I guess the default would be reverse-date, in the usual reply-reply-reply scenario that's so common these days. It seems that everyone wanted to take the comment about "sorting groups of messages by date" as meaning a mailbox full of messages being sorted, which every mailer on the planet can do, but I really don't think that's what the author of the article meant. I think he was talking about sorting messages grouped into a single message, which most mailers don't even try to handle. Well. Whatever. It seemed very clear to me. -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNdItg0lGhIp2tThAQFfSAL/dwNCyWd2Z4Nvy7KuhTvY+ZQxIPOaRLRA 78Edp7I1RUqUTVfl89kJOFc/pJf7Kcb34mIFF4lum+r+E4sVMjL1zJ9tPLlrZGji N0VINkSGiTRsTtQO+Ipq2qoOfft3IYSE =5Y4o -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From roberto@keltia.freenix.fr Tue Feb 3 15:15:46 1998 Return-Path: roberto@keltia.freenix.fr Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA02648 for ; Tue, 3 Feb 1998 15:15:29 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id AAA25298 for mutt-users@cs.hmc.edu; Wed, 4 Feb 1998 00:14:50 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id XAA11581; Tue, 3 Feb 1998 23:54:46 +0100 (CET) (envelope-from roberto) Message-ID: <19980203235446.05276@keltia.freenix.fr> Date: Tue, 3 Feb 1998 23:54:46 +0100 From: Ollivier Robert To: mutt Subject: Re: the FreeBSD 'make install' error Mail-Followup-To: mutt References: <19980202144329.15940@unixshell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980202144329.15940@unixshell.com>; from Ken W on Mon, Feb 02, 1998 at 02:43:29PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4019 AMD-K6 MMX @ 225 MHz According to Ken W: > Where exactly can I disable setgid? In config.h that gets made after cd /var chmod 755 mail cd mutt ./configure Forget that @~^#{@~# write-bit on mail. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Mutt patches collection: From tim@southcom.com.au Tue Feb 3 17:06:23 1998 Return-Path: tim@southcom.com.au Received: from internet5.police.tas.gov.au ([192.190.61.74]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id RAA12063 for ; Tue, 3 Feb 1998 17:06:19 -0800 (PST) Received: from busconductor.police.tas.gov.au ([202.7.9.72]) by internet5.police.tas.gov.au (8.6.11/8.6.6) with SMTP id MAA16068 for ; Wed, 4 Feb 1998 12:05:43 +1100 Date: Wed, 4 Feb 1998 12:03:52 +0000 (GMT) From: TiM X-Sender: tim@busconductor.police.tas.gov.au To: mutt-announce@cs.hmc.edu Subject: subscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From cpfreg@mail.ece.fjtc.edu.tw Tue Feb 3 20:19:04 1998 Return-Path: cpfreg@mail.ece.fjtc.edu.tw Received: from mail.ece.fjtc.edu.tw (mail.ece.fjtc.edu.tw [192.192.113.2]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id UAA18776 for ; Tue, 3 Feb 1998 20:18:57 -0800 (PST) Received: (from cpfreg@localhost) by mail.ece.fjtc.edu.tw (8.8.8/8.8.7) id MAA16019 for mutt-users@cs.hmc.edu; Wed, 4 Feb 1998 12:18:46 +0800 (CST) Date: Wed, 4 Feb 1998 12:18:46 +0800 (CST) From: CP Fong Message-Id: <199802040418.MAA16019@mail.ece.fjtc.edu.tw> To: mutt-users@cs.hmc.edu subscribe end From cpfreg@mail.ece.fjtc.edu.tw Tue Feb 3 21:27:59 1998 Return-Path: cpfreg@mail.ece.fjtc.edu.tw Received: from mail.ece.fjtc.edu.tw (mail.ece.fjtc.edu.tw [192.192.113.2]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id VAA13105 for ; Tue, 3 Feb 1998 21:25:59 -0800 (PST) Received: from localhost (cpfreg@localhost) by mail.ece.fjtc.edu.tw (8.8.8/8.8.7) with SMTP id NAA18022 for ; Wed, 4 Feb 1998 13:25:31 +0800 (CST) Date: Wed, 4 Feb 1998 13:25:31 +0800 (CST) From: CP Fong To: mutt-users@cs.hmc.edu Subject: [Q] mutt and smtp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Does anyone know how to setup smtp-server in mutt? I would like to use other remote smtp-server as my mail server instead of the local one. From mtsirkin@iil.intel.com Wed Feb 4 00:14:19 1998 Return-Path: mtsirkin@iil.intel.com Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA19521 for ; Wed, 4 Feb 1998 00:14:14 -0800 (PST) Received: from iil.intel.com (iil-1.iil.intel.com [143.185.96.171]) by melete.ch.intel.com (8.8.6/8.8.5) with SMTP id IAA19941 for ; Wed, 4 Feb 1998 08:14:04 GMT Received: from ilx347.iil.intel.com by iil.intel.com with SMTP id AA02329 (5.65c+/IDA-1.4.4 for ); Wed, 4 Feb 1998 10:14:01 +0200 Received: by ilx347.iil.intel.com (AIX 4.1/UCB 5.64/IDC-RS6000-AIX-3.2) id AA07940; Wed, 4 Feb 1998 10:14:01 +0200 Message-Id: <19980204101400.55686@iil.intel.com> Date: Wed, 4 Feb 1998 10:14:00 +0200 From: "Michael S. Tsirkin" To: Mutt users mailing list Subject: Re: [0.89.1i] bugfix: buffy sanity checks Reply-To: "Michael S. Tsirkin" Mail-Followup-To: Mutt users mailing list References: <19980202111333.01745@att.com> <19980202133233.45583@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 In-Reply-To: <19980202133233.45583@cs.swarthmore.edu>; from "eisenbud@cs.swarthmore.edu" on Mon, Feb 02, 1998 at 01:32:33PM -0500 X-Url: http://www.toptown.com/hp/mtsirkin Hello! Quoting r. Daniel Eisenbud (eisenbud@cs.swarthmore.edu) "[0.89.1i] bugfix: buffy sanity checks": > --- mutt-0.89.1i.orig/buffy.c Sat Jan 31 08:13:06 1998 > +++ mutt-0.89.1i/buffy.c Mon Feb 2 13:26:34 1998 > @@ -219,6 +219,9 @@ int mutt_force_buffy_check(void) > char path[_POSIX_PATH_MAX]; > struct stat contex_sb; > > + /* update time of last check */ > + BuffyTime = time (NULL); > + > /* fastest return if there are no mailboxes */ > if (!Incoming) > return 0; Daniel, this means that one who does not use buffy at all has to pay performance time for this check (call "time"). Pls put "BuffyTime = time" AFTER the "fastest return" case. MST -- This message content is not part of Intel's views or affairs Michael S. Tsirkin,32000, Technion, Canada dorms 44/3/3,Haifa,Israel; Home:+972-4-8283001; Work:+972-4-8655658; mailto:mtsirkin@usa.net; http://www.toptown.com/hp/mtsirkin/; > Four things are to be strengthened: Torah,and good deeds, > prayer and one's good manners (Berachoth) From mtsirkin@iil.intel.com Wed Feb 4 00:18:12 1998 Return-Path: mtsirkin@iil.intel.com Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA20127 for ; Wed, 4 Feb 1998 00:18:09 -0800 (PST) Received: from iil.intel.com (iil-1.iil.intel.com [143.185.96.171]) by melete.ch.intel.com (8.8.6/8.8.5) with SMTP id IAA20011 for ; Wed, 4 Feb 1998 08:18:07 GMT Received: from ilx347.iil.intel.com by iil.intel.com with SMTP id AA31166 (5.65c+/IDA-1.4.4 for ); Wed, 4 Feb 1998 10:18:06 +0200 Received: by ilx347.iil.intel.com (AIX 4.1/UCB 5.64/IDC-RS6000-AIX-3.2) id AA50574; Wed, 4 Feb 1998 10:18:06 +0200 Message-Id: <19980204101805.35004@iil.intel.com> Date: Wed, 4 Feb 1998 10:18:05 +0200 From: "Michael S. Tsirkin" To: Mutt users mailing list Subject: Re: Repost: [0.89.1i] bugfix: buffy sanity checks Reply-To: "Michael S. Tsirkin" Mail-Followup-To: Mutt users mailing list References: <19980202111333.01745@att.com> <19980202133233.45583@cs.swarthmore.edu> <19980202140932.47994@cs.swarthmore.edu> <19980203004907.02831@ask.tele.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 In-Reply-To: <19980203004907.02831@ask.tele.dk>; from "byrial@post3.tele.dk" on Tue, Feb 03, 1998 at 12:49:07AM +0100 X-Url: http://www.toptown.com/hp/mtsirkin Hello! The mutt_force_buffy is not dealing with the check times at all. For this reason BuffyTime = time should be in mutt_buffy_check, I can not see why "too checks in a row" (which could happend possibly is a problem). Your patch forces two functions (force_check and check) to communicate through a global variable, which si not an example of a good design. Quoting r. Byrial Jensen (byrial@post3.tele.dk) "Re: Repost: [0.89.1i] bugfix: buffy sanity checks": > --- buffy.c.orig Tue Feb 3 00:32:31 1998 > +++ buffy.c Tue Feb 3 00:34:42 1998 > @@ -219,6 +219,9 @@ > char path[_POSIX_PATH_MAX]; > struct stat contex_sb; > > + /* update time of last check */ > + BuffyTime = time (NULL); > + > /* fastest return if there are no mailboxes */ > if (!Incoming) > return 0; > @@ -333,17 +336,14 @@ > return (BuffyCount); > } > > -/* this only checks for new mail each three seconds */ > +/* this only checks for new mail each BuffyTimeout (def. 3) seconds */ > int mutt_buffy_check (void) > { > - time_t t; > /* fastest return if there are no mailboxes */ > if (!Incoming) > return 0; > - t = time (NULL); > - if ((t - BuffyTime) < BuffyTimeout) > + if ((time (NULL) - BuffyTime) < BuffyTimeout) > return BuffyCount; > - BuffyTime = t; > return mutt_force_buffy_check(); > } > > @@ -366,6 +366,10 @@ > return; > } > } > + /* there were no mailboxes needing to be notified, so clean up since > + * BuffyNotify has somehow gottten out of sync > + */ > + BuffyNotify = 0; > } > } > > @@ -377,11 +381,11 @@ > */ > void mutt_buffy (char *s) > { > - int count = 0; > + int count; > BUFFY *tmp = Incoming; > > mutt_expand_path (s, _POSIX_PATH_MAX); > - switch (count = mutt_buffy_check ()) > + switch (mutt_buffy_check ()) > { > case 0: > > @@ -390,26 +394,39 @@ > > case 1: > > - while (!tmp->new) > + while (tmp && !tmp->new) > tmp = tmp->next; > + if (!tmp) > + { > + s = '\0'; > + mutt_force_buffy_check (); /* buffy was wrong - resync things */ > + break; > + } > strcpy (s, tmp->path); > mutt_pretty_mailbox (s); > break; > > default: > - > - FOREVER > + > + count = 0; > + while (count < 3) > { > if (strcmp (s, tmp->path) == 0) > - count = 0; > - else if (count == 0 && tmp->new) > + count++; > + else if (count && tmp->new) > break; > tmp = tmp->next; > - if (tmp == NULL) > + if (!tmp) > { > tmp = Incoming; > - count = 0; > + count++; > } > + } > + if (count >= 3) > + { > + s = '\0'; > + mutt_force_buffy_check (); /* buffy was wrong - resync things */ > + break; > } > strcpy (s, tmp->path); > mutt_pretty_mailbox (s); -- This message content is not part of Intel's views or affairs Michael S. Tsirkin,32000, Technion, Canada dorms 44/3/3,Haifa,Israel; Home:+972-4-8283001; Work:+972-4-8655658; mailto:mtsirkin@usa.net; http://www.toptown.com/hp/mtsirkin/; > Four things are to be strengthened: Torah,and good deeds, > prayer and one's good manners (Berachoth) From livingston@pha.pvtnet.cz Wed Feb 4 04:15:31 1998 Return-Path: livingston@pha.pvtnet.cz Received: from cbu.pvtnet.cz (cbu.pvtnet.cz [194.149.105.18]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id EAA07355 for ; Wed, 4 Feb 1998 04:15:22 -0800 (PST) Received: from goober.baffle.cz (ncutler@berD010.pvt.net [194.149.126.42]) by cbu.pvtnet.cz (8.8.5/8.7.3) with ESMTP id NAA13224 for ; Wed, 4 Feb 1998 13:16:03 +0100 (MET) Received: (from ncutler@localhost) by goober.baffle.cz (8.8.8/8.8.8/Debian/GNU) id KAA04034; Wed, 4 Feb 1998 10:51:33 +0100 Message-ID: <19980204105133.26347@baffle.cz> Date: Wed, 4 Feb 1998 10:51:33 +0100 From: "Nathan L. Cutler" To: Mutt Users Mailing List Subject: message/partial Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Organization: Livingston, s.r.o. X-Operating-System: Debian GNU Linux [ Due to the high volume of this list I'm not subscribed; please CC: me on your reply. ] Emacs mailers have a tendency to break longer files up into multiple messages using the MIME type "message/partial". So, instead of getting one 233 Kb message from an Emacs user I got three 64 Kb messages and one 57 Kb message (as far as I can tell). Can anybody tell me how I can put Humpty Dumpty back together again? (Without installing Emacs of course!!!!) -- Nathan L. Cutler (int'l ++420 instead tel.: 0311-671160 Livingston, s.r.o. of leading zero) fax: 0311-671159 livingston@pha.pvtnet.cz mobile: 0602-251053 From maccy@c6.hadiko.de Wed Feb 4 05:04:09 1998 Return-Path: maccy@c6.hadiko.de Received: from nz15.rz.uni-karlsruhe.de (nz15.rz.uni-karlsruhe.de [129.13.64.15]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id FAA10430 for ; Wed, 4 Feb 1998 05:04:05 -0800 (PST) Received: from hadic006.hadiko.uni-karlsruhe.de (c6.hadiko.de) [129.13.244.111] (maccy) by nz15.rz.uni-karlsruhe.de with esmtp (Exim 1.80 #4) id 0y04SV-0005BZ-00; Wed, 4 Feb 1998 14:01:43 +0100 Received: (from maccy@localhost) by c6.hadiko.de (8.8.5/8.8.5) id OAA00295; Wed, 4 Feb 1998 14:01:33 +0100 Message-ID: <19980204140133.50219@c6.hadiko.de> Date: Wed, 4 Feb 1998 14:01:33 +0100 From: Bjoern Jacke To: CP Fong , mutt-users@cs.hmc.edu Subject: Re: [Q] mutt and smtp References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from CP Fong on Wed, Feb 04, 1998 at 01:25:31PM +0800 On 04.02. at 13:25 +0800 CP Fong sent off: > > Does anyone know how to setup smtp-server in mutt? > I would like to use other remote smtp-server as my mail server > instead of the local one. just put SENDMAIL_SMARTHOST="yoursmtphost" into your /etc/rc.conf -- e-mail: bjoern.jacke@stud.uni-karlsruhe.de URL(mit PGP-Key): http://b.jacke.home.pages.de From ellement@sdd.hp.com Wed Feb 4 07:23:14 1998 Return-Path: ellement@sdd.hp.com Received: from hpsdlo.sdd.hp.com (hpsdlo.sdd.hp.com [15.255.160.64]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id HAA18494 for ; Wed, 4 Feb 1998 07:23:12 -0800 (PST) Received: from epgc352.sdd.hp.com (epgc352.sdd.hp.com [15.64.160.113]) by hpsdlo.sdd.hp.com (8.8.6/8.8.5tis+epg) with ESMTP id HAA19741; Wed, 4 Feb 1998 07:22:26 -0800 (PST) Received: (from ellement@localhost) by epgc352.sdd.hp.com (8.7.6/8.7.3 TIS 5.0/sdd epg) id HAA24009; Wed, 4 Feb 1998 07:22:25 -0800 (PST) Message-ID: <19980204072225.26958@sdd.hp.com> Date: Wed, 4 Feb 1998 07:22:25 -0800 From: David Ellement To: Mutt Users Mailing List Cc: "Nathan L. Cutler" Subject: Re: message/partial Mail-Followup-To: Mutt Users Mailing List , "Nathan L. Cutler" References: <19980204105133.26347@baffle.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204105133.26347@baffle.cz>; from Nathan L. Cutler on Wed, Feb 04, 1998 at 10:51:33AM +0100 On 980204, at 10:51:33, Nathan L. Cutler wrote: > So, instead of getting one 233 Kb message from an Emacs user I got three > 64 Kb messages and one 57 Kb message (as far as I can tell). > > Can anybody tell me how I can put Humpty Dumpty back together again? Take a look at uudeview: http://www.uni-frankfurt.de/~fp/uudeview/ -- David Ellement From eisenbud@allspice.cs.swarthmore.edu Wed Feb 4 08:15:22 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id IAA21896 for ; Wed, 4 Feb 1998 08:15:19 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id LAA23931; Wed, 4 Feb 1998 11:15:14 -0500 (EST) Message-ID: <19980204111514.41783@cs.swarthmore.edu> Date: Wed, 4 Feb 1998 11:15:14 -0500 From: Daniel Eisenbud To: Mutt users mailing list Subject: Re: [0.89.1i] bugfix: buffy sanity checks Mail-Followup-To: Mutt users mailing list References: <19980202111333.01745@att.com> <19980202133233.45583@cs.swarthmore.edu> <19980204101400.55686@iil.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204101400.55686@iil.intel.com>; from Michael S. Tsirkin on Wed, Feb 04, 1998 at 10:14:00AM +0200 On Wed, Feb 04, 1998 at 10:14:00AM +0200, Michael S. Tsirkin wrote: > Daniel, this means that one who does not use buffy at all has to pay > performance time for this check (call "time"). > > Pls put "BuffyTime = time" AFTER the "fastest return" case. OK, will do. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From ca@informatik.uni-kiel.de Wed Feb 4 08:33:48 1998 Return-Path: ca@informatik.uni-kiel.de Received: from mine.informatik.uni-kiel.de (TlIUaKt6ARTxGj7+URohRzRzAtpy/xlw@mine.informatik.uni-kiel.de [134.245.252.204]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id IAA23317 for ; Wed, 4 Feb 1998 08:33:28 -0800 (PST) Received: (from ca@localhost) by mine.informatik.uni-kiel.de (8.8.8/8.8.8) id RAA17649; Wed, 4 Feb 1998 17:32:46 +0100 (MET) Message-ID: <19980204173246.00327@mine.informatik.uni-kiel.de> Date: Wed, 4 Feb 1998 17:32:46 +0100 From: Claus Assmann To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=YZ5djTAD1cGYuMQK In-Reply-To: <19980125180404.18362@mine.informatik.uni-kiel.de>; from Claus Assmann on Sun, Jan 25, 1998 at 06:04:04PM +0100 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Can someone with more knowledge about the internal working of mutt please tell me whether the attached patch has any "bad" side effect? It solves my problem (new mail which created a new folder (thanks to procmail) wasn't recognized). Regards, Claus Assmann --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="buffy.c.patch" *** buffy.c.orig Thu Jan 29 14:58:36 1998 --- buffy.c Thu Jan 29 14:59:00 1998 *************** *** 207,213 **** */ #define STAT_CHECK (sb.st_size > tmp->size) #else ! #define STAT_CHECK (sb.st_mtime > sb.st_atime || (tmp->newly_created && sb.st_ctime == sb.st_mtime && sb.st_ctime == sb.st_atime)) #endif /* BUFFY_SIZE */ int mutt_buffy_check (void) --- 207,213 ---- */ #define STAT_CHECK (sb.st_size > tmp->size) #else ! #define STAT_CHECK (sb.st_mtime >= sb.st_atime || (tmp->newly_created && sb.st_ctime == sb.st_mtime && sb.st_ctime == sb.st_atime)) #endif /* BUFFY_SIZE */ int mutt_buffy_check (void) --YZ5djTAD1cGYuMQK-- From eisenbud@allspice.cs.swarthmore.edu Wed Feb 4 10:54:56 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA05805 for ; Wed, 4 Feb 1998 10:54:53 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id NAA26669; Wed, 4 Feb 1998 13:54:51 -0500 (EST) Message-ID: <19980204135450.49895@cs.swarthmore.edu> Date: Wed, 4 Feb 1998 13:54:50 -0500 From: Daniel Eisenbud To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204173246.00327@mine.informatik.uni-kiel.de>; from Claus Assmann on Wed, Feb 04, 1998 at 05:32:46PM +0100 On Wed, Feb 04, 1998 at 05:32:46PM +0100, Claus Assmann wrote: > Can someone with more knowledge about the internal working of mutt > please tell me whether the attached patch has any "bad" side effect? > It solves my problem (new mail which created a new folder (thanks > to procmail) wasn't recognized). > > Regards, > > Claus Assmann > *** buffy.c.orig Thu Jan 29 14:58:36 1998 > --- buffy.c Thu Jan 29 14:59:00 1998 > *************** > *** 207,213 **** > */ > #define STAT_CHECK (sb.st_size > tmp->size) > #else > ! #define STAT_CHECK (sb.st_mtime > sb.st_atime || (tmp->newly_created && sb.st_ctime == sb.st_mtime && sb.st_ctime == sb.st_atime)) > #endif /* BUFFY_SIZE */ > > int mutt_buffy_check (void) > --- 207,213 ---- > */ > #define STAT_CHECK (sb.st_size > tmp->size) > #else > ! #define STAT_CHECK (sb.st_mtime >= sb.st_atime || (tmp->newly_created && sb.st_ctime == sb.st_mtime && sb.st_ctime == sb.st_atime)) > #endif /* BUFFY_SIZE */ > > int mutt_buffy_check (void) This is probably OK, but it only works for mbox folders. Code I added a while ago was supposed to fix this problem, but it was either broken in the first place, or something else has broken it since. I'll take a look at what's going on. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From eisenbud@allspice.cs.swarthmore.edu Wed Feb 4 11:03:34 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA06533 for ; Wed, 4 Feb 1998 11:03:03 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id OAA26766; Wed, 4 Feb 1998 14:02:48 -0500 (EST) Message-ID: <19980204140247.50536@cs.swarthmore.edu> Date: Wed, 4 Feb 1998 14:02:47 -0500 From: Daniel Eisenbud To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204173246.00327@mine.informatik.uni-kiel.de>; from Claus Assmann on Wed, Feb 04, 1998 at 05:32:46PM +0100 Thinking more about this, doesn't mutt leave atime=mtime if it modifies a folder upon exit? -Daniel On Wed, Feb 04, 1998 at 05:32:46PM +0100, Claus Assmann wrote: > Can someone with more knowledge about the internal working of mutt > please tell me whether the attached patch has any "bad" side effect? > It solves my problem (new mail which created a new folder (thanks > to procmail) wasn't recognized). > > Regards, > > Claus Assmann > *** buffy.c.orig Thu Jan 29 14:58:36 1998 > --- buffy.c Thu Jan 29 14:59:00 1998 > *************** > *** 207,213 **** > */ > #define STAT_CHECK (sb.st_size > tmp->size) > #else > ! #define STAT_CHECK (sb.st_mtime > sb.st_atime || (tmp->newly_created && sb.st_ctime == sb.st_mtime && sb.st_ctime == sb.st_atime)) > #endif /* BUFFY_SIZE */ > > int mutt_buffy_check (void) > --- 207,213 ---- > */ > #define STAT_CHECK (sb.st_size > tmp->size) > #else > ! #define STAT_CHECK (sb.st_mtime >= sb.st_atime || (tmp->newly_created && sb.st_ctime == sb.st_mtime && sb.st_ctime == sb.st_atime)) > #endif /* BUFFY_SIZE */ > > int mutt_buffy_check (void) -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From rsk@gsp.org Wed Feb 4 11:18:25 1998 Return-Path: rsk@gsp.org Received: from gsp.org (rsk.itw.com [208.211.3.21]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA08046 for ; Wed, 4 Feb 1998 11:18:21 -0800 (PST) Received: (from rsk@localhost) by gsp.org (8.8.8/8.8.8) id LAA26907; Wed, 4 Feb 1998 11:58:43 -0500 (EST) Message-ID: <19980204115843.02167@wombat> Date: Wed, 4 Feb 1998 11:58:43 -0500 From: Rich Kulawiec To: mutt-users@cs.hmc.edu Subject: Mutt feature request -- duplicate message detection/deletion Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 I'd like to have a command that will search through an entire message folder (file) and locate messages which have the same Message-ID (or Article-ID) and do a fast-n-dirty comparison (to make sure they're really the same) and delete them. I'd like this to work even if the messages aren't adjacent in the folder. Why? Well, I have a large number of uses for this. One is to do deal with overlapping mailing lists which receive some of the same messages. Also, I sometimes get two or more copies of a message because it's sent to me and CC'd to a mailing list, or vice versa. Another point is that I use newsreaders from the "rn" family, which have the nice capability of saving news articles as mail messages -- which allows me to use mail-oriented tools on them. However, if I combine saved articles which were read on different news servers, I end up with lots and lots of duplicate messages. I'd like to have a handy way to throw the duplicates out other than manually stepping through every message. So, being able to locate, tag and delete the duplicates would be awfully handy. I know that *in theory* one should be able to trust that the Message-ID and Article-ID fields guarantee uniqueness, and that two messages with matching ID fields should really be identical; however, I've seen broken sites that violate this rule. It's further complicated by noticing that in the case of mail messages, the "Received" headers and in the case of news articles, the "Path" headers, will necessarily be different if the messages traveled by different paths between origin and destination. Hence my use of the phrase "fast-n-dirty" comparison; maybe it would be better if I said "comparison based on contents only, not the headers" or "fast comparison to check that sender, subject, and line count match". ---Rsk Rich Kulawiec rsk@gsp.org From ca@informatik.uni-kiel.de Wed Feb 4 11:36:25 1998 Return-Path: ca@informatik.uni-kiel.de Received: from mine.informatik.uni-kiel.de (nGNiw52iompIMfa9ym6IvMlIc9LUk3nO@mine.informatik.uni-kiel.de [134.245.252.204]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA09694 for ; Wed, 4 Feb 1998 11:36:21 -0800 (PST) Received: (from ca@localhost) by mine.informatik.uni-kiel.de (8.8.8/8.8.8) id UAA10515; Wed, 4 Feb 1998 20:36:03 +0100 (MET) Message-ID: <19980204203602.58389@mine.informatik.uni-kiel.de> Date: Wed, 4 Feb 1998 20:36:02 +0100 From: Claus Assmann To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> <19980204140247.50536@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19980204140247.50536@cs.swarthmore.edu>; from Daniel Eisenbud on Wed, Feb 04, 1998 at 02:02:47PM -0500 On Wed, Feb 04, 1998 at 02:02:47PM -0500, Daniel Eisenbud wrote: > Thinking more about this, doesn't mutt leave atime=mtime if it modifies > a folder upon exit? No, at least not here: stat sun-managers-list changed : Wed Feb 4 20:30:15 1998 accessed: Wed Feb 4 20:29:43 1998 modified: Wed Feb 4 20:29:26 1998 I just read this folder before switching to mutt and I deleted some mails therein. Or do I misunderstand your question? Up to now the patch works fine for me (on mbox folders), it never gave me a false positive (saying there is new mail while there isn't) nor (hopefully :-) telling me not about new mail in a newly created folder (I checked it a few times). Thanks for your help, Claus From sec@matrix.42.org Wed Feb 4 11:44:55 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA10239 for ; Wed, 4 Feb 1998 11:44:47 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id UAA03047 (sender ); Wed, 4 Feb 1998 20:44:43 +0100 (CET) Message-ID: <19980204204441.13468@matrix.42.org> Date: Wed, 4 Feb 1998 20:44:42 +0100 From: Stefan `Sec` Zehl To: Rich Kulawiec , mutt-users@cs.hmc.edu Subject: Re: Mutt feature request -- duplicate message detection/deletion Mail-Followup-To: Rich Kulawiec , mutt-users@cs.hmc.edu References: <19980204115843.02167@wombat> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980204115843.02167@wombat>; from Rich Kulawiec on Wed, Feb 04, 1998 at 11:58:43AM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Wed, Feb 04, 1998 at 11:58:43AM -0500, Rich Kulawiec wrote: > I'd like to have a command that will search through an entire > message folder (file) and locate messages which have the same > Message-ID (or Article-ID) and do a fast-n-dirty comparison > (to make sure they're really the same) and delete them. Hm, I guess this will not satisfy you, but i filter dupes with: # Do filter dupes. remove second rule and 'c' in first one to throw them away MAILDIR=$HOME/Mail :0 Whc: msgid.lock | formail -D 65536 $PMDIR/cache.dupes :0 a: dupes in my .procmailrc which works like a charm. So i don't need such a feature :) CU, Sec -- Hiroshima '45 Tsjernobyl '86 Windows '95 From igor@shogun.zynaps.ru Wed Feb 4 11:49:50 1998 Return-Path: igor@shogun.zynaps.ru Received: from shogun.zynaps.ru (shogun.zynaps.ru [194.84.14.39]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA10847 for ; Wed, 4 Feb 1998 11:49:47 -0800 (PST) Received: (from igor@localhost) by shogun.zynaps.ru (8.8.8/8.8.8/Zynaps) id WAA25548; Wed, 4 Feb 1998 22:49:45 +0300 (MSK) (envelope-from igor) Message-ID: <19980204224945.10991@zynaps.ru> Date: Wed, 4 Feb 1998 22:49:45 +0300 From: Igor Vinokurov To: mutt-users@cs.hmc.edu Subject: after pipe to less keyboard _partially_ freez... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i People, Could you explain why arrow-keys not work just after piping to less and return to index? -- Thank you. Igor Vinokurov From rsk@gsp.org Wed Feb 4 11:54:08 1998 Return-Path: rsk@gsp.org Received: from gsp.org (rsk.itw.com [208.211.3.21]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA11537 for ; Wed, 4 Feb 1998 11:54:05 -0800 (PST) Received: (from rsk@localhost) by gsp.org (8.8.8/8.8.8) id OAA28006; Wed, 4 Feb 1998 14:54:57 -0500 (EST) Message-ID: <19980204145456.42102@wombat> Date: Wed, 4 Feb 1998 14:54:56 -0500 From: Rich Kulawiec To: mutt-users@cs.hmc.edu Subject: Re: Mutt feature request -- duplicate message detection/deletion References: <19980204115843.02167@wombat> <19980204204441.13468@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980204204441.13468@matrix.42.org>; from Stefan `Sec` Zehl on Wed, Feb 04, 1998 at 08:44:42PM +0100 > Hm, I guess this will not satisfy you, but i filter dupes with: > > # Do filter dupes. remove second rule and 'c' in first one to throw them away > [...] > > in my .procmailrc which works like a charm. So i don't need such a > feature :) That's correct, it won't work for me. The reason is that I do not wish to filter duplicates as they arrive (especially since some of them are arriving via FTP and NNTP, not SMTP) but later when they're just sitting in a folder. ---Rsk Rich Kulawiec rsk@gsp.org From eisenbud@allspice.cs.swarthmore.edu Wed Feb 4 12:14:54 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA13382 for ; Wed, 4 Feb 1998 12:14:43 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id PAA28347; Wed, 4 Feb 1998 15:14:39 -0500 (EST) Message-ID: <19980204151439.53297@cs.swarthmore.edu> Date: Wed, 4 Feb 1998 15:14:39 -0500 From: Daniel Eisenbud To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> <19980204135450.49895@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204135450.49895@cs.swarthmore.edu>; from Daniel Eisenbud on Wed, Feb 04, 1998 at 01:54:50PM -0500 On Wed, Feb 04, 1998 at 01:54:50PM -0500, Daniel Eisenbud wrote: > This is probably OK, but it only works for mbox folders. Ignore this comment, it has no bearing on the matter, at a glance I thought the code worked differently than it does. See my other reply. -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From sec@matrix.42.org Wed Feb 4 12:37:22 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA16130 for ; Wed, 4 Feb 1998 12:37:18 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id VAA03665 (sender ); Wed, 4 Feb 1998 21:36:31 +0100 (CET) Message-ID: <19980204213630.02066@matrix.42.org> Date: Wed, 4 Feb 1998 21:36:30 +0100 From: Stefan `Sec` Zehl To: Igor Vinokurov , mutt-users@cs.hmc.edu Subject: Re: after pipe to less keyboard _partially_ freez... Mail-Followup-To: Igor Vinokurov , mutt-users@cs.hmc.edu References: <19980204224945.10991@zynaps.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980204224945.10991@zynaps.ru>; from Igor Vinokurov on Wed, Feb 04, 1998 at 10:49:45PM +0300 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Wed, Feb 04, 1998 at 10:49:45PM +0300, Igor Vinokurov wrote: > People, > > Could you explain why arrow-keys not work just after > piping to less and return to index? I guess it's some curses problem, that the curser keys have been put out of the 'application mode' (then they generate difefrent keycodes) I've had just too much troubles with that, and everybody just answered, "Your termcap is broken" (which it possibly is) that i solved it by re-binding the other keycodes to the appropriate functions: .muttrc: bind generic \e[A previous-entry bind generic \e[B next-entry I never had problems after this. CU, Sec -- Actually it's an beta version of Unix-NT. From eisenbud@allspice.cs.swarthmore.edu Wed Feb 4 12:41:07 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA16388 for ; Wed, 4 Feb 1998 12:41:02 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id PAA28972; Wed, 4 Feb 1998 15:40:47 -0500 (EST) Message-ID: <19980204154047.37429@cs.swarthmore.edu> Date: Wed, 4 Feb 1998 15:40:47 -0500 From: Daniel Eisenbud To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> <19980204140247.50536@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204140247.50536@cs.swarthmore.edu>; from Daniel Eisenbud on Wed, Feb 04, 1998 at 02:02:47PM -0500 On Wed, Feb 04, 1998 at 02:02:47PM -0500, Daniel Eisenbud wrote: > Thinking more about this, doesn't mutt leave atime=mtime if it modifies > a folder upon exit? I think what may be happening in your case is that procmail is taking more than a second to create the mailbox, so mtime and atime > ctime. I don't think that we can do much better than this. If you convince us that your change won't cause tons of false positives, maybe we can do it, but I can't see how it would work right. I think that if you want to really depend on detecting this, you should set keep_empty (or at least have a folder-hook to set this for your mailboxes folders) and just make sure your mailboxes folders always exist. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From eisenbud@allspice.cs.swarthmore.edu Wed Feb 4 12:43:01 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA16835 for ; Wed, 4 Feb 1998 12:42:56 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id PAA29027; Wed, 4 Feb 1998 15:42:52 -0500 (EST) Message-ID: <19980204154252.26573@cs.swarthmore.edu> Date: Wed, 4 Feb 1998 15:42:52 -0500 From: Daniel Eisenbud To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> <19980204140247.50536@cs.swarthmore.edu> <19980204203602.58389@mine.informatik.uni-kiel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204203602.58389@mine.informatik.uni-kiel.de>; from Claus Assmann on Wed, Feb 04, 1998 at 08:36:02PM +0100 On Wed, Feb 04, 1998 at 08:36:02PM +0100, Claus Assmann wrote: > On Wed, Feb 04, 1998 at 02:02:47PM -0500, Daniel Eisenbud wrote: > > Thinking more about this, doesn't mutt leave atime=mtime if it modifies > > a folder upon exit? > > No, at least not here: > stat sun-managers-list > changed : Wed Feb 4 20:30:15 1998 > accessed: Wed Feb 4 20:29:43 1998 > modified: Wed Feb 4 20:29:26 1998 > > I just read this folder before switching to mutt and I deleted > some mails therein. Or do I misunderstand your question? > Up to now the patch works fine for me (on mbox folders), > it never gave me a false positive (saying there is new mail > while there isn't) nor (hopefully :-) telling me not about new > mail in a newly created folder (I checked it a few times). Hmm. And we don't think that other mailers, etc, won't do this too? Maybe... I'd be curious to know what the permissions on your folders are immediately after procmail has created them, so I can know how the current scheme is breaking. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From eisenbud@allspice.cs.swarthmore.edu Wed Feb 4 12:47:15 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA17393 for ; Wed, 4 Feb 1998 12:47:12 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id PAA29105; Wed, 4 Feb 1998 15:47:09 -0500 (EST) Message-ID: <19980204154709.10449@cs.swarthmore.edu> Date: Wed, 4 Feb 1998 15:47:09 -0500 From: Daniel Eisenbud To: mutt-users@cs.hmc.edu Subject: Re: Mutt feature request -- duplicate message detection/deletion Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980204115843.02167@wombat> <19980204204441.13468@matrix.42.org> <19980204145456.42102@wombat> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204145456.42102@wombat>; from Rich Kulawiec on Wed, Feb 04, 1998 at 02:54:56PM -0500 On Wed, Feb 04, 1998 at 02:54:56PM -0500, Rich Kulawiec wrote: > > Hm, I guess this will not satisfy you, but i filter dupes with: > > > > # Do filter dupes. remove second rule and 'c' in first one to throw them away > > [...] > > > > in my .procmailrc which works like a charm. So i don't need such a > > feature :) > > That's correct, it won't work for me. The reason is that I do not wish > to filter duplicates as they arrive (especially since some of them are > arriving via FTP and NNTP, not SMTP) but later when they're just sitting in > a folder. So you can use formail to split up the folder and pipe it through procmail. You want to make sure that you use a new message-id cache each run. This doesn't belong in mutt, I think, but if you or someone gets something working, I imagine Michael might be willing to put it in the contrib directory. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From eisenbud@allspice.cs.swarthmore.edu Wed Feb 4 12:50:13 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA17702 for ; Wed, 4 Feb 1998 12:50:01 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id PAA29173; Wed, 4 Feb 1998 15:49:59 -0500 (EST) Message-ID: <19980204154959.21675@cs.swarthmore.edu> Date: Wed, 4 Feb 1998 15:49:59 -0500 From: Daniel Eisenbud To: Mutt users mailing list Subject: Re: [0.89.1i] bugfix: buffy sanity checks Mail-Followup-To: Mutt users mailing list References: <19980202111333.01745@att.com> <19980202133233.45583@cs.swarthmore.edu> <19980204101400.55686@iil.intel.com> <19980204111514.41783@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204111514.41783@cs.swarthmore.edu>; from Daniel Eisenbud on Wed, Feb 04, 1998 at 11:15:14AM -0500 On Wed, Feb 04, 1998 at 11:15:14AM -0500, Daniel Eisenbud wrote: > On Wed, Feb 04, 1998 at 10:14:00AM +0200, Michael S. Tsirkin wrote: > > Daniel, this means that one who does not use buffy at all has to pay > > performance time for this check (call "time"). > > > > Pls put "BuffyTime = time" AFTER the "fastest return" case. > > OK, will do. On second thought, I have to point out that a call to time() doesn't actually take a significant amount of time, given that in the current code that only happens when mutt_force_buffy_check is called explicitly from outside of mutt_buffy_check, which happens once while changing folders. This is truly insignificant. OK, I don't have time to make a patch now, but if you want to, go ahead. I think I will probably do a few more cleanups in buffy.c in a few days, though, so I guess I'll make this change then otherwise. -Daniel -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From rsk@gsp.org Wed Feb 4 12:57:03 1998 Return-Path: rsk@gsp.org Received: from gsp.org (rsk.itw.com [208.211.3.21]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA18416 for ; Wed, 4 Feb 1998 12:56:59 -0800 (PST) Received: (from rsk@localhost) by gsp.org (8.8.8/8.8.8) id PAA28994; Wed, 4 Feb 1998 15:57:51 -0500 (EST) Message-ID: <19980204155749.58554@wombat> Date: Wed, 4 Feb 1998 15:57:49 -0500 From: Rich Kulawiec To: mutt-users@cs.hmc.edu Subject: Re: Mutt feature request -- duplicate message detection/deletion References: <19980204115843.02167@wombat> <19980204204441.13468@matrix.42.org> <19980204145456.42102@wombat> <19980204154709.10449@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980204154709.10449@cs.swarthmore.edu>; from Daniel Eisenbud on Wed, Feb 04, 1998 at 03:47:09PM -0500 On Wed, Feb 04, 1998 at 03:47:09PM -0500, Daniel Eisenbud wrote: > So you can use formail to split up the folder and pipe it through > procmail. You want to make sure that you use a new message-id cache > each run. This doesn't belong in mutt, I think, but if you or someone > gets something working, I imagine Michael might be willing to put it in > the contrib directory. Hmmm, I hadn't thought of that. (Doh!) Alright, I'll give it a try and see if I can't get it to work in reliable fashion. I'm somewhat of a procmail newbie, having only recently tossed Elm's "filter" overboard, but it doesn't look too hideous. I also partially agree with you that this may not belong in mutt; I can think of reasons on both sides of the question and don't really feel terribly strongly about it one way or another. ---Rsk Rich Kulawiec rsk@gsp.org From Ulli.Horlacher@RUS.Uni-Stuttgart.DE Wed Feb 4 13:30:37 1998 Return-Path: Ulli.Horlacher@RUS.Uni-Stuttgart.DE Received: from noc.belwue.de (root@noc.BelWue.DE [129.143.2.1]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA23307 for ; Wed, 4 Feb 1998 13:30:32 -0800 (PST) Received: from bofh.belwue.de (bofh.BelWue.DE [129.143.2.24]) by noc.belwue.de (8.8.8/8.8.8) with ESMTP id WAA26818 for ; Wed, 4 Feb 1998 22:30:26 +0100 (MET) env-from (framstag@bofh.belwue.de) Received: (from framstag@localhost) by bofh.belwue.de (8.8.8/8.8.7) id WAA00457; Wed, 4 Feb 1998 22:30:25 +0100 (MET) Message-ID: <19980204223025.11869@bofh.belwue.de> Date: Wed, 4 Feb 1998 22:30:25 +0100 From: Ulli Horlacher To: mutt-users@turing.cs.hmc.edu Subject: multi language support? Mail-Followup-To: mutt-users@turing.cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Are there any plans to add multi language aka locale support to mutt? I have a lot of mutt users which don't speak any english - or cannot read it, in this case. It is a very hard job to explain them what all those messages and commands mean. And YES - there are some billions people out there in the world which don't know English. My mother is one of them (but she is a mutt-user) :-) -- \ Ulli 'Framstag' Horlacher \ BelWue-Koordination \ framstag@belwue.de \ \ Universitaet Stuttgart \ Allmandring 30 \ D-70550 Stuttgart \ Germany \ \ SAFT://saft.belwue.de/framstag \ HTTP://www.belwue.de/ \ \ "X.500: Security through Complexity" - Juergen G. \ From sec@matrix.42.org Wed Feb 4 13:48:02 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA24873 for ; Wed, 4 Feb 1998 13:47:58 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id WAA04414 (sender ); Wed, 4 Feb 1998 22:47:55 +0100 (CET) Message-ID: <19980204224754.04636@matrix.42.org> Date: Wed, 4 Feb 1998 22:47:54 +0100 From: Stefan `Sec` Zehl To: mutt-users@turing.cs.hmc.edu Subject: Re: multi language support? Mail-Followup-To: mutt-users@turing.cs.hmc.edu References: <19980204223025.11869@bofh.belwue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980204223025.11869@bofh.belwue.de>; from Ulli Horlacher on Wed, Feb 04, 1998 at 10:30:25PM +0100 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Wed, Feb 04, 1998 at 10:30:25PM +0100, Ulli Horlacher wrote: > And YES - there are some billions people out there in the world which don't > know English. My mother is one of them (but she is a mutt-user) :-) We had this topic many many moons ago :) - IIRC we decided that it would not be worth it, since it makes the code ugly, and harder to maintain. We planned to add it 'maybe' after 1.0 - before that, it would just hinder development. And then we have this (strong, IMHO) argument, that mutt is an power-user MUA, and thus is more target to people who speak english. (You need english for most of unix, anyway) CU, Sec P.S.: the only other translated programs i know of, are pgp and tcsh, and both translations to german made swicht back to english instantly. :) -- Hiroshima '45 Tsjernobyl '86 Windows '95 From gomar@c241.fem.tu-ilmenau.de Wed Feb 4 13:52:42 1998 Return-Path: gomar@c241.fem.tu-ilmenau.de Received: from piggy.rz.tu-ilmenau.de (piggy.rz.tu-ilmenau.de [141.24.4.8]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA25483 for ; Wed, 4 Feb 1998 13:52:40 -0800 (PST) Received: from c241.fem.tu-ilmenau.de (c241.fem.tu-ilmenau.de [141.24.68.77]) by piggy.rz.tu-ilmenau.de (8.8.8/8.8.8) with ESMTP id WAA00319 for ; Wed, 4 Feb 1998 22:52:28 +0100 (MET) Received: (from gomar@localhost) by c241.fem.tu-ilmenau.de (8.8.3/8.8.3) id WAA02431; Wed, 4 Feb 1998 22:51:53 +0100 Message-ID: <19980204225152.35377@c241.fem.tu-ilmenau.de> Date: Wed, 4 Feb 1998 22:51:52 +0100 From: Marco Goetze To: mutt-announce@cs.hmc.edu Subject: subscribe Reply-To: Marco Goetze Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i From Vincent.Lefevre@ens-lyon.fr Wed Feb 4 14:20:35 1998 Return-Path: Vincent.Lefevre@ens-lyon.fr Received: from cri.ens-lyon.fr (cri.ens-lyon.fr [140.77.1.32]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id OAA29216 for ; Wed, 4 Feb 1998 14:20:31 -0800 (PST) Received: from zelfde.ens-lyon.fr (zelfde [140.77.11.124]) by cri.ens-lyon.fr (8.8.5/8.8.1) with ESMTP id XAA00728; Wed, 4 Feb 1998 23:20:20 +0100 (MET) Received: (from vlefevre@localhost) by zelfde.ens-lyon.fr (8.8.5/8.8.0) id XAA11014; Wed, 4 Feb 1998 23:20:19 +0100 (MET) Message-ID: <19980204232019.26226@ens-lyon.fr> Date: Wed, 4 Feb 1998 23:20:19 +0100 From: Vincent Lefevre To: mutt-users@cs.hmc.edu Subject: body-search: how? $simple_search bug? Mail-Followup-To: mutt-users@cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 X-Mailer-Info: http://www.ens-lyon.fr/~vlefevre/mutt_eng.html I'd like to know how to replace the old body-search. Do not reply macro index ... "/~b " because this does *not* work when you do several searches on the same pattern, and I want to always use the same key for a body-search. I've tried the following: bind index \e/ search macro index / ":set simple_search='~f %s | ~s %s'\r\e/" macro index \\ ":set simple_search='~b %s'\r\e/" but this doesn't work. It seems that when I change $simple_search, this isn't taken into account if I search for the same pattern. (This is with Mutt 0.89) -- Vincent Lefevre | Acorn Risc PC, StrongARM @ 202MHz WWW: http://www.ens-lyon.fr/~vlefevre/ | 20+2MB RAM, Eagle M2, TV + Teletext PhD st. in Computer Science, 2nd year | Apple CD-300, SyQuest 270MB (SCSI) ----------------------------------------------------------------------------- From eisenbud@allspice.cs.swarthmore.edu Wed Feb 4 14:25:58 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id OAA29884 for ; Wed, 4 Feb 1998 14:25:53 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id RAA02124; Wed, 4 Feb 1998 17:25:50 -0500 (EST) Message-ID: <19980204172550.41448@cs.swarthmore.edu> Date: Wed, 4 Feb 1998 17:25:50 -0500 From: Daniel Eisenbud To: mutt-users@turing.cs.hmc.edu Subject: Re: multi language support? Mail-Followup-To: mutt-users@turing.cs.hmc.edu References: <19980204223025.11869@bofh.belwue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204223025.11869@bofh.belwue.de>; from Ulli Horlacher on Wed, Feb 04, 1998 at 10:30:25PM +0100 On Wed, Feb 04, 1998 at 10:30:25PM +0100, Ulli Horlacher wrote: > Are there any plans to add multi language aka locale support to mutt? > > I have a lot of mutt users which don't speak any english - or cannot read > it, in this case. It is a very hard job to explain them what all those > messages and commands mean. > > And YES - there are some billions people out there in the world which don't > know English. My mother is one of them (but she is a mutt-user) :-) Michael asked about this a while ago. The consensus that developed was that people didn't really want internationalization very much. OTOH, that was probably influenced in part by the fact that everyone on this list speaks English. I don't really remember the discussion very well - you might want to look in the archives and see what people had to say. But I just looked in my copy of the archives, and couldn't find that discussion... Oh, now I did. It's in March 1997 (starting March 12) and the subject is "NLS support survey". -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From Ulli.Horlacher@RUS.Uni-Stuttgart.DE Wed Feb 4 14:52:58 1998 Return-Path: Ulli.Horlacher@RUS.Uni-Stuttgart.DE Received: from noc.belwue.de (root@noc.BelWue.DE [129.143.2.1]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id OAA03147 for ; Wed, 4 Feb 1998 14:52:56 -0800 (PST) Received: from bofh.belwue.de (bofh.BelWue.DE [129.143.2.24]) by noc.belwue.de (8.8.8/8.8.8) with ESMTP id XAA10597 for ; Wed, 4 Feb 1998 23:52:46 +0100 (MET) env-from (framstag@bofh.belwue.de) Received: (from framstag@localhost) by bofh.belwue.de (8.8.8/8.8.7) id XAA00695; Wed, 4 Feb 1998 23:52:45 +0100 (MET) Message-ID: <19980204235245.19870@bofh.belwue.de> Date: Wed, 4 Feb 1998 23:52:45 +0100 From: Ulli Horlacher To: mutt-users@turing.cs.hmc.edu Subject: Re: multi language support? Mail-Followup-To: mutt-users@turing.cs.hmc.edu References: <19980204223025.11869@bofh.belwue.de> <19980204224754.04636@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980204224754.04636@matrix.42.org>; from Stefan `Sec` Zehl on Wed, Feb 04, 1998 at 10:47:54PM +0100 On Wed 1998-02-04 (22:47), Stefan `Sec` Zehl wrote: > mutt is an power-user MUA, and thus is more target to people who speak > english. (You need english for most of unix, anyway) In this case, which UNIX-MUA would you suggest for a german-only speaking person? AND DON'T SAY "INSTALL WINDOWS"! :-) BTW: My mother is 60 and got her very first computer from me, last year. It is a Linux PC. There she uses irc, tin and - of course - mutt. She is very happy with it, but sometimes she has big problems understanding the (error) messages or reading the help pages. BTW-2: since 2 weeks she also uses pgp within mutt! You can see with this exaple HOW easy and good the pgp-integration of mutt is! -- \ Ulli 'Framstag' Horlacher \ BelWue-Koordination \ framstag@belwue.de \ \ Universitaet Stuttgart \ Allmandring 30 \ D-70550 Stuttgart \ Germany \ \ SAFT://saft.belwue.de/framstag \ HTTP://www.belwue.de/ \ \ "X.500: Security through Complexity" - Juergen G. \ From mihannin@cc.hut.fi Wed Feb 4 15:10:35 1998 Return-Path: mihannin@cc.hut.fi Received: from vipunen.hut.fi (root@vipunen.hut.fi [130.233.224.20]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA05422 for ; Wed, 4 Feb 1998 15:10:33 -0800 (PST) Received: from chamber (root@cc-dialin1-34.hut.fi [130.233.251.34]) by vipunen.hut.fi (8.8.8/8.8.7) with ESMTP id BAA168716 for ; Thu, 5 Feb 1998 01:10:30 +0200 Received: (qmail 2623 invoked by alias); 4 Feb 1998 22:55:32 +0200 Received: (qmail 2604 invoked by uid 501); 4 Feb 1998 22:55:31 +0200 Message-ID: <19980204225530.23743@iki.fi> Date: Wed, 4 Feb 1998 22:55:30 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: Rich Kulawiec Cc: mutt-users@cs.hmc.edu Subject: Re: Mutt feature request -- duplicate message detection/deletion Mail-Followup-To: Rich Kulawiec , mutt-users@cs.hmc.edu References: <19980204115843.02167@wombat> <19980204204441.13468@matrix.42.org> <19980204145456.42102@wombat> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.89 In-Reply-To: <19980204145456.42102@wombat>; from Rich Kulawiec on Wed, Feb 04, 1998 at 02:54:56PM -0500 Organization: None X-No-Archive: yes X-WWW-Homepage: http://www.iki.fi/wiz/ Rich Kulawiec wrote on Wed, 04 Feb 1998: > That's correct, it won't work for me. The reason is that I do not wish > to filter duplicates as they arrive (especially since some of them are > arriving via FTP and NNTP, not SMTP) but later when they're just sitting in > a folder. What stops you from running procmail on the folder you wish to purge duplicates from? Procmail filtering doesn't necessarily have to be done at mail arrival. It should be trivial, or at least easy to put together a shell script / procmail combination to do this (which could then be executed from within Mutt too, of course). > ---Rsk -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // // net.freak, DALnet IRC operator, other interests: RPGs (GURPS & other), // // Fantasy & Sci-Fi, Comics (Elfquest & Sandman), Programming, Linux, WWW // // Any sufficiently advanced magic is indistinguishable from technology. // From acup@amug.org Wed Feb 4 15:22:08 1998 Return-Path: acup@amug.org Received: from general.amug.org (amug.org [204.62.193.2]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA07057 for ; Wed, 4 Feb 1998 15:22:06 -0800 (PST) Received: from [204.62.193.30] (alucard.amug.org [204.62.193.30]) by general.amug.org (8.8.6-AMUG.f1c1/8.8.6) with SMTP id QAA23451 for ; Wed, 4 Feb 1998 16:21:12 -0700 (MST) Message-Id: <199802042321.QAA23451@general.amug.org> Subject: subscribe Date: Wed, 4 Feb 98 16:25:54 -0700 x-sender: acup@amug.org x-mailer: Claris Emailer 2.0, March 15, 1997 From: Tim Sanker To: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" From me Wed Feb 4 17:37:11 1998 Return-Path: me Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id RAA22758; Wed, 4 Feb 1998 17:37:04 -0800 (PST) Message-ID: <19980204173704.20914@turing.cs.hmc.edu> Date: Wed, 4 Feb 1998 17:37:04 -0800 From: Michael Elkins To: Robin Kearney Cc: Mutt User List Subject: Re: Mutt and SMTP Mail-Followup-To: Robin Kearney , Mutt User List References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1 In-Reply-To: ; from Robin Kearney on Mon, Feb 02, 1998 at 06:23:29PM +0000 On Mon, Feb 02, 1998 at 06:23:29PM +0000, Robin Kearney wrote: > I use mutt as a mail reader at home and would like to be able to use it at > university as well, but the linux machines at uni don`t run sendmail localy, > some (stupid) systems guy has forced us to use a mail package that can SMTP > to another host, currently the only supported readers are pine or netscape :( > Can mutt be compiled with this functionality, or do I have to fight with pine > for longer??? Mutt does not support direct SMTP negotiation, and will not (at least in the near future). Your best bet is to find some simple program which emulates sendmail's interface which will just shove the mail off. me From murphyja@cig.mot.com Wed Feb 4 21:10:34 1998 Return-Path: murphyja@cig.mot.com Received: from motgate.mot.com (motgate.mot.com [129.188.136.100]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id VAA15927 for ; Wed, 4 Feb 1998 21:10:32 -0800 (PST) Received: from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (8.8.5/8.6.10/MOT-3.8) with ESMTP id XAA15205 for ; Wed, 4 Feb 1998 23:09:23 -0600 (CST) Comments: ( Received on motgate.mot.com from client pobox.mot.com, sender murphyja@cig.mot.com ) Received: from po_box.cig.mot.com ([136.182.15.5]) by pobox.mot.com (8.8.5/8.6.10/MOT-3.8) with SMTP id XAA29445 for ; Wed, 4 Feb 1998 23:09:18 -0600 (CST) Message-Id: <199802050512.AAA15409@po_box.cig.mot.com> Received: (murphyja@localhost) by hsh.cig.mot.com (8.7.5 Motorola CIG/ITS v1.1 (Solaris 2.5)) id XAA28441; Wed, 4 Feb 1998 23:08:29 -0600 (CST) Date: Wed, 4 Feb 1998 23:08:28 -0600 From: Jim Murphy To: mutt-users@cs.hmc.edu Subject: internal pager Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e First - thanks to all for a great MUA. Switched from Elm about Xmass time and it does everything and more of what I hoped someday Elm would do. Can someone tell me is there a way to get the internal pager to recognize a "^L"(ctrl-L) in the body, and put the next part of the document at the top of the next page it displays? I always found this a nice feature in Elm when viewing a report with multiple sections. This made the document much easier to read. So far I have not been able to find anything that would indicate that this is currently possible. Thanks in advance, Jim -- | Jim Murphy | Lead Engineer (Systems & Network) | | Motorola C.I.G. (ITS P&I) | E-Mail: murphyja@cig.mot.com | "The woods are lovely, dark and deep. But I have promises to keep, And lines to code before I sleep, And lines to code before I sleep." From god@omegazone.dyn.ml.org Wed Feb 4 21:55:37 1998 Return-Path: god@omegazone.dyn.ml.org Received: from omegazone.dyn.ml.org (root@d13-ts06.amug.org [198.182.127.142]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id VAA22538 for ; Wed, 4 Feb 1998 21:55:34 -0800 (PST) Received: by omegazone.dyn.ml.org id m0y0KHk-000VR7C (Debian Smail-3.2 1996-Jul-4 #2); Wed, 4 Feb 1998 22:55:40 -0700 (MST) Message-ID: <19980204225540.44862@amug.org> Date: Wed, 4 Feb 1998 22:55:40 -0700 From: alucard@amug.org To: mutt-users@cs.hmc.edu Subject: Home Mailbox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 How do you make mutt use /var/spool/mail/ a default so that after viewing another folder it will go there without having to put in the path, and file name? Thanks for helping this newbie. ;) -- From olsenc@ichips.intel.com Wed Feb 4 22:51:58 1998 Return-Path: olsenc@ichips.intel.com Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id WAA28394 for ; Wed, 4 Feb 1998 22:51:57 -0800 (PST) Received: from ichips-jf.jf.intel.com (ichips-jf.jf.intel.com [134.134.50.200]) by ganymede.or.intel.com (8.8.6/8.8.5) with ESMTP id WAA13435 for ; Wed, 4 Feb 1998 22:55:50 -0800 (PST) Received: from dtthp169 (olsenc@dtthp169.jf.intel.com [134.134.102.22]) by ichips-jf.jf.intel.com (8.8.8/8.8.7) with ESMTP id WAA15820 for ; Wed, 4 Feb 1998 22:51:56 -0800 (PST) Received: by dtthp169 (8.8.8/WW2.1) id WAA09041; Wed, 4 Feb 1998 22:51:56 -0800 (PST) Message-ID: <19980204225155.01246@dtthp169.jf.intel.com> Date: Wed, 4 Feb 1998 22:51:55 -0800 From: Clint Olsen To: mutt-users@cs.hmc.edu Subject: Re: Home Mailbox Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980204225540.44862@amug.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980204225540.44862@amug.org>; from alucard@amug.org on Wed, Feb 04, 1998 at 10:55:40PM -0700 Organization: Intel Corporation, Hillsboro, OR X-Disclaimer: Mutt Bites! On Feb 04, alucard@amug.org wrote: > How do you make mutt use /var/spool/mail/ a default so that > after viewing another folder it will go there without having to put in > the path, and file name? The shortcut for the spoolfile is '!' when using 'c'hange folders from the index menu. -Clint From ca@informatik.uni-kiel.de Thu Feb 5 00:44:28 1998 Return-Path: ca@informatik.uni-kiel.de Received: from mine.informatik.uni-kiel.de (hM3gvCLoSBY+8U0rwZbawccn231yZb1t@mine.informatik.uni-kiel.de [134.245.252.204]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA09371 for ; Thu, 5 Feb 1998 00:44:24 -0800 (PST) Received: (from ca@localhost) by mine.informatik.uni-kiel.de (8.8.8/8.8.8) id JAA22072; Thu, 5 Feb 1998 09:43:51 +0100 (MET) Message-ID: <19980205094351.54837@mine.informatik.uni-kiel.de> Date: Thu, 5 Feb 1998 09:43:51 +0100 From: Claus Assmann To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> <19980204140247.50536@cs.swarthmore.edu> <19980204154047.37429@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19980204154047.37429@cs.swarthmore.edu>; from Daniel Eisenbud on Wed, Feb 04, 1998 at 03:40:47PM -0500 On Wed, Feb 04, 1998 at 03:40:47PM -0500, Daniel Eisenbud wrote: > I think what may be happening in your case is that procmail is taking > more than a second to create the mailbox, so mtime and atime > ctime. No: they are all identical: rz-news changed : Thu Feb 5 09:36:19 1998 accessed: Thu Feb 5 09:36:19 1998 modified: Thu Feb 5 09:36:19 1998 (does this answer the other e-mail too?) Maybe that would give a better test than my simple approach? > I don't think that we can do much better than this. If you convince us > that your change won't cause tons of false positives, maybe we can do > it, but I can't see how it would work right. I think that if you want How can I convince you? It works for me... Maybe someone else can test it too? > to really depend on detecting this, you should set keep_empty (or at > least have a folder-hook to set this for your mailboxes folders) and just > make sure your mailboxes folders always exist. Well, I'll take a look at this. Thanks, Claus From eisenbud@allspice.cs.swarthmore.edu Thu Feb 5 06:09:15 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id GAA03128 for ; Thu, 5 Feb 1998 06:09:13 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id JAA16202; Thu, 5 Feb 1998 09:09:13 -0500 (EST) Message-ID: <19980205090913.46652@cs.swarthmore.edu> Date: Thu, 5 Feb 1998 09:09:13 -0500 From: Daniel Eisenbud To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> <19980204140247.50536@cs.swarthmore.edu> <19980204154047.37429@cs.swarthmore.edu> <19980205094351.54837@mine.informatik.uni-kiel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980205094351.54837@mine.informatik.uni-kiel.de>; from Claus Assmann on Thu, Feb 05, 1998 at 09:43:51AM +0100 On Thu, Feb 05, 1998 at 09:43:51AM +0100, Claus Assmann wrote: > On Wed, Feb 04, 1998 at 03:40:47PM -0500, Daniel Eisenbud wrote: > > > I think what may be happening in your case is that procmail is taking > > more than a second to create the mailbox, so mtime and atime > ctime. > > No: they are all identical: > rz-news > changed : Thu Feb 5 09:36:19 1998 > accessed: Thu Feb 5 09:36:19 1998 > modified: Thu Feb 5 09:36:19 1998 > (does this answer the other e-mail too?) Then the current method should work right! Namely: #define STAT_CHECK (sb.st_mtime > sb.st_atime || (tmp->newly_created && sb.st_ctime == sb.st_mtime && sb.st_ctime == sb.st_atime)) Namely, the newly_created flag should be set on the mailbox, so the fact that ctime==mtime and ctime==atime should be sufficient for mutt to flag the mailbox as new. If it isn't, we have to do some debugging. But the current method should work, and I still think your method will cause false positives. In fact, it certainly will once we fix mutt to not cause false positives when saving to mailboxes folders. Let's move this discussion to mutt-dev. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From ca@informatik.uni-kiel.de Thu Feb 5 06:43:07 1998 Return-Path: ca@informatik.uni-kiel.de Received: from mine.informatik.uni-kiel.de (rlldEmdN5HKVmd8ZNZnVsouV3nlAIi9R@mine.informatik.uni-kiel.de [134.245.252.204]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id GAA05451 for ; Thu, 5 Feb 1998 06:42:56 -0800 (PST) Received: (from ca@localhost) by mine.informatik.uni-kiel.de (8.8.8/8.8.8) id PAA17646; Thu, 5 Feb 1998 15:42:28 +0100 (MET) Message-ID: <19980205154227.02348@mine.informatik.uni-kiel.de> Date: Thu, 5 Feb 1998 15:42:27 +0100 From: Claus Assmann To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980120165857.08460@mine.informatik.uni-kiel.de> <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> <19980204140247.50536@cs.swarthmore.edu> <19980204154047.37429@cs.swarthmore.edu> <19980205094351.54837@mine.informatik.uni-kiel.de> <19980205090913.46652@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19980205090913.46652@cs.swarthmore.edu>; from Daniel Eisenbud on Thu, Feb 05, 1998 at 09:09:13AM -0500 On Thu, Feb 05, 1998 at 09:09:13AM -0500, Daniel Eisenbud wrote: > Then the current method should work right! Namely: > #define STAT_CHECK (sb.st_mtime > sb.st_atime || > (tmp->newly_created && sb.st_ctime == sb.st_mtime && > sb.st_ctime == sb.st_atime)) Yes, I saw this "newly_created" too, but it wasn't set. > Namely, the newly_created flag should be set on the mailbox, so the fact > that ctime==mtime and ctime==atime should be sufficient for mutt to flag > the mailbox as new. If it isn't, we have to do some debugging. The comment in buffy.c is this: if the mailbox still doesn't exist, set the newly created flag to be ready for when it does. and thereafter comes the only time when newly_created is set. However, the folder _exists_ before I enter mutt, so this part of the code isn't reached (I just tried it in the debugger). Sorry, but I don't understand the internals well enough to propose a fix for this part. > Let's move this discussion to mutt-dev. If you do, please Cc: me those mails, because I'm not on that list (too many mails already). Thanks again, Claus From eisenbud@allspice.cs.swarthmore.edu Thu Feb 5 07:43:15 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id HAA09525 for ; Thu, 5 Feb 1998 07:43:12 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id KAA18732; Thu, 5 Feb 1998 10:43:11 -0500 (EST) Message-ID: <19980205104311.46350@cs.swarthmore.edu> Date: Thu, 5 Feb 1998 10:43:11 -0500 From: Daniel Eisenbud To: mutt-users Subject: Re: new mail in mailboxes gets "lost"? (was: wierd effect with mailbox list) Mail-Followup-To: mutt-users References: <19980125150856.39128@mine.informatik.uni-kiel.de> <19980125112440.15184@cnds.jhu.edu> <19980125173958.37629@matrix.42.org> <19980125180404.18362@mine.informatik.uni-kiel.de> <19980204173246.00327@mine.informatik.uni-kiel.de> <19980204140247.50536@cs.swarthmore.edu> <19980204154047.37429@cs.swarthmore.edu> <19980205094351.54837@mine.informatik.uni-kiel.de> <19980205090913.46652@cs.swarthmore.edu> <19980205154227.02348@mine.informatik.uni-kiel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980205154227.02348@mine.informatik.uni-kiel.de>; from Claus Assmann on Thu, Feb 05, 1998 at 03:42:27PM +0100 On Thu, Feb 05, 1998 at 03:42:27PM +0100, Claus Assmann wrote: > On Thu, Feb 05, 1998 at 09:09:13AM -0500, Daniel Eisenbud wrote: > > > Then the current method should work right! Namely: > > #define STAT_CHECK (sb.st_mtime > sb.st_atime || > > (tmp->newly_created && sb.st_ctime == sb.st_mtime && > > sb.st_ctime == sb.st_atime)) > > Yes, I saw this "newly_created" too, but it wasn't set. > > > Namely, the newly_created flag should be set on the mailbox, so the fact > > that ctime==mtime and ctime==atime should be sufficient for mutt to flag > > the mailbox as new. If it isn't, we have to do some debugging. > > The comment in buffy.c is this: > if the mailbox still doesn't exist, set the newly created flag to > be ready for when it does. > and thereafter comes the only time when newly_created is set. > However, the folder _exists_ before I enter mutt, so this part of > the code isn't reached (I just tried it in the debugger). > Sorry, but I don't understand the internals well enough to > propose a fix for this part. Ah, I see. Well, I don't think there is a reliable fix for this part, unfortunately. atime==mtime could mean that there's new mail, but it could also just mean that some program that deals differently with file times modified the mailbox last. There were some other checks in mutt a while ago for this case that were broken in other ways. Basically, I think that if you want "mailboxes" to work reliably, you should make sure that the mailboxes always exist (using keep_empty, at least on those folders.) Maybe we should add this to the docs. I think it's a pretty reasonable tradeoff - there's no harm in just keeping a few empty files around. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From vikasa@att.com Thu Feb 5 08:15:39 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw2.att.com [192.128.133.152]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id IAA12159 for ; Thu, 5 Feb 1998 08:15:23 -0800 (PST) Received: by kcgw2.att.com; Thu Feb 5 09:57 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id JAA12476 for ; Thu, 5 Feb 1998 09:08:40 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id KAA07362; Thu, 5 Feb 1998 10:18:47 -0500 (EST) Message-ID: <19980205101846.23520@att.com> Date: Thu, 5 Feb 1998 10:18:46 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 Attached 2 files from the compose menu. Windows-land BMP (bitmap files). The compose menu shows the first one attached rightly as application/octet-stream with base64 encoding. The second one is attached as 'text/plain with q-p encoding' ! I did 'detach', attach again, no effect. Thought the 2 attachments might be causing a problem. So I aborted this mail and started a new mail and attached just the 2nd file and it still attached it as text/plain! Right now, I also tried to attach the BMP file to _this_ mail and it still gets text/plain. Another thing: I postponed the message with the 2 attachments (app/octet and text/plain) and when I recalled it, the main message body which is usually a filename like /tmp/mutt-machine-1234 is now /tmp/muttaa234. Why did the format of the file-name change? I noticed because my Vim autocommands didnt match the new name! Whats going on here? Thanks, Vikas From vikasa@att.com Thu Feb 5 09:59:53 1998 Return-Path: vikasa@att.com Received: from att.com (cagw1.att.com [192.128.52.89]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id JAA21083 for ; Thu, 5 Feb 1998 09:59:50 -0800 (PST) Received: by cagw1.att.com; Thu Feb 5 10:57 EST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by caig1.att.att.com (AT&T/GW-1.0) with ESMTP id IAA09835 for ; Thu, 5 Feb 1998 08:38:38 -0500 (EST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id IAA07181 for mutt-users@cs.hmc.edu; Thu, 5 Feb 1998 08:47:09 -0500 (EST) Resent-Message-Id: <199802051347.IAA07181@8080b0da.ims.att.com> Message-ID: <19980204141931.03566@att.com> Date: Wed, 4 Feb 1998 14:19:31 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 Resent-From: vikas@att.com Resent-Date: Thu, 5 Feb 1998 08:47:09 -0500 Resent-To: Mutt users mailing list Attached 2 files from the compose menu. Windows-land BMP (bitmap files). The compose menu shows the first one attached rightly as application/octet-stream with base64 encoding. The second one is attached as 'text/plain with q-p encoding' ! I did 'detach', attach again, no effect. Thought the 2 attachments might be causing a problem. So I aborted this mail and started a new mail and attached just the 2nd file and it still attached it as text/plain! Right now, I also tried to attach the BMP file to _this_ mail and it still gets text/plain. Another thing: I postponed the message with the 2 attachments (app/octet and text/plain) and when I recalled it, the main message body which is usually a filename like /tmp/mutt-machine-1234 is now /tmp/muttaa234. Why did the format of the file-name change? I noticed because my Vim autocommands didnt match the new name! Whats going on here? Thanks, Vikas From blong@shell9.ba.best.com Thu Feb 5 11:00:29 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA27091 for ; Thu, 5 Feb 1998 11:00:27 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id KAA13127; Thu, 5 Feb 1998 10:59:48 -0800 (PST) Message-ID: <19980205105948.21420@shell9.ba.best.com> Date: Thu, 5 Feb 1998 10:59:48 -0800 From: Brandon Long To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Reply-To: blong@fiction.net Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980205101846.23520@att.com>; from Vikas Agnihotri on Thu, Feb 05, 1998 at 10:18:46AM -0500 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/05/98 Vikas Agnihotri uttered the following other thing: > Attached 2 files from the compose menu. Windows-land BMP (bitmap files). > The compose menu shows the first one attached rightly as > application/octet-stream with base64 encoding. > > The second one is attached as 'text/plain with q-p encoding' ! > > I did 'detach', attach again, no effect. > > Thought the 2 attachments might be causing a problem. So I aborted this > mail and started a new mail and attached just the 2nd file and it still > attached it as text/plain! > > Right now, I also tried to attach the BMP file to _this_ mail and it still > gets text/plain. Did you check the file? It may actually be pure text, hence mutt's finding. > Another thing: > > I postponed the message with the 2 attachments (app/octet and text/plain) > and when I recalled it, the main message body which is usually a filename > like /tmp/mutt-machine-1234 is now /tmp/muttaa234. Why did the format of > the file-name change? I noticed because my Vim autocommands didnt match the > new name! There are two functions for temp files, they should probably be combined. One is used when the file name is "known" (ie, for attachments) and the other when it is not. If the filename doesn't actually exist, it uses the old mktemp() instead of new one. That should be fixed. Brandon -- Brandon Long "Atheism requires too much faith." MD6 Crash Test Dummy -- Andrew C. Bulhak Intel Corporation I'm too low on the totem pole to speak for Intel. http://www.fiction.net/blong/ From vikasa@att.com Thu Feb 5 12:05:29 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw2.att.com [192.128.133.152]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id MAA05866 for ; Thu, 5 Feb 1998 12:04:45 -0800 (PST) Received: by kcgw2.att.com; Thu Feb 5 13:46 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id NAA13647 for ; Thu, 5 Feb 1998 13:51:35 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id PAA09004; Thu, 5 Feb 1998 15:01:45 -0500 (EST) Message-ID: <19980205150145.31309@att.com> Date: Thu, 5 Feb 1998 15:01:45 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> <19980205105948.21420@shell9.ba.best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1 In-Reply-To: <19980205105948.21420@shell9.ba.best.com>; from Brandon Long on Thu, Feb 05, 1998 at 10:59:48AM -0800 On Thu, Feb 05, 1998 at 10:59:48AM -0800, Brandon Long wrote: > On 02/05/98 Vikas Agnihotri uttered the following other thing: > > Attached 2 files from the compose menu. Windows-land BMP (bitmap files). > > The second one is attached as 'text/plain with q-p encoding' ! > Did you check the file? It may actually be pure text, hence mutt's > finding. No. It is a honest-to-God Windows Bitmap (BMP) file which I can double click on in File Manager (I have Samba'ed my home directory) and have it opened up in Paintbrush or whatever. Just glanced at the code (mutt_get_content_info() ) and it has a blurb about concluding octet-stream ONLY if %lobin >= 10. This might be the problem. What if my file does indeed contain just a handful of lobin characters? Further, if I change the content-type/encoding using ^T and ^E in the Compose menu, will Mutt actually re-encode the file or is this just a cosmetic change to the headers? Vikas From rnapier@cisco.com Thu Feb 5 12:14:13 1998 Return-Path: rnapier@cisco.com Received: from claret.cisco.com (claret.cisco.com [171.69.160.39]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA07135 for ; Thu, 5 Feb 1998 12:14:09 -0800 (PST) Received: (rnapier@localhost) by claret.cisco.com (8.8.4-Cisco.1/8.6.5) id PAA02277; Thu, 5 Feb 1998 15:13:33 -0500 (EST) Message-ID: <19980205151333.27746@cisco.com> Date: Thu, 5 Feb 1998 15:13:33 -0500 From: Robert Napier To: Mutt Users List Subject: Screen redraw problems Mail-Followup-To: Mutt Users List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i I often have trouble with my screen redraw in the pager, particularly the status line. It seems that characters that are not changed, are not properly redrawn, leaving black spaces. A ^L fixes this (so it's not a major deal), but I'd like to find out if others have the same problem. The problem does not always happen, but is fairly reproducible (by hitting "^L", "j", then "k"). Occasionally I also have redraw problems in the body area of the pager. It sometimes (rarely) leaves characters from the last message on the screen when redrawing the screen. ^L fixes this problem too. Here's the stats on my install: Mutt 0.89i, Copyright (C) 1996-8 Michael R. Elkins Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System info: SunOS 5.5.1 [using slang 9938] Compile time definitions: -DOMAIN +HIDDEN_HOST -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR -BUFFY_SIZE SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/users/rnapier/share" ISPELL="/usr/local/bin/ispell" -- Rob Napier | 7025 Kit Creek Road | Check out Triangle Ascension: rnapier@cisco.com | PO Box 14987 | http://www.serve.com/napier/mage 919/472-3941 | RTP, NC 27709 | +===========================================================================+ | Imagine what my body would sound like / Slamming against those rocks | | When it lands / Will my eyes / Be closed or open? -- Bjork "Hyper Ballad" | +===========================================================================+ From lhecking@nmrc.ucc.ie Thu Feb 5 12:22:28 1998 Return-Path: lhecking@nmrc.ucc.ie Received: from bastion.nmrc.ucc.ie (nmrc.ucc.ie [143.239.64.1]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA08242 for ; Thu, 5 Feb 1998 12:21:56 -0800 (PST) Received: from odessa.nmrc.ucc.ie (odessa.nmrc.ucc.ie [143.239.64.65]) by bastion.nmrc.ucc.ie (8.8.8/8.8.8) with ESMTP id UAA27716 for ; Thu, 5 Feb 1998 20:23:30 GMT Message-ID: <19980205202038.26189@nmrc.ucc.ie> Date: Thu, 5 Feb 1998 20:20:38 +0000 From: Lars Hecking To: Mutt Users List Subject: Re: Screen redraw problems Mail-Followup-To: Mutt Users List References: <19980205151333.27746@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980205151333.27746@cisco.com>; from Robert Napier on Thu, Feb 05, 1998 at 03:13:33PM -0500 Robert Napier writes: > I often have trouble with my screen redraw in the pager, particularly > the status line. It seems that characters that are not changed, are > not properly redrawn, leaving black spaces. A ^L fixes this (so it's > not a major deal), but I'd like to find out if others have the same > problem. The problem does not always happen, but is fairly > reproducible (by hitting "^L", "j", then "k"). > > Occasionally I also have redraw problems in the body area of the > pager. It sometimes (rarely) leaves characters from the last message > on the screen when redrawing the screen. ^L fixes this problem too. > > Here's the stats on my install: > > Mutt 0.89i, Copyright (C) 1996-8 Michael R. Elkins > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > Mutt is free software, and you are welcome to redistribute it > under certain conditions; type `mutt -vv' for details. > > System info: SunOS 5.5.1 [using slang 9938] I had similar problems with slang under Solaris, and have switched to ncurses since. No such problems anymore, neither with dtterm nor xterm. From eisenbud@allspice.cs.swarthmore.edu Thu Feb 5 13:00:16 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA12190 for ; Thu, 5 Feb 1998 13:00:01 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id PAA00718; Thu, 5 Feb 1998 15:59:52 -0500 (EST) Message-ID: <19980205155952.62344@cs.swarthmore.edu> Date: Thu, 5 Feb 1998 15:59:52 -0500 From: Daniel Eisenbud To: Mutt Users List Subject: Re: Screen redraw problems Mail-Followup-To: Mutt Users List References: <19980205151333.27746@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980205151333.27746@cisco.com>; from Robert Napier on Thu, Feb 05, 1998 at 03:13:33PM -0500 I've only had this sort of problems when using a really crappy terminal emulator on an old IBM clone of some sort. What sort of terminal are you using? (I am also using mutt on Solaris 2.5.1 with slang 9938, so I doubt the problem is there.) -Daniel On Thu, Feb 05, 1998 at 03:13:33PM -0500, Robert Napier wrote: > I often have trouble with my screen redraw in the pager, particularly > the status line. It seems that characters that are not changed, are > not properly redrawn, leaving black spaces. A ^L fixes this (so it's > not a major deal), but I'd like to find out if others have the same > problem. The problem does not always happen, but is fairly > reproducible (by hitting "^L", "j", then "k"). > > Occasionally I also have redraw problems in the body area of the > pager. It sometimes (rarely) leaves characters from the last message > on the screen when redrawing the screen. ^L fixes this problem too. > > Here's the stats on my install: > > Mutt 0.89i, Copyright (C) 1996-8 Michael R. Elkins > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > Mutt is free software, and you are welcome to redistribute it > under certain conditions; type `mutt -vv' for details. > > System info: SunOS 5.5.1 [using slang 9938] > > Compile time definitions: > -DOMAIN > +HIDDEN_HOST -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK > -USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR -BUFFY_SIZE > SENDMAIL="/usr/lib/sendmail" > MAILPATH="/var/mail" > SHAREDIR="/users/rnapier/share" > ISPELL="/usr/local/bin/ispell" > > -- > Rob Napier | 7025 Kit Creek Road | Check out Triangle Ascension: > rnapier@cisco.com | PO Box 14987 | http://www.serve.com/napier/mage > 919/472-3941 | RTP, NC 27709 | > +===========================================================================+ > | Imagine what my body would sound like / Slamming against those rocks | > | When it lands / Will my eyes / Be closed or open? -- Bjork "Hyper Ballad" | > +===========================================================================+ -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From blong@shell9.ba.best.com Thu Feb 5 13:09:38 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA13429 for ; Thu, 5 Feb 1998 13:09:36 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id NAA18204; Thu, 5 Feb 1998 13:08:58 -0800 (PST) Message-ID: <19980205130857.08929@shell9.ba.best.com> Date: Thu, 5 Feb 1998 13:08:57 -0800 From: Brandon Long To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Reply-To: blong@fiction.net Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> <19980205105948.21420@shell9.ba.best.com> <19980205150145.31309@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980205150145.31309@att.com>; from Vikas Agnihotri on Thu, Feb 05, 1998 at 03:01:45PM -0500 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/05/98 Vikas Agnihotri uttered the following other thing: > On Thu, Feb 05, 1998 at 10:59:48AM -0800, Brandon Long wrote: > > On 02/05/98 Vikas Agnihotri uttered the following other thing: > > > Attached 2 files from the compose menu. Windows-land BMP (bitmap files). > > > The second one is attached as 'text/plain with q-p encoding' ! > > > Did you check the file? It may actually be pure text, hence mutt's > > finding. > > No. It is a honest-to-God Windows Bitmap (BMP) file which I can double > click on in File Manager (I have Samba'ed my home directory) and have it > opened up in Paintbrush or whatever. > > Just glanced at the code (mutt_get_content_info() ) and it has a blurb about > concluding octet-stream ONLY if %lobin >= 10. This might be the problem. > What if my file does indeed contain just a handful of lobin characters? Which is exactly what I meant. How about placing a mime.type for windows bmp in your mime.type file? > Further, if I change the content-type/encoding using ^T and ^E in the > Compose menu, will Mutt actually re-encode the file or is this just a > cosmetic change to the headers? Of course mutt will do the right thing. The files aren't actually encoded til you send them. Brandon -- Brandon Long "Computers make very fast, very accurate, mistakes." MD6 Crash Test Dummy blong@fiction.net I'm too low on the totem pole to speak for Intel. http://www.fiction.net/blong/ From thies@argh.org Thu Feb 5 15:09:56 1998 Return-Path: thies@argh.org Received: from rs1.hrz.tu-darmstadt.de (rs1.hrz.tu-darmstadt.de [130.83.22.60]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id PAA01573 for ; Thu, 5 Feb 1998 15:09:31 -0800 (PST) Received: from argh.org (root@ppp143.stud.tu-darmstadt.de [130.83.177.143]) by rs1.hrz.tu-darmstadt.de (8.6.12/8.6.12.1ms) with ESMTP id AAA92138 for ; Fri, 6 Feb 1998 00:02:59 +0100 Received: (from thies@localhost) by argh.org (8.8.3/8.8.3) id XAA22237; Thu, 5 Feb 1998 23:30:04 +0100 Message-ID: <19980205233002.54667@argh.org> Date: Thu, 5 Feb 1998 23:30:02 +0100 From: Michael Thies To: mutt-users@cs.hmc.edu Subject: [0.89.1i] problems with configuring mutt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Organization: Verein zur Foerderung der Datenkommunikation von Christen (VFDC) X-URL: http://wimbaer.home.pages.de/ X-Address: Pallaswiesenstrasse 42, D-64293 Darmstadt X-Phone: +49 6151 177642 Return-Receipt-To: thies@hrz1.tu-darmstadt.de X-Confirm-Reading-To: thies@hrz1.tu-darmstadt.de Hi all, Sorry, if this questions had been asked about, but I didn't got the mailinglist the last time! .-( I have two questions concerning .muttrc-0.89.1i: a) I always had a send-hook \.edu$ "set attribution='%n wrote about \"%s\":'" and now (with mutt-0.89.1i) a get problems with it, on replies I get Someone wrote about %s: as attribution. If cancel the \", I get Somenone wrote about theoldsubject: But I want to have the double-quotes! b) I wanted to try the color quoted1,...,quotedN-feature and with following in my .muttrc color quoted1 brightyellow black color quoted2 brightred black color quoted3 brightcyan black I get no colors. Who can help me on one or both questions? My mutt -v: System info: Linux 2.0.25 [using ncurses 1.9.9g] Compile time definitions: DOMAIN="argh.org" +HIDDEN_HOST -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR -BUFFY_SIZE SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/usr/local/lib" ISPELL="/usr/bin/ispell" _PGPPATH="/usr/local/bin/pgp" -- \o/ Michael Thies From fox@fuzzy.rsn.hp.com Thu Feb 5 16:07:50 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA09706 for ; Thu, 5 Feb 1998 16:07:48 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id QAA10740 for ; Thu, 5 Feb 1998 16:07:46 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id SAA03691; Thu, 5 Feb 1998 18:07:44 -0600 (CST) Message-ID: <19980205180744.39097@rsn.hp.com> Date: Thu, 5 Feb 1998 18:07:44 -0600 From: David DeSimone To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> <19980205105948.21420@shell9.ba.best.com> <19980205150145.31309@att.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="k1lZvvs/B4yU6o8G" X-Mailer: Mutt 0.89i In-Reply-To: <19980205150145.31309@att.com>; from Vikas Agnihotri on Thu, Feb 05, 1998 at 03:01:45PM -0500 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Vikas Agnihotri wrote: > > Just glanced at the code (mutt_get_content_info() ) and it has a blurb > about concluding octet-stream ONLY if %lobin >= 10. This might be the > problem. What if my file does indeed contain just a handful of lobin > characters? Then a quoted-printable encoding will probably be more efficient than base64. Does the file transfer successfully through the mail, or doesn't it? Did you try it out? -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNpUSw0lGhIp2tThAQHd2QL+OTWmkTCJlltw8l9czA2GNBQOoNk+Kbxo EFzSKZ8XgmbZihbJt/gYNPwclhLl4YK9Rk0gK07J/rGHCHnixf1iCgivZZjZHeT7 Y5eOl36U85af4fhHLcLsh5TrMMcKnhgL =OjM8 -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From Andrew.Large@Eng.Sun.COM Thu Feb 5 17:04:17 1998 Return-Path: Andrew.Large@Eng.Sun.COM Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id RAA16265 for ; Thu, 5 Feb 1998 17:04:13 -0800 (PST) Received: from Eng.Sun.COM (engmail2 [129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id RAA17154 for ; Thu, 5 Feb 1998 17:03:42 -0800 Received: from kea.eng.sun.com (kea.Eng.Sun.COM [129.146.114.224]) by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id RAA26448 for ; Thu, 5 Feb 1998 17:03:40 -0800 Received: from lobo.eng.sun.com by kea.eng.sun.com (SMI-8.6/SMI-SVR4) id RAA18372; Thu, 5 Feb 1998 17:03:37 -0800 Received: by lobo.eng.sun.com (SMI-8.6/SMI-SVR4) id RAA17290; Thu, 5 Feb 1998 17:03:38 -0800 Message-ID: <19980205170338.60275@eng.sun.com> Date: Thu, 5 Feb 1998 17:03:38 -0800 From: "Andrew R. Large" To: Mutt Users Subject: Save hook question Reply-To: alarge@techie.com Mail-Followup-To: Mutt Users Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i Organization: Sun Microsystems, Inc. I'm having this problem with save hooks that I'm hoping someone can help with. What I want to be able to do is set up rules for saving messages to particular folders, based upon the sender of the message. Sounds like save-hook, right? But it doesn't work ... at least not the way I want it to. When trying to match the appropriate save hook, it appears to be looking in the To: and Cc: fields as well. As a result, I get a match based on the *recipients* of the message, not the *sender*. BTW, I should mention that I usually have fcc-hooks for the same users, but that shouldn't affect a *save*, right? Here is an example ... suppose I set up the following hooks: fcc-save-hook bob +bob fcc-save-hook bill +bill If I get a message from 'bill' that is addressed to both 'bob' and myself, and I [s]ave the message, I get '+bob' as the default for save folder! I'm running 0.90.1i, but I don't think that is an issue, since I've seen the same behavior for as long as I've seen hooks (which is why I haven't claimed that this as a bug). -- -=*=-=*=-=*=-=*=-=*=-=*=-=*=+=*=-=*=-=*=-=*=-=*=-=*=-=*=- Andrew Large | Sun Microsystems, Inc. andrew.large@eng.sun.com | 901 San Antonio Road (650) 786-6503 [office] | MS MPK18-209 (650) 786-4101 [fax] | Palo Alto, CA 94303-4900 -=*=-=*=-=*=-=*=-=*=-=*=-=*=+=*=-=*=-=*=-=*=-=*=-=*=-=*=- From eisenbud@allspice.cs.swarthmore.edu Thu Feb 5 18:46:42 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA26808 for ; Thu, 5 Feb 1998 18:45:32 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id VAA07766; Thu, 5 Feb 1998 21:43:42 -0500 (EST) Message-ID: <19980205214341.49262@cs.swarthmore.edu> Date: Thu, 5 Feb 1998 21:43:41 -0500 From: Daniel Eisenbud To: mutt-users@cs.hmc.edu Subject: Re: [0.89.1i] problems with configuring mutt Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980205233002.54667@argh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980205233002.54667@argh.org>; from Michael Thies on Thu, Feb 05, 1998 at 11:30:02PM +0100 On Thu, Feb 05, 1998 at 11:30:02PM +0100, Michael Thies wrote: > b) I wanted to try the color quoted1,...,quotedN-feature > > and with following in my .muttrc > > color quoted1 brightyellow black > color quoted2 brightred black > color quoted3 brightcyan black > > I get no colors. Have you managed to get colors elsewhere in mutt? If not, it's almost certainly a terminal or termcap/terminfo problem. If you get colors elsewhere, but not in quotedN, that's more worrisome. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From vikasa@att.com Thu Feb 5 20:00:12 1998 Return-Path: vikasa@att.com Received: from att.com (cagw2.att.com [192.128.52.90]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id UAA06076 for ; Thu, 5 Feb 1998 20:00:10 -0800 (PST) Received: by cagw2.att.com; Thu Feb 5 18:44 EST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by caig2.att.att.com (AT&T/GW-1.0) with ESMTP id TAA21343 for ; Thu, 5 Feb 1998 19:03:20 -0500 (EST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id SAA09347; Thu, 5 Feb 1998 18:46:37 -0500 (EST) Message-ID: <19980205184637.59890@att.com> Date: Thu, 5 Feb 1998 18:46:37 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: Sorting by date-sent vs. date-received Mail-Followup-To: Mutt users mailing list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1 What is the difference between sorting by date-sent and date-received? For date-sent, Mutt looks at the Date: headers of the mail. For date-received, does Mutt parse my From_ line to actually determine when the mail was received? When sorting according to either of these 2 methods, does Mutt consider the different time zones? i.e. does Mutt normalize all date/time's to a certain timezone and _then_ sort? Thanks, Vikas From vaxerdec@vaxerdec.dyn.ml.org Thu Feb 5 21:01:39 1998 Return-Path: vaxerdec@vaxerdec.dyn.ml.org Received: from node21.frontiernet.net (root@node21.frontiernet.net [209.130.129.196]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id VAA14145 for ; Thu, 5 Feb 1998 21:01:36 -0800 (PST) Received: from vaxerdec.dyn.ml.org (as5300-4-13.roc.ny.frontiernet.net [209.130.137.118]) by node21.frontiernet.net (8.8.8/8.8.6) with ESMTP id XAA80228 for ; Thu, 5 Feb 1998 23:50:17 -0500 Received: (from vaxerdec@localhost) by vaxerdec.dyn.ml.org (8.8.8/8.8.8) id XAA28562; Thu, 5 Feb 1998 23:32:19 -0500 Message-ID: <19980205233219.32623@dyn.ml.org> Date: Thu, 5 Feb 1998 23:32:19 -0500 From: Scott McDermott To: mutt-users@cs.hmc.edu Subject: visited folder memory? Mail-Followup-To: mutt-users@cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 I use procmail to filter list mail to ~/mail/lists/list{1,2,3,...} ; this way upon entering mutt I have my spool file with non-list mail, then I `c' to change to the list dir and read each folder sequentially. One thing I can't seem to be able to do is have it so that when I `c' to say List1, then I'm done with List1 and `c' again, it doesn't automatically advance the target line to the next folder; it has to be done manually. Is there some way I can get this to auto-advance? Thanks, Scott From lillqvis@cc.helsinki.fi Thu Feb 5 21:14:28 1998 Return-Path: lillqvis@cc.helsinki.fi Received: from kontti.Helsinki.FI (lillqvis@kontti.helsinki.fi [128.214.205.13]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id VAA15349 for ; Thu, 5 Feb 1998 21:14:25 -0800 (PST) Received: (from lillqvis@localhost) by kontti.Helsinki.FI (8.8.8-spammers-bug-off/8.8.0) id HAA00431; Fri, 6 Feb 1998 07:12:06 +0200 (EET) Message-ID: <19980206071206.56766@kontti.Helsinki.FI> Date: Fri, 6 Feb 1998 07:12:06 +0200 From: Holger Lillqvist To: Mutt Users Subject: Re: Save hook question References: <19980205170338.60275@eng.sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980205170338.60275@eng.sun.com> Quoting Andrew R. Large (alarge@Eng.Sun.COM): > Here is an example ... suppose I set up the following hooks: > > fcc-save-hook bob +bob > fcc-save-hook bill +bill > > If I get a message from 'bill' that is addressed to both 'bob' and myself, > and I [s]ave the message, I get '+bob' as the default for save folder! > > I'm running 0.90.1i, but I don't think that is an issue, since I've seen the > same behavior for as long as I've seen hooks (which is why I haven't claimed > that this as a bug). I asked this same question a few weeks ago, but got no response. Can't believe this is the intended behavior. Though it has been there fore some time it is nonetheless an irritating bug. Save-hook shouldn't check the cc-line of a message. Holger From ellement@sdd.hp.com Thu Feb 5 22:21:53 1998 Return-Path: ellement@sdd.hp.com Received: from hpsdlo.sdd.hp.com (hpsdlo.sdd.hp.com [15.255.160.64]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id WAA24210 for ; Thu, 5 Feb 1998 22:21:40 -0800 (PST) Received: from hpsdlss0.sdd.hp.com (hpsdlss0.sdd.hp.com [15.26.104.52]) by hpsdlo.sdd.hp.com (8.8.6/8.8.5tis+epg) with ESMTP id WAA09773 for ; Thu, 5 Feb 1998 22:21:27 -0800 (PST) Received: (from ellement@localhost) by hpsdlss0.sdd.hp.com (8.7.6/8.7.3 TIS 5.0/sdd epg) id WAA14945; Thu, 5 Feb 1998 22:21:27 -0800 (PST) Message-ID: <19980205222127.01210@sdd.hp.com> Date: Thu, 5 Feb 1998 22:21:27 -0800 From: David Ellement To: Mutt Users Subject: Re: Save hook question Mail-Followup-To: Mutt Users References: <19980205170338.60275@eng.sun.com> <19980206071206.56766@kontti.Helsinki.FI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980206071206.56766@kontti.Helsinki.FI>; from Holger Lillqvist on Fri, Feb 06, 1998 at 07:12:06AM +0200 On 980206, at 07:12:06, Holger Lillqvist wrote: > Quoting Andrew R. Large (alarge@Eng.Sun.COM): > > Here is an example ... suppose I set up the following hooks: > > > > fcc-save-hook bob +bob > > fcc-save-hook bill +bill > > > > If I get a message from 'bill' that is addressed to both 'bob' and myself, > > and I [s]ave the message, I get '+bob' as the default for save folder! > > > > I'm running 0.90.1i, but I don't think that is an issue, since I've seen the > > same behavior for as long as I've seen hooks (which is why I haven't claimed > > that this as a bug). > > I asked this same question a few weeks ago, but got no response. > Can't believe this is the intended behavior. Though it has been there > fore some time it is nonetheless an irritating bug. Save-hook > shouldn't check the cc-line of a message. The save-hook behavior has been corrected for 0.89: all the hooks are matched against the from addresses first, before comparing the to/cc lists. (The old, broken, behavior compared each hook against the from, then to/cc address, which caused irritating mis-matches). It appears that some additional work is being done on the hooks in the development releases (such as 0.90.x). In all fairness, those who choose to use development versions really should respect the requests of the developers and keep discussions of those releases on the developers list. The time they spend answering our questions about "not yet ready for release" versions is time they aren't working on improving mutt! -- David Ellement From cpfreg@mail.ece.fjtc.edu.tw Fri Feb 6 00:00:08 1998 Return-Path: cpfreg@mail.ece.fjtc.edu.tw Received: from Ymir.Claremont.Edu (Ymir.Claremont.Edu [134.173.254.23]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA04938 for ; Fri, 6 Feb 1998 00:00:01 -0800 (PST) Received: from mail.ece.fjtc.edu.tw by Ymir.Claremont.Edu (PMDF V4.3-12 #18017) id <01IT5PVFAG808XEOH1@Ymir.Claremont.Edu>; Tue, 03 Feb 1998 22:00:30 -0800 (PST) Received: from localhost (cpfreg@localhost) by mail.ece.fjtc.edu.tw (8.8.8/8.8.7) with SMTP id NAA18893 for ; Wed, 4 Feb 1998 13:58:35 +0800 (CST) Date: Wed, 04 Feb 1998 13:58:35 +0800 (CST) From: CP Fong Subject: [Q] mutt and smtp To: mutt-users@cs.hmc.edu Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT Does anyone know how to setup smtp-server in mutt? I would like to use other remote smtp-server as my mail server instead of the local one. When the email has been sent, all the header information are related to the remote smtp-server. The email software PINE has this kind of configure you can setup. I am wondering mutt has it? -cpfreg@mail.ece.fjtc.edu.tw From thies@argh.org Fri Feb 6 01:01:44 1998 Return-Path: thies@argh.org Received: from rs1.hrz.tu-darmstadt.de (rs1.hrz.tu-darmstadt.de [130.83.22.60]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id BAA09720 for ; Fri, 6 Feb 1998 01:01:39 -0800 (PST) Received: from argh.org (root@ppp34.stud.tu-darmstadt.de [130.83.177.34]) by rs1.hrz.tu-darmstadt.de (8.6.12/8.6.12.1ms) with ESMTP id JAA52153 for ; Fri, 6 Feb 1998 09:57:02 +0100 Received: (from thies@localhost) by argh.org (8.8.3/8.8.3) id IAA23534; Fri, 6 Feb 1998 08:51:21 +0100 Message-ID: <19980206085117.01923@argh.org> Date: Fri, 6 Feb 1998 08:51:17 +0100 From: Michael Thies To: mutt-users@cs.hmc.edu Subject: Re: [0.89.1i] problems with configuring mutt Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980205233002.54667@argh.org> <19980205214341.49262@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980205214341.49262@cs.swarthmore.edu>; from Daniel Eisenbud on Thu, Feb 05, 1998 at 09:43:41PM -0500 Organization: Verein zur Foerderung der Datenkommunikation von Christen (VFDC) X-URL: http://wimbaer.home.pages.de/ X-Address: Pallaswiesenstrasse 42, D-64293 Darmstadt X-Phone: +49 6151 177642 Return-Receipt-To: thies@hrz1.tu-darmstadt.de X-Confirm-Reading-To: thies@hrz1.tu-darmstadt.de Daniel Eisenbud hat ueber Re: [0.89.1i] problems with configuring mutt geschrieben: > On Thu, Feb 05, 1998 at 11:30:02PM +0100, Michael Thies wrote: > > b) I wanted to try the color quoted1,...,quotedN-feature > > > > and with following in my .muttrc > > > > color quoted1 brightyellow black > > color quoted2 brightred black > > color quoted3 brightcyan black > > > > I get no colors. > > Have you managed to get colors elsewhere in mutt? If not, it's almost Yes, if I put color quoted brightyellow black in my .muttrc, then I will get all quotes in brightyellow! > certainly a terminal or termcap/terminfo problem. If you get colors > elsewhere, but not in quotedN, that's more worrisome. And the .sig's and the headers are colored! .-( The I tried to set quote_regexp to only "^> " or something like that, but also no colors! .-( And I think, the quotedx-feature ist a good feature! Have a nice day -- \o/ Michael Thies From vikasa@att.com Fri Feb 6 03:44:56 1998 Return-Path: vikasa@att.com Received: from Ymir.Claremont.Edu (Ymir.Claremont.Edu [134.173.254.23]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id DAA22538 for ; Fri, 6 Feb 1998 03:44:55 -0800 (PST) Received: from att.com (cagw1.att.com) by Ymir.Claremont.Edu (PMDF V4.3-12 #18017) id <01IT81DGYPWW8XEF6Y@Ymir.Claremont.Edu>; Thu, 05 Feb 1998 13:51:09 -0800 (PST) Received: by cagw1.att.com; Thu Feb 5 11:50 EST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by caig1.att.att.com (AT&T/GW-1.0) with ESMTP id OAA27330 for ; Wed, 4 Feb 1998 14:11:03 -0500 (EST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id OAA04735; Wed, 4 Feb 1998 14:19:31 -0500 (EST) Date: Wed, 04 Feb 1998 14:19:31 -0500 From: Vikas Agnihotri Subject: [0.89 MIME] Content-type/encoding bug? To: Mutt users mailing list Message-id: <19980204141931.03566@att.com> MIME-version: 1.0 X-Mailer: Mutt 0.89 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Mail-Followup-To: Mutt users mailing list Attached 2 files from the compose menu. Windows-land BMP (bitmap files). The compose menu shows the first one attached rightly as application/octet-stream with base64 encoding. The second one is attached as 'text/plain with q-p encoding' ! I did 'detach', attach again, no effect. Thought the 2 attachments might be causing a problem. So I aborted this mail and started a new mail and attached just the 2nd file and it still attached it as text/plain! Right now, I also tried to attach the BMP file to _this_ mail and it still gets text/plain. Another thing: I postponed the message with the 2 attachments (app/octet and text/plain) and when I recalled it, the main message body which is usually a filename like /tmp/mutt-machine-1234 is now /tmp/muttaa234. Why did the format of the file-name change? I noticed because my Vim autocommands didnt match the new name! Whats going on here? Thanks, Vikas From mmead@goof.com Fri Feb 6 04:52:25 1998 Return-Path: mmead@goof.com Received: from goof.com (goof.com [128.173.247.211]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id EAA27252 for ; Fri, 6 Feb 1998 04:52:24 -0800 (PST) Received: (qmail 16890 invoked by uid 10000); 6 Feb 1998 12:52:21 -0000 Message-ID: <19980206075221.00996@goof.com> Date: Fri, 6 Feb 1998 07:52:21 -0500 From: "matthew c. mead" To: mutt-users@cs.hmc.edu Subject: .89 - "S"earch gone? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i I just upgraded to .89 from .84, and I noticed a few things different (clearly). One of them is that the "S"earch entire message option is no longer available. I found this to be fairly useful! Is there some other way to get this functionality that I'm not able to find in the online manual and faq, or do I need to look into re-integrating it for my local copy of mutt? Thanks for any info! -matt PS - please CC me on responses as I'm not currently subscribed. -- Matthew C. Mead mmead@goof.com http://www.goof.com/~mmead/ From wtopa@ix.netcom.com Fri Feb 6 09:56:38 1998 Return-Path: wtopa@ix.netcom.com Received: from dfw-ix12.ix.netcom.com (dfw-ix12.ix.netcom.com [206.214.98.12]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id JAA02755 for ; Fri, 6 Feb 1998 09:56:34 -0800 (PST) From: wtopa@ix.netcom.com Received: (from smap@localhost) by dfw-ix12.ix.netcom.com (8.8.4/8.8.4) id LAA28450 for ; Fri, 6 Feb 1998 11:55:55 -0600 (CST) Received: from bin-ny3-04.ix.netcom.com(207.93.48.68) by dfw-ix12.ix.netcom.com via smap (V1.3) id rma028274; Fri Feb 6 11:52:46 1998 Received: (qmail 441 invoked by uid 501); 6 Feb 1998 17:39:15 -0000 Message-ID: <19980206123915.08452@ix.netcom.com> Date: Fri, 6 Feb 1998 12:39:15 -0500 To: Michael Thies Cc: mutt-users@cs.hmc.edu Subject: Re: [0.89.1i] problems with configuring mutt Mail-Followup-To: Michael Thies , mutt-users@cs.hmc.edu References: <19980205233002.54667@argh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <19980205233002.54667@argh.org>; from Michael Thies on Thu, Feb 05, 1998 at 11:30:02PM +0100 Michael Your post prompted me to try the color quoted stuff. instead of quoted1,quoted2 use quoted, quoted1, etc. Works here now! Thank you for asking!!! wayne Subject: [0.89.1i] problems with configuring mutt Date: Thu, Feb 05, 1998 at 11:30:02PM +0100 In reply to:Michael Thies Quoting Michael Thies(thies@rbg.informatik.tu-darmstadt.de): > > Hi all, > > Sorry, if this questions had been asked about, but I didn't got the > mailinglist the last time! .-( > > I have two questions concerning .muttrc-0.89.1i: > > a) I always had a > send-hook \.edu$ "set attribution='%n wrote about \"%s\":'" > and now (with mutt-0.89.1i) a get problems with it, on replies I get > > Someone wrote about %s: > > as attribution. > If cancel the \", I get > > Somenone wrote about theoldsubject: > > But I want to have the double-quotes! > > b) I wanted to try the color quoted1,...,quotedN-feature > > and with following in my .muttrc > > color quoted1 brightyellow black > color quoted2 brightred black > color quoted3 brightcyan black > > I get no colors. > > Who can help me on one or both questions? > > My mutt -v: > > System info: Linux 2.0.25 [using ncurses 1.9.9g] > > Compile time definitions: > DOMAIN="argh.org" > +HIDDEN_HOST -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL > -USE_FLOCK > +USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR -BUFFY_SIZE > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/spool/mail" > SHAREDIR="/usr/local/lib" > ISPELL="/usr/bin/ispell" > _PGPPATH="/usr/local/bin/pgp" > > > -- > \o/ > Michael Thies > > > > . From peter@oneway.weimar.thur.de Fri Feb 6 10:00:04 1998 Return-Path: peter@oneway.weimar.thur.de Received: from annwfn.erfurt.thur.de (annwfn.erfurt.thur.de [194.122.210.3]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA03177 for ; Fri, 6 Feb 1998 10:00:00 -0800 (PST) Received: from eastside.UUCP (uucp@localhost) by annwfn.erfurt.thur.de (8.8.8/8.8.8) with BSMTP id SAA06311 for mutt-announce@cs.hmc.edu; Fri, 6 Feb 1998 18:59:46 +0100 Received: from oneway.erfurt.thur.de (uucp@localhost) by eastside.erfurt.thur.de (8.8.8/8.8.8) with bsmtp id RAA19554 for mutt-announce@cs.hmc.edu; Fri, 6 Feb 1998 17:31:27 +0100 Received: (from peter@localhost) by oneway.weimar.thur.de (8.8.8/8.8.8) id RAA01052; Fri, 6 Feb 1998 17:14:22 +0100 Message-ID: <19980206171420.26035@oneway.weimar.thur.de> Date: Fri, 6 Feb 1998 17:14:20 +0100 From: Peter Koellner To: mutt-announce@cs.hmc.edu Subject: unsubscribe Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 unsubscribe mutt-announce peter@oneway.erfurt.thur.de From peter@oneway.weimar.thur.de Fri Feb 6 10:00:07 1998 Return-Path: peter@oneway.weimar.thur.de Received: from annwfn.erfurt.thur.de (annwfn.erfurt.thur.de [194.122.210.3]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA03178 for ; Fri, 6 Feb 1998 10:00:00 -0800 (PST) Received: from eastside.UUCP (uucp@localhost) by annwfn.erfurt.thur.de (8.8.8/8.8.8) with BSMTP id SAA06312 for mutt-announce@cs.hmc.edu; Fri, 6 Feb 1998 18:59:46 +0100 Received: from oneway.erfurt.thur.de (uucp@localhost) by eastside.erfurt.thur.de (8.8.8/8.8.8) with bsmtp id RAA19556 for mutt-announce@cs.hmc.edu; Fri, 6 Feb 1998 17:31:27 +0100 Received: (from peter@localhost) by oneway.weimar.thur.de (8.8.8/8.8.8) id RAA01064; Fri, 6 Feb 1998 17:15:33 +0100 Message-ID: <19980206171531.10199@oneway.weimar.thur.de> Date: Fri, 6 Feb 1998 17:15:31 +0100 From: Peter Koellner To: mutt-announce@cs.hmc.edu Subject: subscribe Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 subscribe mutt-announce peter@oneway.weimar.thur.de From vikasa@att.com Fri Feb 6 10:01:29 1998 Return-Path: vikasa@att.com Received: from muddcs.cs.hmc.edu (muddcs [134.173.42.2]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA03862 for ; Fri, 6 Feb 1998 10:01:27 -0800 (PST) Received: from att.com (kcgw2.att.com [192.128.133.152]) by muddcs.cs.hmc.edu (8.8.5/8.8.5) with SMTP id JAA08790 for ; Fri, 6 Feb 1998 09:19:57 -0800 (PST) Received: by kcgw2.att.com; Fri Feb 6 10:57 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id LAA26128 for ; Fri, 6 Feb 1998 11:02:37 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id MAA11448; Fri, 6 Feb 1998 12:12:46 -0500 (EST) Message-ID: <19980206121246.25613@att.com> Date: Fri, 6 Feb 1998 12:12:46 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> <19980205105948.21420@shell9.ba.best.com> <19980205150145.31309@att.com> <19980205180744.39097@rsn.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1 In-Reply-To: <19980205180744.39097@rsn.hp.com>; from David DeSimone on Thu, Feb 05, 1998 at 06:07:44PM -0600 On Thu, Feb 05, 1998 at 06:07:44PM -0600, David DeSimone wrote: > Vikas Agnihotri wrote: > > Just glanced at the code (mutt_get_content_info() ) and it has a blurb > > about concluding octet-stream ONLY if %lobin >= 10. This might be the > > problem. What if my file does indeed contain just a handful of lobin > > characters? > Then a quoted-printable encoding will probably be more efficient than > base64. Does the file transfer successfully through the mail, or > doesn't it? Did you try it out? It goes thru fine. I mailed it to myself. Saved the attachment as a different filename and was able to open it in M$-land. I was just a little psyched by the fact that 2 files which are of *exactly* the same kind got attached by Mutt as 2 different MIME types! Guess I shouldnt be too bothered with what content-type Mutt decides to use, eh since it _really_ chews the file byte by byte before it arrives at a conclusion. One more quick question: Suppose I have a .mime.types entry: image/x-MS-bitmap: bmp This will take precedence and Mutt will attach my abcd.bmp file as image/x-MS-bitmap How will it encode it in this case? base64 or qp? Cheers, Vikas From reptile@pooh.cs.net.pl Fri Feb 6 10:03:27 1998 Return-Path: reptile@pooh.cs.net.pl Received: from muddcs.cs.hmc.edu (muddcs [134.173.42.2]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA04599 for ; Fri, 6 Feb 1998 10:03:23 -0800 (PST) Received: from pooh.cs.net.pl (qmailr@pooh.cs.net.pl [195.117.250.7]) by muddcs.cs.hmc.edu (8.8.5/8.8.5) with SMTP id GAA07784 for ; Fri, 6 Feb 1998 06:22:12 -0800 (PST) Received: (qmail 20657 invoked by uid 501); 6 Feb 1998 14:21:28 -0000 Message-ID: <19980206152125.57162@pdi.net> Date: Fri, 6 Feb 1998 15:21:25 +0100 From: "Robert Richard George 'reptile' Wal" To: mutt-users@cs.hmc.edu Subject: Re: [Q] mutt and smtp Mail-Followup-To: mutt-users@cs.hmc.edu References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from CP Fong on Wed, Feb 04, 1998 at 01:58:35PM +0800 Organization: Me? Organized? Get real :) X-URL: http://pooh.cs.net.pl (Eternally under construction) X-IRC-Nick: Gadzinka@iRCnET.iRC.nETWORK (Gadzinka -- tiny little reptile) X-Phone: +48(0)42 593453 X-PGP-Fingerprint: 37E1D55F 29793C0C B8D39D01 61FC50CE X-PGP-Key: finger reptile@gryzmak.lodz.pdi.net X-Motto: Fact that you're paranoid doesn't imply that THEY don't follow you. X-Disclaimer: I don't answer mail or news articles below some arbitrary mark. X-Favourites: women, cats, Amiga, Linux, TeX, vim, music, sci-fi, poetry. X-Mount-Entry: mount -t human /dev/reptile /earth/europe/poland/warsaw On 98.02.04 CP Fong pressed the following keys: > Does anyone know how to setup smtp-server in mutt? > I would like to use other remote smtp-server as my mail server > instead of the local one. When the email has been sent, all > the header information are related to the remote smtp-server. > The email software PINE has this kind of configure you can > setup. I am wondering mutt has it? Because Mutt doesn't perform SMTP negotiation. Instead it relies on sendmail to do this. It has additional advantage, that you can use Mutt with any mail system, even incompatible with rfc822/823, as long as you provide proper rfc822 headers. You can always use any smtpclient which will spool your mail and send it when you connect via PPP or sth. As far as I know Mutt won't support SMTP negotiation. If you need additional info, write to me. Reptile -- mailto:reptile@pdi.net :) Women are more complicated than PC... :( Look into my headers and you'll see who I am. :) From reptile@pooh.cs.net.pl Fri Feb 6 10:03:26 1998 Return-Path: reptile@pooh.cs.net.pl Received: from muddcs.cs.hmc.edu (muddcs [134.173.42.2]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA04602 for ; Fri, 6 Feb 1998 10:03:24 -0800 (PST) Received: from pooh.cs.net.pl (qmailr@pooh.cs.net.pl [195.117.250.7]) by muddcs.cs.hmc.edu (8.8.5/8.8.5) with SMTP id GAA07804 for ; Fri, 6 Feb 1998 06:25:59 -0800 (PST) Received: (qmail 20673 invoked by uid 501); 6 Feb 1998 14:27:51 -0000 Message-ID: <19980206152746.36993@pdi.net> Date: Fri, 6 Feb 1998 15:27:46 +0100 From: "Robert Richard George 'reptile' Wal" To: mutt-users@cs.hmc.edu Subject: Re: visited folder memory? Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980205233219.32623@dyn.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.89i In-Reply-To: <19980205233219.32623@dyn.ml.org>; from Scott McDermott on Thu, Feb 05, 1998 at 11:32:19PM -0500 Organization: Me? Organized? Get real :) X-URL: http://pooh.cs.net.pl (Eternally under construction) X-IRC-Nick: Gadzinka@iRCnET.iRC.nETWORK (Gadzinka -- tiny little reptile) X-Phone: +48(0)42 593453 X-PGP-Fingerprint: 37E1D55F 29793C0C B8D39D01 61FC50CE X-PGP-Key: finger reptile@gryzmak.lodz.pdi.net X-Motto: Fact that you're paranoid doesn't imply that THEY don't follow you. X-Disclaimer: I don't answer mail or news articles below some arbitrary mark. X-Favourites: women, cats, Amiga, Linux, TeX, vim, music, sci-fi, poetry. X-Mount-Entry: mount -t human /dev/reptile /earth/europe/poland/warsaw On 98.02.06 Scott McDermott pressed the following keys: > I use procmail to filter list mail to ~/mail/lists/list{1,2,3,...} ; > this way upon entering mutt I have my spool file with non-list mail, > then I `c' to change to the list dir and read each folder sequentially. > One thing I can't seem to be able to do is have it so that when I `c' > to say List1, then I'm done with List1 and `c' again, it doesn't > automatically advance the target line to the next folder; it has to be > done manually. Is there some way I can get this to auto-advance? You can try to define your incoming mailboxem including mboxes for mailing lists with m=08_a=08_i=08_l=08_b=08_o=08_x=08_ command (manual.txt). From n= ow on, whenever you press `c' Mutt will prompt you with first mailbox from the list which has new mail. You can scroll them with space and this can (sort of) fill your needs. Reptile --=20 mailto:reptile@pdi.net :) Women are more complicated than PC... :( Look into my headers and you'll see who I am. :) From fox@fuzzy.rsn.hp.com Fri Feb 6 10:09:31 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA05299 for ; Fri, 6 Feb 1998 10:09:29 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id KAA16172 for ; Fri, 6 Feb 1998 10:09:29 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id MAA04265; Fri, 6 Feb 1998 12:09:27 -0600 (CST) Message-ID: <19980206120927.26355@rsn.hp.com> Date: Fri, 6 Feb 1998 12:09:27 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: [0.89.1i] problems with configuring mutt Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980205233002.54667@argh.org> <19980205214341.49262@cs.swarthmore.edu> <19980206085117.01923@argh.org> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=2Wo0NMKNjxTN9zDK X-Mailer: Mutt 0.89i In-Reply-To: <19980206085117.01923@argh.org>; from Michael Thies on Fri, Feb 06, 1998 at 08:51:17AM +0100 --2Wo0NMKNjxTN9zDK Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Michael Thies wrote: > > > > color quoted1 brightyellow black > > > color quoted2 brightred black > > > color quoted3 brightcyan black > > >=20 > > > I get no colors. >=20 > The I tried to set quote_regexp to only "^> " or something like that, > but also no colors! .-( The manual has this cryptic phrase in regards to quotedX: Note: In order to use the quotedx patterns in the internal pager, you need to set this to a regular expression that matches e=08ex=08xa= =08ac=08ct=08tl=08ly=08y the quote characters at the beginning of quoted lines. As you can see, the regexp that you gave, "^> ", only matches the *first* level of quoting. The rest would be ignored (unmatched) by the regexp. So, you have to use one like this: set quote_regexp=3D"^(> )+" This will match all the quote characters that can be found at the start of the line. I tried this myself, and saw multi-level quote coloring for the first time. It was...hmm... kinda neat, actually. :) --=20 David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --2Wo0NMKNjxTN9zDK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNtR0Q0lGhIp2tThAQGj4wL9EvDC/F7NJjUrZXLvRPZo9wbC6lJjOsas BjGzIh+oR5tH1LZJzPNIRPU0/cZ8rCJ2XZ4t0NbLHvCfiiUCKJoPW+uVdacDglzS becUwbbiPaPO7502KRGc7oABt53ivu3M =VYmk -----END PGP SIGNATURE----- --2Wo0NMKNjxTN9zDK-- From fox@fuzzy.rsn.hp.com Fri Feb 6 10:16:49 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA05899 for ; Fri, 6 Feb 1998 10:16:48 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id KAA09810 for ; Fri, 6 Feb 1998 10:16:47 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id MAA04286; Fri, 6 Feb 1998 12:16:46 -0600 (CST) Message-ID: <19980206121645.39162@rsn.hp.com> Date: Fri, 6 Feb 1998 12:16:45 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: visited folder memory? Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980205233219.32623@dyn.ml.org> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=6Jbt7q3WqK7+MbKy X-Mailer: Mutt 0.89i In-Reply-To: <19980205233219.32623@dyn.ml.org>; from Scott McDermott on Thu, Feb 05, 1998 at 11:32:19PM -0500 --6Jbt7q3WqK7+MbKy Content-Type: text/plain; charset=us-ascii Scott McDermott wrote: > > One thing I can't seem to be able to do is have it so that when I `c' > to say List1, then I'm done with List1 and `c' again, it doesn't > automatically advance the target line to the next folder; it has to be > done manually. Is there some way I can get this to auto-advance? I had this same problem, and solved it by fixing my folder-monitoring program (xbuffy). It turns out that the external program was causing the access-time of the folders to be advanced every time it scanned, which makes Mutt think you already read that folder. I fixed xbuffy to change the access-time back to what it was before the folder was scanned. This fixed my problem. Another fix would probably be (..erf..) buffy-size. -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --6Jbt7q3WqK7+MbKy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNtTig0lGhIp2tThAQGL3QL/Td48p0GIluo1Tfc5FWla7K888WV4B+d8 EDNTNBgA2JTzQLV8Pc+35voxyaoYC1NiqIKrGccd6C8GMlp2p34MECm/0t5X1lF/ ifyixiAsd7BvmGdn0yMzJeL0RCnoeWCP =hGgf -----END PGP SIGNATURE----- --6Jbt7q3WqK7+MbKy-- From fox@fuzzy.rsn.hp.com Fri Feb 6 10:22:18 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA06477 for ; Fri, 6 Feb 1998 10:22:16 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id KAA12012 for ; Fri, 6 Feb 1998 10:22:08 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id MAA04300; Fri, 6 Feb 1998 12:22:07 -0600 (CST) Message-ID: <19980206122206.46861@rsn.hp.com> Date: Fri, 6 Feb 1998 12:22:06 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: .89 - "S"earch gone? Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980206075221.00996@goof.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=fOwhbdpXa4YIat6+ X-Mailer: Mutt 0.89i In-Reply-To: <19980206075221.00996@goof.com>; from matthew c. mead on Fri, Feb 06, 1998 at 07:52:21AM -0500 --fOwhbdpXa4YIat6+ Content-Type: text/plain; charset=us-ascii matthew c. mead wrote: > > One of them is that the "S"earch entire message option is no longer > available. I found this to be fairly useful! The functionality is still there, it's just that there is no longer a direct function to do it. Instead, the function has been merged into the general search command. If you search on a pattern containing ~b, it means to perform a search of the message body. If you want the "S" key back, you can make a macro like I did: macro index S "/~b \"\"\Cb" The macro starts a search, enters the ~b for you, then inserts a pair of quotes and puts your cursor between them, ready to type your search phrase. -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --fOwhbdpXa4YIat6+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNtUyw0lGhIp2tThAQHD/QMAufuK8Dq5+Ge3hhMX1+TJPydMuXumXexq JWBXjHEHa3t6gFptBLsZOcudh9rKUm94ySfwhSdZ2ibYGT/WBuSUSgh7tlglS8AT MwT+4flwmTSTBykKVRKesZ0a8GemicNR =jGlr -----END PGP SIGNATURE----- --fOwhbdpXa4YIat6+-- From fox@fuzzy.rsn.hp.com Fri Feb 6 10:25:43 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA06997 for ; Fri, 6 Feb 1998 10:25:42 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id KAA13859 for ; Fri, 6 Feb 1998 10:25:41 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id MAA04315; Fri, 6 Feb 1998 12:25:40 -0600 (CST) Message-ID: <19980206122540.14761@rsn.hp.com> Date: Fri, 6 Feb 1998 12:25:40 -0600 From: David DeSimone To: Mutt Heads Subject: PGP-signing complaint Mail-Followup-To: Mutt Heads Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="cpfzWZg/htYpY3vC" X-Mailer: Mutt 0.89i --cpfzWZg/htYpY3vC Content-Type: text/plain; charset=us-ascii Since Mutt makes it so easy to use PGP, I've taken to PGP-signing all of my messages that I send out. However, there is one thing that's been annoying me about this. Whenever I sign a message, Mutt always does some sort of check, maybe it's checking my passphrase for correctness, I'm not sure. But it always prints a dump of my key, then asks me to press a key to continue, before it signs and then sends the message. Now, if I enter my passphrase incorrectly, the key display fails, so I know to re-enter it. So, it makes sense to me that the display be there the first time I enter the passphrase. But, Mutt always does the check every time thereafter, even when it's been proven that the passphrase is correct. This leads to an extra keystroke when signing my mail. Okay, so it's a very small complaint. Mutt is that kind of mail program. :) -- David DeSimone "Each day I wake up torn between a desire to improve the world, and a desire to enjoy the world. This makes Richardson RC, SSG planning the day difficult." -- Teilhard de Chardin --cpfzWZg/htYpY3vC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNtVoA0lGhIp2tThAQGO4AL9Fc8ZhDJJQzU9Xe+FuNVTTD8AHBsI3PwP I4XXpLAosIYjiOBFQX/2mhwpoqnrdpGYP3aDHg3vO4Zb5AhGQSup1JAahx1mOzpr 1kw7PXamnXAoOitIJq0Uxzr8wKuUrcZ2 =QRL/ -----END PGP SIGNATURE----- --cpfzWZg/htYpY3vC-- From sallawa@csci.uark.edu Fri Feb 6 10:34:43 1998 Return-Path: sallawa@csci.uark.edu Received: from csci.uark.edu (sallawa@csci.uark.edu [130.184.201.177]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA08077 for ; Fri, 6 Feb 1998 10:34:40 -0800 (PST) Received: (from sallawa@localhost) by csci.uark.edu (8.8.5/8.7.3) id MAA20991; Fri, 6 Feb 1998 12:34:34 -0600 (CST) Message-ID: <19980206123434.16726@csci.uark.edu> Date: Fri, 6 Feb 1998 12:34:34 -0600 From: "Sadiq B. Al-Lawatia" To: mutt-users@cs.hmc.edu Subject: delete function for browser Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 Hi all mutt users, I am a new user to mutt and I would like to know if there is a function for a browser that deletes a mailbox or a file? I have gone through 2 different manuals and can't seem to find one! :/ Thanx in advance --Sadiq ******************************** * Sadiq B. Al-Lawatia * * Computer Science * * sallawa@csci.uark.edu * *http://csci.uark.edu/~sallawa * ******************************** From cgg@netmaine.com Fri Feb 6 10:39:54 1998 Return-Path: cgg@netmaine.com Received: from netmaine.com (cgg@service.netmaine.com [199.191.0.2]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA08592 for ; Fri, 6 Feb 1998 10:39:49 -0800 (PST) Received: (from cgg@localhost) by netmaine.com (8.8.5/1.0.0) id NAA14338; Fri, 6 Feb 1998 13:39:42 -0500 (EST) Message-ID: <19980206133941.42877@netmaine.com> Date: Fri, 6 Feb 1998 13:39:41 -0500 From: Chock Griebel To: mutt-users@cs.hmc.edu Subject: subscribe Mail-Followup-To: mutt-users@cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 Organization: NMI/IES (http://www.nmi.net) subscribe From fox@fuzzy.rsn.hp.com Fri Feb 6 10:45:06 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA09282 for ; Fri, 6 Feb 1998 10:45:02 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id KAA22654 for ; Fri, 6 Feb 1998 10:45:01 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id MAA04359; Fri, 6 Feb 1998 12:45:00 -0600 (CST) Message-ID: <19980206124459.14318@rsn.hp.com> Date: Fri, 6 Feb 1998 12:44:59 -0600 From: David DeSimone To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> <19980205105948.21420@shell9.ba.best.com> <19980205150145.31309@att.com> <19980205180744.39097@rsn.hp.com> <19980206121246.25613@att.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="PEIAKu/WMn1b1Hv9" X-Mailer: Mutt 0.89i In-Reply-To: <19980206121246.25613@att.com>; from Vikas Agnihotri on Fri, Feb 06, 1998 at 12:12:46PM -0500 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Vikas Agnihotri wrote: > > Guess I shouldnt be too bothered with what content-type Mutt decides to > use, eh since it _really_ chews the file byte by byte before it arrives at > a conclusion. Mutt needs to analyze the file to determine the most efficient encoding. It does this for all attachments, whether you type it in by hand, or attach it as a file. > One more quick question: Suppose I have a .mime.types entry: > image/x-MS-bitmap: bmp > This will take precedence and Mutt will attach my abcd.bmp file as > image/x-MS-bitmap > > How will it encode it in this case? base64 or qp? Encoding is completely independent of type. Mutt will not assume that certain types need to be encoded in any particular way. If you have a GIF file which is lucky enough to not contain *any* non-printable characters (highly unlikely!), then Mutt will set the encoding to "7bit". This is not a bug, and it will work just fine, although I myself would give it a second or third glance if I saw it. ;) It is simply the usual case that binary files happen to get encoded as base64. This simply turns out to be the most efficient encoding, most of the time. Sometimes, however, quoted-printable turns out to be more efficient. If you think about it, Q-P encodes most bytes as single bytes, whereas base64 encodes bytes with 33% overhead. For a file with very few non-printable characters, Q-P encoding will actually come out smaller. -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNtaJA0lGhIp2tThAQES4wL9Ghr0Uy4J3m9fkS2GI2QICIut/e4J7erV fXHRYjSJ0juJz4+Ur7J1GFQntUq0wXZY/DwUoSDx2HUSK/SqxmHIiwzDAIJW6LVt 3EY+gfkiR11OpneMbG3KOeX/LxSnoRdv =jnAT -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9-- From dalibor@immd3.informatik.uni-erlangen.de Fri Feb 6 10:45:31 1998 Return-Path: dalibor@immd3.informatik.uni-erlangen.de Received: from faui45.informatik.uni-erlangen.de (root@faui45.informatik.uni-erlangen.de [131.188.30.45]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA09556 for ; Fri, 6 Feb 1998 10:45:28 -0800 (PST) Received: from immd3.informatik.uni-erlangen.de (faui33.informatik.uni-erlangen.de [131.188.33.2]) by faui45.informatik.uni-erlangen.de (8.8.8/8.1.16-FAU) with ESMTP id TAA14672 for ; Fri, 6 Feb 1998 19:45:20 +0100 (MET) Received: (from dalibor@localhost) by immd3.informatik.uni-erlangen.de (8.8.5/8.8.5/evision: 1.9 $) id SAA24447; Fri, 6 Feb 1998 18:45:19 GMT Message-ID: <19980206194519.63167@faui33.informatik.uni-erlangen.de> Date: Fri, 6 Feb 1998 19:45:19 +0100 From: Stefan Dalibor To: mutt-users@cs.hmc.edu Subject: Forwarding of attachments with Mutt 0.89.1i Reply-To: Stefan.Dalibor@informatik.uni-erlangen.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Hello, the manual for Mutt 0.89.1i says: ... From the attachment menu, you can save, print, pipe, and view attachments. You can apply these operations to a group of attachments at once, by tagging the attachments and by using the ``tag-prefix'' operator. You can also reply to the current message from this menu, and only the current attachment (or the attachments tagged) will be quoted in your reply. ... However, if I want to forward a MIME attachment of type application/ postscript or application/compressed-postscript (i.e. a non-text attachment), an empty attachment is appended to the outgoing mail. The same works fine with text-only attachments. I tag the attachments in the Attachments-menu (using `tag-entry') and call then `tag-prefix', followed by `forward-message'. Where am I wrong? Or is this a bug? Please send me a CC of your replies as I'm only on the announcement list. Bye, Stefan Mutt 0.89.1i, Copyright (C) 1996-8 Michael R. Elkins Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System info: SunOS 5.5.1 Compile time definitions: -DOMAIN -HIDDEN_HOST -HOMESPOOL -USE_SETGID +USE_DOTLOCK -USE_FCNTL -USE_FLOCK -USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR -BUFFY_SIZE SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/local/lib/mutt" ISPELL="/local/bin/ispell" _PGPPATH="/local/bin/pgp" From blong@shell9.ba.best.com Fri Feb 6 10:59:48 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA10899 for ; Fri, 6 Feb 1998 10:59:47 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id KAA19718; Fri, 6 Feb 1998 10:58:55 -0800 (PST) Message-ID: <19980206105855.22815@shell9.ba.best.com> Date: Fri, 6 Feb 1998 10:58:55 -0800 From: Brandon Long To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Reply-To: blong@fiction.net Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> <19980205105948.21420@shell9.ba.best.com> <19980205150145.31309@att.com> <19980205180744.39097@rsn.hp.com> <19980206121246.25613@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980206121246.25613@att.com>; from Vikas Agnihotri on Fri, Feb 06, 1998 at 12:12:46PM -0500 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/06/98 Vikas Agnihotri uttered the following other thing: > On Thu, Feb 05, 1998 at 06:07:44PM -0600, David DeSimone wrote: > > Vikas Agnihotri wrote: > > > > Just glanced at the code (mutt_get_content_info() ) and it has a blurb > > > about concluding octet-stream ONLY if %lobin >= 10. This might be the > > > problem. What if my file does indeed contain just a handful of lobin > > > characters? > > > Then a quoted-printable encoding will probably be more efficient than > > base64. Does the file transfer successfully through the mail, or > > doesn't it? Did you try it out? > > It goes thru fine. I mailed it to myself. Saved the attachment as a > different filename and was able to open it in M$-land. > > I was just a little psyched by the fact that 2 files which are of *exactly* > the same kind got attached by Mutt as 2 different MIME types! The files are not exactly the same, that's the point. They merely have the same extension, but mutt doesn't know the extension, so it has nothing more to go on than the content, which is exactly what it does. > Guess I shouldnt be too bothered with what content-type Mutt decides to > use, eh since it _really_ chews the file byte by byte before it arrives at > a conclusion. > > One more quick question: Suppose I have a .mime.types entry: > image/x-MS-bitmap: bmp > This will take precedence and Mutt will attach my abcd.bmp file as > image/x-MS-bitmap > > How will it encode it in this case? base64 or qp? Mutt doesn't care about the mime type for the encoding, it tries for the lowest cost vs required, ie if the file is all 7bit, it'll be encoded as 7bit, if its few 8bits, it'll do qp, and if its a lot of 8bit, it'll do base64. Brandon -- Brandon Long "I know only that what is moral is what you feel good after MD6 Crash Test Dummy and what is is immoral is what you feel bad after." Intel Corporation -- Ernest Hemingway, Death in the Afternoon I'm too low on the totem pole to speak for Intel. http://www.fiction.net/blong/ From blong@shell9.ba.best.com Fri Feb 6 11:03:49 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA11483 for ; Fri, 6 Feb 1998 11:03:48 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id LAA20812; Fri, 6 Feb 1998 11:03:09 -0800 (PST) Message-ID: <19980206110308.31165@shell9.ba.best.com> Date: Fri, 6 Feb 1998 11:03:08 -0800 From: Brandon Long To: "matthew c. mead" , mutt-users@cs.hmc.edu Subject: Re: .89 - "S"earch gone? Reply-To: blong@fiction.net Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980206075221.00996@goof.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980206075221.00996@goof.com>; from matthew c. mead on Fri, Feb 06, 1998 at 07:52:21AM -0500 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/06/98 matthew c. mead uttered the following other thing: > I just upgraded to .89 from .84, and I noticed a few things > different (clearly). One of them is that the "S"earch entire > message option is no longer available. I found this to be fairly > useful! Is there some other way to get this functionality that > I'm not able to find in the online manual and faq, or do I need > to look into re-integrating it for my local copy of mutt? Thanks > for any info! Try /~b Try the search section of the manual. Brandon -- Brandon Long "The only thing nude playing cards are good for Fiction Networks is playing solitaire." -- Harry Anderson, PI 1/7/98 blong@fiction.net http://www.fiction.net/blong/ From sec@matrix.42.org Fri Feb 6 11:26:24 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA14092 for ; Fri, 6 Feb 1998 11:26:18 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id UAA05713 (sender ); Fri, 6 Feb 1998 20:26:14 +0100 (CET) Message-ID: <19980206202613.18011@matrix.42.org> Date: Fri, 6 Feb 1998 20:26:13 +0100 From: Stefan `Sec` Zehl To: Mutt Heads Subject: Re: PGP-signing complaint Mail-Followup-To: Mutt Heads References: <19980206122540.14761@rsn.hp.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="XdP64Ggrk/fb43R8" X-Mailer: Mutt 0.90.1i In-Reply-To: <19980206122540.14761@rsn.hp.com>; from David DeSimone on Fri, Feb 06, 1998 at 12:25:40PM -0600 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ --XdP64Ggrk/fb43R8 Content-Type: text/plain; charset=us-ascii On Fri, Feb 06, 1998 at 12:25:40PM -0600, David DeSimone wrote: > Whenever I sign a message, Mutt always does some sort of check, maybe > it's checking my passphrase for correctness, I'm not sure. But it > always prints a dump of my key, then asks me to press a key to continue, > before it signs and then sends the message. Hm, it doesn't do this for me. It just sends the message. What version of pgp are you using ? Maybe pgp can't determine which is your key? Did you try setting "MYNAME" in config.txt ? CU, Sec -- You haven't seen _multitasking_ until you have seen Doom and Quake run side by side. --XdP64Ggrk/fb43R8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3i iQEVAwUBNNtjzZ5z6wpNWO5RAQFgWwgAlaZqSmaHhdVfB7ZXoHnOCUbqV3KXo5f1 R7Evu+89hpn8O2FnjxZKlgHhnDzuz0vSe+ZYKrFPu8rtOpj2bdXWt45jWFLd/voW XTY3URcUb76pRrJxNnaTJM+rsGxkdb+qjLSu16Flq2/GvMUhtku/Jvn9hpPlK95w riTkIYUHF/gPvHjdDult/I0YTXhUbkJTYKGroW+m1CrlwQfMYshlFskyrST6PU59 XX1/Bd5sSF0B/GocdfK/YstNdzdIsmn8Ga+CjPQJRv3H7ECJfFkItvybG6jkrozb PuYrSoF0Z8B65W3afix7N6mjouS47zxbFjbs4i2eJrR8ELN8jW7DBQ== =RsEw -----END PGP SIGNATURE----- --XdP64Ggrk/fb43R8-- From vikasa@att.com Fri Feb 6 11:28:02 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw1.att.com [192.128.133.151]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id LAA14276 for ; Fri, 6 Feb 1998 11:27:45 -0800 (PST) Received: by kcgw1.att.com; Fri Feb 6 13:21 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id NAA12083; Fri, 6 Feb 1998 13:12:41 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id OAA11949; Fri, 6 Feb 1998 14:23:09 -0500 (EST) Message-ID: <19980206142309.50780@att.com> Date: Fri, 6 Feb 1998 14:23:09 -0500 From: Vikas Agnihotri To: "Sadiq B. Al-Lawatia" , mutt-users@cs.hmc.edu Subject: Re: delete function for browser Mail-Followup-To: "Sadiq B. Al-Lawatia" , mutt-users@cs.hmc.edu References: <19980206123434.16726@csci.uark.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1 In-Reply-To: <19980206123434.16726@csci.uark.edu>; from Sadiq B. Al-Lawatia on Fri, Feb 06, 1998 at 12:34:34PM -0600 On Fri, Feb 06, 1998 at 12:34:34PM -0600, Sadiq B. Al-Lawatia wrote: > Hi all mutt users, > I am a new user to mutt and I would like to know if there is a > function for a browser that deletes a mailbox or a file? > I have gone through 2 different manuals and can't seem to find one! :/ If you delete all the messages in the folder (with D all ) and if you have "unset save_empty", Mutt will remove the folder. Vikas From rnapier@cisco.com Fri Feb 6 12:09:56 1998 Return-Path: rnapier@cisco.com Received: from claret.cisco.com (claret.cisco.com [171.69.160.39]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA18254 for ; Fri, 6 Feb 1998 12:09:55 -0800 (PST) Received: (rnapier@localhost) by claret.cisco.com (8.8.4-Cisco.1/8.6.5) id PAA27818; Fri, 6 Feb 1998 15:09:26 -0500 (EST) Message-ID: <19980206150925.27962@cisco.com> Date: Fri, 6 Feb 1998 15:09:25 -0500 From: Robert Napier To: Mutt Users List Subject: Re: Screen redraw problems Mail-Followup-To: Mutt Users List References: <19980205151333.27746@cisco.com> <19980205202038.26189@nmrc.ucc.ie> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="cCNbCCxyk/YU74BR" X-Mailer: Mutt 0.89.1i In-Reply-To: <19980205202038.26189@nmrc.ucc.ie>; from Lars Hecking on Thu, Feb 05, 1998 at 08:20:38PM +0000 --cCNbCCxyk/YU74BR Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Thu, Feb 05, 1998 at 08:20:38PM +0000, Lars Hecking wrote: > Robert Napier writes: > > I often have trouble with my screen redraw in the pager, particularly > > the status line. It seems that characters that are not changed, are > > not properly redrawn, leaving black spaces. A ^L fixes this (so it's > > not a major deal), but I'd like to find out if others have the same > > problem. The problem does not always happen, but is fairly > > reproducible (by hitting "^L", "j", then "k"). > >=20 > > Occasionally I also have redraw problems in the body area of the > > pager. It sometimes (rarely) leaves characters from the last message > > on the screen when redrawing the screen. ^L fixes this problem too. > >=20 > > Here's the stats on my install: > >=20 > > Mutt 0.89i, Copyright (C) 1996-8 Michael R. Elkins > > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > > Mutt is free software, and you are welcome to redistribute it > > under certain conditions; type `mutt -vv' for details. > >=20 > > System info: SunOS 5.5.1 [using slang 9938] >=20 > I had similar problems with slang under Solaris, and have switched to > ncurses since. No such problems anymore, neither with dtterm nor xterm. Did you have to do anything special to get ncurses to compile under Solaris? I keep getting errors in cursesw.o (undefined reference to 'streambuf::streambuf(int)'). I did a basic ./configure --prefix=3D$HOME. Is there any functional differences in mutt between Slang and ncurses? Rob --=20 Rob Napier | 7025 Kit Creek Road | Check out Triangle Ascension: rnapier@cisco.com | PO Box 14987 | http://www.serve.com/napier/mage 919/472-3941 | RTP, NC 27709 | +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D+ | Imagine what my body would sound like / Slamming against those rocks = | | When it lands / Will my eyes / Be closed or open? -- Bjork "Hyper Ballad"= | +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D+ --cCNbCCxyk/YU74BR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNtt8++HqpsUOMiZAQEgBwL+KpvEwcJodrI8NwSjee6o4uI8mPmfT/fz 8hoFow4za5PAk1IflSvXHQvL0cxsEa6dAmRP9xeZsdBuP/iMnS/FHzzlDcN+qFX1 jTGwUqeCF3nKLIZW1pIrwFnvo3jp5kTm =4Qc+ -----END PGP SIGNATURE----- --cCNbCCxyk/YU74BR-- From hazmat@unixshell.com Fri Feb 6 12:45:11 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (dns1.nws.net [199.234.203.130]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA21949 for ; Fri, 6 Feb 1998 12:45:06 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id MAA07316; Fri, 6 Feb 1998 12:43:42 -0500 (EST) Message-ID: <19980206124342.61877@unixshell.com> Date: Fri, 6 Feb 1998 12:43:42 -0500 From: Ken W To: mutt Subject: compile errors under BSDI? Mail-Followup-To: mutt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X I am trying to compile mutt 0.89.1i under BSDI, and during make, I keep on getting from many different lines: warning: ANSI C does not support `long long' and it eventually craps out. an input would be greatly appreciated. Here is the output if it helps, and I am again not doing this as root: rm -f keymap_defs.h ./gen_defs ./OPS > keymap_defs.h gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c addrbook.c In file included from /usr/include/sys/types.h:48, from /usr/include/stdio.h:47, from mutt.h:21, from addrbook.c:19: /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' In file included from addrbook.c:23: /usr/include/stdlib.h:173: warning: ANSI C does not support `long long' /usr/include/stdlib.h:174: warning: ANSI C does not support `long long' gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c alias.c In file included from /usr/include/sys/types.h:48, from /usr/include/stdio.h:47, from mutt.h:21, from alias.c:19: /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c attach.c In file included from /usr/include/sys/types.h:48, from /usr/include/stdio.h:47, from mutt.h:21, from attach.c:19: /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' In file included from attach.c:30: /usr/include/stdlib.h:173: warning: ANSI C does not support `long long' /usr/include/stdlib.h:174: warning: ANSI C does not support `long long' gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c bind.c In file included from /usr/include/sys/types.h:48, from /usr/include/stdio.h:47, from mutt.h:21, from bind.c:19: /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c browser.c In file included from /usr/include/sys/types.h:48, from /usr/include/stdio.h:47, from mutt.h:21, from browser.c:19: /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' In file included from browser.c:26: /usr/include/stdlib.h:173: warning: ANSI C does not support `long long' /usr/include/stdlib.h:174: warning: ANSI C does not support `long long' browser.c: In function `mutt_select_file': browser.c:590: `KEY_ENTER' undeclared (first use this function) browser.c:590: (Each undeclared identifier is reported only once browser.c:590: for each function it appears in.) browser.c:593: warning: implicit declaration of function `beep' *** Error code 1 Stop. From vikasa@att.com Fri Feb 6 13:06:39 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw1.att.com [192.128.133.151]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id NAA25127 for ; Fri, 6 Feb 1998 13:06:29 -0800 (PST) Received: by kcgw1.att.com; Fri Feb 6 15:01 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id OAA21119 for ; Fri, 6 Feb 1998 14:53:12 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id QAA12319; Fri, 6 Feb 1998 16:03:16 -0500 (EST) Message-ID: <19980206160316.55201@att.com> Date: Fri, 6 Feb 1998 16:03:16 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: Matching real name with ~f/~t Mail-Followup-To: Mutt users mailing list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1 My aplogies if this has been asked before, but.. The ~f and ~t patterns seem to match the email address only and not the real name portion of the header. i.e. ~f abcd does not match From: Mr. abcd I dont know why, but I always thought that it matched the full email address including the real-name part and I could have sworn that in the past, I _was_ able to match on the real name part using ~f Thanks for any help/pointers, Vikas From vikasa@att.com Fri Feb 6 13:13:44 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw2.att.com [192.128.133.152]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id NAA27828 for ; Fri, 6 Feb 1998 13:13:32 -0800 (PST) Received: by kcgw2.att.com; Fri Feb 6 14:55 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id PAA27524 for ; Fri, 6 Feb 1998 15:01:02 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id QAA12367; Fri, 6 Feb 1998 16:11:00 -0500 (EST) Message-ID: <19980206161100.03119@att.com> Date: Fri, 6 Feb 1998 16:11:00 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> <19980205105948.21420@shell9.ba.best.com> <19980205150145.31309@att.com> <19980205180744.39097@rsn.hp.com> <19980206121246.25613@att.com> <19980206105855.22815@shell9.ba.best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.90.1 In-Reply-To: <19980206105855.22815@shell9.ba.best.com>; from Brandon Long on Fri, Feb 06, 1998 at 10:58:55AM -0800 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by kcig2.att.att.com id PAA27524 On Fri, Feb 06, 1998 at 10:58:55AM -0800, Brandon Long wrote:=20 > > I was just a little psyched by the fact that 2 files which are of *ex= actly* > > the same kind got attached by Mutt as 2 different MIME types! > The files are not exactly the same, that's the point. They merely have > the same extension, but mutt doesn't know the extension, so it has > nothing more to go on than the content, which is exactly what it does. Yup. Got it. > > How will it encode it in this case? base64 or qp? > Mutt doesn't care about the mime type for the encoding, it tries for th= e > lowest cost vs required, ie if the file is all 7bit, it'll be encoded a= s > 7bit, if its few 8bits, it'll do qp, and if its a lot of 8bit, it'll do > base64. Ran a small experiment. Started to compose a message using Vim as my editor. Put in all plain 7bi= t text initially. Exited Vim, Compose Menu shows text/plain, 7bit. Went back. Added the =BD (octal 275) character using Vim's digraph abilit= ies. :wq and the Compose menu changed the encoding to 8bit. So far, so good. Went back into editor from Compose menu and added tons of more =BD characters, now the entire file contains only the 8-bit character =BD. But the encoding stays at 8bit. It does not change to base64. Eh? Thanks, Vikas From dubois@primate.wisc.edu Fri Feb 6 13:26:54 1998 Return-Path: dubois@primate.wisc.edu Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA29464 for ; Fri, 6 Feb 1998 13:26:42 -0800 (PST) Received: (from dubois@localhost) by night.primate.wisc.edu (8.8.7/8.8.7) id PAA10783; Fri, 6 Feb 1998 15:26:42 -0600 (CST) Message-ID: <19980206152642.48481@night.primate.wisc.edu> Date: Fri, 6 Feb 1998 15:26:42 -0600 From: Paul DuBois To: mutt-users@cs.hmc.edu Subject: Current equivalent of --disable-domain? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 I'm upgrading from mutt 0.78 to 0.89.1 and I notice that there there's no longer a --disable-domain option for configure (to suppress qualification of local addresses). Is there an equivalent now? It looks like there's a muttrc command "unset use_domain" that does much the same thing -- to achieve the effect I want, do I just put this in the system-wide Muttrc file? -- Paul DuBois dubois@primate.wisc.edu Home page: http://www.primate.wisc.edu/people/dubois Software: http://www.primate.wisc.edu/software From maccy@c6.hadiko.de Fri Feb 6 13:35:32 1998 Return-Path: maccy@c6.hadiko.de Received: from nz15.rz.uni-karlsruhe.de (nz15.rz.uni-karlsruhe.de [129.13.64.15]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id NAA00716 for ; Fri, 6 Feb 1998 13:35:28 -0800 (PST) Received: from hadic006.hadiko.uni-karlsruhe.de (c6.hadiko.de) [129.13.244.111] (maccy) by nz15.rz.uni-karlsruhe.de with esmtp (Exim 1.80 #4) id 0y0vPj-0000Dn-00; Fri, 6 Feb 1998 22:34:23 +0100 Received: (from maccy@localhost) by c6.hadiko.de (8.8.5/8.8.5) id WAA00461; Fri, 6 Feb 1998 22:34:18 +0100 Message-ID: <19980206223418.55326@c6.hadiko.de> Date: Fri, 6 Feb 1998 22:34:18 +0100 From: Bjoern Jacke To: Stefan `Sec` Zehl , MUTT Users Subject: Re: PGP-signing complaint References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980206202613.18011@matrix.42.org>; from Stefan `Sec` Zehl on Fri, Feb 06, 1998 at 08:26:13PM +0100 On 06.02. at 20:26 +0100 Stefan `Sec` Zehl sent off: > On Fri, Feb 06, 1998 at 12:25:40PM -0600, David DeSimone wrote: > > always prints a dump of my key, then asks me to press a key to continue, > > before it signs and then sends the message. > > Hm, it doesn't do this for me. It just sends the message. > What version of pgp are you using ? It was fine for me, too with pgp2.6.x - but with pgp5 I've got the same problem. bj -- e-mail: bjoern.jacke@stud.uni-karlsruhe.de URL(mit PGP-Key): http://b.jacke.home.pages.de From eisenbud@allspice.cs.swarthmore.edu Fri Feb 6 13:51:44 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id NAA02601 for ; Fri, 6 Feb 1998 13:51:41 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id QAA24229; Fri, 6 Feb 1998 16:51:41 -0500 (EST) Message-ID: <19980206165141.05879@cs.swarthmore.edu> Date: Fri, 6 Feb 1998 16:51:41 -0500 From: Daniel Eisenbud To: Mutt users mailing list Subject: Re: Matching real name with ~f/~t Mail-Followup-To: Mutt users mailing list References: <19980206160316.55201@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980206160316.55201@att.com>; from Vikas Agnihotri on Fri, Feb 06, 1998 at 04:03:16PM -0500 On Fri, Feb 06, 1998 at 04:03:16PM -0500, Vikas Agnihotri wrote: > My aplogies if this has been asked before, but.. > > The ~f and ~t patterns seem to match the email address only and not the > real name portion of the header. > > i.e. > ~f abcd > does not match > From: Mr. abcd > > I dont know why, but I always thought that it matched the full email > address including the real-name part and I could have sworn that in the > past, I _was_ able to match on the real name part using ~f > > Thanks for any help/pointers, Yeah, I always used to use this, too, and I'd like it back, too. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From lhecking@nmrc.ucc.ie Fri Feb 6 14:06:21 1998 Return-Path: lhecking@nmrc.ucc.ie Received: from bastion.nmrc.ucc.ie (nmrc.ucc.ie [143.239.64.1]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id OAA04917 for ; Fri, 6 Feb 1998 14:06:18 -0800 (PST) Received: from odessa.nmrc.ucc.ie (odessa.nmrc.ucc.ie [143.239.64.65]) by bastion.nmrc.ucc.ie (8.8.8/8.8.8) with ESMTP id WAA21082 for ; Fri, 6 Feb 1998 22:08:46 GMT Message-ID: <19980206220558.45003@nmrc.ucc.ie> Date: Fri, 6 Feb 1998 22:05:58 +0000 From: Lars Hecking To: Mutt Users List Subject: Re: Screen redraw problems Mail-Followup-To: Mutt Users List References: <19980205151333.27746@cisco.com> <19980205202038.26189@nmrc.ucc.ie> <19980206150925.27962@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980206150925.27962@cisco.com>; from Robert Napier on Fri, Feb 06, 1998 at 03:09:25PM -0500 > > > System info: SunOS 5.5.1 [using slang 9938] > > > > I had similar problems with slang under Solaris, and have switched to > > ncurses since. No such problems anymore, neither with dtterm nor xterm. > > Did you have to do anything special to get ncurses to compile under > Solaris? I keep getting errors in cursesw.o (undefined reference to > 'streambuf::streambuf(int)'). Nope, no problems at all. I'm always using the latest snapshot, currently 4.1-980131 or so. Which compiler are you using? I have egcs-1.0.1 here, and IIRC, even gcc-2.8.0 + libstdc++-2.8.0 works fine. Always make sure you have a matching version of compiler + C++ lib + C++ includes. From fox@fuzzy.rsn.hp.com Fri Feb 6 14:21:03 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id OAA06474 for ; Fri, 6 Feb 1998 14:21:01 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id OAA14870 for ; Fri, 6 Feb 1998 14:20:48 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id QAA05909; Fri, 6 Feb 1998 16:20:47 -0600 (CST) Message-ID: <19980206162046.44948@rsn.hp.com> Date: Fri, 6 Feb 1998 16:20:46 -0600 From: David DeSimone To: Mutt Heads Subject: Re: PGP-signing complaint Mail-Followup-To: Mutt Heads References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=1yeeQ81UyVL57Vl7 X-Mailer: Mutt 0.89i In-Reply-To: <19980206202613.18011@matrix.42.org>; from Stefan `Sec` Zehl on Fri, Feb 06, 1998 at 08:26:13PM +0100 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Stefan `Sec` Zehl wrote: > > > Whenever I sign a message, Mutt always does some sort of check, maybe > > it's checking my passphrase for correctness, I'm not sure. But it > > always prints a dump of my key, then asks me to press a key to continue, > > before it signs and then sends the message. > > Hm, it doesn't do this for me. It just sends the message. > What version of pgp are you using ? I'm using PGP 2.6.2. > Maybe pgp can't determine which is your key? Did you try setting > "MYNAME" in config.txt ? Well, PGP is certainly signing my messages with the right key. My signatures have been verifying for a while now. I haven't heard of this MYNAME directive before. Maybe I should explain further. When I sign this message, I will get a dump that looks like this after I give the "send" command: Key for user ID: David DeSimone 768-bit key, Key ID 29DAD4E1, created 1996/02/12 Also known as: David DeSimone Also known as: David DeSimone Also known as: Fuzzy Fox Also known as: David DeSimone Also known as: David DeSimone Also known as: David DeSimone Also known as: David DeSimone Also known as: David DeSimone Also known as: David DeSimone Also known as: David DeSimone Press any key to continue... So, it seems to me that the right key is being selected. Mutt actually does an endwin() in order to print this info, so I just assumed it was something Mutt needed to do. You say that you don't see this when you sign a message? -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNuMuA0lGhIp2tThAQE3HQL/X8zcZf2gSZEuIloTRJl97jemlrP3MmUB +MELsVqiVfDEUyuNPZiDi/nkVp01XYq0F7+NSTKnsofxhzpMoicRwG2GGVjREHZV a0HsWtWv0sw+VqOODOGgmwTrKCUm/4Ey =jPgx -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7-- From fox@fuzzy.rsn.hp.com Fri Feb 6 14:34:28 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id OAA09158 for ; Fri, 6 Feb 1998 14:34:25 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id OAA26204 for ; Fri, 6 Feb 1998 14:34:24 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id QAA05943; Fri, 6 Feb 1998 16:34:23 -0600 (CST) Message-ID: <19980206163422.20003@rsn.hp.com> Date: Fri, 6 Feb 1998 16:34:22 -0600 From: David DeSimone To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> <19980205105948.21420@shell9.ba.best.com> <19980205150145.31309@att.com> <19980205180744.39097@rsn.hp.com> <19980206121246.25613@att.com> <19980206105855.22815@shell9.ba.best.com> <19980206161100.03119@att.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="S8CxjVDS/+yyDmUD" X-Mailer: Mutt 0.89i In-Reply-To: <19980206161100.03119@att.com>; from Vikas Agnihotri on Fri, Feb 06, 1998 at 04:11:00PM -0500 --S8CxjVDS/+yyDmUD Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Vikas Agnihotri wrote: > > Went back into editor from Compose menu and added tons of more =BD > characters, now the entire file contains only the 8-bit character =BD. >=20 > But the encoding stays at 8bit. It does not change to base64. Well, an 8bit encoding is the most efficient encoding, right? I guess you have $allow_8bit set. --=20 David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --S8CxjVDS/+yyDmUD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNuP6w0lGhIp2tThAQEJEAL/dG1kUBmvpBCI8vPK8tafIfA1dU7IqqUv 7waZKNeEZ+0PVs2DEmvFbhV2q/EEW2QSQAZ51DlfMbw5Bxgry62gZa0McYcScOJM VOiu63LnjbLxWjG9bexzi8uSpzrlj1lq =ZCNa -----END PGP SIGNATURE----- --S8CxjVDS/+yyDmUD-- From olsenc@ichips.intel.com Fri Feb 6 15:02:52 1998 Return-Path: olsenc@ichips.intel.com Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA12594 for ; Fri, 6 Feb 1998 15:02:49 -0800 (PST) Received: from ichips-jf.jf.intel.com (ichips-jf.jf.intel.com [134.134.50.200]) by ganymede.or.intel.com (8.8.6/8.8.5) with ESMTP id PAA03830 for ; Fri, 6 Feb 1998 15:06:55 -0800 (PST) Received: from dtthp169 (olsenc@dtthp169.jf.intel.com [134.134.102.22]) by ichips-jf.jf.intel.com (8.8.8/8.8.7) with ESMTP id PAA08422 for ; Fri, 6 Feb 1998 15:02:47 -0800 (PST) Received: by dtthp169 (8.8.8/WW2.1) id PAA10266; Fri, 6 Feb 1998 15:02:46 -0800 (PST) Message-ID: <19980206150246.15086@dtthp169.jf.intel.com> Date: Fri, 6 Feb 1998 15:02:46 -0800 From: Clint Olsen To: mutt-users@cs.hmc.edu Subject: Re: Current equivalent of --disable-domain? Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980206152642.48481@night.primate.wisc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980206152642.48481@night.primate.wisc.edu>; from Paul DuBois on Fri, Feb 06, 1998 at 03:26:42PM -0600 Organization: Intel Corporation, Hillsboro, OR X-Disclaimer: Mutt Bites! On Feb 06, Paul DuBois wrote: > Is there an equivalent now? It looks like there's a muttrc command > "unset use_domain" that does much the same thing -- to achieve the effect > I want, do I just put this in the system-wide Muttrc file? You got it. -Clint From olsenc@ichips.intel.com Fri Feb 6 15:17:10 1998 Return-Path: olsenc@ichips.intel.com Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA14222 for ; Fri, 6 Feb 1998 15:17:06 -0800 (PST) Received: from ichips-jf.jf.intel.com (ichips-jf.jf.intel.com [134.134.50.200]) by ganymede.or.intel.com (8.8.6/8.8.5) with ESMTP id PAA07163 for ; Fri, 6 Feb 1998 15:21:13 -0800 (PST) Received: from dtthp169 (olsenc@dtthp169.jf.intel.com [134.134.102.22]) by ichips-jf.jf.intel.com (8.8.8/8.8.7) with ESMTP id PAA10170 for ; Fri, 6 Feb 1998 15:17:05 -0800 (PST) Received: by dtthp169 (8.8.8/WW2.1) id PAA12713; Fri, 6 Feb 1998 15:17:04 -0800 (PST) Message-ID: <19980206151704.36785@dtthp169.jf.intel.com> Date: Fri, 6 Feb 1998 15:17:04 -0800 From: Clint Olsen To: Mutt users mailing list Subject: Re: Matching real name with ~f/~t Mail-Followup-To: Mutt users mailing list References: <19980206160316.55201@att.com> <19980206165141.05879@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980206165141.05879@cs.swarthmore.edu>; from Daniel Eisenbud on Fri, Feb 06, 1998 at 04:51:41PM -0500 Organization: Intel Corporation, Hillsboro, OR X-Disclaimer: Mutt Bites! On Feb 06, Daniel Eisenbud wrote: > > Yeah, I always used to use this, too, and I'd like it back, too. Huh? When did this happen? When I limit ~f daniel, all I see is your email. I'm using an internal development version, though. -Clint From elb@chaos.com Fri Feb 6 15:19:25 1998 Return-Path: elb@chaos.com Received: from chaos.com (elb@ppp167.day-oh.siscom.net [206.244.171.167]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA14667 for ; Fri, 6 Feb 1998 15:19:17 -0800 (PST) Received: (from elb@localhost) by chaos.com (8.7.6/8.6.12) id SAA00823; Fri, 6 Feb 1998 18:24:16 -0500 Message-ID: <19980206182416.02483@trc-inc.com> Date: Fri, 6 Feb 1998 18:24:16 -0500 From: Ethan Blanton To: mutt-users@cs.hmc.edu Subject: quote_regexp Mail-Followup-To: mutt-users@cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Operating-System: Linux I am having some difficulties setting my quote_regexp variable to catch all the quoting styles I am seeing... I am not very familiar with regular expressions, so I would like some assistance with this. The problem quote I am getting is from a fellow on one of the mailing lists I recieve, who quotes his lines with [!]. Example: [!]This is a quote My current quote_regexp is set to "^([>|}] )+". I have tried various ways of adding the [!], but I cannot seem to get the regexp parser to treat the [ and ] characters as normal chars and not listing delimiters. (I tried \[ and \], to no avail.) BTW, when I add a : to the list of characters to search ("^([>|:}] )+") all kinds of funky things happen! (Every line after a ':' stays color-hilighted, until the next quote char comes up, etc.) I am using mutt-0.89.1i on Linux w/ slang. Thanks for any helpful hints you might have, Ethan From olsenc@ichips.intel.com Fri Feb 6 15:43:02 1998 Return-Path: olsenc@ichips.intel.com Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA18948 for ; Fri, 6 Feb 1998 15:42:58 -0800 (PST) Received: from ichips-jf.jf.intel.com (ichips-jf.jf.intel.com [134.134.50.200]) by ganymede.or.intel.com (8.8.6/8.8.5) with ESMTP id PAA11952 for ; Fri, 6 Feb 1998 15:47:04 -0800 (PST) Received: from dtthp193 (dtthp193.jf.intel.com [134.134.102.26]) by ichips-jf.jf.intel.com (8.8.8/8.8.7) with ESMTP id PAA12833 for ; Fri, 6 Feb 1998 15:42:57 -0800 (PST) Received: by dtthp193 (8.8.8/WW2.1) id PAA16711; Fri, 6 Feb 1998 15:42:57 -0800 (PST) Message-ID: <19980206154256.45333@dtthp193.jf.intel.com> Date: Fri, 6 Feb 1998 15:42:56 -0800 From: Clint Olsen To: Mutt users mailing list Subject: Re: Sorting by date-sent vs. date-received Mail-Followup-To: Mutt users mailing list References: <19980205184637.59890@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90i In-Reply-To: <19980205184637.59890@att.com>; from Vikas Agnihotri on Thu, Feb 05, 1998 at 06:46:37PM -0500 Organization: Intel Corporation, Hillsboro, OR X-Disclaimer: Mutt Bites! On Feb 05, Vikas Agnihotri wrote: > What is the difference between sorting by date-sent and date-received? Comments below. The main difference is that things are sorted by when *you* receive it (date-received). In case of mail outtages or network problems, this keeps you from getting brand new messages appearing at #30 because some guy sent it from a down ISP 3 days ago. > For date-sent, Mutt looks at the Date: headers of the mail. Yes. > For date-received, does Mutt parse my From_ line to actually determine when > the mail was received? Actually, for those MH/Maildir users, I submitted a patch based on Byrial's comments about parsing Received: headers. So, it should extract the date from the latest Received: header if it exists AND it wasn't already set by the From_ separator (as in mbox). Failing that, we can fall back on the date header. We have to go with the From_ separator first in case the message was Fcc'd to the folder (wasn't actually sent). As a result, it would have *no* received headers. > When sorting according to either of these 2 methods, does Mutt consider > the different time zones? i.e. does Mutt normalize all date/time's to a > certain timezone and _then_ sort? That I don't know. -Clint From michael@tis.com Fri Feb 6 15:43:07 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA18964 for ; Fri, 6 Feb 1998 15:43:04 -0800 (PST) Received: by relay.la.tis.com; id PAA27372; Fri, 6 Feb 1998 15:54:20 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma027329; Fri, 6 Feb 98 15:54:04 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id PAA27658; Fri, 6 Feb 1998 15:39:38 -0800 (PST) Message-ID: <19980206153938.44183@la.tis.com> Date: Fri, 6 Feb 1998 15:39:38 -0800 From: Michael Elkins To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980204141931.03566@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980204141931.03566@att.com>; from Vikas Agnihotri on Wed, Feb 04, 1998 at 02:19:31PM -0500 On Wed, Feb 04, 1998 at 02:19:31PM -0500, Vikas Agnihotri wrote: > Attached 2 files from the compose menu. Windows-land BMP (bitmap files). > The compose menu shows the first one attached rightly as > application/octet-stream with base64 encoding. > > The second one is attached as 'text/plain with q-p encoding' ! > > I did 'detach', attach again, no effect. > > Thought the 2 attachments might be causing a problem. So I aborted this > mail and started a new mail and attached just the 2nd file and it still > attached it as text/plain! > > Right now, I also tried to attach the BMP file to _this_ mail and it still > gets text/plain. In the absense of a ~/.mime.types file which maps filename extensions to content-type, Mutt looks at the content of the file you are attaching and attempts to determine what type it is (either text or binary). Naturally, since this is a heuristic it can be wrong sometimes. If you want it to use the correct type, use the ~/.mime.types (see the manual for more details). > Another thing: > > I postponed the message with the 2 attachments (app/octet and text/plain) > and when I recalled it, the main message body which is usually a filename > like /tmp/mutt-machine-1234 is now /tmp/muttaa234. Why did the format of > the file-name change? I noticed because my Vim autocommands didnt match the > new name! > > Whats going on here? I will have to look at this more. me From fabrice@math.Princeton.EDU Fri Feb 6 15:47:49 1998 Return-Path: fabrice@math.Princeton.EDU Received: from and.Princeton.EDU (root@and.Princeton.EDU [128.112.16.144]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA19394 for ; Fri, 6 Feb 1998 15:47:45 -0800 (PST) Received: from eurydice.Princeton.EDU (eurydice.Princeton.EDU [128.112.16.153]) by and.Princeton.EDU (8.8.8/8.8.3) with ESMTP id SAA15621 for ; Fri, 6 Feb 1998 18:47:41 -0500 (EST) Received: (fabrice@localhost) by eurydice.Princeton.EDU (950413.SGI.8.6.12/8.6.12) id SAA19939; Fri, 6 Feb 1998 18:47:40 -0500 Message-ID: <19980206184740.44535@math.princeton.edu> Date: Fri, 6 Feb 1998 18:47:40 -0500 From: Fabrice Planchon To: Mutt Heads Subject: Re: PGP-signing complaint Mail-Followup-To: Mutt Heads References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> <19980206162046.44948@rsn.hp.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=mP3DRpeJDSE+ciuQ X-Mailer: Mutt 0.89.1i In-Reply-To: <19980206162046.44948@rsn.hp.com>; from David DeSimone on Fri, Feb 06, 1998 at 04:20:46PM -0600 Organization: Princeton University X-http: //www.math.princeton.edu/~fabrice/ --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Fri Feb 06 1998 at 04:20:46PM -0600, David DeSimone wrote: >=20 > I haven't heard of this MYNAME directive before. it's a config line in your config.txt (which I guess sits in your .pgp/) > So, it seems to me that the right key is being selected. Mutt actually > does an endwin() in order to print this info, so I just assumed it was > something Mutt needed to do. You say that you don't see this when you > sign a message? I don't see anything either, with a fairly standard config... F. --=20 Fabrice Planchon (ph) 609/258-6495 Applied Math Program, 210 Fine Hall (fax) 609/258-1735 --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3a iQCVAwUBNNuhHNX42EYNMIltAQE9jwP/SLMY6n/9qMBKsQz50Q8P6WXomoRMxn2l CAcOYcjG4/Po/yIFlD3O5QWcOuZRTiF9qMAO2UuU3BoAfMmvYNy0HvtjeqOm9hBh CmIZ5DDZdRjCjGX6lLO5d96ejHG/wKHQFkPcRriN6X0Rm6I2h9EzXznJWIQrqzgC j66jSQCjU38= =DfwC -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From michael@tis.com Fri Feb 6 15:49:12 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA19476 for ; Fri, 6 Feb 1998 15:49:07 -0800 (PST) Received: by relay.la.tis.com; id QAA27639; Fri, 6 Feb 1998 16:00:20 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma027635; Fri, 6 Feb 98 16:00:16 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id PAA27740; Fri, 6 Feb 1998 15:45:50 -0800 (PST) Message-ID: <19980206154550.33298@la.tis.com> Date: Fri, 6 Feb 1998 15:45:50 -0800 From: Michael Elkins To: Mutt users mailing list Subject: Re: Sorting by date-sent vs. date-received Mail-Followup-To: Mutt users mailing list References: <19980205184637.59890@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980205184637.59890@att.com>; from Vikas Agnihotri on Thu, Feb 05, 1998 at 06:46:37PM -0500 On Thu, Feb 05, 1998 at 06:46:37PM -0500, Vikas Agnihotri wrote: > What is the difference between sorting by date-sent and date-received? > > For date-sent, Mutt looks at the Date: headers of the mail. > > For date-received, does Mutt parse my From_ line to actually determine when > the mail was received? Yes, or it looks for the last Received: line and extracts the date from it. > When sorting according to either of these 2 methods, does Mutt consider the > different time zones? i.e. does Mutt normalize all date/time's to a certain > timezone and _then_ sort? All times are normalized to UTC for comparison, thus accounting for the differences in timezones. me From michael@tis.com Fri Feb 6 15:53:41 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA20006 for ; Fri, 6 Feb 1998 15:53:37 -0800 (PST) Received: by relay.la.tis.com; id QAA27835; Fri, 6 Feb 1998 16:04:50 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma027827; Fri, 6 Feb 98 16:04:45 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id PAA27763; Fri, 6 Feb 1998 15:50:19 -0800 (PST) Message-ID: <19980206155019.48700@la.tis.com> Date: Fri, 6 Feb 1998 15:50:19 -0800 From: Michael Elkins To: "Sadiq B. Al-Lawatia" , mutt-users@cs.hmc.edu Subject: Re: delete function for browser Mail-Followup-To: "Sadiq B. Al-Lawatia" , mutt-users@cs.hmc.edu References: <19980206123434.16726@csci.uark.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980206123434.16726@csci.uark.edu>; from Sadiq B. Al-Lawatia on Fri, Feb 06, 1998 at 12:34:34PM -0600 On Fri, Feb 06, 1998 at 12:34:34PM -0600, Sadiq B. Al-Lawatia wrote: > I am a new user to mutt and I would like to know if there is a > function for a browser that deletes a mailbox or a file? > I have gone through 2 different manuals and can't seem to find one! :/ No there is not. The browser is not intended to be general purpose file manager, just a quick way to find files. me From michael@tis.com Fri Feb 6 15:58:38 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA20554 for ; Fri, 6 Feb 1998 15:58:35 -0800 (PST) Received: by relay.la.tis.com; id QAA28018; Fri, 6 Feb 1998 16:09:50 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma028014; Fri, 6 Feb 98 16:09:44 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id PAA27776; Fri, 6 Feb 1998 15:55:18 -0800 (PST) Message-ID: <19980206155518.03126@la.tis.com> Date: Fri, 6 Feb 1998 15:55:18 -0800 From: Michael Elkins To: Michael Thies , mutt-users@cs.hmc.edu Subject: Re: [0.89.1i] problems with configuring mutt Mail-Followup-To: Michael Thies , mutt-users@cs.hmc.edu References: <19980205233002.54667@argh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980205233002.54667@argh.org>; from Michael Thies on Thu, Feb 05, 1998 at 11:30:02PM +0100 On Thu, Feb 05, 1998 at 11:30:02PM +0100, Michael Thies wrote: > a) I always had a > send-hook \.edu$ "set attribution='%n wrote about \"%s\":'" > and now (with mutt-0.89.1i) a get problems with it, on replies I get > > Someone wrote about %s: > > as attribution. > If cancel the \", I get > > Somenone wrote about theoldsubject: > > But I want to have the double-quotes! This is a known bug, and is on my list of things to fix.. me From michael@tis.com Fri Feb 6 16:00:09 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA21053 for ; Fri, 6 Feb 1998 16:00:05 -0800 (PST) Received: by relay.la.tis.com; id QAA28098; Fri, 6 Feb 1998 16:11:20 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma028086; Fri, 6 Feb 98 16:10:58 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id PAA27787; Fri, 6 Feb 1998 15:56:32 -0800 (PST) Message-ID: <19980206155631.19431@la.tis.com> Date: Fri, 6 Feb 1998 15:56:31 -0800 From: Michael Elkins To: mutt-users@cs.hmc.edu Subject: Re: body-search: how? $simple_search bug? Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980204232019.26226@ens-lyon.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980204232019.26226@ens-lyon.fr>; from Vincent Lefevre on Wed, Feb 04, 1998 at 11:20:19PM +0100 On Wed, Feb 04, 1998 at 11:20:19PM +0100, Vincent Lefevre wrote: > I'd like to know how to replace the old body-search. Do not reply > macro index ... "/~b " > because this does *not* work when you do several searches on the same > pattern, and I want to always use the same key for a body-search. > > I've tried the following: > > bind index \e/ search > macro index / ":set simple_search='~f %s | ~s %s'\r\e/" > macro index \\ ":set simple_search='~b %s'\r\e/" > > but this doesn't work. It seems that when I change $simple_search, > this isn't taken into account if I search for the same pattern. Yeah, right now Mutt checks the non-expanded version of the search string to see if it has changed from the previous search. In your case the non-expanded version is the same, thus the string does not get re-evaulated. I will work on a fix for that. me From fox@fuzzy.rsn.hp.com Fri Feb 6 16:25:55 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA24524 for ; Fri, 6 Feb 1998 16:25:42 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id QAA08391 for ; Fri, 6 Feb 1998 16:25:26 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id SAA06108; Fri, 6 Feb 1998 18:25:25 -0600 (CST) Message-ID: <19980206182524.34820@rsn.hp.com> Date: Fri, 6 Feb 1998 18:25:24 -0600 From: David DeSimone To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980204141931.03566@att.com> <19980206153938.44183@la.tis.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=ZGiS0Q5IWpPtfppv X-Mailer: Mutt 0.89i In-Reply-To: <19980206153938.44183@la.tis.com>; from Michael Elkins on Fri, Feb 06, 1998 at 03:39:38PM -0800 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii I checked this out, and I noticed the same thing as Vikas. If you edit an attachment, Mutt will only choose 8bit, 7bit, or Q-P encoding. It never seems to come to the conclusion that base64 would be an appropriate encoding, even if it really would be (such as a file full of 8bit characters). -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNuprg0lGhIp2tThAQGiWgL/a1k/HHfkrF/fi8kf2AdrWHdgYlLpXkit TCI5NfU3bSgEs2ZXs+KAfG041djgkupBz6guA/YLMndF2kakekHuEEoGtoNv+xPx M1leYkmUt4ny5EU72u5z9wfublzQGcio =SEsv -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From fox@fuzzy.rsn.hp.com Fri Feb 6 16:42:19 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA26496 for ; Fri, 6 Feb 1998 16:42:17 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id QAA14739 for ; Fri, 6 Feb 1998 16:42:16 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id SAA06128; Fri, 6 Feb 1998 18:42:15 -0600 (CST) Message-ID: <19980206184215.12428@rsn.hp.com> Date: Fri, 6 Feb 1998 18:42:15 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: quote_regexp Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980206182416.02483@trc-inc.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=mA2V3Z32TCmWXqIn X-Mailer: Mutt 0.89i In-Reply-To: <19980206182416.02483@trc-inc.com>; from Ethan Blanton on Fri, Feb 06, 1998 at 06:24:16PM -0500 --mA2V3Z32TCmWXqIn Content-Type: text/plain; charset=us-ascii Ethan Blanton wrote: > > I am having some difficulties setting my quote_regexp variable to catch all > the quoting styles I am seeing... The main thing is that the quote_regexp has to match not just a line that has quote characters, but ALL the quote characters that a line could have. For instance, with a line like this: > > > Blah blah > > Whatever > My current quote_regexp is set to "^([>|}] )+". I have tried various > ways of adding the [!], but I cannot seem to get the regexp parser to > treat the [ and ] characters as normal chars and not listing > delimiters. (I tried \[ and \], to no avail.) The problem here is that the regexp is surrounded by double-quotes ("") when you enter it in your .muttrc. So, in order to put a backslash (\) into it, you have to double it (\\). set quote_regexp="^(\\[!\\])|([>|}]) )+" Too many pipes and brackets there, but hopefully you can decipher that and see why it works. :) > BTW, when I add a : to the list of characters to > search ("^([>|:}] )+") all kinds of funky things happen! (Every line after > a ':' stays color-hilighted, until the next quote char comes up, etc.) Umm... haven't seen that one. I found that I didn't like having ":" in my list of quote characters, though. :) -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --mA2V3Z32TCmWXqIn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNut4w0lGhIp2tThAQGbKwL/X4DNErMynQx+jX4R+AP8BAJS4LZ+19B1 bDFZogKICmvQPz3aX7RXU7P0WmgPQrgk3e8O04kuAwLaTTRAh4kZCGhBEXG/Kud1 8vwd63E9G6PEwVoMZ1YGLONw/7sy9Vav =mdM6 -----END PGP SIGNATURE----- --mA2V3Z32TCmWXqIn-- From elb@chaos.com Fri Feb 6 17:24:08 1998 Return-Path: elb@chaos.com Received: from chaos.com (elb@ppp169.day-oh.siscom.net [206.244.171.169]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA01496 for ; Fri, 6 Feb 1998 17:24:03 -0800 (PST) Received: (from elb@localhost) by chaos.com (8.7.6/8.6.12) id UAA01564; Fri, 6 Feb 1998 20:29:05 -0500 Message-ID: <19980206202905.35527@trc-inc.com> Date: Fri, 6 Feb 1998 20:29:05 -0500 From: Ethan Blanton To: mutt-users@cs.hmc.edu Subject: Re: quote_regexp Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980206182416.02483@trc-inc.com> <19980206184215.12428@rsn.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980206184215.12428@rsn.hp.com>; from David DeSimone on Fri, Feb 06, 1998 at 06:42:15PM -0600 X-Operating-System: Linux On Fri, Feb 06, 1998 at 06:42:15PM -0600, David DeSimone wrote: > set quote_regexp="^(\\[!\\])|([>|}]) )+" > > Too many pipes and brackets there, but hopefully you can decipher that > and see why it works. :) Ah, yes! A variation on this is working perfectly... :-) Thanks so much... I farther modified the regexp to recognize named-quotes (i.e. David> or Ethan>), and they are also working, albeit differently than I had expected. I suspect the error is in my regexp... Anyway, it recognizes a line such as: Ethan> This is a quote as a second level quote, when I would want it to be a first-level. (for the purposes of color hilighting) My regexp is currently "^(([^ \n\t]*[>|}] )+|(\\[!\\])+)". I know this is probably hairier than it has to be, but I am not particulary familiar with regular expressions. Thanks again for the help. Ethan From sec@matrix.42.org Fri Feb 6 17:43:20 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA03588 for ; Fri, 6 Feb 1998 17:43:16 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id CAA13848 (sender ); Sat, 7 Feb 1998 02:43:14 +0100 (CET) Message-ID: <19980207024313.61270@matrix.42.org> Date: Sat, 7 Feb 1998 02:43:13 +0100 From: Stefan `Sec` Zehl To: Mutt Heads Subject: Re: PGP-signing complaint Mail-Followup-To: Mutt Heads X-Current-Backlog: 228 messages References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> <19980206162046.44948@rsn.hp.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=mP3DRpeJDSE+ciuQ X-Mailer: Mutt 0.90.1i In-Reply-To: <19980206162046.44948@rsn.hp.com>; from David DeSimone on Fri, Feb 06, 1998 at 04:20:46PM -0600 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Feb 06, 1998 at 04:20:46PM -0600, David DeSimone wrote: > > Maybe pgp can't determine which is your key? Did you try setting > > "MYNAME" in config.txt ?=20 >=20 > Well, PGP is certainly signing my messages with the right key. My > signatures have been verifying for a while now. >=20 > I haven't heard of this MYNAME directive before. It's used to select your own key, in case pgp can't find it out. > So, it seems to me that the right key is being selected. Mutt actually > does an endwin() in order to print this info, so I just assumed it was > something Mutt needed to do. You say that you don't see this when you > sign a message? No, I see no output from pgp at all when sending a message. Your pgp-output makes me think, that your pgp isn't sure about which e-mail it should use for signing. try MYNAME =3D in ~/.pgp/config.txt (if it doesn't exist, create it) CU, Sec --=20 Die k=FCrzesten Computerwitze: 1) M=FC=DFte laufen. --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3i iQEVAwUBNNu8KJ5z6wpNWO5RAQFG2Af+O7yXE+UzvlYf33aapKiDPfCqxGXDyfge OoiFm9xBgt+ZDgican7nTsqHbb+SNudikzdZThvBIB3glo1anlKTXbdASdtn9guv HYTePJYyIFpmlK4IQmjKr3KAQ4KcX2i7UmF+bGJHfeYAk9ybMI90LRA+jXfegLIS +J9ptVLzkBn4P327ikw8M7jdxaICmbtyDZwdcv/v7Ew396LwMiYdEHV+ro2ZteuO PFITG1NjqbDfYbfgPfocA8TO/AZPnpAcfK/fvyoBkYc4ZwgLn/bMEprSNu3Wixki Uaw5U7Z733HG0Wy6IYhBFef/p7zveNfKwIh3nWkPrxOa/EvJjMApmQ== =5PO0 -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From blong@shell9.ba.best.com Fri Feb 6 17:49:56 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA04088 for ; Fri, 6 Feb 1998 17:49:55 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id RAA06004; Fri, 6 Feb 1998 17:49:29 -0800 (PST) Message-ID: <19980206174928.41251@shell9.ba.best.com> Date: Fri, 6 Feb 1998 17:49:28 -0800 From: Brandon Long To: mutt Subject: Re: compile errors under BSDI? Reply-To: blong@fiction.net Mail-Followup-To: mutt References: <19980206124342.61877@unixshell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980206124342.61877@unixshell.com>; from Ken W on Fri, Feb 06, 1998 at 12:43:42PM -0500 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/06/98 Ken W uttered the following other thing: > I am trying to compile mutt 0.89.1i under BSDI, and during make, I > keep on getting from many different lines: > > warning: ANSI C does not support `long long' These warnings are from the -pedantic flag, are in the system headers, and can be safely ignored. > and it eventually craps out. an input would be greatly appreciated. Here is > the output if it helps, and I am again not doing this as root: > > > rm -f keymap_defs.h > ./gen_defs ./OPS > keymap_defs.h > gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c addrbook.c > In file included from /usr/include/sys/types.h:48, > from /usr/include/stdio.h:47, > from mutt.h:21, > from addrbook.c:19: > /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' > In file included from addrbook.c:23: > /usr/include/stdlib.h:173: warning: ANSI C does not support `long long' > /usr/include/stdlib.h:174: warning: ANSI C does not support `long long' > gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c alias.c > In file included from /usr/include/sys/types.h:48, > from /usr/include/stdio.h:47, > from mutt.h:21, > from alias.c:19: > /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' > gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c attach.c > In file included from /usr/include/sys/types.h:48, > from /usr/include/stdio.h:47, > from mutt.h:21, > from attach.c:19: > /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' > In file included from attach.c:30: > /usr/include/stdlib.h:173: warning: ANSI C does not support `long long' > /usr/include/stdlib.h:174: warning: ANSI C does not support `long long' > gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c bind.c > In file included from /usr/include/sys/types.h:48, > from /usr/include/stdio.h:47, > from mutt.h:21, > from bind.c:19: > /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' > gcc -Wall -pedantic -g -O2 -DSHAREDIR=\"/usr/home/shell/hazmat/share\" -I. -c browser.c > In file included from /usr/include/sys/types.h:48, > from /usr/include/stdio.h:47, > from mutt.h:21, > from browser.c:19: > /usr/include/machine/types.h:56: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:57: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:71: warning: ANSI C does not support `long long' > /usr/include/machine/types.h:72: warning: ANSI C does not support `long long' > In file included from browser.c:26: > /usr/include/stdlib.h:173: warning: ANSI C does not support `long long' > /usr/include/stdlib.h:174: warning: ANSI C does not support `long long' > browser.c: In function `mutt_select_file': > browser.c:590: `KEY_ENTER' undeclared (first use this function) > browser.c:590: (Each undeclared identifier is reported only once > browser.c:590: for each function it appears in.) > browser.c:593: warning: implicit declaration of function `beep' > *** Error code 1 This is a more fundamental problem, KEY_ENTER is supposed to be defined by curses, do you have a curses library? If not, you might try compiling either ncurses or slang, and using the --with-curses or --with-slang configure option. Brandon -- Brandon Long "We don't understand the software, and sometimes MD6 Crash Test Dummy we don't understand the hardware, but we can Intel Corporation *see* the blinking lights!" -- Unknown I'm too low on the totem pole to speak for Intel. http://www.fiction.net/blong/ From michael@tis.com Fri Feb 6 18:00:08 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA04986 for ; Fri, 6 Feb 1998 18:00:05 -0800 (PST) Received: by relay.la.tis.com; id SAA01710; Fri, 6 Feb 1998 18:11:20 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma001705; Fri, 6 Feb 98 18:11:16 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id RAA28577; Fri, 6 Feb 1998 17:56:48 -0800 (PST) Message-ID: <19980206175648.62541@la.tis.com> Date: Fri, 6 Feb 1998 17:56:48 -0800 From: Michael Elkins To: "Nathan L. Cutler" , Mutt Users Mailing List Subject: Re: message/partial Mail-Followup-To: "Nathan L. Cutler" , Mutt Users Mailing List References: <19980204105133.26347@baffle.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980204105133.26347@baffle.cz>; from Nathan L. Cutler on Wed, Feb 04, 1998 at 10:51:33AM +0100 On Wed, Feb 04, 1998 at 10:51:33AM +0100, Nathan L. Cutler wrote: > [ Due to the high volume of this list I'm not subscribed; please CC: me on > your reply. ] > > Emacs mailers have a tendency to break longer files up into multiple > messages using the MIME type "message/partial". So, instead of getting one > 233 Kb message from an Emacs user I got three 64 Kb messages and one 57 Kb > message (as far as I can tell). > > Can anybody tell me how I can put Humpty Dumpty back together again? > (Without installing Emacs of course!!!!) This is another thing that is on my todo list... me From michael@tis.com Fri Feb 6 18:03:06 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA05223 for ; Fri, 6 Feb 1998 18:03:04 -0800 (PST) Received: by relay.la.tis.com; id SAA01749; Fri, 6 Feb 1998 18:14:20 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma001745; Fri, 6 Feb 98 18:14:11 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id RAA28589; Fri, 6 Feb 1998 17:59:43 -0800 (PST) Message-ID: <19980206175943.55665@la.tis.com> Date: Fri, 6 Feb 1998 17:59:43 -0800 From: Michael Elkins To: Tim Tsai , Mutt Users List Subject: Re: sendmail voyeur mode Mail-Followup-To: Tim Tsai , Mutt Users List References: <19980131213139.49911@sdd.hp.com> <19980201133719.52099@c6.hadiko.de> <19980201102250.07918@joshua.rivertown.net> <19980202104453.59508@tightrope.demon.co.uk> <19980202071036.42510@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980202071036.42510@futuresouth.com>; from Tim Tsai on Mon, Feb 02, 1998 at 07:10:36AM -0600 On Mon, Feb 02, 1998 at 07:10:36AM -0600, Tim Tsai wrote: > How can I turn on sendmail's voyeur mode from within mutt? I would like > to be able to do this on demand, instead of turning it on automatically. > > With BSD Mail, I just type "Mail -v ...". Currently this is not possible other than creating a macro in the compose menu. Also, I'm not sure how this conflicts with the way Mutt puts sendmail in the background.. me From grog@lemis.com Fri Feb 6 18:18:37 1998 Return-Path: grog@lemis.com Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA06836 for ; Fri, 6 Feb 1998 18:18:31 -0800 (PST) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id MAA10108 for ; Sat, 7 Feb 1998 12:48:10 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id MAA28915; Sat, 7 Feb 1998 12:48:09 +1030 (CST) (envelope-from grog) Message-ID: <19980207124809.27088@freebie.lemis.com> Date: Sat, 7 Feb 1998 12:48:09 +1030 From: Greg Lehey To: Mutt Heads Subject: Re: PGP-signing complaint References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> <19980206162046.44948@rsn.hp.com> <19980207024313.61270@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980207024313.61270@matrix.42.org>; from Stefan `Sec` Zehl on Sat, Feb 07, 1998 at 02:43:13AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 On Sat, 7 February 1998 at 2:43:13 +0100, Stefan `Sec` Zehl wrote: > On Fri, Feb 06, 1998 at 04:20:46PM -0600, David DeSimone wrote: [-- PGP output follows (current time: Sat Feb 7 12:43:49 1998) --] ^GKey matching expected Key ID 4D58EE51 not found in file '/home/grog/.pgp/pubring.pgp'. File '/home/grog/mutt-freeb.$00' has signature, but with no text. Text is assumed to be in file '/home/grog/mutt-freebie-28839-51'. WARNING: Can't find the right public key-- can't check signature integrity. [-- End of PGP output --] [-- The following data is PGP/MIME signed --] It seems to me that if you're going to PGP sign your messages (which I personally think is overkill for this kind of message), you should provide some independent way of verifying the message, such as a web page address. Sure, you've provided one, but I don't find any PGP signature there. How about it? This isn't picking on Stefan, of course--it seems like a good idea for everybody. Greg From fox@fuzzy.rsn.hp.com Fri Feb 6 18:26:22 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA07838 for ; Fri, 6 Feb 1998 18:26:20 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id SAA14798 for ; Fri, 6 Feb 1998 18:26:19 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id UAA06299; Fri, 6 Feb 1998 20:26:18 -0600 (CST) Message-ID: <19980206202618.51243@rsn.hp.com> Date: Fri, 6 Feb 1998 20:26:18 -0600 From: David DeSimone To: mutt-users@cs.hmc.edu Subject: Re: quote_regexp Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980206182416.02483@trc-inc.com> <19980206184215.12428@rsn.hp.com> <19980206202905.35527@trc-inc.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=vkogqOf2sHV7VnPd X-Mailer: Mutt 0.89i In-Reply-To: <19980206202905.35527@trc-inc.com>; from Ethan Blanton on Fri, Feb 06, 1998 at 08:29:05PM -0500 --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Ethan Blanton wrote: > > Anyway, it recognizes a line such as: > Ethan> This is a quote > as a second level quote, when I would want it to be a first-level. > (for the purposes of color hilighting) My regexp is currently > "^(([^ \n\t]*[>|}] )+|(\\[!\\])+)". Ah, now we get to the topic of quote levels. I knew it would come to that. Most people expect that the longer string is the deepest quote level. However, Mutt does not see it that way. Example: > > > Quote 3 > > > Quote 3 > > Quote 2 > > Quote 2 > Quote 1 > Quote 1 Mutt instead sees that the first line has a string "> > > " that matches the regexp, so this is considered the first quote level, and will be colored by the "quoted" color object. The next line matches the same string, so it is colored the same way. Next, the string "> > " matches, but is not identical to the first string, so it is considered the next quoting level, and is colored as "quoted1". The next level is just "> ", and is colored as "quoted2". Just so you know what's going on when you finally get it working. :) -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNvGNA0lGhIp2tThAQE+qwMArWsyP6EgsT6BjifaANEEsyqaaLmdcinR xS70KMiVEhcCxHB7t0A5cIrHm+6bHJPc3h5y3KjxlytgtCbtGjb9SKGE+aYCVfTd WuFA9xBVEfHB2Ufht2kd1oKQPq2SHexg =p7VV -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd-- From fox@fuzzy.rsn.hp.com Fri Feb 6 18:30:59 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA08535 for ; Fri, 6 Feb 1998 18:30:56 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id SAA03672 for ; Fri, 6 Feb 1998 18:30:54 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id UAA06361; Fri, 6 Feb 1998 20:30:53 -0600 (CST) Message-ID: <19980206203053.26950@rsn.hp.com> Date: Fri, 6 Feb 1998 20:30:53 -0600 From: David DeSimone To: Mutt Heads Subject: Re: PGP-signing complaint Mail-Followup-To: Mutt Heads References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> <19980206162046.44948@rsn.hp.com> <19980207024313.61270@matrix.42.org> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="EGEL1/lMxI0MVQ29" X-Mailer: Mutt 0.89i In-Reply-To: <19980207024313.61270@matrix.42.org>; from Stefan `Sec` Zehl on Sat, Feb 07, 1998 at 02:43:13AM +0100 --EGEL1/lMxI0MVQ29 Content-Type: text/plain; charset=us-ascii Stefan `Sec` Zehl wrote: > > Your pgp-output makes me think, that your pgp isn't sure about which > e-mail it should use for signing. try > > MYNAME = > > in ~/.pgp/config.txt I gave this a try, and it didn't change anything. Thanks for the tip, though. The manual says that PGP will use the first secret key it finds, if MyName isn't given. Since I only have one secret key, I can't see any ambiguity. It seems, however, that I am the only Mutt user with PGP 2.6.2. Everyone else seems to have 2.6.3. I'll try upgrading and see how that goes. -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --EGEL1/lMxI0MVQ29 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNNvHWQ0lGhIp2tThAQFcYgL9F5I3gdHVn4pfiY5fZlEibgkwprtHPf+l BRmS3CLFfG79ohIhYmuPWjFtDcZPB0E4NOV7kr+edJQVNAjPXEriIQ4bxlIKvhdl ogkIYoQnA8AWfqAtYf7vvkAjEI+0ifK+ =90f4 -----END PGP SIGNATURE----- --EGEL1/lMxI0MVQ29-- From jra@scfn.thpl.lib.fl.us Fri Feb 6 18:40:48 1998 Return-Path: jra@scfn.thpl.lib.fl.us Received: from scfn.thpl.lib.fl.us (jra@scfn.thpl.lib.fl.us [204.198.80.3]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA09860 for ; Fri, 6 Feb 1998 18:40:42 -0800 (PST) Received: (jra@localhost) by scfn.thpl.lib.fl.us (8.8.5/8.6.5) id VAA24862; Fri, 6 Feb 1998 21:35:35 -0500 (EST) Message-ID: <19980206213535.00459@scfn.thpl.lib.fl.us> Date: Fri, 6 Feb 1998 21:35:35 -0500 From: "Jay R. Ashworth" To: Mutt Users List Subject: Re: sendmail voyeur mode References: <19980131213139.49911@sdd.hp.com> <19980201133719.52099@c6.hadiko.de> <19980201102250.07918@joshua.rivertown.net> <19980202104453.59508@tightrope.demon.co.uk> <19980202071036.42510@futuresouth.com> <19980206175943.55665@la.tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19980206175943.55665@la.tis.com>; from Michael Elkins on Fri, Feb 06, 1998 at 05:59:43PM -0800 Organization: Ashworth & Associates, St Pete FL USA On Fri, Feb 06, 1998 at 05:59:43PM -0800, Michael Elkins wrote: > On Mon, Feb 02, 1998 at 07:10:36AM -0600, Tim Tsai wrote: > > How can I turn on sendmail's voyeur mode from within mutt? I would like > > to be able to do this on demand, instead of turning it on automatically. > > > > With BSD Mail, I just type "Mail -v ...". > > Currently this is not possible other than creating a macro in the compose > menu. Also, I'm not sure how this conflicts with the way Mutt puts sendmail > in the background.. A birdie tells me this is exactly _why_ it needs to be a special case. If you're voyuering it, you don't _want_ it amped off, you want to sleep and wait for it to finish. Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Unsolicited Commercial Emailers Sued The Suncoast Freenet "Two words: Darth Doogie." -- Jason Colby, Tampa Bay, Florida on alt.fan.heinlein +1 813 790 7592 Managing Editor, Top Of The Key sports e-zine ------------ http://www.totk.com From blong@shell9.ba.best.com Fri Feb 6 18:44:57 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA10375 for ; Fri, 6 Feb 1998 18:44:54 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id SAA19786; Fri, 6 Feb 1998 18:44:08 -0800 (PST) Message-ID: <19980206184408.01938@shell9.ba.best.com> Date: Fri, 6 Feb 1998 18:44:08 -0800 From: Brandon Long To: Mutt Users List Subject: Re: sendmail voyeur mode Reply-To: blong@fiction.net Mail-Followup-To: Mutt Users List References: <19980131213139.49911@sdd.hp.com> <19980201133719.52099@c6.hadiko.de> <19980201102250.07918@joshua.rivertown.net> <19980202104453.59508@tightrope.demon.co.uk> <19980202071036.42510@futuresouth.com> <19980206175943.55665@la.tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980206175943.55665@la.tis.com>; from Michael Elkins on Fri, Feb 06, 1998 at 05:59:43PM -0800 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/06/98 Michael Elkins uttered the following other thing: > On Mon, Feb 02, 1998 at 07:10:36AM -0600, Tim Tsai wrote: > > How can I turn on sendmail's voyeur mode from within mutt? I would like > > to be able to do this on demand, instead of turning it on automatically. > > > > With BSD Mail, I just type "Mail -v ...". > > Currently this is not possible other than creating a macro in the compose > menu. Also, I'm not sure how this conflicts with the way Mutt puts sendmail > in the background.. This could be done with my sendmail_wait patch from several versions ago. To recap, it was a boolean var, which if set, would cause mutt to wait for sendmail (and do an endwin() to show messages). Brandon -- Brandon Long "Computers make very fast, very accurate, mistakes." MD6 Crash Test Dummy blong@fiction.net I'm too low on the totem pole to speak for Intel. http://www.fiction.net/blong/ From sec@matrix.42.org Fri Feb 6 18:59:52 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA11893 for ; Fri, 6 Feb 1998 18:59:48 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id DAA18141 (sender ); Sat, 7 Feb 1998 03:58:50 +0100 (CET) Message-ID: <19980207035849.32733@matrix.42.org> Date: Sat, 7 Feb 1998 03:58:49 +0100 From: Stefan `Sec` Zehl To: Greg Lehey , Mutt Heads Subject: Re: PGP-signing complaint Mail-Followup-To: Greg Lehey , Mutt Heads References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> <19980206162046.44948@rsn.hp.com> <19980207024313.61270@matrix.42.org> <19980207124809.27088@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980207124809.27088@freebie.lemis.com>; from Greg Lehey on Sat, Feb 07, 1998 at 12:48:09PM +1030 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Sat, Feb 07, 1998 at 12:48:09PM +1030, Greg Lehey wrote: > WARNING: Can't find the right public key-- can't check signature integrity. > > It seems to me that if you're going to PGP sign your messages (which I > personally think is overkill for this kind of message), I have pgp_replysign set to on, so if someone thinks the subject is 'important enough' to use pgp, i will happily join in. > you should > provide some independent way of verifying the message, such as a web > page address. Sure, you've provided one, but I don't find any PGP > signature there. How about it? Hm, I give in, that my webpage is not a clear list of things, but rather some text with the links embedded, and I've been to lazy to translate it to english. I really should do that now. If you'd searched for "PGP" you would have found it. It's: | E-Mail: | sec@42.org (at Home) (PGP preferred) "PGP" is an link to my key . You're happily welcome to phone me up, if you want to check my pgp fingerprint. Anyway, my key should also be available via the international Keyservers , the 'mutt users'-pgp ring (available from mutt's homepage ). I already managed to get some signatures from some other people on my key, and it is listed in the Cambridge "Global Trust Register"-Book . > This isn't picking on Stefan, of course--it seems like a good idea for > everybody. Yup, you're right :) CU, Sec -- Ich glaube die schrecklichste Erfindung der Menschheit war die Uhr. From elb@chaos.com Fri Feb 6 19:07:07 1998 Return-Path: elb@chaos.com Received: from chaos.com (elb@[206.244.92.26]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id TAA12482 for ; Fri, 6 Feb 1998 19:07:02 -0800 (PST) Received: (from elb@localhost) by chaos.com (8.7.6/8.6.12) id WAA02745; Fri, 6 Feb 1998 22:11:36 -0500 Message-ID: <19980206221136.05774@trc-inc.com> Date: Fri, 6 Feb 1998 22:11:36 -0500 From: Ethan Blanton To: mutt-users@cs.hmc.edu Subject: Re: quote_regexp Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980206182416.02483@trc-inc.com> <19980206184215.12428@rsn.hp.com> <19980206202905.35527@trc-inc.com> <19980206202618.51243@rsn.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980206202618.51243@rsn.hp.com>; from David DeSimone on Fri, Feb 06, 1998 at 08:26:18PM -0600 X-Operating-System: Linux On Fri, Feb 06, 1998 at 08:26:18PM -0600, David DeSimone wrote: > Most people expect that the longer string is the deepest quote level. > However, Mutt does not see it that way. > ... > Mutt instead sees that the first line has a string "> > > " that matches > the regexp, so this is considered the first quote level, and will be > ... > Next, the string "> > " matches, > ... Aha! This explains the behavior... As I look over the files I used to test it, this could very well explain what I was seeing. User head space and timing... ;-) Ethan From bonkey@matylda.silesia.linux.org.pl Fri Feb 6 19:48:45 1998 Return-Path: bonkey@matylda.silesia.linux.org.pl Received: from pikus.wnaft.agh.edu.pl (uucp@pikus.wnaft.agh.edu.pl [149.156.117.124]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id TAA16766 for ; Fri, 6 Feb 1998 19:48:39 -0800 (PST) Received: from matylda.UUCP (uucp@localhost) by pikus.wnaft.agh.edu.pl (8.8.8/8.8.8) with bsmtp id EAA06162 for mutt-users@cs.hmc.edu; Sat, 7 Feb 1998 04:53:47 +0100 Received: (from bonkey@localhost) by matylda.silesia.linux.org.pl (8.8.5/8.8.7) id EAA27795; Sat, 7 Feb 1998 04:39:56 +0100 Message-ID: <19980207043956.05395@matylda.silesia.linux.org.pl> Date: Sat, 7 Feb 1998 04:39:56 +0100 From: Daniel Bauke To: Mutt Heads Subject: toggle verify_sig Mail-Followup-To: Mutt Heads Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Operating-System: Linux 2.0.33 i586 X-Writing-Started: Sat Feb 7 04:33:12 MET 1998 I've got: macro index \cv ":toggle verify_sig^M" macro pager \cv ":toggle verify_sig^M" but it doesn't works. Well, in fact it works but only one time. When I turn it on it freezes at that position and I can't change it without exiting from mutt. -- Daniel Bauke | bonkey@matylda.silesia.linux.org.pl vulgo bonkey | http://www.silesia.linux.org.pl/~bonkey/ & rat's all 4 U (2) know... From thomas@darkstar.rhein-neckar.de Sat Feb 7 01:41:08 1998 Return-Path: thomas@darkstar.rhein-neckar.de Received: from tutnix.rhein-neckar.de (tutnix.rhein-neckar.de [193.197.89.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id BAA19664 for ; Sat, 7 Feb 1998 01:41:05 -0800 (PST) Received: (from uucp@localhost) by tutnix.rhein-neckar.de (8.8.5/8.7.3) with UUCP id KAA08322 for mutt-users@cs.hmc.edu; Sat, 7 Feb 1998 10:41:03 +0100 (MET) Received: (from thomas@localhost) by darkstar.rhein-neckar.de (8.8.5/8.8.5) id KAA11383; Sat, 7 Feb 1998 10:33:20 +0100 Message-ID: <19980207103319.51095@darkstar.rhein-neckar.de> Date: Sat, 7 Feb 1998 10:33:19 +0100 From: Thomas Kluge To: mutt-list Subject: Macro-Problems with 0.89.1i Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.89.1i Hi, with 0.88, i used this macro without problems: macro index a "!${EDITOR:-vi} $HOME/.mutt/aliases\n:source ~/.mutt/aliases\n" (all in one line) By pressing a, my editor was launched and the alias-file was loaded. With 0.89.1i, mutt says:=20 sh: /home/thomas/.mutt/aliases: Permission denied Press any key to continue... Permissions were: -rw------- 1 thomas users 1964 Feb 7 10:22 aliases (i'm logged in as "thomas", of course) Then i've set the permissions to -rwxrwxrwx, trying to run the macro, mutt says: /home/thomas/.mutt/aliases: line 1: syntax error near unexpected token ' /home/thomas/.mutt/aliases: line 1: =01lias heinz Heinz Diehl ' Press any key to continue... Seems that the editing-command doesn't work and mutt encounters problems with the source-command. What's wrong, did i detect a new bug, or is there any way to fix the problem by changing my macro? Sorry if the answer is in the documentation, i tried to find the answer by myself, but i didn't find it. Thank you in advance for your hints, Thomas --=20 EMAIL: thomas@darkstar.rhein-neckar.de WWW: www.rhein-neckar.de/~darkstar/ IRC: ctom SITE: Tommi Online PGP: send email with subject "get pgpkey" -------------------This site is powered by Linux 2.0.33------------------- From vaxerdec@vaxerdec.dyn.ml.org Sat Feb 7 09:31:54 1998 Return-Path: vaxerdec@vaxerdec.dyn.ml.org Received: from node21.frontiernet.net (root@node21.frontiernet.net [209.130.129.196]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id JAA08754 for ; Sat, 7 Feb 1998 09:31:52 -0800 (PST) Received: from vaxerdec.dyn.ml.org (srv-16-25.roc.ny.frontiernet.net [209.130.133.82]) by node21.frontiernet.net (8.8.8/8.8.6) with ESMTP id MAA97134 for ; Sat, 7 Feb 1998 12:31:52 -0500 Received: (from vaxerdec@localhost) by vaxerdec.dyn.ml.org (8.8.8/8.8.8) id MAA09752; Sat, 7 Feb 1998 12:27:52 -0500 Message-ID: <19980207122752.35393@dyn.ml.org> Date: Sat, 7 Feb 1998 12:27:52 -0500 From: Scott McDermott To: mutt-users@cs.hmc.edu Subject: universal `cancel operation' ? Mail-Followup-To: mutt-users@cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 Is there a semi-universal key that will just about always cancel the current operation? Scott From sec@matrix.42.org Sat Feb 7 09:56:28 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id JAA09991 for ; Sat, 7 Feb 1998 09:56:25 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id SAA26278 (sender ); Sat, 7 Feb 1998 18:56:15 +0100 (CET) Message-ID: <19980207185614.43025@matrix.42.org> Date: Sat, 7 Feb 1998 18:56:14 +0100 From: Stefan `Sec` Zehl To: mutt-users@cs.hmc.edu Subject: Re: universal `cancel operation' ? Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980207122752.35393@dyn.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980207122752.35393@dyn.ml.org>; from Scott McDermott on Sat, Feb 07, 1998 at 12:27:52PM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Sat, Feb 07, 1998 at 12:27:52PM -0500, Scott McDermott wrote: > Is there a semi-universal key that will just about always cancel the > current operation? ^g should do the trick CU, Sec -- Since compiler users outnumber compiler writers 1000:1, if it's possible to save a compiler user 1 hour, it's worth 1000 hours of the compiler writer's time. From eisenbud@allspice.cs.swarthmore.edu Sat Feb 7 10:11:41 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA10894 for ; Sat, 7 Feb 1998 10:11:39 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id NAA08783; Sat, 7 Feb 1998 13:11:40 -0500 (EST) Message-ID: <19980207131139.00471@cs.swarthmore.edu> Date: Sat, 7 Feb 1998 13:11:39 -0500 From: Daniel Eisenbud To: mutt-users@cs.hmc.edu Subject: Re: universal `cancel operation' ? Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980207122752.35393@dyn.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980207122752.35393@dyn.ml.org>; from Scott McDermott on Sat, Feb 07, 1998 at 12:27:52PM -0500 On Sat, Feb 07, 1998 at 12:27:52PM -0500, Scott McDermott wrote: > Is there a semi-universal key that will just about always cancel the > current operation? Control-G. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From rsk@gsp.org Sat Feb 7 10:21:37 1998 Return-Path: rsk@gsp.org Received: from gsp.org (rsk.itw.com [208.211.3.21]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA11587 for ; Sat, 7 Feb 1998 10:21:34 -0800 (PST) Received: (from rsk@localhost) by gsp.org (8.8.8/8.8.8) id NAA22832; Sat, 7 Feb 1998 13:21:17 -0500 (EST) Message-ID: <19980207132105.48910@wombat> Date: Sat, 7 Feb 1998 13:21:05 -0500 From: Rich Kulawiec To: Rich Kulawiec Cc: mutt-users@cs.hmc.edu Subject: Re: Mutt feature request -- duplicate message detection/deletion References: <19980204115843.02167@wombat> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980204115843.02167@wombat>; from Rich Kulawiec on Wed, Feb 04, 1998 at 11:58:43AM -0500 On Wed, Feb 04, 1998 at 11:58:43AM -0500, Rich Kulawiec wrote: > I'd like to have a command that will search through an entire > message folder (file) and locate messages which have the same > Message-ID (or Article-ID) and do a fast-n-dirty comparison > (to make sure they're really the same) and delete them. Yes, I'm following up my own message. No, I have not lost my mind. ;-) I just thought I'd share something that addresses a good chunk of my problem, and that's the program "formail" which comes as part of the "procmail" package. "formail" is a general-purpose mail slicer-dicer that can rewrite headers, eliminate duplicate messages, and do other useful stuff. Happily, it works just great on mail folders full of saved news articles (saved in mailbox format). I've been busy off-and-on for the last few days pushing archives of messages through it and watching my free disk space climb. I believe formail may also solve another problem that I've had with Elm and Mutt: malformed "From " lines due to munged news headers. I haven't quite figured out exactly how to use it to yield precisely what I want on that particular header line, but I think I just to need to RTFM a little more and maybe do some experimenting. ---Rsk Rich Kulawiec rsk@gsp.org From roberto@keltia.freenix.fr Sat Feb 7 10:30:41 1998 Return-Path: roberto@keltia.freenix.fr Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA12317 for ; Sat, 7 Feb 1998 10:30:36 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id TAA03382 for mutt-users@cs.hmc.edu; Sat, 7 Feb 1998 19:30:34 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id TAA05959; Sat, 7 Feb 1998 19:27:59 +0100 (CET) (envelope-from roberto) Message-ID: <19980207192759.36033@keltia.freenix.fr> Date: Sat, 7 Feb 1998 19:27:59 +0100 From: Ollivier Robert To: mutt-users@cs.hmc.edu Subject: Re: universal `cancel operation' ? Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980207122752.35393@dyn.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980207122752.35393@dyn.ml.org>; from Scott McDermott on Sat, Feb 07, 1998 at 12:27:52PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4049 AMD-K6 MMX @ 225 MHz According to Scott McDermott: > Is there a semi-universal key that will just about always cancel the > current operation? You're probably looking for this: ^G n/a abort -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Mutt patches collection: From vikasa@att.com Sat Feb 7 16:22:28 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw2.att.com [192.128.133.152]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id QAA17048 for ; Sat, 7 Feb 1998 16:22:25 -0800 (PST) Received: by kcgw2.att.com; Sat Feb 7 18:05 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id SAA09118 for ; Sat, 7 Feb 1998 18:10:36 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id TAA14336; Sat, 7 Feb 1998 19:20:45 -0500 (EST) Message-ID: <19980207192045.50613@att.com> Date: Sat, 7 Feb 1998 19:20:45 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980204141931.03566@att.com> <19980206153938.44183@la.tis.com> <19980206182524.34820@rsn.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1 In-Reply-To: <19980206182524.34820@rsn.hp.com>; from David DeSimone on Fri, Feb 06, 1998 at 06:25:24PM -0600 On Fri, Feb 06, 1998 at 06:25:24PM -0600, David DeSimone wrote: > I checked this out, and I noticed the same thing as Vikas. If you > edit an attachment, Mutt will only choose 8bit, 7bit, or Q-P encoding. > It never seems to come to the conclusion that base64 would be an > appropriate encoding, even if it really would be (such as a file full of > 8bit characters). What if I explicitly change the encoding to base64 using ^E in the Compose menu? Does Mutt re-encode the attachment or just change the header to indicate this? What is _really_ meant by "encoding", in this context? Some enlightment, please? Thanks, Vikas From vikasa@att.com Sat Feb 7 16:33:52 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw2.att.com [192.128.133.152]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id QAA18525 for ; Sat, 7 Feb 1998 16:33:50 -0800 (PST) Received: by kcgw2.att.com; Sat Feb 7 18:16 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id SAA11914 for ; Sat, 7 Feb 1998 18:22:01 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id TAA14369; Sat, 7 Feb 1998 19:32:11 -0500 (EST) Message-ID: <19980207193211.38339@att.com> Date: Sat, 7 Feb 1998 19:32:11 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980205101846.23520@att.com> <19980205105948.21420@shell9.ba.best.com> <19980205150145.31309@att.com> <19980205180744.39097@rsn.hp.com> <19980206121246.25613@att.com> <19980206105855.22815@shell9.ba.best.com> <19980206161100.03119@att.com> <19980206163422.20003@rsn.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.90.1 In-Reply-To: <19980206163422.20003@rsn.hp.com>; from David DeSimone on Fri, Feb 06, 1998 at 04:34:22PM -0600 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by kcig2.att.att.com id SAA11914 On Fri, Feb 06, 1998 at 04:34:22PM -0600, David DeSimone wrote:=20 > Vikas Agnihotri wrote: > > Went back into editor from Compose menu and added tons of more =BD > > characters, now the entire file contains only the 8-bit character =BD. > > But the encoding stays at 8bit. It does not change to base64. > Well, an 8bit encoding is the most efficient encoding, right? I guess > you have $allow_8bit set. Correct. I do have $allow_8bit set. What is the deal here? What are the ramifications of unsetting allow_8bit?=20 I did my earlier experiment with $allow_8bit off and it used q-p encoding where earlier it used 8bit, with a file full of 8bit characters. >From the manual snippet below and the results of my experiment, it seems like $allow_8bit=3D0 (off) is the way to go, right?=20 Basically, what is the point of having this option and how does it affect Mutt sending mail efficiently encoded? Still trying to understand all this. Thanks, Vikas 6.3.4. allow_8bit Type: boolean Default: set Controls whether 8-bit data is converted to 7-bit using either Quoted- Printable or Base64 encoding when sending mail. From eisenbud@allspice.cs.swarthmore.edu Sat Feb 7 17:46:35 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA28232 for ; Sat, 7 Feb 1998 17:46:29 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id UAA13907; Sat, 7 Feb 1998 20:46:18 -0500 (EST) Message-ID: <19980207204617.48285@cs.swarthmore.edu> Date: Sat, 7 Feb 1998 20:46:17 -0500 From: Daniel Eisenbud To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980204141931.03566@att.com> <19980206153938.44183@la.tis.com> <19980206182524.34820@rsn.hp.com> <19980207192045.50613@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980207192045.50613@att.com>; from Vikas Agnihotri on Sat, Feb 07, 1998 at 07:20:45PM -0500 On Sat, Feb 07, 1998 at 07:20:45PM -0500, Vikas Agnihotri wrote: > On Fri, Feb 06, 1998 at 06:25:24PM -0600, David DeSimone wrote: > > I checked this out, and I noticed the same thing as Vikas. If you > > edit an attachment, Mutt will only choose 8bit, 7bit, or Q-P encoding. > > It never seems to come to the conclusion that base64 would be an > > appropriate encoding, even if it really would be (such as a file full of > > 8bit characters). > > What if I explicitly change the encoding to base64 using ^E in the Compose > menu? Does Mutt re-encode the attachment or just change the header to > indicate this? What is _really_ meant by "encoding", in this context? Some > enlightment, please? I don't know, but it seems to me that it will take you about a minute to try it and find out. I'd be curious to hear what you do discover, though, if you do this. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From hazmat@unixshell.com Sat Feb 7 21:13:38 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (hazmat@dns1.nws.net [199.234.203.130]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id VAA28922 for ; Sat, 7 Feb 1998 21:13:37 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id VAA07918; Sat, 7 Feb 1998 21:13:05 -0500 (EST) Message-ID: <19980207211305.14614@unixshell.com> Date: Sat, 7 Feb 1998 21:13:05 -0500 From: Ken W To: mutt Subject: [0.89.1i] unset help ignored Mail-Followup-To: mutt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X I compiled 0.89.1i under BSDI 3.1 and unset help in my .muttrc gets ignored and the help bar is displayed. Incidentally I have set status_on_top as well. Under FreeBSD with basically the same compilation, this doesn't happen. If it helps, mutt -v diaplays the following: Mutt 0.89.1i, Copyright (C) 1996-8 Michael R. Elkins Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System info: BSD/OS 3.1 [using ncurses 4.1] Compile time definitions: -DOMAIN -HIDDEN_HOST -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR -BUFFY_SIZE SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/home/shell/hazmat/share" ISPELL="/usr/contrib/bin/ispell" Thanks. -Ken -- hazmat@unixshell.com hazmat@shore.net http://www.shore.net/~hazmat From hazmat@unixshell.com Sat Feb 7 21:16:41 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (hazmat@dns1.nws.net [199.234.203.130]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id VAA29024 for ; Sat, 7 Feb 1998 21:16:39 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id VAA07986; Sat, 7 Feb 1998 21:16:08 -0500 (EST) Message-ID: <19980207211608.14661@unixshell.com> Date: Sat, 7 Feb 1998 21:16:08 -0500 From: Ken W To: mutt Subject: [0.89.1i] folder-hook set hdr_format error Mail-Followup-To: mutt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X In 0.89.1i, using set hdr_format with a folder-hook messes up the index. It looks like the left-most column is displayed and that's it. The rest is blank. -Ken -- hazmat@unixshell.com hazmat@shore.net http://www.shore.net/~hazmat From vikasa@att.com Sat Feb 7 21:44:44 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw1.att.com [192.128.133.151]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id VAA02965 for ; Sat, 7 Feb 1998 21:44:42 -0800 (PST) Received: by kcgw1.att.com; Sat Feb 7 23:41 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id XAA02116 for ; Sat, 7 Feb 1998 23:32:33 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id AAA14843; Sun, 8 Feb 1998 00:43:03 -0500 (EST) Message-ID: <19980208004303.53412@att.com> Date: Sun, 8 Feb 1998 00:43:03 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980204141931.03566@att.com> <19980206153938.44183@la.tis.com> <19980206182524.34820@rsn.hp.com> <19980207192045.50613@att.com> <19980207204617.48285@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 In-Reply-To: <19980207204617.48285@cs.swarthmore.edu>; from Daniel Eisenbud on Sat, Feb 07, 1998 at 08:46:17PM -0500 On Sat, Feb 07, 1998 at 08:46:17PM -0500, Daniel Eisenbud wrote: > On Sat, Feb 07, 1998 at 07:20:45PM -0500, Vikas Agnihotri wrote: > > On Fri, Feb 06, 1998 at 06:25:24PM -0600, David DeSimone wrote: > > > I checked this out, and I noticed the same thing as Vikas. If you > > > edit an attachment, Mutt will only choose 8bit, 7bit, or Q-P encoding. > > > It never seems to come to the conclusion that base64 would be an > > > appropriate encoding, even if it really would be (such as a file full of > > > 8bit characters). > > What if I explicitly change the encoding to base64 using ^E in the Compose > > menu? Does Mutt re-encode the attachment or just change the header to > > indicate this? What is _really_ meant by "encoding", in this context? Some > > enlightment, please? > I don't know, but it seems to me that it will take you about a minute to > try it and find out. Not really. I attached the file (abcd.bmp). Mutt gave me text/plain-qp in the Compose menu. ^E to base64. Compose menu shows text/plain-base64. ^E to 8bit, fine. ^E 7bit, fine. What I am saying is that Mutt simply nods its head at whatever encoding I ask it to do, making me wonder, is it just changing the header, or actually _doing_ something? Hence the question. And I really couldnt figure out a way to "find out" one way or the other even after "a minute" :-) > I'd be curious to hear what you do discover, though, if you do this. Dunno. I think Mutt calls mutt_get_content_info() to chew the attachment only after I detach/attach a file, _or- change the content-type with ^T or edit the attachment and drop back into the Compose menu. Anything I do with ^E, Mutt simply thinks I know what I am asking it to do. AFAICT, that is. Am I right, or am I right? :) Vikas From hazmat@unixshell.com Sun Feb 8 00:20:28 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (hazmat@dns1.nws.net [199.234.203.130]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA07980 for ; Sun, 8 Feb 1998 00:20:26 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id AAA12650; Sun, 8 Feb 1998 00:19:55 -0500 (EST) Message-ID: <19980208001955.05850@unixshell.com> Date: Sun, 8 Feb 1998 00:19:55 -0500 From: Ken W To: mutt Subject: Re: [0.89.1i] unset help ignored Mail-Followup-To: mutt References: <19980207211305.14614@unixshell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980207211305.14614@unixshell.com>; from Ken W on Sat, Feb 07, 1998 at 09:13:05PM -0500 X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X Sorry to follow up on my own message, but I fixed it. I recompiled and it's okay. Sorry. On Sat, Feb 7, 1998, I wrote: > I compiled 0.89.1i under BSDI 3.1 and unset help in my .muttrc gets > ignored and the help bar is displayed. Incidentally I have set status_on_top > as well. Under FreeBSD with basically the same compilation, this > doesn't happen. If it helps, mutt -v diaplays the following: > > Mutt 0.89.1i, Copyright (C) 1996-8 Michael R. Elkins > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > Mutt is free software, and you are welcome to redistribute it > under certain conditions; type `mutt -vv' for details. > > System info: BSD/OS 3.1 [using ncurses 4.1] > > Compile time definitions: > -DOMAIN > -HIDDEN_HOST -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL > -USE_FLOCK > -USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR -BUFFY_SIZE > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/mail" > SHAREDIR="/usr/home/shell/hazmat/share" > ISPELL="/usr/contrib/bin/ispell" > > > Thanks. > > > -Ken > > -- > hazmat@unixshell.com > hazmat@shore.net > http://www.shore.net/~hazmat From blong@shell9.ba.best.com Sun Feb 8 00:48:11 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA09992 for ; Sun, 8 Feb 1998 00:48:09 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id AAA17676; Sun, 8 Feb 1998 00:47:20 -0800 (PST) Message-ID: <19980208004719.12751@shell9.ba.best.com> Date: Sun, 8 Feb 1998 00:47:20 -0800 From: Brandon Long To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Reply-To: blong@fiction.net Mail-Followup-To: Mutt users mailing list References: <19980204141931.03566@att.com> <19980206153938.44183@la.tis.com> <19980206182524.34820@rsn.hp.com> <19980207192045.50613@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980207192045.50613@att.com>; from Vikas Agnihotri on Sat, Feb 07, 1998 at 07:20:45PM -0500 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/07/98 Vikas Agnihotri uttered the following other thing: > On Fri, Feb 06, 1998 at 06:25:24PM -0600, David DeSimone wrote: > > I checked this out, and I noticed the same thing as Vikas. If you > > edit an attachment, Mutt will only choose 8bit, 7bit, or Q-P encoding. > > It never seems to come to the conclusion that base64 would be an > > appropriate encoding, even if it really would be (such as a file full of > > 8bit characters). > > What if I explicitly change the encoding to base64 using ^E in the Compose > menu? Does Mutt re-encode the attachment or just change the header to > indicate this? What is _really_ meant by "encoding", in this context? Some > enlightment, please? Mutt doesn't encode attachments until it sends them. So, when you use ^E, you are merely telling mutt what it should encode them as. When you send the mail, it will attempt to encode them with what you told it. Brandon -- Brandon Long "The bible says [blah blah blah], therefore the Bible MD6 Crash Test Dummy is a metaphorical expression of the ideas of people Intel Corporation in ancient times." -- Ken L. Holder I'm too low on the totem pole to speak for Intel. http://www.fiction.net/blong/ From aaron+mutt@schrab.com Sun Feb 8 01:01:36 1998 Return-Path: aaron+mutt@schrab.com Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.16.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id BAA11311 for ; Sun, 8 Feb 1998 01:01:33 -0800 (PST) Received: from fnord.execpc.com (windowpane.execpc.com [169.207.1.11]) by mailgw02.execpc.com (8.8.8) id DAA27859 for ; Sun, 8 Feb 1998 03:01:33 -0600 (CST) Received: by fnord.execpc.com id DAA24484; Sun, 8 Feb 1998 03:01:28 -0600 Message-ID: <19980208030128.03884@fnord.guru.execpc.com> Date: Sun, 8 Feb 1998 03:01:28 -0600 From: Aaron Schrab To: Mutt users mailing list Subject: Re: [0.89 MIME] Content-type/encoding bug? Mail-Followup-To: Mutt users mailing list References: <19980204141931.03566@att.com> <19980206153938.44183@la.tis.com> <19980206182524.34820@rsn.hp.com> <19980207192045.50613@att.com> <19980207204617.48285@cs.swarthmore.edu> <19980208004303.53412@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980208004303.53412@att.com>; from Vikas Agnihotri on Sun, Feb 08, 1998 at 12:43:03AM -0500 At 00:43 -0500, 08 Feb. 1998, Vikas Agnihotri wrote: > Not really. I attached the file (abcd.bmp). Mutt gave me text/plain-qp in > the Compose menu. ^E to base64. Compose menu shows text/plain-base64. ^E to > 8bit, fine. ^E 7bit, fine. > > What I am saying is that Mutt simply nods its head at whatever encoding I > ask it to do, making me wonder, is it just changing the header, or actually > _doing_ something? Hence the question. And I really couldnt figure out a > way to "find out" one way or the other even after "a minute" :-) > Anything I do with ^E, Mutt simply thinks I know what I am asking it to do. When you're in the compose menu, mutt hasn't yet encoded the attachment, so if you change the encoding, there's really nothing for it to do. It first does the encoding when you send the message, and it does honor any encoding change. If requested to, it will even use 7bit encoding when the attachment contains 8bit data (I'd say that this is a bug). The way to figure this out is to send yourself test messages. When you receive the message (or look at an FCC'd copy), it will show what mutt does with the attachment. -- Aaron Schrab aaron@schrab.com http://www.execpc.com/~aarons/ Beware of the Turing Tar-pit in which everything is possible but nothing of interest is easy. From sec@matrix.42.org Sun Feb 8 04:49:33 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id EAA28952 for ; Sun, 8 Feb 1998 04:49:27 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id NAA07131 (sender ); Sun, 8 Feb 1998 13:49:24 +0100 (CET) Message-ID: <19980208134923.04102@matrix.42.org> Date: Sun, 8 Feb 1998 13:49:23 +0100 From: Stefan `Sec` Zehl To: mutt Subject: Re: [0.89.1i] folder-hook set hdr_format error Mail-Followup-To: mutt References: <19980207211608.14661@unixshell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980207211608.14661@unixshell.com>; from Ken W on Sat, Feb 07, 1998 at 09:16:08PM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Sat, Feb 07, 1998 at 09:16:08PM -0500, Ken W wrote: > In 0.89.1i, using set hdr_format with a folder-hook messes up the > index. It looks like the left-most column is displayed and that's it. > The rest is blank. I think, you might have a quoteing problem. Send us the offending line, so we can see. CU, Sec -- "Computers make very fast, very accurate, mistakes." From sallawa@csci.uark.edu Sun Feb 8 06:50:07 1998 Return-Path: sallawa@csci.uark.edu Received: from csci.uark.edu (sallawa@csci.uark.edu [130.184.201.177]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id GAA06427 for ; Sun, 8 Feb 1998 06:50:05 -0800 (PST) Received: (from sallawa@localhost) by csci.uark.edu (8.8.5/8.7.3) id IAA02353; Sun, 8 Feb 1998 08:50:02 -0600 (CST) Message-ID: <19980208085002.39940@csci.uark.edu> Date: Sun, 8 Feb 1998 08:50:02 -0600 From: Sadiq Al-Lawatia To: mutt-users@cs.hmc.edu Subject: quote_regexp Mail-Followup-To: mutt-users@cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 Hi all, Am quite new to mutt and to its .muttrc file and I would like to know what quote_regexp is in simple english pls :-) Thank you, Sadiq -- ******************************** * Sadiq B. Al-Lawatia * * Computer Science * * sallawa@csci.uark.edu * *http://csci.uark.edu/~sallawa * ******************************** From hazmat@unixshell.com Sun Feb 8 09:29:31 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (hazmat@dns1.nws.net [199.234.203.130]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id JAA14554 for ; Sun, 8 Feb 1998 09:29:29 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id JAA26981; Sun, 8 Feb 1998 09:29:00 -0500 (EST) Message-ID: <19980208092900.25528@unixshell.com> Date: Sun, 8 Feb 1998 09:29:00 -0500 From: Ken W To: mutt Subject: Re: [0.89.1i] folder-hook set hdr_format error Mail-Followup-To: mutt References: <19980207211608.14661@unixshell.com> <19980208134923.04102@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980208134923.04102@matrix.42.org>; from Stefan `Sec` Zehl on Sun, Feb 08, 1998 at 01:49:23PM +0100 X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X On Sun, Feb 8, 1998, Stefan `Sec` Zehl wrote: > On Sat, Feb 07, 1998 at 09:16:08PM -0500, Ken W wrote: > > In 0.89.1i, using set hdr_format with a folder-hook messes up the > > index. It looks like the left-most column is displayed and that's it. > > The rest is blank. > > I think, you might have a quoteing problem. Send us the offending line, > so we can see. Okay, this is what I tried: folder-hook . set hdr_format=" %S %3C %[%b %d] %T %-20.20n (%3l) %s" folder-hook sent set hdr_format=" %3C %[%b %d] %-20.20t (%3l) %s" This is basically to change the =sent index to see who whom the mail was sent, and clean it up while I am at it. The default folder hook is simply copied and pasted from my hdr_format. Thanks. -Ken -- hazmat@unixshell.com hazmat@shore.net http://www.shore.net/~hazmat From sec@matrix.42.org Sun Feb 8 10:04:39 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA16477 for ; Sun, 8 Feb 1998 10:04:36 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id TAA14507 (sender ); Sun, 8 Feb 1998 19:04:22 +0100 (CET) Message-ID: <19980208190421.07558@matrix.42.org> Date: Sun, 8 Feb 1998 19:04:21 +0100 From: Stefan `Sec` Zehl To: mutt Subject: Re: [0.89.1i] folder-hook set hdr_format error Mail-Followup-To: mutt References: <19980207211608.14661@unixshell.com> <19980208134923.04102@matrix.42.org> <19980208092900.25528@unixshell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980208092900.25528@unixshell.com>; from Ken W on Sun, Feb 08, 1998 at 09:29:00AM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Sun, Feb 08, 1998 at 09:29:00AM -0500, Ken W wrote: > Okay, this is what I tried: > > folder-hook . set hdr_format=" %S %3C %[%b %d] %T %-20.20n (%3l) %s" > > folder-hook sent set hdr_format=" %3C %[%b %d] %-20.20t (%3l) %s" Okay, this is indeed a quoting problem. You should use: folder-hook . 'set hdr_format=" %S %3C %[%b %d] %T %-20.20n (%3l) %s"' folder-hook sent 'set hdr_format=" %3C %[%b %d] %-20.20t (%3l) %s"' CU, Sec -- Black holes are where GOD is dividing by zero From newgroups-errors@isc.org Sun Feb 8 10:20:54 1998 Return-Path: newgroups-errors@isc.org Received: from gro.dd.org (tale@gro.dd.org [206.66.153.102]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA17735 for ; Sun, 8 Feb 1998 10:20:50 -0800 (PST) Received: (from tale@localhost) by gro.dd.org (8.8.5/8.7.3) id NAA12575 for mutt-announce@cs.hmc.edu; Sun, 8 Feb 1998 13:20:47 -0500 (EST) Date: Sun, 8 Feb 1998 13:20:47 -0500 (EST) From: Michael Elkins Newsgroups: news.announce.newgroups,news.groups,comp.mail.misc,comp.mail.elm Subject: RFD: comp.mail.mutt Followup-To: news.groups Message-ID: <886962047.12571@isc.org> Errors-To: newgroups-errors@isc.org To: mutt-announce@cs.hmc.edu REQUEST FOR DISCUSSION (RFD) unmoderated group comp.mail.mutt This is a formal Request For Discussion (RFD) for the creation of a world-wide unmoderated Usenet newsgroup comp.mail.mutt. This is not a Call for Votes (CFV); you cannot vote at this time. Procedural details are below. Newsgroup line: comp.mail.mutt The Mutt E-Mail Program. RATIONALE: comp.mail.mutt Mutt is an e-mail client for Unix operating systems which has seen increased use due to the recent inclusion in several free unix distributions (RedHat, Debian, FreeBSD). A mailing list for Mutt was started in mid-1996 to keep those interested in the project informed of happenings. In early 1997 the list was split up into three separate lists: one for announcements only, one for users, and the last for developers. The current subscribership of the announce and user list is 857, and 905 if you include the development list. Roughly 30 posts per day are seen on users lists on active days. Currently, posts regarding Mutt are showing up daily in the newsgroup comp.mail.elm. However, Mutt is not releated to ELM other than the fact that the author of Mutt previously worked on ELM; Mutt is not an offshoot of ELM, it was written from scratch. Therefore, posts to comp.mail.elm are not appropriate. CHARTER: comp.mail.mutt comp.mail.mutt will provide a place for the discussion of the Mutt e-mail client. No binary posting is allowed. No spamming or off topic posting is allowed. END CHARTER. PROCEDURE: This is a request for discussion, not a call for votes. In this phase of the process, any potential problems with the proposed newsgroups should be raised and resolved. The discussion period will continue for a minimum of 21 days (starting from when the first RFD for this proposal is posted to news.announce.newgroups), after which a Call For Votes (CFV) may be posted by a neutral vote taker if the discussion warrants it. Please do not attempt to vote until this happens. All discussion of this proposal should be posted to news.groups. This RFD attempts to comply fully with the Usenet newsgroup creation guidelines outlined in "How to Create a New Usenet Newsgroup" and "How to Format and Submit a New Group Proposal". Please refer to these documents (available in news.announce.newgroups) if you have any questions about the process. DISTRIBUTION: This RFD has been posted to the following newsgroups: news.announce.newgroups, news.groups, comp.mail.elm, comp.mail.misc and to the following mailing list: mutt-announce@cs.hmc.edu Proponent: Michael Elkins From hazmat@unixshell.com Sun Feb 8 12:00:02 1998 Return-Path: hazmat@unixshell.com Received: from unixshell.com (hazmat@dns1.nws.net [199.234.203.130]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA24351 for ; Sun, 8 Feb 1998 12:00:00 -0800 (PST) Received: (from hazmat@localhost) by unixshell.com (8.8.8/8.8.6) id LAA02136; Sun, 8 Feb 1998 11:59:32 -0500 (EST) Message-ID: <19980208115932.29092@unixshell.com> Date: Sun, 8 Feb 1998 11:59:32 -0500 From: Ken W To: mutt Subject: Re: [0.89.1i] folder-hook set hdr_format error Mail-Followup-To: mutt References: <19980207211608.14661@unixshell.com> <19980208134923.04102@matrix.42.org> <19980208092900.25528@unixshell.com> <19980208190421.07558@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980208190421.07558@matrix.42.org>; from Stefan `Sec` Zehl on Sun, Feb 08, 1998 at 07:04:21PM +0100 X-Editor: vim-5.0r X-Languages: English, Portuguese (BR) X-X: X On Sun, Feb 8, 1998, Stefan `Sec` Zehl wrote: > > folder-hook . set hdr_format=" %S %3C %[%b %d] %T %-20.20n (%3l) %s" > > > > folder-hook sent set hdr_format=" %3C %[%b %d] %-20.20t (%3l) %s" > > Okay, this is indeed a quoting problem. You should use: > > folder-hook . 'set hdr_format=" %S %3C %[%b %d] %T %-20.20n (%3l) %s"' > folder-hook sent 'set hdr_format=" %3C %[%b %d] %-20.20t (%3l) %s"' Ah, that did indeed do it. Thanks. Weird, though, it worked without the single quotes in 0.88. -Ken -- hazmat@unixshell.com hazmat@shore.net http://www.shore.net/~hazmat From elb@chaos.com Sun Feb 8 15:36:30 1998 Return-Path: elb@chaos.com Received: from chaos.com (elb@ppp172.day-oh.siscom.net [206.244.171.172]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA21501 for ; Sun, 8 Feb 1998 15:36:26 -0800 (PST) Received: (from elb@localhost) by chaos.com (8.7.6/8.6.12) id SAA05681; Sun, 8 Feb 1998 18:36:51 -0500 Message-ID: <19980208183651.31124@trc-inc.com> Date: Sun, 8 Feb 1998 18:36:51 -0500 From: Ethan Blanton To: mutt-users@cs.hmc.edu Subject: Feature suggestion Mail-Followup-To: mutt-users@cs.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Operating-System: Linux How about support for multiple editors in mutt, based on environment conditions? i.e. editor="jed" xeditor="xjed", etc. This is another place where conditionals would be handy... #ifdef XWINDOWS editor="xjed" #else editor="jed" #endif Ethan From reader@fever.semiotek.com Sun Feb 8 16:02:49 1998 Return-Path: reader@fever.semiotek.com Received: from fever.semiotek.com ([206.108.246.81]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA24793 for ; Sun, 8 Feb 1998 16:02:47 -0800 (PST) Received: (from reader@localhost) by fever.semiotek.com (8.8.7/8.8.7) id TAA25840; Sun, 8 Feb 1998 19:02:46 -0500 (EST) (envelope-from reader) Message-ID: <19980208190245.18960@fever.semiotek.com> Date: Sun, 8 Feb 1998 19:02:45 -0500 From: List Reader To: mutt-users@cs.hmc.edu Subject: PGP mutt and MIME types Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 I've just started using mutt this week, and so far it's been great. My primary reason for switching (from elm) was to get better MIME and PGP support. Mutt does a pretty good job of that, I have to say. But there is one case that I am having trouble with: People frequently send me PGP encrypted messages that do not have the correct MIME type. I would like to be able to feed this to the PGP reader in mutt and view it anyway. I don't mind if at this point I have to enter some special menu or some key to do it -- so long as I don't have to save it to disk and decode it by hand. Yes, I can yell at the people who send me this stuff and tell them to get a better mailer, but I probably won't succeed :) I did check the documentation, but if I've missed where this question is answered please just point me to the right place and accept my apology for the stupid question. Thanks, Justin From eisenbud@allspice.cs.swarthmore.edu Sun Feb 8 16:14:59 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA26427 for ; Sun, 8 Feb 1998 16:14:56 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id TAA26808; Sun, 8 Feb 1998 19:14:54 -0500 (EST) Message-ID: <19980208191454.29755@cs.swarthmore.edu> Date: Sun, 8 Feb 1998 19:14:54 -0500 From: Daniel Eisenbud To: mutt-users@cs.hmc.edu Subject: Re: Feature suggestion Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208183651.31124@trc-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980208183651.31124@trc-inc.com>; from Ethan Blanton on Sun, Feb 08, 1998 at 06:36:51PM -0500 On Sun, Feb 08, 1998 at 06:36:51PM -0500, Ethan Blanton wrote: > How about support for multiple editors in mutt, based on environment > conditions? i.e. editor="jed" xeditor="xjed", etc. This is another place > where conditionals would be handy... > > #ifdef XWINDOWS > editor="xjed" > #else > editor="jed" > #endif There are several ways to deal with this. You can set your editor variable to a two-line shell script wrapper that does this for you. You can use backquote expansion in the muttrc, with a different shell script that just outputs the name of the correct editor to use under the circumstances. People have asked for this feature before, but nobody has ever given an example of a useful thing to condition on that can't be done with this sort of trick. If you want to have larger blocks depend on something like this, make a new rc file for each of the cases, and use a source command with backquote expansion. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From nneul@umr.edu Sun Feb 8 16:16:32 1998 Return-Path: nneul@umr.edu Received: from umr.edu (hermes.cc.umr.edu [131.151.1.68]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA26549 for ; Sun, 8 Feb 1998 16:16:29 -0800 (PST) Received: from infinity.cc.umr.edu (infinity.cc.umr.edu [131.151.37.9]) via ESMTP by hermes.cc.umr.edu (8.8.7/R.4.20) id SAA23710; Sun, 8 Feb 1998 18:16:22 -0600 (CST) Received: from (nneul@localhost) by infinity.cc.umr.edu (8.8.6/M.3.01) id SAA30667; Sun, 8 Feb 1998 18:16:21 -0600 Message-ID: <19980208181620.33974@umr.edu> Date: Sun, 8 Feb 1998 18:16:20 -0600 From: Nathan Neulinger To: mutt-users@cs.hmc.edu Subject: Re: Feature suggestion References: <19980208183651.31124@trc-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980208183651.31124@trc-inc.com>; from Ethan Blanton on Sun, Feb 08, 1998 at 06:36:51PM -0500 Unless I remember incorrectly, the following will take care of that: editor=`somecommand` Where 'somecommand' is a script that would return the proper editor to use. -- Nathan On Sun, Feb 08, 1998 at 06:36:51PM -0500, Ethan Blanton wrote: > How about support for multiple editors in mutt, based on environment > conditions? i.e. editor="jed" xeditor="xjed", etc. This is another place > where conditionals would be handy... > > #ifdef XWINDOWS > editor="xjed" > #else > editor="jed" > #endif > > Ethan ------------------------------------------------------------ Nathan Neulinger EMail: nneul@umr.edu University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 From sec@matrix.42.org Sun Feb 8 16:25:27 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA27986 for ; Sun, 8 Feb 1998 16:25:23 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id BAA20579 (sender ); Mon, 9 Feb 1998 01:25:17 +0100 (CET) Message-ID: <19980209012516.42796@matrix.42.org> Date: Mon, 9 Feb 1998 01:25:16 +0100 From: Stefan `Sec` Zehl To: List Reader , mutt-users@cs.hmc.edu Subject: Re: PGP mutt and MIME types Mail-Followup-To: List Reader , mutt-users@cs.hmc.edu References: <19980208190245.18960@fever.semiotek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.90.1i In-Reply-To: <19980208190245.18960@fever.semiotek.com>; from List Reader on Sun, Feb 08, 1998 at 07:02:45PM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Sun, Feb 08, 1998 at 07:02:45PM -0500, List Reader wrote: > People frequently send me PGP encrypted messages that do not have the > correct MIME type. [...] > I did check the documentation, but if I've missed where this question > is answered please just point me to the right place and accept my > apology for the stupid question. Look at: http://www.math.fu-berlin.de/~leitner/mutt/faq.html#nonmimepgp CU, Sec -- Die kürzesten Computerwitze: 1) Müßte laufen. From manojk@xanadu.io.com Sun Feb 8 16:41:48 1998 Return-Path: manojk@xanadu.io.com Received: from xanadu.io.com (manojk@xanadu.io.com [199.170.88.6]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA00763 for ; Sun, 8 Feb 1998 16:41:45 -0800 (PST) Received: (from manojk@localhost) by xanadu.io.com (8.8.5/8.8.5) id SAA28146; Sun, 8 Feb 1998 18:41:42 -0600 (CST) Message-ID: <19980208184142.46028@io.com> Date: Sun, 8 Feb 1998 18:41:42 -0600 From: Manoj Kasichainula To: mutt-users@cs.hmc.edu Subject: Re: PGP mutt and MIME types Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208190245.18960@fever.semiotek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980208190245.18960@fever.semiotek.com>; from List Reader on Sun, Feb 08, 1998 at 07:02:45PM -0500 X-spam-bait: postmaster@warez.io.com abuse@warez.io.com On Sun, Feb 08, 1998 at 07:02:45PM -0500, List Reader wrote: > People frequently send me PGP encrypted messages that do not have the > correct MIME type. I would like to be able to feed this to the PGP reader > in mutt and view it anyway.robably won't succeed :) > > I did check the documentation, but if I've missed where this question > is answered please just point me to the right place and accept my > apology for the stupid question. OK, check the FAQ. You'll find a procmail recipe to tag PGP messages there. -- Manoj Kasichainula - manojk at io dot com - http://www.io.com/~manojk/ "Don't. You're too young to experience that much pain." -- Cmdr. Susan Ivanova, Babylon 5 From jrand@fast.net Sun Feb 8 17:11:10 1998 Return-Path: jrand@fast.net Received: from post1.fast.net (post1.fast.net [198.69.204.13]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA05327 for ; Sun, 8 Feb 1998 17:11:09 -0800 (PST) From: jrand@fast.net Received: from tnt01-abe-linux.fast.net (qmailr@tnt01-abe-054.FAST.NET [204.95.116.54]) by post1.fast.net (8.8.5/8.8.5) with SMTP id UAA07583 for ; Sun, 8 Feb 1998 20:11:08 -0500 (EST) Received: (qmail 2889 invoked by uid 501); 9 Feb 1998 01:11:29 -0000 Message-ID: <19980208201129.41811@opus.expnet.net> Date: Sun, 8 Feb 1998 20:11:29 -0500 To: mutt-users@cs.hmc.edu Subject: Re: PGP mutt and MIME types Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208190245.18960@fever.semiotek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980208190245.18960@fever.semiotek.com>; from List Reader on Sun, Feb 08, 1998 at 07:02:45PM -0500 On Sun, Feb 08, 1998 at 07:02:45PM -0500, List Reader wrote: > People frequently send me PGP encrypted messages that do not have the > correct MIME type. I would like to be able to feed this to the PGP reader > in mutt and view it anyway. I don't mind if at this point I have to > enter some special menu or some key to do it -- so long as I don't have > to save it to disk and decode it by hand. I use procmail and formail to add/modify these MIME types to make mutt recognize the PGP data. Here is what the relevant portion of my .procmailrc looks like: ---cut--- # # PGP mail that doesn't have the proper Content-Type # # Add a "Content-Type: application/pgp" header so Mutt will know the # mail is encrypted. :0 fBw * ^-----BEGIN PGP MESSAGE----- { :0 fHw * ^Content-Type: *text/plain | formail -I "Content-Type: application/pgp; format=text; x-action=encryptsign" :0 fHw | formail -a "Content-Type: application/pgp; format=text; x-action=encryptsign" } # Add a "Content-Type: application/pgp" header so Mutt will know the # mail is signed. :0 fBw * ^-----BEGIN PGP SIGNED MESSAGE----- { :0 fHw * ^Content-Type: *text/plain | formail -I "Content-Type: application/pgp; format=text; x-action=sign" :0 fHw | formail -a "Content-Type: application/pgp; format=text; x-action=sign" } --- This is a modified version of a solution I found to this problem on a web page somewhere (sorry, I don't remember the URL or author). Originally, it would add a Content-type header for PGP only if the Content-type header didn't already exist. I modified it to override a Content-type header that already exists if it is incorrectly specifying text/plain. This .procmailrc makes procmail complain about an "extraneous filter flag" as it delivers mail, but it seems to work anyway, so I haven't tracked that problem down yet. If anyone sees what I did wrong, I'd appreciate a pointer to it. -- ::: John Randolph :::::::: linux 2.0.xx ::: PGP key: http://www.users.fast.net/~jrand/pgpkey.txt From eisenbud@allspice.cs.swarthmore.edu Sun Feb 8 17:19:04 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA06387 for ; Sun, 8 Feb 1998 17:18:59 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id UAA28275; Sun, 8 Feb 1998 20:18:59 -0500 (EST) Message-ID: <19980208201859.53475@cs.swarthmore.edu> Date: Sun, 8 Feb 1998 20:18:59 -0500 From: Daniel Eisenbud To: mutt-users@cs.hmc.edu Subject: Re: PGP mutt and MIME types Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208190245.18960@fever.semiotek.com> <19980208184142.46028@io.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Ty3Mrz/UPE2dbVgV" X-Mailer: Mutt 0.90.2i In-Reply-To: <19980208184142.46028@io.com>; from Manoj Kasichainula on Sun, Feb 08, 1998 at 06:41:42PM -0600 --Ty3Mrz/UPE2dbVgV Content-Type: text/plain; charset=us-ascii On Sun, Feb 08, 1998 at 06:41:42PM -0600, Manoj Kasichainula wrote: > On Sun, Feb 08, 1998 at 07:02:45PM -0500, List Reader wrote: > > People frequently send me PGP encrypted messages that do not have the > > correct MIME type. I would like to be able to feed this to the PGP reader > > in mutt and view it anyway.robably won't succeed :) > > > > I did check the documentation, but if I've missed where this question > > is answered please just point me to the right place and accept my > > apology for the stupid question. > > OK, check the FAQ. You'll find a procmail recipe to tag PGP messages > there. However, a better set of recipes than the one in the FAQ is the attached file. These work on messages with no content-type and also on messages that are text/plain, which catches some more cases. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu --Ty3Mrz/UPE2dbVgV Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="rc.oldpgp" :0 H * ^Content-Type: text/plain; charset=.*us-ascii.* { :0 fBw * ^-----BEGIN PGP MESSAGE----- | formail -I "Content-Type: application/pgp; format=text; x-action=encryptsign" :0 fBw * ^-----BEGIN PGP SIGNED MESSAGE----- | formail -I "Content-Type: application/pgp; format=text; x-action=sign" } # Add a "Content-Type: application/pgp" header so Mutt will know the # mail is encrypted. :0 fBw * ^-----BEGIN PGP MESSAGE----- | formail -a "Mime-Version: 1.0" -a "Content-Type: application/pgp; format=text; x-action=encryptsign" # Add a "Content-Type: application/pgp" header so Mutt will know the # mail is signed. :0 fBw * ^-----BEGIN PGP SIGNED MESSAGE----- | formail -a "Mime-Version: 1.0" -a "Content-Type: application/pgp; format=text; x-action=sign" --Ty3Mrz/UPE2dbVgV-- From michael@tis.com Sun Feb 8 17:58:58 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA10314 for ; Sun, 8 Feb 1998 17:58:57 -0800 (PST) Received: by relay.la.tis.com; id SAA12142; Sun, 8 Feb 1998 18:10:21 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma012138; Sun, 8 Feb 98 18:09:52 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id RAA05184; Sun, 8 Feb 1998 17:55:00 -0800 (PST) Message-ID: <19980208175500.26523@la.tis.com> Date: Sun, 8 Feb 1998 17:55:00 -0800 From: Michael Elkins To: Thomas Kluge , mutt-list Subject: Re: Macro-Problems with 0.89.1i Mail-Followup-To: Thomas Kluge , mutt-list References: <19980207103319.51095@darkstar.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980207103319.51095@darkstar.rhein-neckar.de>; from Thomas Kluge on Sat, Feb 07, 1998 at 10:33:19AM +0100 On Sat, Feb 07, 1998 at 10:33:19AM +0100, Thomas Kluge wrote: > with 0.88, i used this macro without problems: > > macro index a "!${EDITOR:-vi} $HOME/.mutt/aliases\n:source > ~/.mutt/aliases\n" In 0.89.x, Mutt attempt to expand environment varibles itself, but it does not understand the `:' syntax. You can force Mutt to not attempt to evaluate it (thus sending it to the shell) by using single quotes instead of double, or using backtics (backtic is a better choice here because \n will not get expanded with single quotes): macro index a "!\${EDITOR:-vi} $HOME/.mutt/aliases\n:source ~/.mutt/aliases\n" ^ note the backtic me From michael@tis.com Sun Feb 8 18:57:01 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id SAA19202 for ; Sun, 8 Feb 1998 18:56:58 -0800 (PST) Received: by relay.la.tis.com; id TAA12280; Sun, 8 Feb 1998 19:08:22 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma012276; Sun, 8 Feb 98 19:07:53 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id SAA05300; Sun, 8 Feb 1998 18:53:02 -0800 (PST) Message-ID: <19980208185302.24716@la.tis.com> Date: Sun, 8 Feb 1998 18:53:02 -0800 From: Michael Elkins To: Thomas Kluge , mutt-list Subject: Re: Macro-Problems with 0.89.1i Mail-Followup-To: Thomas Kluge , mutt-list References: <19980207103319.51095@darkstar.rhein-neckar.de> <19980208175500.26523@la.tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980208175500.26523@la.tis.com>; from Michael Elkins on Sun, Feb 08, 1998 at 05:55:00PM -0800 On Sun, Feb 08, 1998 at 05:55:00PM -0800, Michael Elkins wrote: > On Sat, Feb 07, 1998 at 10:33:19AM +0100, Thomas Kluge wrote: > > with 0.88, i used this macro without problems: > > > > macro index a "!${EDITOR:-vi} $HOME/.mutt/aliases\n:source > > ~/.mutt/aliases\n" > > In 0.89.x, Mutt attempt to expand environment varibles itself, but it does > not understand the `:' syntax. You can force Mutt to not attempt to > evaluate it (thus sending it to the shell) by using single quotes instead of > double, or using backtics (backtic is a better choice here because \n will > not get expanded with single quotes): > > macro index a "!\${EDITOR:-vi} $HOME/.mutt/aliases\n:source ~/.mutt/aliases\n" > ^ > note the backtic Someone just pointed out that I was hallucinating when I wrote that. I meant to say `backslash' instead of `backtic'. backslash => \ backtic => ` The example is correct, just the wrong word for the explanation ;) me From efraim@desire.argh.org Sun Feb 8 23:35:41 1998 Return-Path: efraim@desire.argh.org Received: from mail.provi.de (mail.provi.de [193.98.9.7]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id XAA08216 for ; Sun, 8 Feb 1998 23:35:38 -0800 (PST) Received: from news.hamburg.pop.de (claimed popnews.hamburg.pop.de, is IP 193.98.9.248) (root) by mail.provi.de with smtp (Exim 1.80 #2) id 0y1nlD-0003Qz-00; Mon, 9 Feb 1998 08:36:11 +0100 Received: from desire.argh.org by popnews.hamburg.pop.de with bsmtp (Smail3.2.0.95 #6) id m0y1nlw-00071RC; Mon, 9 Feb 1998 08:36:56 +0100 (MET) Received: from efraim by desire.argh.org with local (Exim 1.82 #1) id 0y1nfU-00080m-00 ; Mon, 9 Feb 1998 08:30:16 +0100 Message-ID: <19980209083016.06920@deadend.argh.org> Date: Mon, 9 Feb 1998 08:30:16 +0100 From: Alexander Koch To: mutt-users@cs.hmc.edu Subject: Re: PGP mutt and MIME types Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208190245.18960@fever.semiotek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980208190245.18960@fever.semiotek.com>; from "List Reader" on Sun, 08 Feb 1998 19:02:45 -0500 Sender: Alexander Koch Hiya. What are the correct macros for sending pgp keys (esc-k?) and extracting them from a plain file (esc-a)? What MIME-autoview-entries and what scripts are neccessary? Alexander -- ... Microsoft: Problems for a small planet. Alexander Koch - <>< - aka Efraim - PGP - 0xA78FB1E9 - Wedel - Germany From efraim@desire.argh.org Sun Feb 8 23:54:42 1998 Return-Path: efraim@desire.argh.org Received: from mail.provi.de (mail.provi.de [193.98.9.7]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id XAA11125 for ; Sun, 8 Feb 1998 23:54:38 -0800 (PST) Received: from news.hamburg.pop.de (claimed popnews.hamburg.pop.de, is IP 193.98.9.248) (root) by mail.provi.de with smtp (Exim 1.80 #2) id 0y1o3N-0003ga-00; Mon, 9 Feb 1998 08:54:57 +0100 Received: from desire.argh.org by popnews.hamburg.pop.de with bsmtp (Smail3.2.0.95 #6) id m0y1o46-00071RC; Mon, 9 Feb 1998 08:55:42 +0100 (MET) Received: from efraim by desire.argh.org with local (Exim 1.82 #1) id 0y1nzF-00088R-00 ; Mon, 9 Feb 1998 08:50:41 +0100 Message-ID: <19980209085040.08687@deadend.argh.org> Date: Mon, 9 Feb 1998 08:50:40 +0100 From: Alexander Koch To: mutt-users@cs.hmc.edu Subject: Re: PGP mutt and MIME types Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208190245.18960@fever.semiotek.com> <19980208184142.46028@io.com> <19980208201859.53475@cs.swarthmore.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980208201859.53475@cs.swarthmore.edu>; from "Daniel Eisenbud" on Sun, 08 Feb 1998 20:18:59 -0500 Sender: Alexander Koch On Sun, 8 February 1998 20:18:59 -0500, Daniel Eisenbud wrote: > :0 H > * ^Content-Type: text/plain; charset=.*us-ascii.* This didn't work with me. I know at least three different programs sending the plainest of all plain files in 8Bit, no matter if there're umlauts in it or not. I removed charset and it catches nearly all. Alexander From roessler@sobolev.rhein.de Mon Feb 9 04:34:55 1998 Return-Path: roessler@sobolev.rhein.de Received: from riemann.iam.uni-bonn.de (root@riemann.iam.uni-bonn.de [131.220.223.83]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id EAA21531 for ; Mon, 9 Feb 1998 04:34:51 -0800 (PST) Received: (from uucp@localhost) by riemann.iam.uni-bonn.de (8.8.8/8.8.5) with UUCP id NAA19424 for mutt-users@cs.hmc.edu; Mon, 9 Feb 1998 13:23:36 +0100 Received: (from roessler@localhost) by sobolev.rhein.de (8.8.8/8.8.8) id MAA25503 ; Mon, 9 Feb 1998 12:57:30 +0100 Message-ID: <19980209125730.52394@sobolev.rhein.de> Date: Mon, 9 Feb 1998 12:57:30 +0100 From: Thomas Roessler To: mutt-users@cs.hmc.edu Subject: Re: PGP mutt and MIME types Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208190245.18960@fever.semiotek.com> <19980209083016.06920@deadend.argh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.90.2i In-Reply-To: <19980209083016.06920@deadend.argh.org> On Mon, Feb 09, 1998 at 08:30:16AM +0100, Alexander Koch wrote: > What are the correct macros for sending pgp keys (esc-k?) > and extracting them from a plain file (esc-a)? eh? Just try esc-k and ctrl-k on the pager and browser menus; no autoview entries or scripts should be necessary. tlr -- Thomas Roessler · 74a353cc0b19 · dg1ktr · http://home.pages.de/~roessler/ 2048/CE6AC6C1 · 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1 From had@joker.pdas.cz Mon Feb 9 05:39:56 1998 Return-Path: had@joker.pdas.cz Received: from joker.pdas.cz (ujs1.pdpro.cz [194.108.144.32]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id FAA29355 for ; Mon, 9 Feb 1998 05:39:50 -0800 (PST) Received: (from had@localhost) by joker.pdas.cz (8.8.8/8.8.8) id OAA10099; Mon, 9 Feb 1998 14:39:14 +0100 Message-ID: <19980209143914.49711@pdas.cz> Date: Mon, 9 Feb 1998 14:39:14 +0100 From: Hanus Adler To: Mutt User List Subject: Searching in mail folders Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Hello, I'd like to switch from pine to mutt but I have a problem: I am trying to select (tag or limit) meesages in a folder based on what text they contain. However, I'm not able to find out how to tell mutt to search inside the folder -- all I get is search through From, To and Subject of the messages. Can anyone help me? Thanks, Hanus Adler -- Contrary to popular belief, Unix is user friendly. It just happens to be selective about who it makes friends with. -- Dave Parnas From mtsirkin@iil.intel.com Mon Feb 9 06:34:10 1998 Return-Path: mtsirkin@iil.intel.com Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id GAA05752 for ; Mon, 9 Feb 1998 06:34:09 -0800 (PST) Received: from iil.intel.com (iil-1.iil.intel.com [143.185.96.171]) by melete.ch.intel.com (8.8.6/8.8.5) with SMTP id OAA06151; Mon, 9 Feb 1998 14:34:05 GMT Received: from ilx347.iil.intel.com by iil.intel.com with SMTP id AA21995 (5.65c+/IDA-1.4.4); Mon, 9 Feb 1998 16:34:01 +0200 Received: by ilx347.iil.intel.com (AIX 4.1/UCB 5.64/IDC-RS6000-AIX-3.2) id AA56160; Mon, 9 Feb 1998 16:34:00 +0200 Message-Id: <19980209163358.07192@iil.intel.com> Date: Mon, 9 Feb 1998 16:33:58 +0200 From: "Michael S. Tsirkin" To: Hanus Adler , Mutt User List Subject: Re: Searching in mail folders Reply-To: "Michael S. Tsirkin" Mail-Followup-To: Hanus Adler , Mutt User List References: <19980209143914.49711@pdas.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.89 In-Reply-To: <19980209143914.49711@pdas.cz>; from "had@pdas.cz" on Mon, Feb 09, 1998 at 02:39:14PM +0100 X-Url: http://www.toptown.com/hp/mtsirkin Hello! /~b pattern is what you=A0want. hth mst Quoting r. Hanus Adler (had@pdas.cz) "Searching in mail folders": > Hello, >=20 > I'd like to switch from pine to mutt but I have a problem: I am trying > to select (tag or limit) meesages in a folder based on what text they > contain. However, I'm not able to find out how to tell mutt to search > inside the folder -- all I get is search through From, To and Subject of > the messages. >=20 > Can anyone help me? >=20 > Thanks, >=20 > Hanus Adler >=20 > --=20 > Contrary to popular belief, Unix is user friendly. > It just happens to be selective about who it makes friends with. > -- Dave Parnas 20 --=20 This message content is not part of Intel's views or affairs=0D Michael S. Tsirkin,32000, Technion, Canada dorms 44/3/3,Haifa,Israel; =0D Home:+972-4-8283001; Work:+972-4-8655658; =0D mailto:mtsirkin@usa.net; http://www.toptown.com/hp/mtsirkin/; =0D > Four things are to be strengthened: Torah,and good deeds,=0D > prayer and one's good manners (Berachoth)=0D From reptile@pooh.cs.net.pl Mon Feb 9 06:34:17 1998 Return-Path: reptile@pooh.cs.net.pl Received: from pooh.cs.net.pl (qmailr@pooh.cs.net.pl [195.117.250.7]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id GAA05771 for ; Mon, 9 Feb 1998 06:34:14 -0800 (PST) Received: (qmail 21700 invoked by uid 501); 9 Feb 1998 14:37:27 -0000 Message-ID: <19980209153724.48232@pooh.cs.net.pl> Date: Mon, 9 Feb 1998 15:37:24 +0100 From: "Robert Richard George 'reptile' Wal" To: mutt-users@cs.hmc.edu Subject: Re: Feature suggestion Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208183651.31124@trc-inc.com> <19980208181620.33974@umr.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980208181620.33974@umr.edu>; from Nathan Neulinger on Sun, Feb 08, 1998 at 06:16:20PM -0600 Organization: Me? Organized? Get real :) X-URL: http://pooh.cs.net.pl (Eternally under construction) X-IRC-Nick: Gadzinka@iRCnET.iRC.nETWORK (Gadzinka -- tiny little reptile) X-PGP-Fingerprint: 37E1D55F 29793C0C B8D39D01 61FC50CE X-PGP-Key: finger reptile@gryzmak.lodz.pdi.net X-Motto: Fact that you're paranoid doesn't imply that THEY don't follow you. X-Disclaimer: I don't answer mail or news articles below some arbitrary mark. X-Favourites: women, cats, Amiga, Linux, TeX, vim, music, sci-fi, poetry. X-Mount-Entry: mount -t human /dev/reptile /earth/europe/poland/warsaw On 98.02.09 Nathan Neulinger pressed the following keys: > Unless I remember incorrectly, the following will take care of that: > > editor=`somecommand` > > Where 'somecommand' is a script that would return the proper editor to use. editor=`if [ "$DISPLAY" = "" ] ; then echo vi ; else echo xjed ; fi` This should be enough, w/o external script (tested). Reptile -- mailto:reptile@pdi.net :) Women are more complicated than PC... :( Look into my headers and you'll see who I am. :) From vikasa@att.com Mon Feb 9 06:55:59 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw1.att.com [192.128.133.151]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id GAA08562 for ; Mon, 9 Feb 1998 06:55:45 -0800 (PST) Received: by kcgw1.att.com; Mon Feb 9 08:44 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id IAA26497; Mon, 9 Feb 1998 08:36:12 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id JAA18575; Mon, 9 Feb 1998 09:46:11 -0500 (EST) Message-ID: <19980209094611.34087@att.com> Date: Mon, 9 Feb 1998 09:46:11 -0500 From: Vikas Agnihotri To: Hanus Adler , Mutt User List Subject: Re: Searching in mail folders Mail-Followup-To: Hanus Adler , Mutt User List References: <19980209143914.49711@pdas.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 In-Reply-To: <19980209143914.49711@pdas.cz>; from Hanus Adler on Mon, Feb 09, 1998 at 02:39:14PM +0100 On Mon, Feb 09, 1998 at 02:39:14PM +0100, Hanus Adler wrote: > I'd like to switch from pine to mutt but I have a problem: I am trying > to select (tag or limit) meesages in a folder based on what text they > contain. However, I'm not able to find out how to tell mutt to search > inside the folder -- all I get is search through From, To and Subject of > the messages. Read Section 4.1.2 (Searching) of the manual. It explains all the various options you have for limiting/tagging of messages based on various criteria. You need the '~b' operator which searches the bodies of the messages. Vikas From cgg@netmaine.com Mon Feb 9 07:05:51 1998 Return-Path: cgg@netmaine.com Received: from netmaine.com (cgg@service.netmaine.com [199.191.0.2]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id HAA09710 for ; Mon, 9 Feb 1998 07:05:49 -0800 (PST) Received: (from cgg@localhost) by netmaine.com (8.8.5/1.0.0) id KAA16711; Mon, 9 Feb 1998 10:05:48 -0500 (EST) Message-ID: <19980209100547.29488@netmaine.com> Date: Mon, 9 Feb 1998 10:05:47 -0500 From: Chock Griebel To: Mutt User List Subject: Color under BSDI 2.1 Mail-Followup-To: Mutt User List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89 Organization: NMI/IES (http://www.nmi.net) Does anyone have color working properly under BSDI 2.1. I tried compiling in S-Lang and then curses and I couldn't get colors to work. I _can_ get color Vim working great so I suspect that I need to change compile options for mutt. Following the suggestions in the FAQ, I have tried setting XTERM to xterm-color (then I get only blue and yellow and they're puky to say the least). I have also upgraded screen and run mutt under it and colors come out great but vim does from SEGV under screen. I can't have that. I appreciate any help and I apologize if this has been asked before (I'm new to the list). Chock Griebel cgg@netmaine.com From god@omegazone.dyn.ml.org Mon Feb 9 07:18:25 1998 Return-Path: god@omegazone.dyn.ml.org Received: from omegazone.dyn.ml.org (root@d1-ts06.amug.org [198.182.127.130]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id HAA11129 for ; Mon, 9 Feb 1998 07:18:12 -0800 (PST) Received: by omegazone.dyn.ml.org id m0y1uyc-000VRgC (Debian Smail-3.2 1996-Jul-4 #2); Mon, 9 Feb 1998 08:18:30 -0700 (MST) Message-ID: <19980209081830.27842@amug.org> Date: Mon, 9 Feb 1998 08:18:30 -0700 From: alucard@amug.org To: Mutt User List Subject: To and From Mail-Followup-To: Mutt User List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 I have noticed that my mutt sometimes switches from showing the From Field, to showing the To field. Is there a way to toggle this back. If I quit mutt, and restart, all my messages show who sent them. Any ideas on this? From vikasa@att.com Mon Feb 9 07:26:27 1998 Return-Path: vikasa@att.com Received: from att.com (kcgw2.att.com [192.128.133.152]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id HAA12299 for ; Mon, 9 Feb 1998 07:26:23 -0800 (PST) Received: by kcgw2.att.com; Mon Feb 9 09:09 CST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id JAA02283 for ; Mon, 9 Feb 1998 09:14:00 -0600 (CST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id KAA18714; Mon, 9 Feb 1998 10:24:19 -0500 (EST) Message-ID: <19980209102419.17109@att.com> Date: Mon, 9 Feb 1998 10:24:19 -0500 From: Vikas Agnihotri To: Mutt users mailing list Subject: Capitalizing headers? Mail-Followup-To: Mutt users mailing list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2 Some of the mails I get have, case-mangled headers like 'from:' instead of 'From:' and subject: instead of Subject: I am not positive, but I think that in the past, Mutt used to display these mails in the pager with the first letter of the header capitalized. I dont see that anymore in 0.89. It just shows me what is in my folder. I realize that, per RFCs, header-names are case-insensitive, but... Just a nit really, but it _would_ be aesthetically more pleasing to 'normalize' headers in this fashion when showing them in the pager. IMHO, of course. Thanks, Vikas From rnapier@cisco.com Mon Feb 9 07:50:54 1998 Return-Path: rnapier@cisco.com Received: from claret.cisco.com (claret.cisco.com [171.69.160.39]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id HAA15422 for ; Mon, 9 Feb 1998 07:50:52 -0800 (PST) Received: (rnapier@localhost) by claret.cisco.com (8.8.4-Cisco.1/8.6.5) id KAA18479; Mon, 9 Feb 1998 10:50:00 -0500 (EST) Message-ID: <19980209104959.53543@cisco.com> Date: Mon, 9 Feb 1998 10:49:59 -0500 From: Robert Napier To: Mutt users mailing list Subject: Re: Capitalizing headers? Mail-Followup-To: Mutt users mailing list References: <19980209102419.17109@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980209102419.17109@att.com>; from Vikas Agnihotri on Mon, Feb 09, 1998 at 10:24:19AM -0500 procmail is probably you're best solution to fixing this up before mutt sees it (that way it's "really" fixed, rather than just displayed). Rob On Mon, Feb 09, 1998 at 10:24:19AM -0500, Vikas Agnihotri wrote: > Some of the mails I get have, case-mangled headers like 'from:' instead of > 'From:' and subject: instead of Subject: > > I am not positive, but I think that in the past, Mutt used to display these > mails in the pager with the first letter of the header capitalized. I dont > see that anymore in 0.89. It just shows me what is in my folder. > > I realize that, per RFCs, header-names are case-insensitive, but... > > Just a nit really, but it _would_ be aesthetically more pleasing to > 'normalize' headers in this fashion when showing them in the pager. > > IMHO, of course. > > Thanks, > Vikas > -- Rob Napier | 7025 Kit Creek Road | Check out Triangle Ascension: rnapier@cisco.com | PO Box 14987 | http://www.serve.com/napier/mage 919/472-3941 | RTP, NC 27709 | +===========================================================================+ | Imagine what my body would sound like / Slamming against those rocks | | When it lands / Will my eyes / Be closed or open? -- Bjork "Hyper Ballad" | +===========================================================================+ From fox@fuzzy.rsn.hp.com Mon Feb 9 10:19:52 1998 Return-Path: fox@fuzzy.rsn.hp.com Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA07641 for ; Mon, 9 Feb 1998 10:19:49 -0800 (PST) Received: from fuzzy.rsn.hp.com (fox@fuzzy.rsn.hp.com [15.99.4.115]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id KAA22457 for ; Mon, 9 Feb 1998 10:19:45 -0800 (PST) Received: (from fox@localhost) by fuzzy.rsn.hp.com (8.7.1/8.7.1) id MAA07181; Mon, 9 Feb 1998 12:19:44 -0600 (CST) Message-ID: <19980209121943.20974@rsn.hp.com> Date: Mon, 9 Feb 1998 12:19:43 -0600 From: David DeSimone To: Mutt Heads Subject: Re: PGP-signing complaint Mail-Followup-To: Mutt Heads References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> <19980206162046.44948@rsn.hp.com> <19980207024313.61270@matrix.42.org> <19980207124809.27088@freebie.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=RRV7LY7NUeQGEoCm X-Mailer: Mutt 0.89i In-Reply-To: <19980207124809.27088@freebie.lemis.com>; from Greg Lehey on Sat, Feb 07, 1998 at 12:48:09PM +1030 --RRV7LY7NUeQGEoCm Content-Type: text/plain; charset=us-ascii Greg Lehey wrote: > > It seems to me that if you're going to PGP sign your messages, you > should provide some independent way of verifying the message, such as > a web page address. When I want to verify a signature (like this one, from you), I go to the PGP keyservers, which is sort of an "independent" source. Is it more trustworthy than the user's web page? Mmm... I dunno. :) -- David DeSimone | "The doctrine of human equality reposes on this: fox@rsn.hp.com | 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 --RRV7LY7NUeQGEoCm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNN9IvA0lGhIp2tThAQHznQMAxZfYodVvts8Kv2F5WaJ+BCZDter23cLx OqKcgQZ22q30vbsE61jdA11HFodw2KmNa4yEc3tjffYAciaYRPgj6J71W7O2kgn5 K/sSgseYKEHpqVMm543cQeTVnWHk/a2V =xC8n -----END PGP SIGNATURE----- --RRV7LY7NUeQGEoCm-- From michael@tis.com Mon Feb 9 10:29:58 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA09100 for ; Mon, 9 Feb 1998 10:29:57 -0800 (PST) Received: by relay.la.tis.com; id KAA17648; Mon, 9 Feb 1998 10:41:21 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma017635; Mon, 9 Feb 98 10:41:00 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id KAA08253; Mon, 9 Feb 1998 10:26:02 -0800 (PST) Message-ID: <19980209102601.30810@la.tis.com> Date: Mon, 9 Feb 1998 10:26:01 -0800 From: Michael Elkins To: Mutt User List Subject: Re: To and From Mail-Followup-To: Mutt User List References: <19980209081830.27842@amug.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980209081830.27842@amug.org>; from alucard@amug.org on Mon, Feb 09, 1998 at 08:18:30AM -0700 On Mon, Feb 09, 1998 at 08:18:30AM -0700, alucard@amug.org wrote: > I have noticed that my mutt sometimes switches from showing the From > Field, to showing the To field. Is there a way to toggle this back. If I > quit mutt, and restart, all my messages show who sent them. Any ideas on > this? The default $hdr_format uses %L which will show who the mail was sent To: when either you are the sender or Mutt finds a matching `lists' entry. If you always want to see the sender, you can use %n or %F (see the manual for details). me From michael@tis.com Mon Feb 9 10:32:31 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA09519 for ; Mon, 9 Feb 1998 10:32:26 -0800 (PST) Received: by relay.la.tis.com; id KAA17686; Mon, 9 Feb 1998 10:43:51 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma017677; Mon, 9 Feb 98 10:43:47 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id KAA08475; Mon, 9 Feb 1998 10:28:48 -0800 (PST) Message-ID: <19980209102848.56990@la.tis.com> Date: Mon, 9 Feb 1998 10:28:48 -0800 From: Michael Elkins To: Mutt users mailing list Subject: Re: Capitalizing headers? Mail-Followup-To: Mutt users mailing list References: <19980209102419.17109@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980209102419.17109@att.com>; from Vikas Agnihotri on Mon, Feb 09, 1998 at 10:24:19AM -0500 On Mon, Feb 09, 1998 at 10:24:19AM -0500, Vikas Agnihotri wrote: > Some of the mails I get have, case-mangled headers like 'from:' instead of > 'From:' and subject: instead of Subject: > > I am not positive, but I think that in the past, Mutt used to display these > mails in the pager with the first letter of the header capitalized. I dont > see that anymore in 0.89. It just shows me what is in my folder. > > I realize that, per RFCs, header-names are case-insensitive, but... > > Just a nit really, but it _would_ be aesthetically more pleasing to > 'normalize' headers in this fashion when showing them in the pager. > > IMHO, of course. Mutt does not alter your mail except to add things like content-length, and status information. Nor has it even normalized the display. I think your best bet is to use something like procmail if you want to reformat your mail. me From lillqvis@cc.helsinki.fi Mon Feb 9 10:34:16 1998 Return-Path: lillqvis@cc.helsinki.fi Received: from kontti.Helsinki.FI (lillqvis@kontti.helsinki.fi [128.214.205.13]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA09689 for ; Mon, 9 Feb 1998 10:34:11 -0800 (PST) Received: (from lillqvis@localhost) by kontti.Helsinki.FI (8.8.8-spammers-bug-off/8.8.0) id UAA20835; Mon, 9 Feb 1998 20:34:08 +0200 (EET) Message-ID: <19980209203408.25056@kontti.Helsinki.FI> Date: Mon, 9 Feb 1998 20:34:08 +0200 From: Holger Lillqvist To: Mutt User List Subject: Re: To and From References: <19980209081830.27842@amug.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980209081830.27842@amug.org> Quoting alucard@amug.org (alucard@amug.org): > I have noticed that my mutt sometimes switches from showing the From > Field, to showing the To field. Is there a way to toggle this back. If I > quit mutt, and restart, all my messages show who sent them. Any ideas on > this? Hmm, seems that you have messed up something with your folder-hooks.. Check your .muttrc. For example, if you have a folder-hook for your `sent' folder which sets the hdr_format to use `%F' or `%t' (index shows To: field) instead of `%n', you also need a default folder-hook to reset the format when you change to another folder. It could be something like this: folder-hook . 'set hdr_format="%3C %Z %{%d/%m} %-16.16n (%2l) %s"' folder-hook sent 'set hdr_format="%3C %Z %{%d/%m} %-16.16F (%2l) %s"' Holger From michael@tis.com Mon Feb 9 10:34:29 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA09731 for ; Mon, 9 Feb 1998 10:34:26 -0800 (PST) Received: by relay.la.tis.com; id KAA17708; Mon, 9 Feb 1998 10:45:51 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma017705; Mon, 9 Feb 98 10:45:50 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id KAA08667; Mon, 9 Feb 1998 10:30:51 -0800 (PST) Message-ID: <19980209103051.63486@la.tis.com> Date: Mon, 9 Feb 1998 10:30:51 -0800 From: Michael Elkins To: mutt-users@cs.hmc.edu Subject: Re: quote_regexp Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208085002.39940@csci.uark.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980208085002.39940@csci.uark.edu>; from Sadiq Al-Lawatia on Sun, Feb 08, 1998 at 08:50:02AM -0600 On Sun, Feb 08, 1998 at 08:50:02AM -0600, Sadiq Al-Lawatia wrote: > Am quite new to mutt and to its .muttrc file and I would like to know > what quote_regexp is in simple english pls :-) Was the manual not clear on this subject? $quote_regexp is a regular expression used to match the `quoting' strings that you see in front of text when you reply to someone elses message. For example, the text of your message above has ` >' in front of each line. $quote_regexp is used to find quoted text so that it can be displayed in a special color in the pager (using `color quoted ...'). me From michael@tis.com Mon Feb 9 10:37:57 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA10286 for ; Mon, 9 Feb 1998 10:37:56 -0800 (PST) Received: by relay.la.tis.com; id KAA17875; Mon, 9 Feb 1998 10:49:21 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma017871; Mon, 9 Feb 98 10:49:18 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id KAA08774; Mon, 9 Feb 1998 10:34:19 -0800 (PST) Message-ID: <19980209103419.59208@la.tis.com> Date: Mon, 9 Feb 1998 10:34:19 -0800 From: Michael Elkins To: Jim Murphy , mutt-users@cs.hmc.edu Subject: Re: internal pager Mail-Followup-To: Jim Murphy , mutt-users@cs.hmc.edu References: <199802050512.AAA15409@po_box.cig.mot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <199802050512.AAA15409@po_box.cig.mot.com>; from Jim Murphy on Wed, Feb 04, 1998 at 11:08:28PM -0600 On Wed, Feb 04, 1998 at 11:08:28PM -0600, Jim Murphy wrote: > Can someone tell me is there a way to get the internal pager to recognize > a "^L"(ctrl-L) in the body, and put the next part of the document at the > top of the next page it displays? I always found this a nice feature in > Elm when viewing a report with multiple sections. This made the document > much easier to read. So far I have not been able to find anything that > would indicate that this is currently possible. Mutt does not support this, but it does sound like it would be somewhat useful. me From lillqvis@cc.helsinki.fi Mon Feb 9 10:43:26 1998 Return-Path: lillqvis@cc.helsinki.fi Received: from kontti.Helsinki.FI (lillqvis@kontti.helsinki.fi [128.214.205.13]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA11015 for ; Mon, 9 Feb 1998 10:43:24 -0800 (PST) Received: (from lillqvis@localhost) by kontti.Helsinki.FI (8.8.8-spammers-bug-off/8.8.0) id UAA00752; Mon, 9 Feb 1998 20:43:22 +0200 (EET) Message-ID: <19980209204322.26263@kontti.Helsinki.FI> Date: Mon, 9 Feb 1998 20:43:22 +0200 From: Holger Lillqvist To: mutt-users@cs.hmc.edu Subject: Suggestion: skip beyond quote Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In slrn, there are two commands that have to do with reading stuff which contains quoted text: toggle display of quotes (similar to mutt's), and skip beyond quote, a command which scrolls ahead to the next non-quoted paragraph and places it on top of the screen. I use this function quite a lot, and have found it more useful than totally hiding the quoted context. This feature would be nice in mutt, too. Holger From blong@shell9.ba.best.com Mon Feb 9 10:54:36 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA13018 for ; Mon, 9 Feb 1998 10:54:35 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id KAA26566; Mon, 9 Feb 1998 10:54:21 -0800 (PST) Message-ID: <19980209105421.53605@shell9.ba.best.com> Date: Mon, 9 Feb 1998 10:54:21 -0800 From: Brandon Long To: Mutt User List Subject: Re: To and From Reply-To: blong@fiction.net Mail-Followup-To: Mutt User List References: <19980209081830.27842@amug.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980209081830.27842@amug.org>; from alucard@amug.org on Mon, Feb 09, 1998 at 08:18:30AM -0700 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/09/98 alucard@amug.org uttered the following other thing: > I have noticed that my mutt sometimes switches from showing the From > Field, to showing the To field. Is there a way to toggle this back. If I > quit mutt, and restart, all my messages show who sent them. Any ideas on > this? I thought the only reason mutt would show to is if it finds your address (listed in $alternates) in the From field, but it shouldn't switch unless you change the alternates variable. Brandon -- Brandon Long "If organized religion is the opium of the masses, MD6 Crash Test Dummy then disorganized religion is the marijuana of the Intel Corporation lunatic fringe." -- Kerry Thornley, "Principia" I'm too low on the totem pole to speak for Intel. http://www.fiction.net/blong/ From blong@shell9.ba.best.com Mon Feb 9 10:55:40 1998 Return-Path: blong@shell9.ba.best.com Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA13163 for ; Mon, 9 Feb 1998 10:55:38 -0800 (PST) Received: (from blong@localhost) by shell9.ba.best.com (8.8.8/8.8.BEST) id KAA26773; Mon, 9 Feb 1998 10:55:06 -0800 (PST) Message-ID: <19980209105506.13620@shell9.ba.best.com> Date: Mon, 9 Feb 1998 10:55:06 -0800 From: Brandon Long To: Mutt users mailing list Subject: Re: Capitalizing headers? Reply-To: blong@fiction.net Mail-Followup-To: Mutt users mailing list References: <19980209102419.17109@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88.14i In-Reply-To: <19980209102419.17109@att.com>; from Vikas Agnihotri on Mon, Feb 09, 1998 at 10:24:19AM -0500 Organization: Fiction L Networks X-Pgp-Public-Key: X-Uri: On 02/09/98 Vikas Agnihotri uttered the following other thing: > Some of the mails I get have, case-mangled headers like 'from:' instead of > 'From:' and subject: instead of Subject: > > I am not positive, but I think that in the past, Mutt used to display these > mails in the pager with the first letter of the header capitalized. I dont > see that anymore in 0.89. It just shows me what is in my folder. No, mutt doesn't mangle headers, all it does is decode them. Brandon -- Brandon Long "Quantum Mechanics: The dreams stuff is made of" Fiction Networks -- Steven Wright blong@fiction.net http://www.fiction.net/blong/ From eisenbud@allspice.cs.swarthmore.edu Mon Feb 9 11:27:56 1998 Return-Path: eisenbud@allspice.cs.swarthmore.edu Received: from allspice.cs.swarthmore.edu (allspice.cs.swarthmore.edu [130.58.68.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA18403 for ; Mon, 9 Feb 1998 11:27:53 -0800 (PST) Received: (from eisenbud@localhost) by allspice.cs.swarthmore.edu (8.8.8/8.8.8) id OAA16265; Mon, 9 Feb 1998 14:27:52 -0500 (EST) Message-ID: <19980209142752.36393@cs.swarthmore.edu> Date: Mon, 9 Feb 1998 14:27:52 -0500 From: Daniel Eisenbud To: mutt-users@cs.hmc.edu Subject: Re: Suggestion: skip beyond quote Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980209204322.26263@kontti.Helsinki.FI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980209204322.26263@kontti.Helsinki.FI>; from Holger Lillqvist on Mon, Feb 09, 1998 at 08:43:22PM +0200 On Mon, Feb 09, 1998 at 08:43:22PM +0200, Holger Lillqvist wrote: > In slrn, there are two commands that have to do with reading stuff which > contains quoted text: toggle display of quotes (similar to mutt's), and > skip beyond quote, a command which scrolls ahead to the next non-quoted > paragraph and places it on top of the screen. I use this function quite > a lot, and have found it more useful than totally hiding the quoted > context. This feature would be nice in mutt, too. This sounds like it might not be that hard. I don't know the pager that well, but I'll try to take a look later this week. -Daniel -- Daniel Eisenbud eisenbud@cs.swarthmore.edu From roessler@sobolev.rhein.de Mon Feb 9 12:08:14 1998 Return-Path: roessler@sobolev.rhein.de Received: from riemann.iam.uni-bonn.de (root@riemann.iam.uni-bonn.de [131.220.223.83]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA24866 for ; Mon, 9 Feb 1998 12:08:09 -0800 (PST) Received: from sobolev.rhein.de (roessler@sobolev.iam.uni-bonn.de [131.220.223.85]) by riemann.iam.uni-bonn.de (8.8.8/8.8.5) with ESMTP id VAA28330 for ; Mon, 9 Feb 1998 21:08:08 +0100 Received: (from roessler@localhost) by sobolev.rhein.de (8.8.8/8.8.8) id VAA09851 ; Mon, 9 Feb 1998 21:08:01 +0100 Message-ID: <19980209210800.16246@sobolev.rhein.de> Date: Mon, 9 Feb 1998 21:08:00 +0100 From: Thomas Roessler To: "The mutt users' list" Subject: [0.89.1i] PGP-bugfixes roll-up patch Mail-Followup-To: The mutt users' list Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=U+BazGySraz5kW0T X-Mailer: Mutt 0.90.2i --U+BazGySraz5kW0T Content-Type: multipart/mixed; boundary="/9DWx/yDrRhgMJTb" --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable The attached patch contains various PGP related bug-fixes. It is taken against a vanilla 0.89.1i version. tlr --=20 Thomas Roessler =B7 74a353cc0b19 =B7 dg1ktr =B7 http://home.pages.de/~roess= ler/ 2048/CE6AC6C1 =B7 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="mutt-0.89.1i.pl1.diff" This file contains various PGP-related bug-fixes relative to Mutt 0.89.1i. Fixed bugs include: - On the compose menu, adding a PGP public key as the 5th attachment would lead to a core dump. - When extracting public keys from attachments, a random garbage prefix would be printed in front of every line. - The PGP 5 invocation code contained several typographic errors. - When displaying a singed (but not encrypted) message's attachments, mutt would ask you for your pass phrase. - When referencing PGP 5 subkeys, the corresponding "main" key's ID is now used. This seems to be the correct behaviour. Most of these patches are contained in the development version 0.90.2i; all will be included in 0.90.3i. tlr , 98-02-09 diff -urN /var/tmp/mutt-0.89.1i/compose.c mutt-0.89.1i/compose.c --- /var/tmp/mutt-0.89.1i/compose.c Fri Jan 23 08:08:55 1998 +++ mutt-0.89.1i/compose.c Mon Feb 9 20:58:18 1998 @@ -426,7 +426,10 @@ case OP_COMPOSE_ATTACH_KEY: =20 if (idxlen =3D=3D idxmax) + { safe_realloc ((void **) &idx, sizeof (ATTACHPTR *) * (idxmax +=3D 5)); + menu->data =3D idx; + } =09 idx[idxlen] =3D (ATTACHPTR *) safe_calloc (1, sizeof (ATTACHPTR)); if ((idx[idxlen]->content =3D pgp_make_key_attachment(NULL)) !=3D NULL) @@ -732,6 +735,7 @@ case OP_FILTER: CHECK_COUNT; mutt_pipe_attachment_list (NULL, menu->tagprefix, menu->tagprefix ? msg->= content : idx[menu->current]->content, op =3D=3D OP_FILTER); + menu->redraw =3D REDRAW_CURRENT; break; =20 case OP_EXIT: diff -urN /var/tmp/mutt-0.89.1i/doc/pgp-Notes.txt mutt-0.89.1i/doc/pgp-Note= s.txt --- /var/tmp/mutt-0.89.1i/doc/pgp-Notes.txt Sat Jan 31 14:12:57 1998 +++ mutt-0.89.1i/doc/pgp-Notes.txt Mon Feb 9 20:58:41 1998 @@ -33,41 +33,6 @@ =20 =20 =20 -Q: "Why doesn't this work with PGP 5.0i-b8?" - -Because pgp-5.0i-b8 is not usable for our purpose: - -=B7 pgp-5.0i-b8 doesn't support passing the pass phrase - through a previously-openend file descriptor (aka - PGPPASSFD). This non-existing feature is required by - mutt. - -=B7 pgp-5.0i-b8 doesn't support redirecting specific parts - of it's output to certain file descriptors (aka - --OutputInformationFD). - -But don't despair, the folks at www.pgpi.com are -apparently working on a legally exported Unix release -version of PGP which will most probably be able to do what -we need. - - - -Q: "Why don't you use the SDK? It's available on the net!" - -The old answer on this question said something about -illegal export and so on. Well, www.pgpi.com has the SDK -for quite some time now, so we could actually start using -it. =20 - -But by now, most of the code needed to do the things we -want to do is in place, and it's mostly independent of the -PGP version you are using - PGP 5.*, PGP 2.*, g10. Support -for other versions can easily be added by changing -pgpinvoke.c. - - - Q: "People are sending PGP messages which mutt doesn't recognize. What can I do?" =20 @@ -113,6 +78,7 @@ ------------------------------ =20 =20 + Q: "I don't like that PGP/MIME stuff, but want to use the old way of PGP-signing my mails. Can't you include that with mutt?" @@ -130,8 +96,3 @@ =20 =20 =20 -If you encounter any bugs with mutt's PGP integration, -please drop me a short note about what happens, how to -reproduce it without illegally exporting PGP 5* from the -U.S. and how to fix the problem. I'll happily integrate -any fixes with mutt's PGP support.=20 diff -urN /var/tmp/mutt-0.89.1i/pgp.c mutt-0.89.1i/pgp.c --- /var/tmp/mutt-0.89.1i/pgp.c Sat Jan 31 14:12:57 1998 +++ mutt-0.89.1i/pgp.c Mon Feb 9 20:58:34 1998 @@ -111,6 +111,9 @@ =20 char *pgp_keyid(KEYINFO *k) { + if((k->flags & KEYFLAG_SUBKEY) && k->mainkey) + k =3D k->mainkey; + if(option(OPTPGPLONGIDS)) return k->keyid; else @@ -584,6 +587,8 @@ return; } =20 + memset(&s, 0, sizeof(STATE)); + =20 mutt_mktemp(tempfname); if(!(s.fpout =3D safe_fopen(tempfname, "w"))) { @@ -645,9 +650,12 @@ mutt_perror(tempfname); return; } + + memset(&s, 0, sizeof(STATE)); + =20 s.fpin =3D fp; s.fpout =3D tempfp; - + =20 mutt_body_handler(top, &s); =20 fclose(tempfp); @@ -676,10 +684,9 @@ pgp_extract_keys_from_attachment (fp, top); =20 if(!tag) - return; + break; } =20 - mutt_any_key_to_continue(NULL); unset_option(OPTDONTHANDLEPGPKEYS); } =20 diff -urN /var/tmp/mutt-0.89.1i/pgpinvoke.c mutt-0.89.1i/pgpinvoke.c --- /var/tmp/mutt-0.89.1i/pgpinvoke.c Fri Jan 23 08:07:44 1998 +++ mutt-0.89.1i/pgpinvoke.c Mon Feb 9 20:58:00 1998 @@ -235,7 +235,7 @@ break; =20 case PGP3: - snprintf(cmd, sizeof(cmd), "%sk +pubring=3D%s +secring=3D%s --Output= InformationFD=3D1 %s", + snprintf(cmd, sizeof(cmd), "%sk +pubring=3D%s +secring=3D%s -a --Out= putInformationFD=3D1 %s", Pgp, PgpPubring, PgpSecring, fname); break; =20 @@ -289,7 +289,7 @@ break; =20 case PGP3: - snprintf(cmd, sizeof(cmd), "sk -xa +pubring=3D%s +secring=3D%s --Out= putInformationFD=3D1 0x%8s", + snprintf(cmd, sizeof(cmd), "%sk -xa +pubring=3D%s +secring=3D%s --Ou= tputInformationFD=3D1 0x%8s", Pgp, PgpPubring, PgpSecring, id); break; =20 diff -urN /var/tmp/mutt-0.89.1i/recvattach.c mutt-0.89.1i/recvattach.c --- /var/tmp/mutt-0.89.1i/recvattach.c Tue Jan 27 10:04:35 1998 +++ mutt-0.89.1i/recvattach.c Mon Feb 9 20:58:21 1998 @@ -456,7 +456,14 @@ return; =20 #ifdef _PGPPATH - if (hdr->pgp =3D=3D PGPENCRYPT && hdr->content->type =3D=3D TYPEMULTIPAR= T) + =20 + if((hdr->pgp & PGPENCRYPT) && !pgp_valid_passphrase()) + { + mx_close_message(&msg); + return; + } + =20 + if ((hdr->pgp & PGPENCRYPT) && hdr->content->type =3D=3D TYPEMULTIPART) { STATE s; =20 @@ -561,7 +568,7 @@ case OP_LIST_REPLY: case OP_FORWARD_MESSAGE: #ifdef _PGPPATH - if (hdr->pgp =3D=3D PGPENCRYPT && hdr->content->type =3D=3D TYPEMULTIPART) + if ((hdr->pgp & PGPENCRYPT) && hdr->content->type =3D=3D TYPEMULTIPART) { mutt_error ( "This operation is not currently supported for PGP messages."); diff -urN /var/tmp/mutt-0.89.1i/send.c mutt-0.89.1i/send.c --- /var/tmp/mutt-0.89.1i/send.c Sat Jan 31 14:13:06 1998 +++ mutt-0.89.1i/send.c Mon Feb 9 20:58:21 1998 @@ -361,7 +361,7 @@ #ifdef _PGPPATH if (cur->pgp) { - if (cur->pgp =3D=3D PGPENCRYPT) + if (cur->pgp & PGPENCRYPT) { /* make sure we have the user's passphrase before proceeding... */ pgp_valid_passphrase (); @@ -940,9 +940,9 @@ msg->pgp |=3D PGPSIGN; if (option (OPTPGPAUTOENCRYPT)) msg->pgp |=3D PGPENCRYPT; - if (option (OPTPGPREPLYENCRYPT) && cur && cur->pgp =3D=3D PGPENCRYPT) + if (option (OPTPGPREPLYENCRYPT) && cur && cur->pgp & PGPENCRYPT) msg->pgp |=3D PGPENCRYPT; - if (option (OPTPGPREPLYSIGN) && cur && cur->pgp =3D=3D PGPSIGN) + if (option (OPTPGPREPLYSIGN) && cur && cur->pgp & PGPSIGN) msg->pgp |=3D PGPSIGN; } #endif /* _PGPPATH */ --/9DWx/yDrRhgMJTb-- --U+BazGySraz5kW0T Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use iQEVAwUBNN9iHNImKUTOasbBAQHNUQgApngbIpERi1Bz5vxPlBspMF8Fjyd1K9BJ /Cx0cnCzxGe3ovI418fYMP1yCdcF39rf56pLlvzXsZFa1kFNHPwUjSQ85LaBma0b wpb5EtDnUItAaSWBBdibnT36YX4hcHBGMWQZiL8wEfkqtum5Zr60WXSzBAz9WMWf Sg2PjWl/9xYJUQv8szUJsbHHQnUDKTZ5n6GegpIKLtxFH36RnaoJjiWRsOpxLvDf FfRN2DP082qzSGhi8PXi9ehKyA8D1Rj3kKM9f7e41ML2xHeJuV0oD9FZUWex5gui e8IDzn2/AHMyOZzEbCzbzSu5GLnZ1tZ24lg0dOTGO0zQfbHqx+oBPw== =1/Zr -----END PGP SIGNATURE----- --U+BazGySraz5kW0T-- From fog.in-berlin.de!rainbow.in-berlin.de!rj@calle.in-berlin.de Mon Feb 9 12:11:55 1998 Return-Path: fog.in-berlin.de!rainbow.in-berlin.de!rj@calle.in-berlin.de Received: from methan.in-berlin.de (methan.in-berlin.de [160.45.10.13]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id MAA25254 for ; Mon, 9 Feb 1998 12:11:25 -0800 (PST) Received: by methan.in-berlin.de (Smail3.2.0.98) from calle.in-berlin.de (193.175.21.97) with esmtp id ; Mon, 9 Feb 1998 21:11:11 +0100 (MET) Received: by calle.in-berlin.de (Smail3.2.0.98) from fog.in-berlin.de with bsmtp id ; Mon, 9 Feb 1998 21:11:09 +0100 (MET) Received: from rainbow.in-berlin.de(rainbow.internal[192.168.144.1]) (3428 bytes) by fog.in-berlin.de via sendmail with P:esmtp/R:smart_host/T:uusmtp (sender: ) id for ; Mon, 9 Feb 1998 20:17:34 +0100 (MET) (Smail-3.2.0.98 1997-Oct-16 #2 built 1998-Jan-8) Received: from localhost (3011 bytes) by rainbow.in-berlin.de via sendmail with P:stdio/R:smart_host/T:smtp (sender: ) (ident using unix) id for ; Mon, 9 Feb 1998 20:17:30 +0100 (MET) (Smail-3.2.0.101 1997-Dec-17 #2 built 1998-Jan-3) Message-ID: <19980209201729.14337@rainbow.in-berlin.de> Date: Mon, 9 Feb 1998 20:17:29 +0100 From: Robert Joop To: mutt-users@cs.hmc.edu Subject: Re: suggestion: variable attribution References: <19971217172343.46122@home.fokus.gmd.de> <19971217101527.34124@zzyzx.la.tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19971217101527.34124@zzyzx.la.tis.com>; from Michael Elkins on Wed, Dec 17, 1997 at 10:15:27AM -0800 On 97-12-17 19:15:27 MET, Michael Elkins wrote: > On Wed, Dec 17, 1997 at 05:23:43PM +0100, Robert Joop wrote: > > i'd like to have a different $attribution depending on who i'm > > responding to. > > > > when i'm replying to a mail in the same timezone, i'd like to have a > > simple attribution, > > when i'm replying to a mail in a different timezone, i'd like to have an > > attribution that indicates the time the mail has been sent expressed in > > both timezones, the correspondent's and mine. > > > > set attribution="`...`" > > does not work because it is evaluated only once. even > > send-hook . set attribution="`...`" > > is executed just once! (seems to get optimized away. setting > > send-hook . set attribution="`date`" > > and replying to one mail gives me "Wed Dec 17 16:57:33 MET 1997", > > replying to another email gives me that same string again.) > > You will be able to have the backtics expanded when the hook is evaluated in > the next version of Mutt. The quoting rules have changed to be similar to > many popular shell programs so you can just do: > send-hook . set attribution='"`date`"' > the single quotes cause the backtics not to be expanded immediately. michael, the new functionality still doesn't give me the necessary tool to get what i want. i intended to call an external program that compares its arguments and echoes all or only a few of them. send-hook . 'set attribution="`$HOME/.mutt/attrib \"%{%y-%m-%d %T %Z}\" \"%[%y-%m-%d %T %Z]\" \"%n\"`"' this calls my program not with two arguments, but with seven: 7 args:("%{%y-%m-%d)(%T)(%Z}")("%[%y-%m-%d)(%T)(%Z]")("%n") btw, the attrib program looks like this: #!/bin/sh echo "placeholder" # nothing useful, yet exec 1>&2 echo -n "$# args:" for a do echo -n "($a)"; done echo '' sleep 5 the %{} and %[] are unbalanced. ok, second try: send-hook . 'set attribution="`$HOME/.mutt/attrib %{%y-%m-%d} %{%T} %{%Z} %[%y-%m-%d] %[%T] %[%Z] %n`"' this gives me: 7 args:(%{%y-%m-%d})(%{%T})(%{%Z})(%[%y-%m-%d])(%[%T])(%[%Z])(%n) well, the problem is, and that's why i'm echoing to stderr: only there can i see that the %-escapes aren't substituted, yet. they get substituted after my program has run. looks like we've got two options: - you change the time where %-escapes get substituted. - i've got to write an $editor that parses a reply, locates a generic attribution and possibly shortens it. which option do you want to chose? :-) rj From roessler@sobolev.rhein.de Mon Feb 9 12:14:33 1998 Return-Path: roessler@sobolev.rhein.de Received: from riemann.iam.uni-bonn.de (root@riemann.iam.uni-bonn.de [131.220.223.83]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA25927 for ; Mon, 9 Feb 1998 12:14:31 -0800 (PST) Received: (from uucp@localhost) by riemann.iam.uni-bonn.de (8.8.8/8.8.5) with UUCP id VAA28215 for mutt-users@cs.hmc.edu; Mon, 9 Feb 1998 21:03:28 +0100 Received: (from roessler@localhost) by sobolev.rhein.de (8.8.8/8.8.8) id UAA08884 ; Mon, 9 Feb 1998 20:23:01 +0100 Message-ID: <19980209202300.17902@sobolev.rhein.de> Date: Mon, 9 Feb 1998 20:23:00 +0100 From: Thomas Roessler To: Mutt Heads Subject: Re: PGP-signing complaint Mail-Followup-To: Mutt Heads References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> <19980206162046.44948@rsn.hp.com> <19980207024313.61270@matrix.42.org> <19980207124809.27088@freebie.lemis.com> <19980209121943.20974@rsn.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.90.2i In-Reply-To: <19980209121943.20974@rsn.hp.com> On Mon, Feb 09, 1998 at 12:19:43PM -0600, David DeSimone wrote: > When I want to verify a signature (like this one, from > you), I go to the PGP keyservers, which is sort of an > "independent" source. Is it more trustworthy than the > user's web page? Mmm... I dunno. :) None of these sources is trustworthy. To make public-key cryptography work, you need an authenticated channel from the key's owner to yourself. This can be the key's owner telling you the fingerprint during a face-to-face meeting, this can be the signature of a trusted third party. Fetching the key from a public key server or the user's home page should _not_ be considered a trustworthy source. Don't do it. ;-) tlr -- Thomas Roessler · 74a353cc0b19 · dg1ktr · http://home.pages.de/~roessler/ 2048/CE6AC6C1 · 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1 From hkantola@cc.helsinki.fi Mon Feb 9 12:29:09 1998 Return-Path: hkantola@cc.helsinki.fi Received: from vesuri.Helsinki.FI (hkantola@vesuri.helsinki.fi [128.214.205.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA28447 for ; Mon, 9 Feb 1998 12:29:07 -0800 (PST) Received: (from hkantola@localhost) by vesuri.Helsinki.FI (8.8.8-spammers-bug-off/8.8.0) id WAA28982; Mon, 9 Feb 1998 22:28:53 +0200 (EET) Message-ID: <19980209222853.40675@vesuri.helsinki.fi> Date: Mon, 9 Feb 1998 22:28:53 +0200 From: Heikki Kantola To: mutt-users@cs.hmc.edu Subject: Re: quote_regexp Reply-To: Heikki.Kantola@iki.fi References: <19980208085002.39940@csci.uark.edu> <19980209103051.63486@la.tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88 In-Reply-To: <19980209103051.63486@la.tis.com>; from Michael Elkins on Mon, Feb 09, 1998 at 10:30:51AM -0800 X-Mailer-Info: http://www.math.fu-berlin.de/%7Eguckes/mutt/ According to Michael Elkins : > $quote_regexp is used to find > quoted text so that it can be displayed in a special color in the pager > (using `color quoted ...'). That reminds me that for couple times I've wished that Mutt would have similar skip_quoted-function as Slrn newsreader does... -- Heikki "Hezu" Kantola, Lähettämällä mainoksia tai muuta asiatonta sähköpostia yllä olevaan osoitteeseen sitoudut maksamaan oikolukupalvelusta FIM500 alkavalta tunnilta. From manojk@bermuda.io.com Mon Feb 9 12:41:54 1998 Return-Path: manojk@bermuda.io.com Received: from bermuda.io.com (manojk@bermuda.io.com [199.170.88.7]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id MAA00206 for ; Mon, 9 Feb 1998 12:41:52 -0800 (PST) Received: (from manojk@localhost) by bermuda.io.com (8.8.5/8.8.5) id OAA16369; Mon, 9 Feb 1998 14:41:25 -0600 (CST) Message-ID: <19980209144125.16069@io.com> Date: Mon, 9 Feb 1998 14:41:25 -0600 From: Manoj Kasichainula To: Mutt Heads Subject: Re: PGP-signing complaint Mail-Followup-To: Mutt Heads References: <19980206122540.14761@rsn.hp.com> <19980206202613.18011@matrix.42.org> <19980206162046.44948@rsn.hp.com> <19980207024313.61270@matrix.42.org> <19980207124809.27088@freebie.lemis.com> <19980209121943.20974@rsn.hp.com> <19980209202300.17902@sobolev.rhein.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980209202300.17902@sobolev.rhein.de>; from Thomas Roessler on Mon, Feb 09, 1998 at 08:23:00PM +0100 X-spam-bait: postmaster@warez.io.com abuse@warez.io.com On Mon, Feb 09, 1998 at 08:23:00PM +0100, Thomas Roessler wrote: > Fetching the key from a public key server or the user's > home page should _not_ be considered a trustworthy source. Which is why when I do this, I don't sign the key I receive. Then, mutt tells me that the sig is verified, but this might not necessarily mean anything. When I know for a fact that somekone's key belongs to the ID on the key, I sign it. -- Manoj Kasichainula - manojk at io dot com - http://www.io.com/~manojk/ "Never offend people with style when you can offend them with substance." -- Sam Brown, "The Washington Post", January 26, 1977 From bm11455@mercury.themis.ag.gov.bc.ca Mon Feb 9 14:56:41 1998 Return-Path: bm11455@mercury.themis.ag.gov.bc.ca Received: from mercury.themis.ag.gov.bc.ca (mercury.themis.ag.gov.bc.ca [142.22.5.94]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id OAA24448 for ; Mon, 9 Feb 1998 14:56:29 -0800 (PST) Received: (from bm11455@localhost) by mercury.themis.ag.gov.bc.ca (8.8.5/8.8.5) id OAA03563; Mon, 9 Feb 1998 14:55:16 -0800 Message-ID: <19980209145516.43571@themis.ag.gov.bc.ca> Date: Mon, 9 Feb 1998 14:55:16 -0800 From: Jason Baker To: mutt-users@cs.hmc.edu Subject: Re: quote_regexp Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208085002.39940@csci.uark.edu> <19980209103051.63486@la.tis.com> <19980209222853.40675@vesuri.helsinki.fi> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=1yeeQ81UyVL57Vl7 X-Mailer: Mutt 0.90i In-Reply-To: <19980209222853.40675@vesuri.helsinki.fi>; from Heikki Kantola on Mon, Feb 09, 1998 at 10:28:53PM +0200 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On February 09, Heikki Kantola wrote: > According to Michael Elkins : > > $quote_regexp is used to find > > quoted text so that it can be displayed in a special color in the pager > > (using `color quoted ...'). >=20 > That reminds me that for couple times I've wished that Mutt would > have similar skip_quoted-function as Slrn newsreader does... How would that differ from toggle-quoted ('T' for me)? --=20 jbaker@themis.ag.gov.bc.ca | PGP key available Systems Administrator, Information Systems | from MIT keyserver. BC Family Maintenance Enforcement Program | KeyID: 6DA770E9 BUGS: If there was a single standard for the English language it would not be necessary to support redundant spellings. -- ls (1) man page, Debian Linux --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBNN+JUz6wJThtp3DpAQGRlQQAtgNtnrRSRqAjJWLCHFlJWSwFJrGSVvCc dZRq8wcyI+XTFu+n9QmaAhN8EKNoLIyBeKEOFwguViqx82irLj/WGk4RcLbZ0IiL z7LPcTA3kSPdnyLzPkSXtWF7K4f6U8nRlMB6BAvRC22DKaRWpeIBjgqbSHktpiFY VI1af4/4EDA= =mfvX -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7-- From koenig@ceres.tat.physik.uni-tuebingen.de Mon Feb 9 15:10:05 1998 Return-Path: koenig@ceres.tat.physik.uni-tuebingen.de Received: from x400link.zdv.uni-tuebingen.de (outmail.zdv.uni-tuebingen.de [134.2.2.23]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA26706 for ; Mon, 9 Feb 1998 15:10:00 -0800 (PST) Received: from ceres.tat.physik.uni-tuebingen.de (ceres.tat.physik.uni-tuebingen.de [134.2.170.12]) by x400link.zdv.uni-tuebingen.de (8.8.8/8.8.8) with ESMTP id AAA18370; Tue, 10 Feb 1998 00:09:37 +0100 (MET) Received: (from koenig@localhost) by ceres.tat.physik.uni-tuebingen.de (8.8.8/8.8.8) id AAA25342; Tue, 10 Feb 1998 00:09:36 +0100 (MEZ) Received: (from root@localhost) by turtle.tat.physik.uni-tuebingen.de (8.8.8/8.8.5) id AAA01567; Tue, 10 Feb 1998 00:08:21 +0100 Message-ID: <19980210000821.30266@tat.physik.uni-tuebingen.de> Date: Tue, 10 Feb 1998 00:08:21 +0100 From: Harald Koenig To: mutt-users@cs.hmc.edu Cc: Thomas Roessler , Harald Koenig Subject: mutt doesn't quote TABs in quoted-printable enc. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 X-fingerprint: 3B CD 5A A9 73 44 DD 04 A0 4E A0 34 20 7B 1E 38 Hi, mutt-0.88 and 0.89.1i don't quote TAB characters when using quoted-printable encoding. I had to realize this when I sent a PGP-signed mail to a mailing list and my copy which I've received back from the list showed a broken PGP signature. reason have been three TAB characters at the start of lines which have been replaced by 8 spaces by some mailer (my outgoing copy still have TABs). isn't this a bug of quoted-printable encoding (aside from the fact that I hate broken mailers which remove TABs) ??? Harald -- All SCSI disks will from now on ___ _____ be required to send an email notice 0--,| /OOOOOOO\ 24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\ \ \/OOOOOOOOOOOOOOO\ \ OOOOOOOOOOOOOOOOO|// Harald Koenig, \/\/\/\/\/\/\/\/\/ Inst.f.Theoret.Astrophysik // / \\ \ koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^ From mason@acheron.middleboro.ma.us Mon Feb 9 15:41:17 1998 Return-Path: mason@acheron.middleboro.ma.us Received: from snowball.webtrek.com (root@snowball.webtrek.com [206.239.36.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id PAA01219 for ; Mon, 9 Feb 1998 15:41:14 -0800 (PST) Received: (from uucp@localhost) by snowball.webtrek.com (8.8.7/8.8.5) with UUCP id RAA26782 for mutt-users@cs.hmc.edu; Mon, 9 Feb 1998 17:53:29 -0500 Received: (from mason@localhost) by acheron.middleboro.ma.us (8.8.8/8.8.8) id RAA01261; Mon, 9 Feb 1998 17:45:01 -0500 (EST) Message-ID: <19980209174457.09386@acheron.middleboro.ma.us> Date: Mon, 9 Feb 1998 17:44:57 -0500 From: Mason Loring Bliss To: mutt-users mailing list Subject: Mutt 0.88 and S-Lang 1.0.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Hi! I was wondering... If I build the newest S-Lang, will it likely break my current installation of Mutt? (I'm running 0.88.) I noted on the Mutt home page: - [patch-0.89.bj.slang10config.1] fixed configure script to work with slang-1.0 beta Also, on the S-Lang home page, there was a note that the newest S-Lang wasn't necessarily backwards compatible. Has anyone tried running S-Lang 1.0 or newer with Mutt 0.88, or can someone who knows what changed speculate on my probable success if I install the new S-Lang I snagged without doing anything to Mutt? Thanks! -- Mason Loring Bliss...mason@acheron.middleboro.ma.us...www.webtrek.com/mason "In the drowsy dark cave of the mind dreams build their nest with fragments dropped from day's caravan."--Rabindranath Tagore...awake ? sleep : dream; From michael@tis.com Mon Feb 9 16:12:23 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id QAA07128 for ; Mon, 9 Feb 1998 16:12:18 -0800 (PST) Received: by relay.la.tis.com; id QAA03090; Mon, 9 Feb 1998 16:22:21 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma003085; Mon, 9 Feb 98 16:22:17 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id QAA13374; Mon, 9 Feb 1998 16:07:16 -0800 (PST) Message-ID: <19980209160715.61500@la.tis.com> Date: Mon, 9 Feb 1998 16:07:15 -0800 From: Michael Elkins To: Harald Koenig , mutt-users@cs.hmc.edu Cc: Thomas Roessler Subject: Re: mutt doesn't quote TABs in quoted-printable enc. Mail-Followup-To: Harald Koenig , mutt-users@cs.hmc.edu, Thomas Roessler References: <19980210000821.30266@tat.physik.uni-tuebingen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980210000821.30266@tat.physik.uni-tuebingen.de>; from Harald Koenig on Tue, Feb 10, 1998 at 12:08:21AM +0100 On Tue, Feb 10, 1998 at 12:08:21AM +0100, Harald Koenig wrote: > mutt-0.88 and 0.89.1i don't quote TAB characters when using quoted-printable > encoding. > > isn't this a bug of quoted-printable encoding (aside from the fact that > I hate broken mailers which remove TABs) ??? Whitespace is only required to be encoded on the end of lines, not anywhere else. I've never heard of mail software being *that* broken before! me From notting@xenomorph.dyn.ml.org Mon Feb 9 17:07:01 1998 Return-Path: notting@xenomorph.dyn.ml.org Received: from xenomorph.dyn.ml.org (notting@dialin2-106.wustl.edu [128.252.82.106]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id RAA16476 for ; Mon, 9 Feb 1998 17:06:56 -0800 (PST) Received: (from notting@localhost) by xenomorph.dyn.ml.org (8.8.7/8.8.7) id TAA10667; Mon, 9 Feb 1998 19:03:44 -0600 Message-ID: <19980209190344.32076@xenomorph.dyn.ml.org> Date: Mon, 9 Feb 1998 19:03:44 -0600 From: Bill Nottingham To: mutt-users@cs.hmc.edu Subject: Re: quote_regexp Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208085002.39940@csci.uark.edu> <19980209103051.63486@la.tis.com> <19980209222853.40675@vesuri.helsinki.fi> <19980209145516.43571@themis.ag.gov.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2 In-Reply-To: <19980209145516.43571@themis.ag.gov.bc.ca>; from Jason Baker on Mon, Feb 09, 1998 at 02:55:16PM -0800 Jason Baker (bm11455@themis.ag.gov.bc.ca) said: > On February 09, Heikki Kantola wrote: > > According to Michael Elkins : > > > $quote_regexp is used to find > > > quoted text so that it can be displayed in a special color in the pager > > > (using `color quoted ...'). > > > > That reminds me that for couple times I've wished that Mutt would > > have similar skip_quoted-function as Slrn newsreader does... > > How would that differ from toggle-quoted ('T' for me)? What I'm assuming he means is that instead of turning off the quoting, the 'skip_quoted' just skips to the next non-quoted text in the pager. Bill From me Tue Feb 10 00:00:36 1998 Return-Path: me Received: (from me@localhost) by turing.cs.hmc.edu (8.8.5/8.8.4) id AAA00128; Tue, 10 Feb 1998 00:00:34 -0800 (PST) Message-ID: <19980210000034.00081@turing.cs.hmc.edu> Date: Tue, 10 Feb 1998 00:00:34 -0800 From: Michael Elkins To: Mason Loring Bliss , mutt-users mailing list Subject: Re: Mutt 0.88 and S-Lang 1.0.2 Mail-Followup-To: Mason Loring Bliss , mutt-users mailing list References: <19980209174457.09386@acheron.middleboro.ma.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1 In-Reply-To: <19980209174457.09386@acheron.middleboro.ma.us>; from Mason Loring Bliss on Mon, Feb 09, 1998 at 05:44:57PM -0500 On Mon, Feb 09, 1998 at 05:44:57PM -0500, Mason Loring Bliss wrote: > Hi! I was wondering... If I build the newest S-Lang, will it likely break > my current installation of Mutt? (I'm running 0.88.) > > I noted on the Mutt home page: > > - [patch-0.89.bj.slang10config.1] fixed configure script to work with > slang-1.0 beta > > Also, on the S-Lang home page, there was a note that the newest S-Lang > wasn't necessarily backwards compatible. > > Has anyone tried running S-Lang 1.0 or newer with Mutt 0.88, or can someone > who knows what changed speculate on my probable success if I install the > new S-Lang I snagged without doing anything to Mutt? Most of the changes were to the S-Lang interpreter which Mutt does not use. Only one function in the screen management package changed names, which is what that patch was for (0.88 will not work with S-Lang 1.0 without that patch). me From koenig@ceres.tat.physik.uni-tuebingen.de Tue Feb 10 00:26:52 1998 Return-Path: koenig@ceres.tat.physik.uni-tuebingen.de Received: from comserv.zdv.uni-tuebingen.de (comserv.zdv.uni-tuebingen.de [134.2.2.6]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id AAA04833; Tue, 10 Feb 1998 00:26:49 -0800 (PST) Received: from ceres.tat.physik.uni-tuebingen.de (ceres.tat.physik.uni-tuebingen.de [134.2.170.12]) by comserv.zdv.uni-tuebingen.de (8.8.8/8.8.8) with ESMTP id JAA03460; Tue, 10 Feb 1998 09:26:32 +0100 (MET) Received: (from koenig@localhost) by ceres.tat.physik.uni-tuebingen.de (8.8.8/8.8.8) id JAA12242; Tue, 10 Feb 1998 09:26:31 +0100 (MEZ) Received: (from root@localhost) by turtle.tat.physik.uni-tuebingen.de (8.8.8/8.8.5) id IAA04121; Tue, 10 Feb 1998 08:53:00 +0100 Message-ID: <19980210085259.22832@tat.physik.uni-tuebingen.de> Date: Tue, 10 Feb 1998 08:52:59 +0100 From: Harald Koenig To: Michael Elkins Cc: mutt-users@cs.hmc.edu, Thomas Roessler , Harald Koenig Subject: Re: mutt doesn't quote TABs in quoted-printable enc. References: <19980210000821.30266@tat.physik.uni-tuebingen.de> <19980209160715.61500@la.tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980209160715.61500@la.tis.com>; from Michael Elkins on Mon, Feb 09, 1998 at 04:07:15PM -0800 X-fingerprint: 3B CD 5A A9 73 44 DD 04 A0 4E A0 34 20 7B 1E 38 On Feb 09, Michael Elkins wrote: > On Tue, Feb 10, 1998 at 12:08:21AM +0100, Harald Koenig wrote: > > mutt-0.88 and 0.89.1i don't quote TAB characters when using quoted-printable > > encoding. > > > > isn't this a bug of quoted-printable encoding (aside from the fact that > > I hate broken mailers which remove TABs) ??? > > Whitespace is only required to be encoded on the end of lines, not anywhere > else. I've never heard of mail software being *that* broken before! well, as I had to realize it still exists (and ~10 years ago it wasn't sure at all that TABs will be retained in emails...) but I wasn't aware that TABs are _still_ a problem. the mailing list where this happend was managed by `LISTSERV' -- which is based on pretty old BITNET-based technology (basically punch cards;) even if this was on a internet-only host/net. I'll send some test mails today and try to figure out which mail gateway or mailing list really clobbered my PGP-signed mail... Harald -- All SCSI disks will from now on ___ _____ be required to send an email notice 0--,| /OOOOOOO\ 24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\ \ \/OOOOOOOOOOOOOOO\ \ OOOOOOOOOOOOOOOOO|// Harald Koenig, \/\/\/\/\/\/\/\/\/ Inst.f.Theoret.Astrophysik // / \\ \ koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^ From baumann@zib.de Tue Feb 10 00:51:40 1998 Return-Path: baumann@zib.de Received: from mailserv.zib.de (mailsrv2.zib.de [130.73.121.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id AAA08351 for ; Tue, 10 Feb 1998 00:51:36 -0800 (PST) Received: from aves1.zib.de by mailserv.zib.de (SMI-8.6/ESMTP Sendmail 8.8.7/8.8.7) id JAA06610; Tue, 10 Feb 1998 09:51:22 +0100 Received: from aves1 by aves1.zib.de (SMI-8.6/SMI-SVR4) id JAA04532; Tue, 10 Feb 1998 09:51:22 +0100 Received: by aves1 (950413.SGI.8.6.12/ZIB-Mini.conf) id JAA12755; Tue, 10 Feb 1998 09:51:21 +0100 Message-ID: <19980210095121.58998@zib.de> Date: Tue, 10 Feb 1998 09:51:21 +0100 From: "Wolfgang W. Baumann" To: Mutt users Subject: [date_format] different in pager and replys? Reply-To: "Wolfgang W. Baumann" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Organisation: ZIB Berlin / Supercomputing Department X-Address: Takustrasse 7, D-14195 Berlin-Dahlem X-Phone: +49-30-84185-176 X-Fax: +49-30-84185-311 X-URL: http://www.zib.de/baumann/ X-Disclaimer: "Speaking 4 myself -- if at all" In my replys I like to have a date_format different from that in the pager. Currently I have set date_format="%y/%b/%d" In replys however, I like to have something like date_format="%d %b %Y" So far I have not been able to come up with a combo of folder and send hooks to accomplish this. BTW, this is mutt-0.88e. Any ideas? Have A Nice Day, Wolfgang -- Wolfgang W. Baumann / CFD Consultant @ ZIB Berlin / mailto: baumann@zib.de From efraim@desire.argh.org Tue Feb 10 02:46:19 1998 Return-Path: efraim@desire.argh.org Received: from mail.provi.de (mail.provi.de [193.98.9.7]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id CAA27607 for ; Tue, 10 Feb 1998 02:46:16 -0800 (PST) Received: from news.hamburg.pop.de (claimed popnews.hamburg.pop.de, is IP 193.98.9.248) (root) by mail.provi.de with smtp (Exim 1.80 #2) id 0y2DDG-000401-00; Tue, 10 Feb 1998 11:46:50 +0100 Received: from desire.argh.org by popnews.hamburg.pop.de with bsmtp (Smail3.2.0.95 #6) id m0y2DE6-00071RC; Tue, 10 Feb 1998 11:47:42 +0100 (MET) Received: from efraim by desire.argh.org with local (Exim 1.82 #1) id 0y2D9Q-0003wi-00 ; Tue, 10 Feb 1998 11:42:52 +0100 Message-ID: <19980210114252.19079@deadend.argh.org> Date: Tue, 10 Feb 1998 11:42:52 +0100 From: Alexander Koch To: mutt-users@cs.hmc.edu Subject: Re: PGP mutt and MIME types Mail-Followup-To: mutt-users@cs.hmc.edu References: <19980208190245.18960@fever.semiotek.com> <19980209083016.06920@deadend.argh.org> <19980209125730.52394@sobolev.rhein.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980209125730.52394@sobolev.rhein.de>; from "Thomas Roessler" on Mon, 09 Feb 1998 12:57:30 +0100 Sender: Alexander Koch On Mon, 9 February 1998 12:57:30 +0100, Thomas Roessler wrote: > > What are the correct macros for sending pgp keys (esc-k?) > > and extracting them from a plain file (esc-a)? > eh? Just try esc-k and ctrl-k on the pager and browser > menus; no autoview entries or scripts should be necessary. There's a key I sent to myself but I get to see: "mailcap entry for type application/pgp-keys not found" in the bottom line and I get shown there's just one attachment. "[-- application/pgp-keys is unsupported (use 'v' to view this part) --]" shouldn't "auto_view application/pgp-keys" do exactly that? I personally hate all that mailcap thingies as I hate metamail. Though I guess I'll have to do something to that. When I type "v" in there and view it as text, the extract keys command is unbound, so I'll have to revisit the keybindings again. however, any pointers? Alexander -- I generally avoid temptation unless I can't resist it. Alexander Koch - <>< - aka Efraim - PGP - 0xA78FB1E9 - Wedel - Germany From david@ice.bae.uga.edu Tue Feb 10 04:19:22 1998 Return-Path: david@ice.bae.uga.edu Received: from listmail.cc.uga.edu (listmail.cc.uga.edu [128.192.232.10]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id EAA10430 for ; Tue, 10 Feb 1998 04:19:18 -0800 (PST) Received: from ice.bae.uga.edu by listmail.cc.uga.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.33534730@listmail.cc.uga.edu>; Tue, 10 Feb 1998 7:19:18 -0500 Received: (from david@localhost) by ice.bae.uga.edu (8.8.5/8.8.3) id HAA07525; Tue, 10 Feb 1998 07:19:17 -0500 (EST) Message-ID: <19980210071917.13947@bae.uga.edu> Date: Tue, 10 Feb 1998 07:19:17 -0500 From: David Thorburn-Gundlach To: mutt-users@cs.hmc.edu Subject: Re: quote_regexp References: <19980208085002.39940@csci.uark.edu> <19980209103051.63486@la.tis.com> <19980209222853.40675@vesuri.helsinki.fi> <19980209145516.43571@themis.ag.gov.bc.ca> <19980209190344.32076@xenomorph.dyn.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980209190344.32076@xenomorph.dyn.ml.org>; from Bill Nottingham on Mon, Feb 09, 1998 at 07:03:44PM -0600 X-Wedding-Date: 94/01/15-19:30 X-Wedding-Time: 35677 hours of wedded bliss :-) X-Madison-Date: 96/12/13-12:00 X-Madison-Time: 10171 hours of fatherhood :-) ...and then Bill Nottingham said... % Jason Baker (bm11455@themis.ag.gov.bc.ca) said: % > On February 09, Heikki Kantola wrote: % > > % > > That reminds me that for couple times I've wished that Mutt would % > > have similar skip_quoted-function as Slrn newsreader does... % > % > How would that differ from toggle-quoted ('T' for me)? % % What I'm assuming he means is that instead of turning off the quoting, % the 'skip_quoted' just skips to the next non-quoted text in the pager. That's what I figured, too. I wonder, though, why you can't just do your editor's equivalent of '}' in vi, which means "jump to the next paragraph break", which ought to be how quoted pieces are separated, I'd think... % % Bill % :-D -- David Thorburn-Gundlach * It's easier to fight for one's principles (play) david@bae.uga.edu * than to live up to them. -- fortune cookie (work) david_thorburn-gundlach@groton.pfizer.com Helping out at Pfizer http://www.bae.uga.edu/other/david/ From byrial@post3.tele.dk Tue Feb 10 05:25:35 1998 Return-Path: byrial@post3.tele.dk Received: from mail-in2.inet.tele.dk (mail-in2.inet.tele.dk [194.182.148.151]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id FAA18901 for ; Tue, 10 Feb 1998 05:25:32 -0800 (PST) Received: (qmail 10234 invoked from network); 10 Feb 1998 13:25:07 -0000 Received: from post3.tele.dk (194.239.134.166) by mail-in2.inet.tele.dk with SMTP; 10 Feb 1998 13:25:07 -0000 Received: from ask.ask ([194.239.129.49]) by post3.tele.dk (Netscape Mail Server v2.02) with ESMTP id AAA41554 for ; Tue, 10 Feb 1998 14:25:05 +0100 Received: (qmail 474 invoked by uid 500); 10 Feb 1998 09:42:42 -0000 Message-ID: <19980210104242.42438@ask.tele.dk> Date: Tue, 10 Feb 1998 10:42:42 +0100 From: Byrial Jensen To: Mason Loring Bliss , mutt-users mailing list Cc: Byrial Jensen Subject: Re: Mutt 0.88 and S-Lang 1.0.2 Mail-Followup-To: Mason Loring Bliss , mutt-users mailing list References: <19980209174457.09386@acheron.middleboro.ma.us> <19980210000034.00081@turing.cs.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980210000034.00081@turing.cs.hmc.edu>; from Michael Elkins on Tue, Feb 10, 1998 at 12:00:34AM -0800 On Tue, Feb 10, 1998 at 12:00:34AM -0800, Michael Elkins wrote: > On Mon, Feb 09, 1998 at 05:44:57PM -0500, Mason Loring Bliss wrote: > > I noted on the Mutt home page: > > > > - [patch-0.89.bj.slang10config.1] fixed configure script to work with > > slang-1.0 beta > > Most of the changes were to the S-Lang interpreter which Mutt does not use. > Only one function in the screen management package changed names, which is > what that patch was for (0.88 will not work with S-Lang 1.0 without that > patch). To compile Mutt with S-Lang you have to find the text "init_SLang" in the file configure.in and replace it by "SLtt_get_terminfo", and afterwards run autoconf to update configure. That is what the patch do. Or if you don't have autoconf, you can make the change directly in configure. Best regards - Byrial From reptile@pooh.cs.net.pl Tue Feb 10 05:27:48 1998 Return-Path: reptile@pooh.cs.net.pl Received: from pooh.cs.net.pl (qmailr@pooh.cs.net.pl [195.117.250.7]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id FAA19126 for ; Tue, 10 Feb 1998 05:27:43 -0800 (PST) Received: (qmail 29007 invoked by uid 501); 10 Feb 1998 13:30:47 -0000 Message-ID: <19980210143044.24313@pdi.net> Date: Tue, 10 Feb 1998 14:30:44 +0100 From: "Robert Richard George 'reptile' Wal" To: Mutt users Subject: Re: [date_format] different in pager and replys? Mail-Followup-To: Mutt users References: <19980210095121.58998@zib.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=mutta28877 X-Mailer: Mutt 0.89i In-Reply-To: <19980210095121.58998@zib.de>; from Wolfgang W. Baumann on Tue, Feb 10, 1998 at 09:51:21AM +0100 Organization: Me? Organized? Get real :) X-URL: http://pooh.cs.net.pl (Eternally under construction) X-IRC-Nick: Gadzinka@iRCnET.iRC.nETWORK (Gadzinka -- tiny little reptile) X-PGP-Fingerprint: 37E1D55F 29793C0C B8D39D01 61FC50CE X-PGP-Key: finger reptile@gryzmak.lodz.pdi.net X-Motto: Fact that you're paranoid doesn't imply that THEY don't follow you. X-Disclaimer: I don't answer mail or news articles below some arbitrary mark. X-Favourites: women, cats, Amiga, Linux, TeX, vim, music, sci-fi, poetry. X-Mount-Entry: mount -t human /dev/reptile /earth/europe/poland/warsaw On 98.02.10 Wolfgang W. Baumann pressed the following keys: > In my replys I like to have a date_format different from > that in the pager. > > Currently I have > > set date_format="%y/%b/%d" > > In replys however, I like to have something like > > date_format="%d %b %Y" > > So far I have not been able to come up with a combo of > folder and send hooks to accomplish this. > BTW, this is mutt-0.88e. you dont have to set any hooks. Just don't use formatted date placeholder in your attribution: set attribution="On %[%y.%m.%d] %n pressed the following keys:\n" which produces attribution like shown at the top of this mail. Reptile -- mailto:reptile@pdi.net :) Women are more complicated than PC... :( Look into my headers and you'll see who I am. :) From mihannin@cc.hut.fi Tue Feb 10 05:30:25 1998 Return-Path: mihannin@cc.hut.fi Received: from vipunen.hut.fi (root@vipunen.hut.fi [130.233.224.20]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id FAA19567 for ; Tue, 10 Feb 1998 05:30:03 -0800 (PST) Received: from chamber (root@cc-dialin1-4.hut.fi [130.233.251.4]) by vipunen.hut.fi (8.8.8/8.8.7) with ESMTP id PAA120054 for ; Tue, 10 Feb 1998 15:29:42 +0200 Received: (qmail 1557 invoked by alias); 10 Feb 1998 15:27:02 +0200 Received: (qmail 1547 invoked by uid 501); 10 Feb 1998 15:27:00 +0200 Message-ID: <19980210152700.43160@iki.fi> Date: Tue, 10 Feb 1998 15:27:00 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: The Mutt Users List Subject: Toggling pager_index_lines? Mail-Followup-To: The Mutt Users List Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.89 Organization: The DALnet IRC network X-No-Archive: yes X-WWW-Homepage: http://www.iki.fi/wiz/ Hi, I thought that it would be nice to have a key in the pager for toggling $pager_index_lines (between 0 and N), but I couldn't figure out how to do this. Does anyone have any suggestions? -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // // net.freak, DALnet IRC operator, other interests: RPGs (GURPS & other), // // Fantasy & Sci-Fi, Comics (Elfquest & Sandman), Programming, Linux, WWW // // Any sufficiently advanced magic is indistinguishable from technology. // From hkantola@cc.helsinki.fi Tue Feb 10 05:55:06 1998 Return-Path: hkantola@cc.helsinki.fi Received: from kontti.Helsinki.FI (hkantola@kontti.helsinki.fi [128.214.205.13]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id FAA23016 for ; Tue, 10 Feb 1998 05:55:03 -0800 (PST) Received: (from hkantola@localhost) by kontti.Helsinki.FI (8.8.8-spammers-bug-off/8.8.0) id PAA28995; Tue, 10 Feb 1998 15:54:47 +0200 (EET) Message-ID: <19980210155447.44689@kontti.Helsinki.FI> Date: Tue, 10 Feb 1998 15:54:47 +0200 From: Heikki Kantola To: The Mutt Users List Subject: Re: Toggling pager_index_lines? Reply-To: Heikki.Kantola@iki.fi References: <19980210152700.43160@iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88 In-Reply-To: =?iso-8859-1?Q?=3C19980210152700=2E43160=40iki=2Efi=3E=3B_from_Mikko_H?= =?iso-8859-1?Q?=E4nninen_on_Tue=2C_Feb_10=2C_1998_at_03=3A27=3A00PM_+020?= =?iso-8859-1?Q?0?= X-Mailer-Info: http://www.math.fu-berlin.de/%7Eguckes/mutt/ According to Mikko Hänninen : > I thought that it would be nice to have a key in the pager for toggling > $pager_index_lines (between 0 and N), but I couldn't figure out how to > do this. Does anyone have any suggestions? How about along these lines: macro pager "\e9" ":set pager_index_lines=9\n" macro pager "\e0" ":set pager_index_lines=0\n" -- Heikki "Hezu" Kantola, Lähettämällä mainoksia tai muuta asiatonta sähköpostia yllä olevaan osoitteeseen sitoudut maksamaan oikolukupalvelusta FIM500 alkavalta tunnilta. From baumann@zib.de Tue Feb 10 06:17:58 1998 Return-Path: baumann@zib.de Received: from mailserv.zib.de (mailsrv2.zib.de [130.73.121.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id GAA26187 for ; Tue, 10 Feb 1998 06:17:53 -0800 (PST) Received: from aves1.zib.de by mailserv.zib.de (SMI-8.6/ESMTP Sendmail 8.8.7/8.8.7) id PAA09773; Tue, 10 Feb 1998 15:16:35 +0100 Received: from aves1 by aves1.zib.de (SMI-8.6/SMI-SVR4) id PAA07722; Tue, 10 Feb 1998 15:16:31 +0100 Received: by aves1 (950413.SGI.8.6.12/ZIB-Mini.conf) id PAA13192; Tue, 10 Feb 1998 15:16:31 +0100 Message-ID: <19980210151631.46965@zib.de> Date: Tue, 10 Feb 1998 15:16:31 +0100 From: "Wolfgang W. Baumann" To: "Robert Richard George 'reptile' Wal" Cc: Mutt users Subject: Re: Re: [date_format] different in pager and replys? Reply-To: "Wolfgang W. Baumann" References: <19980210095121.58998@zib.de> <19980210143044.24313@pdi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88e In-Reply-To: <19980210143044.24313@pdi.net>; from Robert Richard George 'reptile' Wal on 98/Feb/10 X-Organisation: ZIB Berlin / Supercomputing Department X-Address: Takustrasse 7, D-14195 Berlin-Dahlem X-Phone: +49-30-84185-176 X-Fax: +49-30-84185-311 X-URL: http://www.zib.de/baumann/ X-Disclaimer: "Speaking 4 myself -- if at all" On 10 Feb 1998 14:30 Robert Richard George 'reptile' Wal wrote: : On 98.02.10 Wolfgang W. Baumann pressed the following keys: : : > In my replys I like to have a date_format different from : > that in the pager. : [...] : you dont have to set any hooks. Just don't use formatted date placeholder : in your attribution: : : set attribution="On %[%y.%m.%d] %n pressed the following keys:\n" : : which produces attribution like shown at the top of this mail. Thanks! That does it. And (sigh!) it's even mentioned in the manual (hdr_format). Now I use set attribution="On %[%d %b %Y %R]\n %n <%a> wrote:" to have a two-line attribution shown above. Mutt never fails to impress me with its features. Good work, and looking forward to version 1.00 in the near future ;-) Have A Nice Day, Wolfgang -- Wolfgang W. Baumann / CFD Consultant @ ZIB Berlin / mailto: baumann@zib.de http://www.zib.de/baumann / fon: +49-30-84185-176 / fax: -311 / sekr.: -131 Konrad-Zuse-Zentrum für Informationstechnik Berlin Supercomputing Dept. / Takustraße 7, #3356 / D-14195 Berlin-Dahlem, Germany From wacker@quincke.Physik.Uni-Dortmund.DE Tue Feb 10 06:21:46 1998 Return-Path: wacker@quincke.Physik.Uni-Dortmund.DE Received: from quincke.Physik.Uni-Dortmund.DE (quincke.Physik.Uni-Dortmund.DE [129.217.160.87]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id GAA26723 for ; Tue, 10 Feb 1998 06:21:41 -0800 (PST) Received: by quincke.Physik.Uni-Dortmund.DE (AIX 4.1/UCB 5.64/4.03/06) id AA27590; Tue, 10 Feb 1998 15:21:38 +0100 Message-Id: <19980210152137.16684@physik.uni-dortmund.de> Date: Tue, 10 Feb 1998 15:21:37 +0100 From: Klaus Wacker To: Mutt User List Subject: Problem with verifying PGP signatures Reply-To: wacker@Physik.Uni-Dortmund.DE Mail-Followup-To: Mutt User List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Whenever I get PGP-signed mail, mutt shows me something like the following: --cut-here-------------------------------------------------------------------- Date: Sat, 31 Jan 1998 14:31:11 +0100 From: Thomas Roessler Subject: [Announce] Mutt 0.89.1i released To: Mutt Announcement List X-Mailer: Mutt 0.89.1i [-- PGP output follows (current time: Tue Feb 10 14:51:14 1998) --] File '/tmp/mutt-quinc.$00' has signature, but with no text. Text is assumed to be in file '/tmp/mutt-quincke-32632-248'. ^G WARNING: Bad signature, doesn't match file contents!^G Bad signature from user "Thomas Roessler ". Signature made 1998/01/31 13:31 GMT using 2048-bit key, key ID CE6AC6C1 ^G WARNING: Because this public key is not certified with a trusted signature, it is not known with high confidence that this public key actually belongs to: "Thomas Roessler ". [-- End of PGP output --] [-- The following data is PGP/MIME signed --] --cut-here-------------------------------------------------------------------- I have never seen a signature recognized as good by mutt/pgp, but I somehow cannot believe that all these messages are forged :-). I know on the other hand that my PGP installation is not totally broken because I was able to verify Thomas' signature on mutt-0.89.1i.tar.gz. Does anybody have any idea what could be wrong? I have tried to save the text and the signature into two separate files from the attachment menu. Running pgp on these files gives the same result (Bad signature). Is that supposed to work? Exactly which part of the message is signed by mutt/pgp, just the text or does it include any headers? Installation details: ~> mutt -v Mutt 0.89.1i, Copyright (C) 1996-8 Michael R. Elkins Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System info: AIX 4.1 Compile time definitions: -DOMAIN +HIDDEN_HOST -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_POP +HAVE_REGCOMP -USE_GNU_RX +HAVE_COLOR +BUFFY_SIZE SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/usr/local/share" ISPELL="/usr/local/bin/ispell" _PGPPATH="/usr/local/bin/pgp" ~> pgp Pretty Good Privacy(tm) 2.6.3ia - Public-key encryption for the masses. (c) 1990-96 Philip Zimmermann, Phil's Pretty Good Software. 1996-03-04 International version - not for use in the USA. Does not use RSAREF. Current time: 1998/02/10 14:06 GMT -- Klaus Wacker wacker@Physik.Uni-Dortmund.DE Experimentelle Physik V http://www.physik.uni-dortmund.de/~wacker Universitaet Dortmund Tel.: +49 (231) 755 3587 D-44221 Dortmund Fax: +49 (231) 755 3569 From vikasa@att.com Tue Feb 10 06:23:48 1998 Return-Path: vikasa@att.com Received: from att.com (cagw2.att.com [192.128.52.90]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id GAA26914 for ; Tue, 10 Feb 1998 06:23:46 -0800 (PST) Received: by cagw2.att.com; Tue Feb 10 09:16 EST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by caig2.att.att.com (AT&T/GW-1.0) with ESMTP id JAA06678 for ; Tue, 10 Feb 1998 09:35:14 -0500 (EST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id JAA24386; Tue, 10 Feb 1998 09:18:22 -0500 (EST) Message-ID: <19980210091822.43106@att.com> Date: Tue, 10 Feb 1998 09:18:22 -0500 From: Vikas Agnihotri To: The Mutt Users List Subject: Re: Toggling pager_index_lines? Mail-Followup-To: The Mutt Users List References: <19980210152700.43160@iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.90.2 In-Reply-To: =?iso-8859-1?Q?=3C19980210152700=2E43160=40iki=2Efi=3E=3B_from_Mikko_H?= =?iso-8859-1?Q?=E4nninen_on_Tue=2C_Feb_10=2C_1998_at_03=3A27=3A00PM_+020?= =?iso-8859-1?Q?0?= Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by caig2.att.att.com id JAA06678 On Tue, Feb 10, 1998 at 03:27:00PM +0200, Mikko H=E4nninen wrote:=20 > Hi, > I thought that it would be nice to have a key in the pager for toggling > $pager_index_lines (between 0 and N), but I couldn't figure out how to > do this. Does anyone have any suggestions? Well, you cant do it with the same key, since Mutt macros cant accept arguments and all. I have the following macro index f3 ":set pager_index_lines=3D" macro pager f3 ":set pager_index_lines=3D" Then I simply type the new value and hit Enter. You can set a key for pager_index_lines=3D0 and another for pager_index_lines=3DN. Vikas From reptile@pooh.cs.net.pl Tue Feb 10 07:14:33 1998 Return-Path: reptile@pooh.cs.net.pl Received: from pooh.cs.net.pl (qmailr@pooh.cs.net.pl [195.117.250.7]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id HAA03825 for ; Tue, 10 Feb 1998 07:14:14 -0800 (PST) Received: (qmail 29599 invoked by uid 501); 10 Feb 1998 15:17:38 -0000 Message-ID: <19980210161736.05676@pooh.cs.net.pl> Date: Tue, 10 Feb 1998 16:17:36 +0100 From: "Robert Richard George 'reptile' Wal" To: The Mutt Users List Subject: Re: Toggling pager_index_lines? Mail-Followup-To: The Mutt Users List References: <19980210152700.43160@iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.89i In-Reply-To: =?iso-8859-2?Q?=3C19980210152700=2E43160=40iki=2Efi=3E=3B_from_Mikko_H?= =?iso-8859-2?Q?=E4nninen_on_Tue=2C_Feb_10=2C_1998_at_03=3A27=3A00PM_+020?= =?iso-8859-2?Q?0?= Organization: Me? Organized? Get real :) X-URL: http://pooh.cs.net.pl (Eternally under construction) X-IRC-Nick: Gadzinka@iRCnET.iRC.nETWORK (Gadzinka -- tiny little reptile) X-PGP-Fingerprint: 37E1D55F 29793C0C B8D39D01 61FC50CE X-PGP-Key: finger reptile@gryzmak.lodz.pdi.net X-Motto: Fact that you're paranoid doesn't imply that THEY don't follow you. X-Disclaimer: I don't answer mail or news articles below some arbitrary mark. X-Favourites: women, cats, Amiga, Linux, TeX, vim, music, sci-fi, poetry. X-Mount-Entry: mount -t human /dev/reptile /earth/europe/poland/warsaw On 98.02.10 Mikko Hänninen pressed the following keys: > Hi, > > I thought that it would be nice to have a key in the pager for toggling > $pager_index_lines (between 0 and N), but I couldn't figure out how to > do this. Does anyone have any suggestions? macro pager \ei ":set pager_index_lines='`( (stty size 2>/dev/null||echo 24 80);echo s0 5/1+p)|dc`'\Cm" macro pager \eI ":set pager_index_lines=0\Cm" And ESC-i will turn on the indexlines, while ESC-I will turn it off. Change bindings however you wish, and of course you can change the computation of index size to some fixed value (note quoting of text caused by multiple parsing). Reptile -- mailto:reptile@pdi.net :) Women are more complicated than PC... :( Look into my headers and you'll see who I am. :) From sec@matrix.42.org Tue Feb 10 08:39:17 1998 Return-Path: sec@matrix.42.org Received: from matrix.42.org (sec@matrix.42.org [192.68.213.129]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id IAA14479 for ; Tue, 10 Feb 1998 08:39:06 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.6) id RAA15610 (sender ); Tue, 10 Feb 1998 17:38:50 +0100 (CET) Message-ID: <19980210173850.16447@matrix.42.org> Date: Tue, 10 Feb 1998 17:38:50 +0100 From: Stefan `Sec` Zehl To: The Mutt Users List Subject: Re: Toggling pager_index_lines? Mail-Followup-To: The Mutt Users List References: <19980210152700.43160@iki.fi> <19980210091822.43106@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: <19980210091822.43106@att.com>; from Vikas Agnihotri on Tue, Feb 10, 1998 at 09:18:22AM -0500 I-love-doing-this: really X-Visit-My-Mutt-Page: http://sec.42.org/mutt/ On Tue, Feb 10, 1998 at 09:18:22AM -0500, Vikas Agnihotri wrote: > Well, you cant do it with the same key, since Mutt macros cant accept > arguments and all. never say never :) macro pager \e\e0 ":set pager_index_lines=0\n:macro pager I \\e\\e1\n" macro pager \e\e1 ":set pager_index_lines=8\n:macro pager I \\e\\e0\n" macro pager I "\e\e1" set pager_index_lines=0 then you can toggle pager_inde_lines with "I" in your pager. CU, Sec -- Hiroshima '45 Tsjernobyl '86 Windows '95 From koenig@ceres.tat.physik.uni-tuebingen.de Tue Feb 10 09:19:44 1998 Return-Path: koenig@ceres.tat.physik.uni-tuebingen.de Received: from zrvsun.zdv.uni-tuebingen.de (zrvsun.zdv.uni-tuebingen.de [134.2.2.35]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id JAA20104; Tue, 10 Feb 1998 09:19:26 -0800 (PST) Received: from ceres.tat.physik.uni-tuebingen.de (ceres.tat.physik.uni-tuebingen.de [134.2.170.12]) by zrvsun.zdv.uni-tuebingen.de (8.8.8/8.8.8) with ESMTP id SAA21206; Tue, 10 Feb 1998 18:19:15 +0100 (MET) Received: (from koenig@localhost) by ceres.tat.physik.uni-tuebingen.de (8.8.8/8.8.8) id SAA02031; Tue, 10 Feb 1998 18:19:14 +0100 (MEZ) Received: (from root@localhost) by turtle.tat.physik.uni-tuebingen.de (8.8.8/8.8.5) id RAA16140; Tue, 10 Feb 1998 17:13:48 +0100 Message-ID: <19980210171348.61403@tat.physik.uni-tuebingen.de> Date: Tue, 10 Feb 1998 17:13:48 +0100 From: Harald Koenig To: Michael Elkins Cc: mutt-users@cs.hmc.edu, Thomas Roessler , Harald Koenig Subject: Re: mutt doesn't quote TABs in quoted-printable enc. References: <19980210000821.30266@tat.physik.uni-tuebingen.de> <19980209160715.61500@la.tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980209160715.61500@la.tis.com>; from Michael Elkins on Mon, Feb 09, 1998 at 04:07:15PM -0800 X-fingerprint: 3B CD 5A A9 73 44 DD 04 A0 4E A0 34 20 7B 1E 38 On Feb 09, Michael Elkins wrote: > Whitespace is only required to be encoded on the end of lines, not anywhere > else. I've never heard of mail software being *that* broken before! I tested this a bit by sending emails with TABs to various lists, private accounts (on 3 different contients;) and through some mail gateways. the _only_ cases where TABs have been converted to spaces are two different mailing lists which are using `LISTSERV' as administration software. are there any RFCs which state that TABs shouldn't be converted? I know it's a non-printing character, so I maybe I can't complain about this ?! anyhow, since I don't think we (mutt-users) will make all LISTSERVs in the world change their systems to retain TABs, what about a mutt optin at least when using PGP which quotes _all_ TABs ? Harald -- All SCSI disks will from now on ___ _____ be required to send an email notice 0--,| /OOOOOOO\ 24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\ \ \/OOOOOOOOOOOOOOO\ \ OOOOOOOOOOOOOOOOO|// Harald Koenig, \/\/\/\/\/\/\/\/\/ Inst.f.Theoret.Astrophysik // / \\ \ koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^ From ulusa@lacueva.ddns.org Tue Feb 10 09:54:43 1998 Return-Path: ulusa@lacueva.ddns.org Received: from mx1.landsraad.net (chusuk.arrakis.es [195.5.65.35]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id JAA25677 for ; Tue, 10 Feb 1998 09:53:59 -0800 (PST) Received: from lacueva.ddns.org (ih-212.arrakis.es [195.5.77.212]) by mx1.landsraad.net (8.8.6/8.7.3) with ESMTP id SAA29268 for ; Tue, 10 Feb 1998 18:52:54 +0100 (MET) Received: (from ulusa@localhost) by lacueva.ddns.org (8.7.5/8.6.9) id SAA01805; Tue, 10 Feb 1998 18:52:16 +0100 Message-ID: <19980210185216.47617@lacueva.ddns.org> Date: Tue, 10 Feb 1998 18:52:16 +0100 From: Urko Lusa To: mutt-announce@cs.hmc.edu Subject: subscribe Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i From vikasa@att.com Tue Feb 10 10:27:48 1998 Return-Path: vikasa@att.com Received: from att.com (cagw1.att.com [192.128.52.89]) by turing.cs.hmc.edu (8.8.5/8.8.4) with SMTP id KAA00882 for ; Tue, 10 Feb 1998 10:27:46 -0800 (PST) Received: by cagw1.att.com; Tue Feb 10 13:21 EST 1998 Received: from 8080b0da.ims.att.com (8080b0da.ims.att.com [135.67.128.9]) by caig1.att.att.com (AT&T/GW-1.0) with ESMTP id NAA15538 for ; Tue, 10 Feb 1998 13:17:27 -0500 (EST) Received: (from vikas@localhost) by 8080b0da.ims.att.com (8.8.8/8.8.8) id NAA25230; Tue, 10 Feb 1998 13:26:04 -0500 (EST) Message-ID: <19980210132604.01643@att.com> Date: Tue, 10 Feb 1998 13:26:04 -0500 From: Vikas Agnihotri To: The Mutt Users List Subject: Re: Toggling pager_index_lines? Mail-Followup-To: The Mutt Users List References: <19980210152700.43160@iki.fi> <19980210091822.43106@att.com> <19980210173850.16447@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2 In-Reply-To: <19980210173850.16447@matrix.42.org>; from Stefan `Sec` Zehl on Tue, Feb 10, 1998 at 05:38:50PM +0100 On Tue, Feb 10, 1998 at 05:38:50PM +0100, Stefan `Sec` Zehl wrote: > On Tue, Feb 10, 1998 at 09:18:22AM -0500, Vikas Agnihotri wrote: > > Well, you cant do it with the same key, since Mutt macros cant accept > > arguments and all. > never say never :) > macro pager \e\e0 ":set pager_index_lines=0\n:macro pager I \\e\\e1\n" > macro pager \e\e1 ":set pager_index_lines=8\n:macro pager I \\e\\e0\n" > macro pager I "\e\e1" > set pager_index_lines=0 > then you can toggle pager_inde_lines with "I" in your pager. Wow! All right, all right, I am impressed! :-) Stop showing off now, Sec. Vikas From michael@tis.com Tue Feb 10 10:48:00 1998 Return-Path: michael@tis.com Received: from relay.la.tis.com (firewall-user@relay.la.tis.com [198.51.22.11]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id KAA04093 for ; Tue, 10 Feb 1998 10:47:59 -0800 (PST) Received: by relay.la.tis.com; id KAA15582; Tue, 10 Feb 1998 10:59:21 -0800 (PST) Received: from gila.la.tis.com(192.5.49.200) by relay.la.tis.com via smap (3.2) id xma015569; Tue, 10 Feb 98 10:59:03 -0800 Received: (from michael@localhost) by gila.la.tis.com (8.8.7/8.8.7) id KAA18245; Tue, 10 Feb 1998 10:44:00 -0800 (PST) Message-ID: <19980210104359.64967@la.tis.com> Date: Tue, 10 Feb 1998 10:43:59 -0800 From: Michael Elkins To: Harald Koenig Cc: mutt-users@cs.hmc.edu, Thomas Roessler Subject: Re: mutt doesn't quote TABs in quoted-printable enc. Mail-Followup-To: Harald Koenig , mutt-users@cs.hmc.edu, Thomas Roessler References: <19980210000821.30266@tat.physik.uni-tuebingen.de> <19980209160715.61500@la.tis.com> <19980210171348.61403@tat.physik.uni-tuebingen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.2i In-Reply-To: <19980210171348.61403@tat.physik.uni-tuebingen.de>; from Harald Koenig on Tue, Feb 10, 1998 at 05:13:48PM +0100 On Tue, Feb 10, 1998 at 05:13:48PM +0100, Harald Koenig wrote: > are there any RFCs which state that TABs shouldn't be converted? I know > it's a non-printing character, so I maybe I can't complain about this ?! They *can* be converted, but it is not required by RFC2047 (see the section on quoted-printable encoding). > anyhow, since I don't think we (mutt-users) will make all LISTSERVs in the > world change their systems to retain TABs, what about a mutt optin at > least when using PGP which quotes _all_ TABs ? This could probably be controlled by $pgp_strict_enc. No need for another variable. me From jkj@sco.com Tue Feb 10 11:35:21 1998 Return-Path: jkj@sco.com Received: from hyperion.pdev.sco.com (root@hyperion.pdev.sco.COM [132.147.65.44]) by turing.cs.hmc.edu (8.8.5/8.8.4) with ESMTP id LAA11568 for ; Tue, 10 Feb 1998 11:35:17 -0800 (PST) Received: from localhost (2795 bytes) by hyperion.pdev.sco.com via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Tue, 10 Feb 1998 11:39:34 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Feb-2) Message-ID: <19980210113934.11707@sco.com> Date: Tue, 10 Feb 1998 11:39:34 -0800 From: "J. Kean Johnston" To: Mutt User List Subject: meta key patch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 Organization: The Santa Cruz Operation, Inc. I posted this a while back but never saw it come to the list, so I am re-posting. If it did indeed make it out, sorry for the double post. This patch adds a new boolean option "meta_key", which makes Mutt interpret keystrokes with the high bit set as two keystrokes: the ESC character and whatever the result of stripping the high bit from the input character is. Allows things like Alt-t to be the same as ESC t on SCO, Linux and other consoles. *** curs_lib.c.jkj Mon Feb 2 22:41:15 1998 --- curs_lib.c Mon Feb 2 22:43:47 1998 *************** *** 56,61 **** --- 56,68 ---- ch = getch (); if (Signals & S_INTERRUPT) mutt_query_exit (); + + if ((ch & 0x80) && option (OPTMETAKEY)) + { + ch &= ~0x80; + mutt_ungetch(ch); + ch = '\033'; + } return (ch == ctrl ('G') ? ERR : ch); } *** init.h.jkj Mon Feb 2 22:34:44 1998 --- init.h Mon Feb 2 22:36:18 1998 *************** *** 107,112 **** --- 107,113 ---- { "mask", DT_RX, R_NONE, &Mask }, { "mbox", DT_PATH, R_BOTH, S_DECL(Inbox) }, { "mbox_type", DT_MAGIC,R_NONE, &DefaultMagic }, + { "meta_key", DT_BOOL, R_NONE, (void *) OPTMETAKEY, 0 }, { "metoo", DT_BOOL, R_NONE, (void *) OPTMETOO, 0 }, { "menu_scroll", DT_BOOL, R_NONE, (void *) OPTMENUSCROLL }, { "mime_fwd", DT_BOOL, R_NONE, (void *) OPTMIMEFWD, 0 }, *** mutt.h.jkj Mon Feb 2 22:36:28 1998 --- mutt.h Mon Feb 2 22:36:59 1998 *************** *** 172,177 **** --- 172,178 ---- OPTSTATUSONTOP, OPTALLOW8BIT, OPTASCIICHARS, + OPTMETAKEY, OPTMETOO, OPTEDITHDRS, OPTARROWCURSOR, *** doc/manual.sgml.jkj Mon Feb 2 22:50:20 1998 --- doc/manual.sgml Mon Feb 2 22:55:01 1998 *************** *** 2554,2559 **** --- 2554,2571 ---- The default mailbox type used when creating new folders. May be any of mbox, MMDF, MH and Maildir. + meta_key