From pinedev@shiva0.cac.washington.edu Mon Jun 1 09:15:19 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 1 Jun 1998 09:15:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA04827 for ; Mon, 1 Jun 1998 09:15:17 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA27422; Mon, 1 Jun 1998 09:15:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA21682; Mon, 1 Jun 1998 09:09:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA39892 for ; Mon, 1 Jun 1998 09:07:45 -0700 Received: from solstice.zdi.zd.com (solstice.zdi.zd.com [155.40.99.126]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA21605 for ; Mon, 1 Jun 1998 09:07:40 -0700 Received: from jhekmanpc.zd.com (cwashburnpc.zdi.zd.com [155.40.99.19]) by solstice.zdi.zd.com (8.8.7/8.8.7) with SMTP id LAA14343 for ; Mon, 1 Jun 1998 11:09:38 -0400 Message-Id: Date: Mon, 1 Jun 1998 12:05:22 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jessica Perry Hekman To: Pine Discussion Forum Subject: PCPine and hanging IMAP connection MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: jphekman@shell3.shore.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have a request for the developers out there: I've observed that when PCPine (3.96) tries to connect to its IMAP server and gets a slow connection, it ties up my entire machine (Windows 95, and unfortunately upgrading to NT may not be an option). In other words, I can't use other applications while waiting for that server response. I'm assuming, of course, that I'm not missing some configuration option :) Is there any chance of getting this fixed in a future release? --- Jessica Perry Hekman * http://www.arborius.net/~jphekman/ Composed with DragonDictate ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Mon Jun 1 10:57:45 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 1 Jun 1998 10:57:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA06261 for ; Mon, 1 Jun 1998 10:57:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA26297; Mon, 1 Jun 1998 10:57:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA11927; Mon, 1 Jun 1998 10:53:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA15576 for ; Mon, 1 Jun 1998 10:51:52 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA23774 for ; Mon, 1 Jun 1998 10:51:51 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id MAA29537 for ; Mon, 1 Jun 1998 12:51:49 -0500 Message-Id: Date: Mon, 1 Jun 1998 12:51:49 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: PCPine and hanging IMAP connection In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Jessica Perry Hekman >Date: Mon, 1 Jun 1998 12:05:22 -0400 (Eastern Daylight Time) >I have a request for the developers out there: I've observed that when PCPine >(3.96) tries to connect to its IMAP server and gets a slow connection, it ties >up my entire machine (Windows 95, and unfortunately upgrading to NT may not be >an option). The behavior of attempting to connect to a slow server is the same on NT or Unix Pine, for that matter. I agree that it's annoying not to be able to run such a process in background. From pinedev@shiva0.cac.washington.edu Mon Jun 1 11:20:58 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 1 Jun 1998 11:20:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA06881 for ; Mon, 1 Jun 1998 11:20:56 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id LAA01159; Mon, 1 Jun 1998 11:20:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA12871; Mon, 1 Jun 1998 11:17:00 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA74586 for ; Mon, 1 Jun 1998 11:16:04 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA10818 for ; Mon, 1 Jun 1998 11:16:03 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id OAA21952; Mon, 1 Jun 1998 14:15:55 -0400 (EDT) Received: from rock.me.mtu.edu (root@rock.me.mtu.edu [141.219.25.31]) by mtu.edu (8.8.8/8.8.8) with ESMTP id OAA22202; Mon, 1 Jun 1998 14:15:55 -0400 (EDT) Received: from aegir.me.mtu.edu (aegir.me.mtu.edu [141.219.24.49]) by rock.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with SMTP id OAA06796; Mon, 1 Jun 1998 14:15:52 -0400 (EDT) Message-Id: Date: Mon, 1 Jun 1998 14:15:50 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: Re: PCPine and hanging IMAP connection In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Sender: edan@aegir.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 1 Jun 1998, Adam H. Kerman wrote: > The behavior of attempting to connect to a slow server is the same on NT or Unix > Pine, for that matter. I agree that it's annoying not to be able to run such a > process in background. It hangs your entire Unix machine? That is what the original author wrote about a Win95 box, and I highly doubt that Unix Pine connecting to a IMAP server hangs the entire machine. It certainly will hang your Pine session, of course. I did grow tired of waiting for Pine's "status updating" to complete--pine would suddenly freeze in the middle of reading a message, and usually when I wanted to go to the next page :) But I moved my mailbox to a different server and shrunk it down... now the wait is shorter so I don't care. I wonder if there is a way to make that update asynchronous--it seems like a fair trade off to make the inbox "(READONLY)" while the update is occurring, but I suppose you would either need to make Pine multithreaded, and have that mess of different platforms, or fork another Pine process and use shared memory... and have that mess of different platforms. So it doesn't surprise me that it hasn't been done yet :) - edan -- Edan Idzerda System Administrator -- Michigan Technological University, Houghton MI USA It seemed like a good idea, at the time. From pinedev@shiva0.cac.washington.edu Mon Jun 1 11:44:23 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 1 Jun 1998 11:44:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA07348 for ; Mon, 1 Jun 1998 11:44:22 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id LAA28040; Mon, 1 Jun 1998 11:44:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA11843; Mon, 1 Jun 1998 11:40:15 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA28366 for ; Mon, 1 Jun 1998 11:39:11 -0700 Received: from solstice.zdi.zd.com (solstice.zdi.zd.com [155.40.99.126]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA13657 for ; Mon, 1 Jun 1998 11:39:10 -0700 Received: from jhekmanpc.zd.com (cwashburnpc.zdi.zd.com [155.40.99.19]) by solstice.zdi.zd.com (8.8.7/8.8.7) with SMTP id NAA14396; Mon, 1 Jun 1998 13:38:51 -0400 Message-Id: Date: Mon, 1 Jun 1998 14:34:27 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jessica Perry Hekman To: Pine Discussion Forum Subject: Re: PCPine and hanging IMAP connection In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Edan Idzerda X-Cc: Pine Discussion Forum X-X-Sender: jphekman@shell3.shore.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 1 Jun 1998, Edan Idzerda wrote: > I wonder if there is a way to make that update asynchronous--it seems > like a fair trade off to make the inbox "(READONLY)" while the update is > occurring, but I suppose you would either need to make Pine multithreaded, > and have that mess of different platforms, or fork another Pine process and > use shared memory... and have that mess of different platforms. I'd definitely settle for being able to use other applications while PCpine works. Unix users should already be able to do this by hopping to another window. (Notice I'm assuming everyone uses X. This is probably a faulty assumption, but there you go :) --- Jessica Perry Hekman * http://www.arborius.net/~jphekman/ Composed with DragonDictate From pinedev@shiva0.cac.washington.edu Tue Jun 2 10:02:47 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Tue, 2 Jun 1998 10:02:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA18110 for ; Tue, 2 Jun 1998 10:02:45 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA25923; Tue, 2 Jun 1998 10:02:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA10678; Tue, 2 Jun 1998 09:58:41 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA38508 for ; Tue, 2 Jun 1998 09:56:01 -0700 Received: from ashawna.eni.net (firewall-user@chastity.eni.net [206.135.49.2]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA11696 for ; Tue, 2 Jun 1998 09:55:59 -0700 Received: from localhost (drachen@localhost [127.0.0.1]) by ashawna.eni.net (8.8.7/8.8.7) with SMTP id JAA07826 for ; Tue, 2 Jun 1998 09:54:38 -0700 Message-Id: Date: Tue, 2 Jun 1998 09:54:36 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Vinnie Chassot To: Pine Discussion Forum Subject: killfiles MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I know this has been discussed before, but I suck and didn't save the info. I tried searching the archived message database, but I only came up with one of robin's .sigs. And Robin's page is down. So I ask the stupid, FAQ which is not in the FAQ Are we getting killfiles? Do we already have killfiles (I was told by someone that pine does, but having read through the helpfiles and the man page more times than I want to know, I'm sure I would have noticed) and we just don't know it? When? Vinnie -- drachen@eni.net System Administrator Epoch Internet "It's more than just eye to eye learn the things I could never apply" -- Least Complicated ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Tue Jun 2 10:24:51 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Tue, 2 Jun 1998 10:24:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA28015 for ; Tue, 2 Jun 1998 10:24:49 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA26599; Tue, 2 Jun 1998 10:24:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA24037; Tue, 2 Jun 1998 10:19:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA55970 for ; Tue, 2 Jun 1998 10:17:20 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA06694 for ; Tue, 2 Jun 1998 10:17:12 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id MAA16542 for ; Tue, 2 Jun 1998 12:17:14 -0500 Message-Id: Date: Tue, 2 Jun 1998 12:17:14 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: killfiles In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Vinnie Chassot >Date: Tue, 2 Jun 1998 09:54:36 -0700 (PDT) >I know this has been discussed before, but I suck and didn't save the >info. I tried searching the archived message database, but I only came up >with one of robin's .sigs. And Robin's page is down. Excuse me. Self flagellation is not permitted on this list. Please wait to receive abuse through normal channels. >Are we getting killfiles? No. >Do we already have killfiles (I was told by someone that pine does, but having >read through the helpfiles and the man page more times than I want to know, I'm >sure I would have noticed) and we just don't know it? There is an FAQ describing how to use the killfile features of rn-style newsreaders (trn, slrn, etc.) in batch-processing mode. This'll mark messages accordingly in your .newsrc. Then, you can read news with pine. It's posted to news.software.readers. Or get it from http://www.faq.org/ or ftp it from rtfm.mit.edu. From pinedev@shiva0.cac.washington.edu Tue Jun 2 17:23:25 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Tue, 2 Jun 1998 17:23:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA28692 for ; Tue, 2 Jun 1998 17:23:24 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id RAA08553; Tue, 2 Jun 1998 17:23:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id RAA16640; Tue, 2 Jun 1998 17:20:32 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id RAA71684 for ; Tue, 2 Jun 1998 17:19:57 -0700 Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA28237 for ; Tue, 2 Jun 1998 17:19:56 -0700 Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA24121 for ; Tue, 2 Jun 1998 17:19:56 -0700 (MST) Received: from usr10.primenet.com(206.165.6.210) via SMTP by smtp03.primenet.com, id smtpd011909; Tue Jun 2 17:05:14 1998 Message-Id: Date: Tue, 2 Jun 1998 17:03:48 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Kanipso To: Pine Discussion Forum Subject: Re: PCPine and hanging IMAP connection MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- I had the same problem and I changed these lines in my pinerc file. The folder colloection line I added 143 (the port that most imap servers run on). Then changed the rsh timeout to 0 (pine tries to connect via rsh first). after that I haven't noticed any lag. folder-collections=/user/j/jamallen/mail/[], BARBZ {imap2.asu.edu:143/user=mattt}INBOX.[] rsh-open-timeout=0 From: Jessica Perry Hekman Date: Mon, 1 Jun 1998 14:34:27 -0400 (Eastern Daylight Time) To: Pine Discussion Forum Subject: Re: PCPine and hanging IMAP connection Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 1 Jun 1998, Edan Idzerda wrote: > I wonder if there is a way to make that update asynchronous--it seems > like a fair trade off to make the inbox "(READONLY)" while the update is > occurring, but I suppose you would either need to make Pine multithreaded, > and have that mess of different platforms, or fork another Pine process and > use shared memory... and have that mess of different platforms. I'd definitely settle for being able to use other applications while PCpine works. Unix users should already be able to do this by hopping to another window. (Notice I'm assuming everyone uses X. This is probably a faulty assumption, but there you go :) - --- Jessica Perry Hekman * http://www.arborius.net/~jphekman/ Composed with DragonDictate _______ ,--. _____ kanipso@primenet.com (_____ ) \ |_ (_____)___ jamallen@primenet.com __/ / (__ _) _. __,-' ) death@cybermail.net Y / ,-' `-'_.- / _ ,' d0cd00m@hotmail.com / ;' <_--\ \' (_,-'/ ,' kanipso@thepentagon.com /_/ \ \ /,' kanipso@usa.net / \_\ /' kanipso316@aol.com PGP fingerprint = 33 08 75 BE 0B B0 69 EB 03 B4 A8 20 88 57 1C 60 Sitting in A room full of candles thinking of the people I have dismantled.. Sometimes You Bleed just to know your alive.. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNXSS6SZKLn+j1Vr9AQFjUgP+KPhGYe4silRAuURFVjE0BmULjjUhbEtu Q7F+HvWmnlLfyYxWmm7Xn4gnWN0OquzQq1gW86hBbRd6d5KnYCebbMZg5QqQQ9ZS AKGLIglbVYpmGn47W/WICgM54r6Ia6VFautOU0NWkSpgRIGDS8Nfi32z3jz2kXWC zZefZZIwRfk= =HU/0 -----END PGP SIGNATURE----- From pinedev@shiva0.cac.washington.edu Wed Jun 3 12:33:46 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Wed, 3 Jun 1998 12:33:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA23566 for ; Wed, 3 Jun 1998 12:33:45 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id MAA29122; Wed, 3 Jun 1998 12:33:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA27759; Wed, 3 Jun 1998 12:26:24 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA68658 for ; Wed, 3 Jun 1998 12:22:32 -0700 Received: from home.merit.edu (home.merit.edu [198.108.60.42]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA31384 for ; Wed, 3 Jun 1998 12:22:25 -0700 Received: from home.merit.edu (localhost [127.0.0.1]) by home.merit.edu (8.8.8/merit-2.0) with ESMTP id PAA01526 for ; Wed, 3 Jun 1998 15:22:31 -0400 (EDT) Message-Id: <199806031922.PAA01526@home.merit.edu> Date: Wed, 03 Jun 1998 15:22:30 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Pat Smith To: Pine Discussion Forum Subject: Pine---> Netscape transition X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi -- I have some customers who are currently reading mail using Pine. We need to move them to a Netscape Messaging server environment. Does anyone have experience moving the directories where users have filed their mail when using Pine to the Netscape environment without disturbing the directory structure. i.e., keep it transparent to the users? Pine is in a SunOS environment and NS Messaging server is Solaris. thanks in advance for help or pointers to help. - pat smith ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Wed Jun 3 12:48:18 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Wed, 3 Jun 1998 12:48:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA23810 for ; Wed, 3 Jun 1998 12:48:16 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id MAA29422; Wed, 3 Jun 1998 12:48:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA28549; Wed, 3 Jun 1998 12:40:41 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA35916 for ; Wed, 3 Jun 1998 12:38:52 -0700 Received: from mailhost.unifiedtech.com (paulaner.unifiedtech.com [205.219.167.102]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id MAA00750 for ; Wed, 3 Jun 1998 12:38:46 -0700 Received: from unifiedtech.com by mailhost.unifiedtech.com (SMI-8.6/SMI-SVR4) id PAA06655; Wed, 3 Jun 1998 15:38:16 -0400 Message-Id: <3575A628.64DB6921@unifiedtech.com> Date: Wed, 03 Jun 1998 15:38:16 -0400 Reply-To: Paul.Kraus@unifiedtech.com Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Paul Kraus To: Pine Discussion Forum Subject: Re: Pine---> Netscape transition References: <199806031922.PAA01526@home.merit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: pfk@unifiedtech.com X-To: Pat Smith X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Pat Smith wrote: > I have some customers who are currently reading mail using Pine. We > need to move them to a Netscape Messaging server environment. Does > anyone have experience moving the directories where users have filed > their mail when using Pine to the Netscape environment without disturbing > the directory structure. i.e., keep it transparent to the users? I move back and forth between OINE and NETSCAPE MESSENGER transparently all the time (I prefer Pine but Netscape gives me threading and hot links). Both save their mail "folders" as plain text files. As long as you set the Netscape local (or server if you are using IMAP) path to the same location as the PINE folders you should be OK. > Pine is in a SunOS environment and NS Messaging server is Solaris. > > thanks in advance for help or pointers to help. > > - pat smith > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- -- -------|-------|-------|-------|-------|-------|-------|-------|-------| Paul Kraus email Paul.Kraus@unifiedtech.com IT Engineering voice +1 518 283 1003 ext. 2778 UNIFIED Technologies fax +1 518 283 1189 From pinedev@shiva0.cac.washington.edu Wed Jun 3 12:58:46 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Wed, 3 Jun 1998 12:58:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA23959 for ; Wed, 3 Jun 1998 12:58:45 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id MAA29681; Wed, 3 Jun 1998 12:58:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA22884; Wed, 3 Jun 1998 12:54:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA81020 for ; Wed, 3 Jun 1998 12:52:12 -0700 Received: from server.northland.lib.mi.us (nsms@server.northland.lib.mi.us [198.108.1.170]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA20952 for ; Wed, 3 Jun 1998 12:52:09 -0700 Received: from merit.edu ([198.108.60.148]) by server.northland.lib.mi.us (Netscape Messaging Server 3.52) with ESMTP id AAAD7B; Wed, 3 Jun 1998 15:52:06 -0400 Message-Id: <3575A895.1DDA8CB0@merit.edu> Date: Wed, 03 Jun 1998 15:48:38 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Pat Smith" To: Pine Discussion Forum Subject: Re: Pine---> Netscape transition References: <199806031922.PAA01526@home.merit.edu> <3575A628.64DB6921@unifiedtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: Paul.Kraus@unifiedtech.com, pine-info@u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is helpful but I have additional questions. (note that I am not a sys admin ... so may not phrase things correctly) Anyway, we are moving all the users from one machine where they read mail in the Pine environment, to another machine where Messaging svr is running. I suppose each (pine and mess svr) have their own directory place to plop down the user directories. I figured if one could just copy from one machine to the other and put them in the correct place all would be well. Does this make sense? In the new environment, the users will be a mix of POP3 with a variety of clients and IMAP4 using Communicator. Thanks for your response. - pat Paul Kraus wrote: > Pat Smith wrote: > > > I have some customers who are currently reading mail using Pine. We > > need to move them to a Netscape Messaging server environment. Does > > anyone have experience moving the directories where users have filed > > their mail when using Pine to the Netscape environment without disturbing > > the directory structure. i.e., keep it transparent to the users? > > I move back and forth between OINE and NETSCAPE MESSENGER transparently > all the time (I prefer Pine but Netscape gives me threading and hot > links). Both save their mail "folders" as plain text files. As long as > you set the Netscape local (or server if you are using IMAP) path to the > same location as the PINE folders you should be OK. > > > Pine is in a SunOS environment and NS Messaging server is Solaris. > > > > thanks in advance for help or pointers to help. > > > > - pat smith > > > > ----------------------------------------------------------------- > > For information about this mailing list, and its archives, see: > > http://www.washington.edu/pine/pine-info/ > > ----------------------------------------------------------------- > > -- > -------|-------|-------|-------|-------|-------|-------|-------|-------| > Paul Kraus email Paul.Kraus@unifiedtech.com > IT Engineering voice +1 518 283 1003 ext. 2778 > UNIFIED Technologies fax +1 518 283 1189 From pinedev@shiva0.cac.washington.edu Wed Jun 3 14:40:50 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Wed, 3 Jun 1998 14:40:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA25923 for ; Wed, 3 Jun 1998 14:40:49 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id OAA02751; Wed, 3 Jun 1998 14:40:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA21670; Wed, 3 Jun 1998 14:36:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA35902 for ; Wed, 3 Jun 1998 14:33:23 -0700 Received: from solstice.zdi.zd.com (solstice.zdi.zd.com [155.40.99.126]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA06172 for ; Wed, 3 Jun 1998 14:33:22 -0700 Received: from jhekmanpc.zd.com (cwashburnpc.zdi.zd.com [155.40.99.19]) by solstice.zdi.zd.com (8.8.7/8.8.7) with SMTP id QAA15568 for ; Wed, 3 Jun 1998 16:35:43 -0400 Message-Id: Date: Wed, 3 Jun 1998 17:30:46 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jessica Perry Hekman To: Pine Discussion Forum Subject: Re: PCPine and hanging IMAP connection In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: jphekman@shell3.shore.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 2 Jun 1998, Kanipso wrote: > I had the same problem and I changed these lines in my pinerc file. > The folder colloection line I added 143 (the port that most imap servers > run on). Then changed the rsh timeout to 0 (pine tries to connect via rsh > first). after that I haven't noticed any lag. I tried this and saw no difference. Maybe it depends on your local network setup? --- Jessica Perry Hekman * http://www.arborius.net/~jphekman/ Composed with DragonDictate From pinedev@shiva0.cac.washington.edu Wed Jun 3 15:06:34 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Wed, 3 Jun 1998 15:06:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA26324 for ; Wed, 3 Jun 1998 15:06:33 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id PAA03233; Wed, 3 Jun 1998 15:06:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA08539; Wed, 3 Jun 1998 15:03:42 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id PAA72944 for ; Wed, 3 Jun 1998 15:01:40 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA21907 for ; Wed, 3 Jun 1998 15:01:39 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id SAA14021; Wed, 3 Jun 1998 18:01:36 -0400 (EDT) Received: from rock.me.mtu.edu (root@rock.me.mtu.edu [141.219.25.31]) by mtu.edu (8.8.8/8.8.8) with ESMTP id SAA13336; Wed, 3 Jun 1998 18:01:35 -0400 (EDT) Received: from aegir.me.mtu.edu (aegir.me.mtu.edu [141.219.24.49]) by rock.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with SMTP id SAA22553; Wed, 3 Jun 1998 18:01:31 -0400 (EDT) Message-Id: Date: Wed, 3 Jun 1998 18:01:32 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: Re: PCPine and hanging IMAP connection In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Perry Hekman X-Cc: Pine Discussion Forum X-Sender: edan@aegir.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 3 Jun 1998, Jessica Perry Hekman wrote: > On Tue, 2 Jun 1998, Kanipso wrote: > > > I had the same problem and I changed these lines in my pinerc file. > > The folder colloection line I added 143 (the port that most imap servers > > run on). Then changed the rsh timeout to 0 (pine tries to connect via rsh > > first). after that I haven't noticed any lag. > > I tried this and saw no difference. Maybe it depends on your local network > setup? I think that "Kanipso" failed to realize that you were using PCPine. At least, I don't believe that PC's use "rsh" to do anything, not unless you've set up some funky cygwin32-opennt thing. I agree that it sucks that you can't do anything else while it is connecting, but I'm no crack dos/windoze programmer so I can't help you much. Run Linux? :-) - edan From pinedev@shiva0.cac.washington.edu Thu Jun 4 00:31:24 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Thu, 4 Jun 1998 00:31:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA32317 for ; Thu, 4 Jun 1998 00:31:23 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id AAA12920; Thu, 4 Jun 1998 00:31:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id AAA11024; Thu, 4 Jun 1998 00:28:29 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA72014 for ; Thu, 4 Jun 1998 00:26:54 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA21162 for ; Thu, 4 Jun 1998 00:26:54 -0700 Received: from luomat.peak.org (cc344191-a.ewndsr1.nj.home.com [24.2.83.40]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id AAA12273 for ; Thu, 4 Jun 1998 00:26:51 -0700 Received: (from luomat@localhost) by luomat.peak.org (8.8.8/8.8.8) id DAA16479 for pine-info@cac.washington.edu; Thu, 4 Jun 1998 03:26:47 -0400 (EDT) Message-Id: <199806040726.DAA16479@luomat.peak.org> Date: Thu, 4 Jun 98 03:26:44 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: ``Development of Pine 4.00 is nearing completion'' Content-Type: text/plain MIME-Version: 1.0 X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Come on folks, the announcement was made THREE months ago that ``Development of Pine 4.00 is nearing completion'' An email was sent to the PINE-announce list, and a webpage was started. Then three months of "Real Soon Now" to break up the otherwise defeaning silence. No followup messages, the web page hasn't changed since it went live. Is this thing coming out within the next month or not? TjL -- For PEAK related mail, please use: luomat+PEAK@luomat.peak.org PEAK NeXT/OpenStep/Rhapsody FTP Site http://www.peak.org/next ftp://next-ftp.peak.org/pub/next http://www.peak.org/openstep ftp://next-ftp.peak.org/pub/openstep http://www.peak.org/rhapsody ftp://next-ftp.peak.org/pub/rhapsody ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Thu Jun 4 08:55:47 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Thu, 4 Jun 1998 08:55:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA08898 for ; Thu, 4 Jun 1998 08:55:45 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id IAA20523; Thu, 4 Jun 1998 08:55:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA24901; Thu, 4 Jun 1998 08:51:53 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA75626 for ; Thu, 4 Jun 1998 08:51:19 -0700 Received: from pump2.york.ac.uk (pump2.york.ac.uk [144.32.128.12]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA15357 for ; Thu, 4 Jun 1998 08:51:18 -0700 Received: from pippin.york.ac.uk (pippin.york.ac.uk [144.32.128.9]) by pump2.york.ac.uk (8.8.7/8.8.7) with SMTP id QAA00568 for ; Thu, 4 Jun 1998 16:51:16 +0100 (BST) Message-Id: <1734372.3105967875@pippin.york.ac.uk> Date: Thu, 04 Jun 1998 16:51:15 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Mike Brudenell" To: Pine Discussion Forum Subject: Pine 4.00: Will it have True Threading? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi! Does anybody know/can anyone remember whether Pine 4.00 will have proper threading for reading Usenet News (as against the current Ordered Subject approximation)? I've checked the Pine 4.00 Preview page at the Pine Information Centre but threading isn't mentioned (as far as I can see) one way or the other. Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel: +44-1904-433811 FAX: +44-1904-433740 http://www.york.ac.uk/~pmb1/ * Unsolicited commercial e-mail is NOT welcome at this e-mail address. * ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Thu Jun 4 09:29:37 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Thu, 4 Jun 1998 09:29:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA09705 for ; Thu, 4 Jun 1998 09:29:36 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA21080; Thu, 4 Jun 1998 09:29:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA25313; Thu, 4 Jun 1998 09:25:31 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA78298 for ; Thu, 4 Jun 1998 09:24:06 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA32148 for ; Thu, 4 Jun 1998 09:23:58 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id LAA24434 for ; Thu, 4 Jun 1998 11:24:03 -0500 Message-Id: Date: Thu, 4 Jun 1998 11:24:03 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Pine 4.00: Will it have True Threading? In-Reply-To: <1734372.3105967875@pippin.york.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Mike Brudenell >Date: Thu, 04 Jun 1998 16:51:15 +0100 >Does anybody know/can anyone remember whether Pine 4.00 will have proper >threading for reading Usenet News? I'd rather have it order mail messages where In-Reply-To headers exist. If they don't, I'd like to have the ability to select additional messages while I'm reading, not just from the Index screen. From pinedev@shiva0.cac.washington.edu Thu Jun 4 21:45:07 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Thu, 4 Jun 1998 21:45:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA17390 for ; Thu, 4 Jun 1998 21:45:05 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id VAA09123; Thu, 4 Jun 1998 21:44:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id VAA27355; Thu, 4 Jun 1998 21:40:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id VAA11038 for ; Thu, 4 Jun 1998 21:36:48 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA01594 for ; Thu, 4 Jun 1998 21:36:46 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id AAA26067 for ; Fri, 5 Jun 1998 00:36:44 -0400 (EDT) Received: from rock.me.mtu.edu (root@rock.me.mtu.edu [141.219.25.31]) by mtu.edu (8.8.8/8.8.8) with ESMTP id AAA02498 for ; Fri, 5 Jun 1998 00:36:44 -0400 (EDT) Received: from rock.me.mtu.edu (edan@rock.me.mtu.edu [141.219.25.31]) by rock.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with SMTP id AAA00095 for ; Fri, 5 Jun 1998 00:36:41 -0400 (EDT) Message-Id: Date: Fri, 5 Jun 1998 00:36:39 -0400 (EDT) Reply-To: Edan Idzerda Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: vi-style key bindings MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: edan@rock.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Call me evil, call me what you will, but I wrote a patch a while back to use vi-style key bindings, primarily just so that j/k would duplicate n/p. I wrote it as a new 'feature' called enable-vi-keys and it seems to work quite well. I wanted to actually change the behavior of the global key input function, but it didn't have access to the "state" variable so I just hacked it in all the different modules I wanted it to work in. I was a long time Elm user, and I've used this feature to convert a number of others... what are the chances that something like this could be worked into the production tree? I'm willing to rewrite my patches in a way that changes fewer files, but again it seemed to require too great a change to read_char() in ttyin.c. Instead, I chose to add sections of code like: if(F_ON(F_ENABLE_VI_KEYS,state)) { if (command == 'j') command = 'n'; else if (command == 'k') command = 'p'; } To places where I wanted to circumvent Pine's regular keystrokes with vi-style ones. Surprisingly, the main menu is the only place with significant conflicts (that I could tell). Sure, the index has "j" for jump by default, but if you're an Elm user you'll just want to type the number anyway. Did I miss an address for patches? Or does the development team like to keep code changes to within their castle? In any event, my patches are just a trivial but nice addition to a fine program. - edan ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Thu Jun 4 22:43:43 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Thu, 4 Jun 1998 22:43:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA20939 for ; Thu, 4 Jun 1998 22:43:41 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id WAA09818; Thu, 4 Jun 1998 22:43:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id WAA28776; Thu, 4 Jun 1998 22:41:49 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id WAA24884 for ; Thu, 4 Jun 1998 22:37:51 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA05435 for ; Thu, 4 Jun 1998 22:37:50 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id BAA27514 for ; Fri, 5 Jun 1998 01:37:49 -0400 (EDT) Received: from rock.me.mtu.edu (root@rock.me.mtu.edu [141.219.25.31]) by mtu.edu (8.8.8/8.8.8) with ESMTP id BAA14527 for ; Fri, 5 Jun 1998 01:37:48 -0400 (EDT) Received: from rock.me.mtu.edu (edan@rock.me.mtu.edu [141.219.25.31]) by rock.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with SMTP id BAA00183 for ; Fri, 5 Jun 1998 01:37:45 -0400 (EDT) Message-Id: Date: Fri, 5 Jun 1998 01:37:44 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: Re: vi-style key bindings In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: edan@rock.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 5 Jun 1998, Edan Idzerda wrote: > Call me evil, call me what you will, but I wrote a patch a while > back to use vi-style key bindings, primarily just so that j/k > would duplicate n/p. Call me silly, replying to my own email. Shortly after I sent this message, I went back to the source to examine it again. If I had been more patient I wouldn't have sent the message. My original patchset modified addrbook.c folder.c init.c mailcmd.c mailindx.c other.c pine.h Now I only modify init.c (one line added) ttyin.c (six lines added) pine.h (one line added, one line changed) The only difference is that the original patchset allowed j/k to be used at any time, except in the folder index where it would check the state. Now the only problem is that j/k are now always replaced with n/p, even when inputing text. Bummer :) If anyone is interested in this sort of thing, let me know. These sort of vi-key bindings really get user-interface messy on the "MAIN MENU" screen where you have J)ournal and K)eyboard lock. But everywhere else, it's no problem. The last time I worked on it, I just didn't let vi keys work on the main menu, since I always pick the letter away. Blah. That's enough out of me for tonight. - edan From pinedev@shiva0.cac.washington.edu Fri Jun 5 03:01:28 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Fri, 5 Jun 1998 03:01:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA25753 for ; Fri, 5 Jun 1998 03:01:23 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id CAA12512; Fri, 5 Jun 1998 02:36:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id CAA05848; Fri, 5 Jun 1998 02:33:40 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id CAA21726 for ; Fri, 5 Jun 1998 02:32:06 -0700 Received: from plato.physik.uni-konstanz.de (plato.physik.uni-konstanz.de [134.34.147.28]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA18511 for ; Fri, 5 Jun 1998 02:32:03 -0700 Received: from localhost (flo@localhost) by plato.physik.uni-konstanz.de (8.8.5/8.8.5) with SMTP id LAA00309 for ; Fri, 5 Jun 1998 11:31:51 +0200 Message-Id: Date: Fri, 5 Jun 1998 11:31:51 +0200 (CEST) Reply-To: Florian Kolbe Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Florian Kolbe To: Pine Discussion Forum Subject: To: vs. X-To: ('To:' entry missing domain) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I got an e-mail where the 'To:' entry was missing the domain (see below). Pine simply added my own default domain when displaying the simple header. The resulting 'To:' address is simply wrong. Why doesn't pine use the 'X-To:' entry? (see full header below) Cheers, Florian Kolbe Full header (partial, note 'To:' entry missing domain): From: "Mike Brudenell" To: Pine Discussion Forum Subject: Pine 4.00: Will it have True Threading? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Simple header ('To:' entry is wrong): Date: Thu, 4 Jun 1998 16:51:15 +0100 From: Mike Brudenell To: Pine Discussion Forum Subject: Pine 4.00: Will it have True Threading? ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Fri Jun 5 07:23:11 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Fri, 5 Jun 1998 07:23:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA29910 for ; Fri, 5 Jun 1998 07:23:10 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA16303; Fri, 5 Jun 1998 07:23:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA12333; Fri, 5 Jun 1998 07:18:15 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA56032 for ; Fri, 5 Jun 1998 07:17:20 -0700 Received: from ns3.quik.com (ns3.quik.com [209.80.13.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA07638 for ; Fri, 5 Jun 1998 07:17:12 -0700 Received: from ns3.quik.com (ns3.quik.com [209.80.13.1]) by ns3.quik.com (8.8.7/8.8.5) with SMTP id OAA47050; Fri, 5 Jun 1998 14:16:41 GMT Message-Id: Date: Fri, 5 Jun 1998 07:16:39 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Colin J. Raven" To: Pine Discussion Forum Subject: Re: vi-style key bindings In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Edan Idzerda X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Call me evil, call me what you will, but I wrote a patch a while > back to use vi-style key bindings, primarily just so that j/k > would duplicate n/p. Yes, you are evil if you bring *anything* from that accursed pox-ridden son of Beelzebub called vi > I wrote it as a new 'feature' called enable-vi-keys and it seems > to work quite well. Now I am definitely in awe. Anyone who can write "features" just acquired God-like status in my eyes, but please go on....sorry to interrupt. >I wanted to actually change the behavior of > the global key input function, but it didn't have access to the > "state" variable so I just hacked it in all the different modules > I wanted it to work in. Er, OK I guess. Hacking *anything* in a mail program is an accomplishment. You have just become elevated to "Deity" status. I am not only in awe, now I'm afraid, very afraid. > I was a long time Elm user, At the risk of seeming somewhat small minded here (I am, I like Pine a helluva lot) you are a long time...what now??? "Elm User"??? Did I hear you correctly? > and I've used this feature to convert a number of others... "Convert others"?? To what Edan, Devil Worship??? > what are the chances that something like > this could be worked into the production tree? I cannot speak for my superhero Stefan, and his band of caped crusaders coding a new Pine long into the night, BUT.........No! There is no chance that any arcane vi attribute will *ever* find it's way into the king of all mail programs. > my patches are just a trivial but nice addition to > a fine program. Edan, lest you think I'm just lashing out in a fit of blind bigotry, I'm *not* The fact that you know enough to write patches to a mail program is awesome in my mind (and I'm *not* kidding, believe me) but here's the point as I see it. Pine represents a step forward, from it's first iteration onwards to this version which is "about as good as it gets". It's intuitive, it just "knows" what users want to do (or it's development team do anyway). Elm is about the most infuriating mail program you could ever find. It 'aint intuitive, it's kludgy, and it's learning curve sucks. vi blows dead monkeys period. You couldn't ask for a more obscure editor than vi. It's quirky, and requires a thought process that could best be described as "lateral" in order to use it properly. Why would you want to import features from packages like that I wonder? Pine and pico have on-screen help that allows some real new folks to get up and running in a heartbeat, and is sufficiently powerful to allow sophisticated users to process huge amounts of mail rapidly and efficiently. When you think "obscure" most people think of emacs...nosir, vi takes the first prize. Emacs is at least a gift from the gods in that it has "power" to do amazing things. (ask Robin) Nononono, if you want a text editor that the average person can use, quickly and effectively, Pico is the way to go. If you want real power, learn emacs. Gawd, why do I always rise to the bait? Edan, I salute you for the try...really. Spend those awesome talents on worthwhile projects. I'm going to lubricate my Pelican now, he looks kinda hungry. -Colin. ---------------------------------------------- Colin J. Raven Network & Systems Administrator, HDS Lab, Inc. Costa Mesa, CA | Harrison, NY "Communications at the Speed of Life" From pinedev@shiva0.cac.washington.edu Fri Jun 5 13:29:39 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Fri, 5 Jun 1998 13:29:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA03353 for ; Fri, 5 Jun 1998 13:29:38 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA25556; Fri, 5 Jun 1998 13:29:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA29273; Fri, 5 Jun 1998 13:25:32 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA15454 for ; Fri, 5 Jun 1998 13:23:43 -0700 Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id NAA06520 for ; Fri, 5 Jun 1998 13:23:42 -0700 Received: from sushi.uni-bonn.de (131.220.225.110,29327) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Fri, 05 Jun 98 22:23:44 MEZ Received: (from robin@localhost) by sushi.uni-bonn.de (8.8.8/8.8.8) id WAA12322; Fri, 5 Jun 1998 22:04:13 +0200 Message-Id: Date: 05 Jun 1998 22:04:12 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: vi-style key bindings In-Reply-To: "Colin J. Raven"'s message of "Fri, 5 Jun 1998 07:16:39 -0700 (PDT)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-To: Pine Discussion Forum X-Attribution: Fireball X-Alignment: Chaotic Evil X-URL: http://franck.pc.uni-koeln.de/~robin/ X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Colin J Raven writes: >> Call me evil, call me what you will, but I wrote a patch a while >> back to use vi-style key bindings, primarily just so that j/k would >> duplicate n/p. > Yes, you are evil if you bring *anything* from that accursed > pox-ridden son of Beelzebub called vi "Conversations devolve to 'vi' for much the same reason that small children eventually start discussing excrement. As disgusting as it is, there is a horrid fascination with it." (Joseph M. Newcomer) [stuff] >> what are the chances that something like this could be worked into >> the production tree? > I cannot speak for my superhero Stefan, and his band of caped > crusaders coding a new Pine long into the night, BUT.........No! > There is no chance that any arcane vi attribute will *ever* find > it's way into the king of all mail programs. I don't quite agree. There is much elegance in vi's movement keymapping. tin has nice movement keybindings, too. Pine does not. YMMV. >> my patches are just a trivial but nice addition to a fine program. > [blabla] Pine represents a step forward, from it's first iteration > onwards to this version which is "about as good as it gets". It's > intuitive, it just "knows" what users want to do (or it's > development team do anyway). Not in my opinion. There are some minor but quite annoying quirks in pine's initial behaviour, e.g. the signature thing and pico's utterly braindead yanking behaviour. [elm bashing] > vi blows dead monkeys period. You couldn't ask for a more obscure > editor than vi. It's quirky, and requires a thought process that > could best be described as "lateral" in order to use it > properly. That is not entirely correct. vi (and vim in particular) is a very, very good editor. It's certainly not "user friendly", but which good program is? > Why would you want to import features from packages like that I > wonder? Because it's fast and efficient. > Pine and pico have on-screen help that allows some real new folks to > get up and running in a heartbeat, and is sufficiently powerful to > allow sophisticated users to process huge amounts of mail rapidly > and efficiently. Not. High volume mailing lists soon bring pine to a grinding halt and pico is an abomination.[1] Unless you throw in procmail and vi or jed, pine is quite unusable for larger amounts of mail. I get about 500 mails a day, and without Gnus, I would spend half my time writing weighted score rules for procmail. Before I switched to Gnus, I had about 900k of procmail code. > When you think "obscure" most people think of emacs...nosir, vi > takes the first prize. Good boy. > Emacs is at least a gift from the gods in that it has "power" to do > amazing things. (ask Robin) Ummm... nope. You always have to take into account that XEmacs is a monster when it comes to sucking up resources. robin@sushi:/usr/local/lib > du xemacs 58217 xemacs robin@sushi:/usr/local/lib > du xemacs-21.0-b42/ 16715 xemacs-21.0-b42 And that's without MULE and my personal elisp dir. Nope, you cannot quite compare that. And there's this, too: USER PID %CPU %MEM NI VSZ RSS SHRD TT STAT TIME COMMAND robin 278 5.4 23.1 0 20356 14672 2332 9 S 330:59 xemacs robin 12075 0.0 1.2 0 1468 784 620 p0 S 0:00 vi robin 12116 0.0 1.5 0 2900 1012 784 p0 S 0:00 pine > Nononono, if you want a text editor that the average person can use, > quickly and effectively, Pico is the way to go. mcedit, fte, joe (jmacs, jstar), jed... There are many that are about as big and much more powerful. I find mcedit (Midnight Commander's editor) a very interesting alternative in that it much behaves like the editor in Norton Commander. Nice tool. local/lib > for i in pico vim jove xemacs-21.0-b42 jed ;\ do ll `which $i` ; done -rwxr-xr-x 1 root root 3907308 May 31 11:09 /usr/bin/xemacs-21.0-b42 -rwxr-xr-x 1 root root 442531 May 9 05:02 /usr/bin/pico -rwxr-xr-x 1 root root 321064 Nov 14 1997 /usr/bin/vim -rwxr-xr-x 1 root root 175187 Nov 15 1997 /usr/bin/jove -rwxr-xr-x 1 root root 187512 Jun 13 1995 /usr/bin/jed So... pine and jed would make a wonderful pair, especially since jed comes with a WordStar mode... *sigh* > If you want real power, learn emacs. Gawd, why do I always rise to > the bait? Editor envy? "Mine is bigger than anyone else's", y'know? > Edan, I salute you for the try...really. Spend those awesome talents > on worthwhile projects. I'm going to lubricate my Pelican now, he > looks kinda hungry. Is that, like, something you'd rather not talk about in public? Robin Footnotes: [1] Whoever wrote it: don't take it personally. -- Robin S. Socha Join the Fight: Turn your Pentium into a gameboy...Type "WIN" at the prompt From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Sat, 6 Jun 1998 17:21:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA21319 for ; Sat, 6 Jun 1998 17:21:18 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id RAA17455; Sat, 6 Jun 1998 17:21:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id RAA00959; Sat, 6 Jun 1998 17:17:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id RAA77304 for ; Sat, 6 Jun 1998 17:14:36 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA18310 for ; Sat, 6 Jun 1998 17:14:34 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id TAA01369 for ; Sat, 6 Jun 1998 19:14:19 -0500 Message-Id: Date: Sat, 6 Jun 1998 19:14:19 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: vi-style key bindings In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: "Robin S. Socha" >Date: 05 Jun 1998 22:04:12 +0200 >>Colin J Raven writes: >>>Call me evil, call me what you will, but I wrote a patch a while back to use >>>vi-style key bindings, primarily just so that j/k would duplicate n/p. >>Yes, you are evil if you bring *anything* from that accursed pox-ridden son of >>Beelzebub called vi Colin, you don't understand. "j and k" are used because of the arcane nature of the keyboard we use, left to us from the original machine put together from gears and levers attached to individual pieces of type. The gears and levers didn't retract quickly enough in the original model, so a keyboard was designed partly out of a desire to slow down users and partly to fit the type in. Subsequent generations of typewriters solved that problem, actually within a year or two. But, they reused the same key order. (There were other keyboards in use, such as on a Monotype machine, operated entirely with the left hand! while the right hand threw the levers that cast the type. Another keyboard, invented by an Army technician during the WWII who claimed that a different arrangement of the keys could speed up typing. After all, wars cannot be fought without properly processing the paperwork. But, historians have proven that Mr. Dvorak falsifyed his studies. QWERTY order will always be on keyboards.) vi uses "j" and "k" because they are next to each other on the keyboard! Which is a damn good reason to use them. Terminals are still in use today that don't have arrows, or with arrow keys with different key codes. And, most keyboards stick the arrows in uncomfortable locations. "n" and "p" have only a vague advantage over arrows on some keyboards. But, "j" and "k" have a clear advantage. pine really doesn't use neumonics for key bindings. Yes, "j" stands for "jump", but that's a silly thing to call a command. "k" isn't used in the index or the message pager. In the composer, it stands for "kut" so ^c could be used for "cancel". >I don't quite agree. There is much elegance in vi's movement keymapping. tin >has nice movement keybindings, too. Pine does not. YMMV. You start using vi (well, vim really these days) and your fingers learn the commands. It does follow a design which becomes clear AFTER you get used to it. It really doesn't take that long. >Not in my opinion. There are some minor but quite annoying quirks in >pine's initial behaviour, e.g. the signature thing and pico's utterly >braindead yanking behaviour. That's leftover from slow modem days. It's a helpful feature at 1200 or 2400. >High volume mailing lists soon bring pine to a grinding halt . . . Robin, who would want to use pine for use with large lists? >I get about 500 mails a day, and without Gnus, I would spend half my time >writing weighted score rules for procmail. Before I switched to Gnus, I had >about 900k of procmail code. How on earth do people receive that much mail? If I'm on a talky list that I don't keep up with, I trash it. >So... pine and jed would make a wonderful pair, especially since jed >comes with a WordStar mode... *sigh* Heh. On DOS, I still use PC-Write, written by an ex-WordStar encoder. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 8 Jun 1998 00:11:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA06766 for ; Mon, 8 Jun 1998 00:11:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id AAA06718; Mon, 8 Jun 1998 00:11:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id AAA08295; Mon, 8 Jun 1998 00:07:51 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA37434 for ; Mon, 8 Jun 1998 00:03:00 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA25850 for ; Mon, 8 Jun 1998 00:02:59 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id DAA19211 for ; Mon, 8 Jun 1998 03:02:57 -0400 (EDT) Received: from rock.me.mtu.edu (root@rock.me.mtu.edu [141.219.25.31]) by mtu.edu (8.8.8/8.8.8) with ESMTP id DAA17104 for ; Mon, 8 Jun 1998 03:02:57 -0400 (EDT) Received: from rock.me.mtu.edu (edan@rock.me.mtu.edu [141.219.25.31]) by rock.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with SMTP id DAA09237 for ; Mon, 8 Jun 1998 03:02:53 -0400 (EDT) Message-Id: Date: Mon, 8 Jun 1998 03:02:52 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: Re: vi-style key bindings In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: edan@rock.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sat, 6 Jun 1998, Adam H. Kerman wrote: > "n" and "p" have only a vague advantage over arrows on some keyboards. > But, "j" and "k" have a clear advantage. I agree wholeheartedly. I prefer j/k over n/p because it allows my fingers to remain on the home row and doesn't feel like it will lead to a repetitive motion injury. There's that, and the fact that I'm using vi right now. In fact, it was Pine's enable-alt-editor-implicity feature that helped cement my transition to it from Elm. With Pine, in most cases I could now go from folder index to message editor just by hitting 'r' and you have to love that. I'm a Pine Evangelist around here. My vi-keys patch is part of how I lure hardened Elm users away. Frankly, I find Pine without j/k kind of lame now. Did I mention I was using vi right now? I've got my patch down to three files, so that 'j' -> 'n' 'k' -> 'p' '/' -> 'w' The only conflict I'm aware of is the main menu. I haven't decided how to resolve it. You end up losing (J)ournal which I think is a useful function occassionally. You also lose (K)eyboard lock, but I don't really care :) I also presume that if you want vi keys, you don't use the builtin pico. A full-blown vi mode, where you can hit Esc and use vi editing commands in parts of pine where you edit text... is definitely not planned. >:) I'm not going to get into a editor religious war, suffice to say that I use vi because it's powerful and nasty and isn't a 20MB binary. My pine patch is fairly inocuous and obvious is nature; I just wondered if anyone in the Pine community would be interested. - edan p.s. Patching read_command instead of read_char was much smarter. :) From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 8 Jun 1998 07:30:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA14298 for ; Mon, 8 Jun 1998 07:30:55 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA12272; Mon, 8 Jun 1998 07:30:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA15164; Mon, 8 Jun 1998 07:25:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA44504 for ; Mon, 8 Jun 1998 07:23:42 -0700 Received: from ns3.quik.com (ns3.quik.com [209.80.13.1]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA04061 for ; Mon, 8 Jun 1998 07:23:42 -0700 Received: from ns3.quik.com (ns3.quik.com [209.80.13.1]) by ns3.quik.com (8.8.7/8.8.5) with SMTP id OAA44032; Mon, 8 Jun 1998 14:24:55 GMT Message-Id: Date: Mon, 8 Jun 1998 07:24:53 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Colin J. Raven" To: Pine Discussion Forum Subject: Re: vi-style key bindings In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN OK Adam, Edan, here it is.... I'm basically stupid, lazy (or maybe too damn busy) to learn that beast called vi. In the light of what Edan wrote, I fired up vi on Saturday night, and actually read the book while playing with the thing. Yeah, OK I see what you and he are saying. Y'see, one of the effects of being so stupid is that it makes a person very self-righteous in support of the "easy solution". However.....somewhere along the way I thought things were supposed to be as simple as possible. You, Edan, Robin and many others are so far ahead of me it's ridiculous. I guess editors that are more powerful are more appropriate when you're doing advanced stuff. (ask Robin I guess) *But* I *do* believe that an editor that you can use in any condition (and that certainly applies to me) with immediate and predictable reults is the one you stick with until you (or the editor) run outta steam. Same goes for Elm I s'pose. Believe it or not Adam, *that's* what I was getting at. I'm just plain in awe of Edan and folks like him who can write C (to start with) and can modify a mail programs' feature-set. Well, that's my .02 worth for today...maybe. -Colin. On Sat, 6 Jun 1998, Adam H. Kerman wrote: > >From: "Robin S. Socha" > >Date: 05 Jun 1998 22:04:12 +0200 > > >>Colin J Raven writes: > > >>>Call me evil, call me what you will, but I wrote a patch a while back to use > >>>vi-style key bindings, primarily just so that j/k would duplicate n/p. > > >>Yes, you are evil if you bring *anything* from that accursed pox-ridden son of > >>Beelzebub called vi > > Colin, you don't understand. "j and k" are used because of the arcane nature of > the keyboard we use, left to us from the original machine put together from > gears and levers attached to individual pieces of type. The gears and levers > didn't retract quickly enough in the original model, so a keyboard was designed > partly out of a desire to slow down users and partly to fit the type in. > > Subsequent generations of typewriters solved that problem, actually within a > year or two. But, they reused the same key order. (There were other keyboards in > use, such as on a Monotype machine, operated entirely with the left hand! while > the right hand threw the levers that cast the type. Another keyboard, invented > by an Army technician during the WWII who claimed that a different arrangement > of the keys could speed up typing. After all, wars cannot be fought without > properly processing the paperwork. But, historians have proven that Mr. Dvorak > falsifyed his studies. QWERTY order will always be on keyboards.) > > vi uses "j" and "k" because they are next to each other on the keyboard! Which > is a damn good reason to use them. Terminals are still in use today that don't > have arrows, or with arrow keys with different key codes. > > And, most keyboards stick the arrows in uncomfortable locations. > > "n" and "p" have only a vague advantage over arrows on some keyboards. But, "j" > and "k" have a clear advantage. > > pine really doesn't use neumonics for key bindings. Yes, "j" stands for "jump", > but that's a silly thing to call a command. > > "k" isn't used in the index or the message pager. In the composer, it stands for > "kut" so ^c could be used for "cancel". > > >I don't quite agree. There is much elegance in vi's movement keymapping. tin > >has nice movement keybindings, too. Pine does not. YMMV. > > You start using vi (well, vim really these days) and your fingers learn the > commands. It does follow a design which becomes clear AFTER you get used to it. > It really doesn't take that long. > > >Not in my opinion. There are some minor but quite annoying quirks in > >pine's initial behaviour, e.g. the signature thing and pico's utterly > >braindead yanking behaviour. > > That's leftover from slow modem days. It's a helpful feature at 1200 or 2400. > > >High volume mailing lists soon bring pine to a grinding halt . . . > > Robin, who would want to use pine for use with large lists? > > >I get about 500 mails a day, and without Gnus, I would spend half my time > >writing weighted score rules for procmail. Before I switched to Gnus, I had > >about 900k of procmail code. > > How on earth do people receive that much mail? If I'm on a talky list that I > don't keep up with, I trash it. > > >So... pine and jed would make a wonderful pair, especially since jed > >comes with a WordStar mode... *sigh* > > Heh. On DOS, I still use PC-Write, written by an ex-WordStar encoder. > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 8 Jun 1998 07:43:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA14412 for ; Mon, 8 Jun 1998 07:43:44 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA12148; Mon, 8 Jun 1998 07:43:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA27283; Mon, 8 Jun 1998 07:37:35 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA50154 for ; Mon, 8 Jun 1998 07:36:12 -0700 Received: from ns3.quik.com (ns3.quik.com [209.80.13.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA21750 for ; Mon, 8 Jun 1998 07:36:11 -0700 Received: from ns3.quik.com (ns3.quik.com [209.80.13.1]) by ns3.quik.com (8.8.7/8.8.5) with SMTP id OAA09668; Mon, 8 Jun 1998 14:37:23 GMT Message-Id: Date: Mon, 8 Jun 1998 07:37:21 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Colin J. Raven" To: Pine Discussion Forum Subject: Re: vi-style key bindings In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Edan Idzerda X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Edan, Read my post to Adam on this (it's really to you also) > I'm a Pine Evangelist around here. My vi-keys patch is part of how I > lure hardened Elm users away. Frankly, I find Pine without j/k > kind of lame now. AAAAAAARRRGGGHHHHHH! (You *had to* didn't you?) :-) > Did I mention I was using vi right now? Well, *now* you're talking...yup, that's true, no question. vi is lean 'an mean. > I'm not going to get into a editor religious war, suffice to say > that I use vi because it's powerful and nasty and isn't a 20MB > binary. I say again (already said on the post to Adam) that I'm in awe of anyone who can; a) write C b) write (or modify) feature-sets for a mail program Yes, the patches *are* innocuous..absolutely. > My pine patch is fairly inocuous and obvious is nature; > I just wondered if anyone in the Pine community would be interested. I wonder what Stefan thinks? This list got real quiet suddenly :-) It's almost as though the spectators became hushed, awaiting the spectacle of combat in the arena below :) hahahaha! I wasn't flaming you, I hope you realize that. Later oh guru of C -Colin From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 8 Jun 1998 09:57:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA16895 for ; Mon, 8 Jun 1998 09:57:07 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA15792; Mon, 8 Jun 1998 09:57:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA13966; Mon, 8 Jun 1998 09:52:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA70170 for ; Mon, 8 Jun 1998 09:50:57 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA20539 for ; Mon, 8 Jun 1998 09:50:56 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id LAA00045 for ; Mon, 8 Jun 1998 11:50:54 -0500 Message-Id: Date: Mon, 8 Jun 1998 11:50:54 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: vi-style key bindings In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Edan Idzerda >Date: Mon, 8 Jun 1998 03:02:52 -0400 (EDT) >I've got my patch down to three files, so that > 'j' -> 'n' > 'k' -> 'p' > '/' -> 'w' The "/" drives me nuts. That's such a common way to invoke searches in pagers and editors. I always hit it first; the error message reminds me of "w". I wish pine would implicitly enable alternate pagers, which would solve some of the problems. I'd use less. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 8 Jun 1998 11:26:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA18538 for ; Mon, 8 Jun 1998 11:26:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id LAA18698; Mon, 8 Jun 1998 11:26:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA23304; Mon, 8 Jun 1998 11:13:14 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA24936 for ; Mon, 8 Jun 1998 11:11:54 -0700 Received: from lexmark.lexmark.com (interlock2.lexmark.com [192.146.101.10]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id LAA20341 for ; Mon, 8 Jun 1998 11:11:42 -0700 Received: by interlock2.lexmark.com id AA00158 (InterLock SMTP Gateway 3.0 for pine-info@u.washington.edu); Mon, 8 Jun 1998 14:11:49 -0400 Received: by interlock2.lexmark.com (Protected-side Proxy Mail Agent-2); Mon, 8 Jun 1998 14:11:49 -0400 Received: by interlock2.lexmark.com (Protected-side Proxy Mail Agent-1); Mon, 8 Jun 1998 14:11:49 -0400 Message-Id: <199806081811.AA00158@interlock2.lexmark.com> Date: Mon, 8 Jun 1998 14:11:47 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Keith Shapiro To: Pine Discussion Forum Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: kshapiro@gloom X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello! I was wondering if there was anyway within Unix pine to alter the From: header. I have one of those nifty "free e-mail redirection for life" accounts and I was hoping to set up my outgoing mail to show up from that address instead of from my actual address. I'm not terribly concerned about people reading mail headers. I just want the default reply to be to the "redirector" address. I know, I know.. "Reply-To:". Except that most of the mailing lists I'm on alter Reply-To: to reply to the list. Any help would be appreciated. Keith Shapiro Lexmark International, Inc. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 8 Jun 1998 11:45:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA19564 for ; Mon, 8 Jun 1998 11:45:46 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id LAA19289; Mon, 8 Jun 1998 11:45:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA27003; Mon, 8 Jun 1998 11:39:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA14702 for ; Mon, 8 Jun 1998 11:38:03 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA09771 for ; Mon, 8 Jun 1998 11:38:02 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id OAA14895; Mon, 8 Jun 1998 14:37:58 -0400 (EDT) Received: from rock.me.mtu.edu (root@rock.me.mtu.edu [141.219.25.31]) by mtu.edu (8.8.8/8.8.8) with ESMTP id OAA27486; Mon, 8 Jun 1998 14:37:57 -0400 (EDT) Received: from aegir.me.mtu.edu (aegir.me.mtu.edu [141.219.24.49]) by rock.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with SMTP id OAA12849; Mon, 8 Jun 1998 14:37:54 -0400 (EDT) Message-Id: Date: Mon, 8 Jun 1998 14:37:53 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: Re: your mail In-Reply-To: <199806081811.AA00158@interlock2.lexmark.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Keith Shapiro X-Cc: Pine Discussion Forum X-Sender: edan@aegir.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > I was wondering if there was anyway within Unix pine to alter the From: > header. I have one of those nifty "free e-mail redirection for life" Try reading the nifty documentation :) http://www.washington.edu/pine/QandA/custom.html#xtocid301935 - edan From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 8 Jun 1998 14:30:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA22231 for ; Mon, 8 Jun 1998 14:30:37 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id OAA24005; Mon, 8 Jun 1998 14:30:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA02828; Mon, 8 Jun 1998 14:27:18 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA83320 for ; Mon, 8 Jun 1998 14:25:24 -0700 Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id OAA30071 for ; Mon, 8 Jun 1998 14:25:23 -0700 Received: from sushi.uni-bonn.de (131.220.225.111,6419) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Mon, 08 Jun 98 23:25:26 MEZ Received: (from robin@localhost) by sushi.uni-bonn.de (8.8.8/8.8.8) id WAA15111; Mon, 8 Jun 1998 22:20:59 +0200 Message-Id: Date: 08 Jun 1998 22:20:55 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: vi-style key bindings In-Reply-To: "Colin J. Raven"'s message of "Mon, 8 Jun 1998 07:24:53 -0700 (PDT)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-To: "Colin J. Raven" X-Cc: Pine Discussion Forum X-Attribution: Fireball X-Alignment: Chaotic Evil X-URL: http://franck.pc.uni-koeln.de/~robin/ X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Colin J Raven writes: > OK Adam, Edan, here it is.... I'm basically stupid, lazy (or maybe > too damn busy) to learn that beast called vi. In the light of what > Edan wrote, I fired up vi on Saturday night, and actually read the > book while playing with the thing. Yeah, OK I see what you and he > are saying. It's about as addictive as Emacs. Wait till you get to the syntax higlighting stuff... ;-) > Y'see, one of the effects of being so stupid is that it makes a > person very self-righteous in support of the "easy solution". pico is not easy. You'll lose much more time adjusting paragraphs and lines than you'd spend on reading the vi or jed FM. [...] > I guess editors that are more powerful are more appropriate when > you're doing advanced stuff. (ask Robin I guess) What's "advanced"? I use XEmacs and that's not really an editor but a programming environment. vi or jed, however, are really easy to learn (once you find out how to start with the help menu on) and simple things like yanking in complex quotes or quickly requoting reginons is a pretty cool thing if you do a lot of mail/news. > *But* I *do* believe that an editor that you can use in any condition > (and that certainly applies to me) with immediate and predictable > results is the one you stick with until you (or the editor) run outta > steam. Happened with pico after 20 minutes ]:-> Ever tried justifying super-cite quotes (RSS> )? Icky. > Same goes for Elm I s'pose. Believe it or not Adam, *that's* what I > was getting at. I'm just plain in awe of Edan and folks like him > who can write C (to start with) and can modify a mail programs' > feature-set. Well, that's my .02 worth for today...maybe. Ever tried mutt with vi? Cool stuff - threaded, coloured, killing, PGP, blablabla. Ummm... and there's Gnus. Heheee... Robin -- Robin S. Socha Join the Fight: Micro$oft Windows 98, n. - a belated upgrade to a 32 bit hack of a 16-bit shell for an 8-bit operating system designed for a 4-bit processor by a 2-bit company that's not worth one bit of attention. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(6) for mailarch+pine-info; Mon, 8 Jun 1998 19:11:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA26582 for ; Mon, 8 Jun 1998 19:11:14 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id TAA29961; Mon, 8 Jun 1998 19:11:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id TAA06481; Mon, 8 Jun 1998 19:08:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id TAA50066 for ; Mon, 8 Jun 1998 19:06:41 -0700 Received: from luomat.peak.org (cc344191-a.ewndsr1.nj.home.com [24.2.83.40]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA07330 for ; Mon, 8 Jun 1998 19:06:30 -0700 Received: (from luomat@localhost) by luomat.peak.org (0.0.0/0.0.0) id WAA24049 for pine-info@u.washington.edu; Mon, 8 Jun 1998 22:06:27 -0400 (EDT) Message-Id: <199806090206.WAA24049@luomat.peak.org> Date: Mon, 8 Jun 98 22:06:25 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: NONE (from Keith Shapiro ) In-Reply-To: <199806081811.AA00158@interlock2.lexmark.com> References: <199806081811.AA00158@interlock2.lexmark.com> Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: Keith Shapiro Original-Date: Mon, 8 Jun 1998 14:11:47 -0400 (EDT) Message-ID: <199806081811.AA00158@interlock2.lexmark.com> > I was wondering if there was anyway within Unix pine to alter the From: > header. Yes, it's in the FAQ http://www.washington.edu/pine/ and gets asked about 1000 times a week. TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 11 Jun 1998 13:21:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA20192 for ; Thu, 11 Jun 1998 13:21:12 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA15184 for ; Thu, 11 Jun 1998 13:21:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA15042; Thu, 11 Jun 1998 13:17:30 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA36044 for ; Thu, 11 Jun 1998 13:15:10 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA28236 for ; Thu, 11 Jun 1998 13:14:57 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id PAA29971 for ; Thu, 11 Jun 1998 15:15:04 -0500 Message-Id: Date: Thu, 11 Jun 1998 15:15:04 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: NONE (from Keith Shapiro ) In-Reply-To: <199806090206.WAA24049@luomat.peak.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Timothy J Luoma >Date: Mon, 8 Jun 98 22:06:25 -0400 > Author: Keith Shapiro > Original-Date: Mon, 8 Jun 1998 14:11:47 -0400 (EDT) > Message-ID: <199806081811.AA00158@interlock2.lexmark.com> >>I was wondering if [asked a very frequently asked question] >Yes, it's in the FAQ I, for one, intend to ignore this question in the future, and any other FAQ that gets asked so repetitively. We don't help anyone who can't trouble himself to read the FAQs. Especially, those who can't even bother to use a Subject. They aren't even worth insulting. Delete 'em like spam. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 11 Jun 1998 13:36:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA18954 for ; Thu, 11 Jun 1998 13:36:17 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA15581 for ; Thu, 11 Jun 1998 13:36:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA29575; Thu, 11 Jun 1998 13:31:41 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA11132 for ; Thu, 11 Jun 1998 13:30:23 -0700 Received: from sefl.satelnet.org (wildman@sefl.satelnet.org [208.162.32.55]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA29953 for ; Thu, 11 Jun 1998 13:30:10 -0700 Received: from wildman@localhost (HELO localhost) by sefl.satelnet.org (8.8.8/8.8.8) via SMTP id RAA32315 for ; Thu, 11 Jun 1998 17:03:14 -0400 (EDT) env-from (wildman@sefl.satelnet.org) Message-Id: Date: Thu, 11 Jun 1998 17:03:13 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Wild Man To: Pine Discussion Forum Subject: something I can't find MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have looked, and, with some timidity because of asking a frequently asked question, still I want to know how to jump to the end of a long message in pine. Hopefully I won't get my head bitten off for asking this. Steve ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 11 Jun 1998 13:46:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA17096 for ; Thu, 11 Jun 1998 13:46:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA15802 for ; Thu, 11 Jun 1998 13:46:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA12428; Thu, 11 Jun 1998 13:43:25 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA39886 for ; Thu, 11 Jun 1998 13:41:38 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA31268 for ; Thu, 11 Jun 1998 13:41:24 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id PAA30405 for ; Thu, 11 Jun 1998 15:41:35 -0500 Message-Id: Date: Thu, 11 Jun 1998 15:41:34 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: something I can't find In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Wild Man >Date: Thu, 11 Jun 1998 17:03:13 -0400 (EDT) >I have looked, and, with some timidity because of asking a frequently >asked question, still I want to know how to jump to the end of a long >message in pine. >Hopefully I won't get my head bitten off for asking this. >Steve ^w ^v From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 11 Jun 1998 14:16:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA24638 for ; Thu, 11 Jun 1998 14:15:57 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id OAA16709 for ; Thu, 11 Jun 1998 14:15:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA09175; Thu, 11 Jun 1998 14:10:13 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA70644 for ; Thu, 11 Jun 1998 14:08:26 -0700 Received: from ferrari.autobahn.org (danielh@ferrari.autobahn.org [206.79.223.25]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA22897 for ; Thu, 11 Jun 1998 14:08:26 -0700 Received: from localhost (danielh@localhost) by ferrari.autobahn.org (8.8.7/8.8.7) with SMTP id OAA02263 for ; Thu, 11 Jun 1998 14:08:21 -0700 Message-Id: Date: Thu, 11 Jun 1998 14:08:21 -0700 (PDT) Reply-To: Daniel Halperin Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Daniel Halperin To: Pine Discussion Forum Subject: (for Pine discussion section) Printing problem In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Help! Until recently I had no problem printing a message in pine; I would simply type "y" and my printer would print out the current message or whatever else then appearing on my screen. I recently had some problems with my modem and internet service, etc. after I installed MS Internet-Explorer program (figures), and now have finally gotten most of the bugs out...However, when I hit "y" in pine, my (H-P 682) printer churns and makes all the usual noises and prep. motions, but then nothing happens (yet the printer works fine in other applications...) Any ideas? I'm stuck, even tried re-installing my communications/modem software (Bitcom in DOS), but same problem...Help! Thanks. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 11 Jun 1998 14:23:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA24842 for ; Thu, 11 Jun 1998 14:23:20 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id OAA16951 for ; Thu, 11 Jun 1998 14:23:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA01371; Thu, 11 Jun 1998 14:19:43 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA27828 for ; Thu, 11 Jun 1998 14:18:04 -0700 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA03111 for ; Thu, 11 Jun 1998 14:17:50 -0700 Received: from eskimo.com (thumper@eskimo.com [204.122.16.13]) by mx1.eskimo.com (8.8.8/8.8.8) with ESMTP id OAA19272; Thu, 11 Jun 1998 14:18:04 -0700 Received: from localhost (thumper@localhost) by eskimo.com (8.8.8/8.8.8) with SMTP id OAA01197; Thu, 11 Jun 1998 14:17:54 -0700 (PDT) Message-Id: Date: Thu, 11 Jun 1998 14:17:53 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Kevin LaRose To: Pine Discussion Forum Subject: Re: something I can't find In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Wild Man X-Cc: Pine Discussion Forum X-Authentication-Warning: eskimo.com: thumper owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN CHOMP! CHOMP! Nice clean bite...head came off in only two chomps. On Thu, 11 Jun 1998, Wild Man wrote: > I have looked, and, with some timidity because of asking a frequently > asked question, still I want to know how to jump to the end of a long > message in pine. > Hopefully I won't get my head bitten off for asking this. > Steve > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > Kevin LaRose Owner: Sportstalk-l Mailing List I am not a nitwit, but I do play one on some mailing lists. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 12 Jun 1998 12:34:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA12092 for ; Fri, 12 Jun 1998 12:34:54 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id MAA10814; Fri, 12 Jun 1998 12:34:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA21753; Fri, 12 Jun 1998 12:32:55 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA15724 for ; Fri, 12 Jun 1998 12:28:45 -0700 Received: from eve.assumption.edu (eve.assumption.edu [192.80.61.5]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id MAA15272 for ; Fri, 12 Jun 1998 12:28:38 -0700 Received: from [206.33.81.4] by eve.assumption.edu (5.65/DEC-Ultrix/4.3) id AA01639; Fri, 12 Jun 1998 15:32:58 -0400 Message-Id: <9806121932.AA01639@eve.assumption.edu> Date: Fri, 12 Jun 1998 15:27:53 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Brian K. Niece" To: Pine Discussion Forum Subject: PCPine and Fetchmail? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I know this is a somewhat hare-brained scheme, but I am increasingly frustrated with other mail clients, and I really want to be able to use pine at work. I've appended an explanation of why I want to do this at the end. Our mail server does not run an IMAP server, but I would like to be able to use PCPine. What I would like to do is run a program such as fetchmail on my pc so that it downloads the mail which I would then read with pine just as if this were a dial-up connected linux box or the like. I haven't been able to find a PC analog of fetchmail, but I'm willing to try the port if there's some hope of this working. The immediate problem I see, however, is that PCPine will not read from an inbox on the local computer, even if one is there. It only speaks IMAP. So, my questions are as follows: Will PCPine 4.0 be able to read from an inbox on the local machine like unix-pine does? Is there some reason that I haven't foreseen why running a fetchmail sort of program on a PC won't work? The reasons I have decided that this is about my only option are as follows: 1. In 10 years of using email with MUAs ranging from unix-mail to Netscape, I have never found a client that I like as well as pine. 2. My office computer is owned by my employer, so running linux on it is not an option. 3. Our mail server is SERIOUSLY overloaded. Even pop connections are slow. When I am logged in and try to use Pine on the server, there is often not enough free core to fork an editor. On some occasions there is not even enough memory for me to start unix mail, let alone pine. Given these constraints, requests to run an IMAP server are hopeless, and perpetually open POP connections are not likely to perform well, either. Thanks, Brian -- Brian Niece Assumption College Assistant Professor of Chemistry Division of Natural Sciences bniece@assumption.edu 500 Salisbury St. (508) 767-7210 Worcester, MA 01615 ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 12 Jun 1998 12:46:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA12287 for ; Fri, 12 Jun 1998 12:46:42 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id MAA11191; Fri, 12 Jun 1998 12:46:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA13462; Fri, 12 Jun 1998 12:45:29 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA61440 for ; Fri, 12 Jun 1998 12:41:55 -0700 Received: from sefl.satelnet.org (wildman@sefl.satelnet.org [208.162.32.55]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA16569 for ; Fri, 12 Jun 1998 12:41:54 -0700 Received: from wildman@localhost (HELO localhost) by sefl.satelnet.org (8.8.8/8.8.8) via SMTP id QAA31844 for ; Fri, 12 Jun 1998 16:14:50 -0400 (EDT) env-from (wildman@sefl.satelnet.org) Message-Id: Date: Fri, 12 Jun 1998 16:14:50 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Wild Man To: Pine Discussion Forum Subject: a conundrum for some blind folks MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am a blind pine user and some of my friends and I are wondering if there is a command to jump from one word to the next without having to use the ^w and searching for the next space. For instance, in most editers, control right arrow or left arrow will jump to previous or next word. Is this possible in pine? Steve ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 12 Jun 1998 12:55:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA12403 for ; Fri, 12 Jun 1998 12:55:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id MAA11367; Fri, 12 Jun 1998 12:54:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA13749; Fri, 12 Jun 1998 12:53:52 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA32814 for ; Fri, 12 Jun 1998 12:51:09 -0700 Received: from equake.geol.vt.edu (equake.geol.vt.edu [128.173.184.42]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id MAA05035 for ; Fri, 12 Jun 1998 12:50:56 -0700 Received: from localhost (snoke@localhost) by equake.geol.vt.edu (8.6.9/8.6.9) with SMTP id PAA18626; Fri, 12 Jun 1998 15:51:07 -0400 Message-Id: Date: Fri, 12 Jun 1998 15:51:06 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Arthur Snoke To: Pine Discussion Forum Subject: edit before printing/saving MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: snoke@equake X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Is there any way to edit a mail file I have received in PINE before printing it or saving it? Sometimes I would like to fix up the formatting, get rid of leading >>, etc. The only ways I have come up with are to export it to a file or mail it to myself (editing it before sending it). Also, can I delete an attachment before saving a received mail file? ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 12 Jun 1998 13:04:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA12351 for ; Fri, 12 Jun 1998 13:04:51 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA11524; Fri, 12 Jun 1998 13:04:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA26983; Fri, 12 Jun 1998 13:03:30 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA61528 for ; Fri, 12 Jun 1998 13:00:53 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA26895 for ; Fri, 12 Jun 1998 13:00:52 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id PAA13120 for ; Fri, 12 Jun 1998 15:00:50 -0500 Message-Id: Date: Fri, 12 Jun 1998 15:00:50 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: a conundrum for some blind folks In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Wild Man >Date: Fri, 12 Jun 1998 16:14:50 -0400 (EDT) >I am a blind pine user and some of my friends and I are wondering if there >is a command to jump from one word to the next without having to use the >^w and searching for the next space. control-space However, I've yet to see a telnet or terminal emulation that doesn't trap this. So, you may have to use the workaround escape-escape-space From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 12 Jun 1998 13:09:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA12906 for ; Fri, 12 Jun 1998 13:09:15 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA11653; Fri, 12 Jun 1998 13:09:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA23264; Fri, 12 Jun 1998 13:08:03 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA32224 for ; Fri, 12 Jun 1998 13:05:24 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA27463 for ; Fri, 12 Jun 1998 13:05:23 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id PAA13178 for ; Fri, 12 Jun 1998 15:04:51 -0500 Message-Id: Date: Fri, 12 Jun 1998 15:04:51 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: edit before printing/saving In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Arthur Snoke >Date: Fri, 12 Jun 1998 15:51:06 -0400 (EDT) >Is there any way to edit a mail file I have received in PINE before >printing it or saving it? No. I recommend saving it to a temporary mail folder, exiting pine, and then editing the file. Then, in pine, save it to a permanent folder. >Also, can I delete an attachment before saving a received mail file? No. Edit as above. Others will recommend using postponed-msgs and then editing in the composer. However, this will change most of the headers, so I don't care for this method. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 12 Jun 1998 13:15:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA12995 for ; Fri, 12 Jun 1998 13:15:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA11850; Fri, 12 Jun 1998 13:15:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA15115; Fri, 12 Jun 1998 13:14:38 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA68816 for ; Fri, 12 Jun 1998 13:11:52 -0700 Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA07309 for ; Fri, 12 Jun 1998 13:11:38 -0700 Received: from localhost (jim@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id QAA16858 for ; Fri, 12 Jun 1998 16:11:49 -0400 (EDT) Message-Id: Date: Fri, 12 Jun 1998 16:11:49 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jim Sander To: Pine Discussion Forum Subject: Re: a conundrum for some blind folks In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > control-space > > However, I've yet to see a telnet or terminal emulation that doesn't trap this. > So, you may have to use the workaround > > escape-escape-space I am using the beta of secure CRT right now, (2.2b4) from vandyke- and control-space works great. ($term=vt220) Never knew this- it's pretty usefull to me, even though I can see fine. ;) -=Jim=- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 12 Jun 1998 13:48:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA13670 for ; Fri, 12 Jun 1998 13:48:19 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA12944; Fri, 12 Jun 1998 13:48:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA03482; Fri, 12 Jun 1998 13:47:03 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA14796 for ; Fri, 12 Jun 1998 13:43:58 -0700 Received: from mail.utep.edu (mail.utep.edu [129.108.1.4]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA22237 for ; Fri, 12 Jun 1998 13:43:57 -0700 Received: from Dimitri.utep.edu ([129.108.30.238]) by mail.utep.edu (8.8.8/8.8.8) with SMTP id OAA61742 for ; Fri, 12 Jun 1998 14:43:55 -0600 Message-Id: <3.0.1.32.19980612144140.006a6be0@utep.edu> Date: Fri, 12 Jun 1998 14:41:40 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: rufranco@utep.edu To: Pine Discussion Forum Subject: E-mail Filtering Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: rufranco@utep.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Our old System was running HP-UX 10.20 Our new system is Running AIX 4.2.1 Pine Users on Our old system use to be able to filter messages with a file called ".mailfilt" in their home directories. What do we need to have on our AIX system to enable this function? ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 12 Jun 1998 16:14:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA16370 for ; Fri, 12 Jun 1998 16:14:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id QAA17862; Fri, 12 Jun 1998 16:14:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id QAA21955; Fri, 12 Jun 1998 16:13:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id QAA12932 for ; Fri, 12 Jun 1998 16:10:46 -0700 Received: from 192-106.reduno.com.mx (192-106.reduno.com.mx [192.100.183.106]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA27846 for ; Fri, 12 Jun 1998 16:10:30 -0700 Received: by 192-106.reduno.com.mx (8.9.0/8.9.0) id SAA10327 for pine-info@u.washington.edu; Fri, 12 Jun 1998 18:09:34 -0600 (CST) Message-Id: <199806130009.SAA10327@192-106.reduno.com.mx> Date: Fri, 12 Jun 1998 18:09:34 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: ANA LIDIA FALCON BALDERAS To: Pine Discussion Forum Content-Type: text X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi! I'm System Administrator, and this week I was configuring pine, but, I want the users can't save files in disk, but, I don't know how to do it. Do you know if there is a compile way to avoid the users can't save files in disk and not use espace? I hope you can helpme Thanks in Advanced p.d. I'm sorry but, my english is poor. Ana Lidia Falcon B. Consorcio Red Uno S.A de C.V anaf@reduno.com.mx Tel. (525) 6244400 Ext. 4603 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sat, 13 Jun 1998 17:14:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA32464 for ; Sat, 13 Jun 1998 17:14:24 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id RAA04960; Sat, 13 Jun 1998 17:14:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id RAA05037; Sat, 13 Jun 1998 17:13:12 -0700 Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id RAA85060 for ; Sat, 13 Jun 1998 17:05:18 -0700 Received: from localhost (jim@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id UAA18969 for ; Sat, 13 Jun 1998 20:05:17 -0400 (EDT) Message-Id: Date: Sat, 13 Jun 1998 20:05:16 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jim Sander To: Pine Discussion Forum Subject: ^-space MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@lists.u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Also, am using the 2.7b version of NCSA telnet for the mac, it's emulation also handles the control-space character for jumping to the next word. So, that means I'm 2-for-2 on emulations I have checked... maybe this isn't so rare after all, eh? -=Jim=- P.S. Since this only has marginal relation to pine, I'll give a whack at the question about preventing users from saving things to the mail spool directory... First, why not stick the spool file in the users' directories- I know this can be done, although it might mean hacking sendmail. OK, so I just answered why not all on my own. ;) Second, if you can- limit the user to their home directory with pine's (forget that dang name right now) feature. Be warned though- at least on my system I couldn't use an alternate editor or speller. Third, set up a quota on the spool partition that only allows one block. As long as it's a different logical partition, that should work. This is turning in to one of those questions like "how do I make a mailing list" - there are literally 1024 answers or more. Maybe these ideas will give someone better ones. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 14 Jun 1998 20:49:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA16041 for ; Sun, 14 Jun 1998 20:49:28 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id UAA22422; Sun, 14 Jun 1998 20:49:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA04011; Sun, 14 Jun 1998 20:48:06 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA19072 for ; Sun, 14 Jun 1998 20:45:21 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA19977 for ; Sun, 14 Jun 1998 20:45:21 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id UAA22375 for ; Sun, 14 Jun 1998 20:45:18 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id VAA20171 for ; Sun, 14 Jun 1998 21:45:17 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id VAA51460 for ; Sun, 14 Jun 1998 21:45:13 -0600 Message-Id: Date: Sun, 14 Jun 1998 21:45:13 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: IMAP--empty list. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've been accessing the pine-info mailing list about once a month for about ten months (been away for about three) with this set up: PINE 3.95 SETUP CONFIGURATION postponed-msgs 10 Msgs personal-name = Raja BrewHaHa user-domain = smtp-server = nntp-server = news.sas.ab.ca inbox-path = folder-collections = mail/[] *{ftp.cac.washington.edu/anonymous}pine/pine-info/[] news-collections = news *{news.sas.ab.ca/nntp}[] incoming-archive-folders = pruned-folders = default-fcc = default-saved-msg-folder = postponed-folder = read-message-folder = signature-file = global-address-book = address-book = feature-list = Set Feature Name ? Help E Exit Config P Prev - PrevPage A Add Value Y prYnt C [Change Val] N Next Spc NextPage D Delete Val W WhereIs _________End screen shot________ The problem is that the folder I get from the IMAP server is now always "empty". I had no problem before. I have no problem FTPing that directory with Lynx, and it is far from empty. I've tried it as a news collection. Can anyone tell me what could have chanjed? Hav I been getting by miraculously with the wrong syntax? _______ Let the hairy fish roll. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 02:44:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA21227 for ; Mon, 15 Jun 1998 02:44:21 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id CAA27629; Mon, 15 Jun 1998 02:44:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id CAA27884; Mon, 15 Jun 1998 02:42:59 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id CAA38814 for ; Mon, 15 Jun 1998 02:40:42 -0700 Received: from plato.physik.uni-konstanz.de (flo@plato.physik.uni-konstanz.de [134.34.147.28]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA28740 for ; Mon, 15 Jun 1998 02:40:41 -0700 Received: from localhost (flo@localhost) by plato.physik.uni-konstanz.de (8.8.5/8.8.5) with SMTP id LAA21133 for ; Mon, 15 Jun 1998 11:40:35 +0200 Message-Id: Date: Mon, 15 Jun 1998 11:40:35 +0200 (CEST) Reply-To: Florian Kolbe Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Florian Kolbe To: Pine Discussion Forum Subject: Re: edit before printing/saving In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 12 Jun 1998, Arthur Snoke wrote: > Also, can I delete an attachment before saving a received mail file? This is supposed to be added in 4.0. See the 'MIME' section under: http://www.washington.edu/pine/changes/4.00-preview/ Florian ############################################################################ # Florian Kolbe - Florian.Kolbe@uni-konstanz.de # # Uni Konstanz, P1003, Tel. 88-3859 # ############################################################################ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 03:34:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA22214 for ; Mon, 15 Jun 1998 03:34:57 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id DAA26909; Mon, 15 Jun 1998 03:34:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id DAA28367; Mon, 15 Jun 1998 03:28:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id DAA39794 for ; Mon, 15 Jun 1998 03:26:32 -0700 Received: from plato.physik.uni-konstanz.de (plato.physik.uni-konstanz.de [134.34.147.28]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA01339 for ; Mon, 15 Jun 1998 03:26:28 -0700 Received: from localhost (flo@localhost) by plato.physik.uni-konstanz.de (8.8.5/8.8.5) with SMTP id MAA21377 for ; Mon, 15 Jun 1998 12:26:20 +0200 Message-Id: Date: Mon, 15 Jun 1998 12:26:20 +0200 (CEST) Reply-To: Florian Kolbe Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Florian Kolbe To: Pine Discussion Forum Subject: wish for 4.0: pgp-awareness MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I hate it, when Pine says: [Part 1, Application/PGP 667bytes] [Cannot display this part. Press "V" then "S" to save in a file] So I added the following line in my .mailcap: application/pgp; cat %s; copiousoutput So now pine says: [Part 1, Application/PGP 667bytes] [Not Shown. Use the "V" command to view or save this part] and I have to type vv to finally view the message. This is still a crutch! Or is there another way? (apart from hacking pine) I know this has been said before, but I'll say it again: PLEASE make pine 4.0 pgp-aware. Florian Kolbe ############################################################################ # Florian Kolbe - Florian.Kolbe@uni-konstanz.de # # Uni Konstanz, P1003, Tel. 88-3859 # ############################################################################ ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 07:48:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA25396 for ; Mon, 15 Jun 1998 07:48:57 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA01611; Mon, 15 Jun 1998 07:48:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA14228; Mon, 15 Jun 1998 07:47:39 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA57374 for ; Mon, 15 Jun 1998 07:45:25 -0700 Received: from sefl.satelnet.org (wildman@sefl.satelnet.org [208.162.32.55]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA09538 for ; Mon, 15 Jun 1998 07:45:24 -0700 Received: from wildman@localhost (HELO localhost) by sefl.satelnet.org (8.8.8/8.8.8) via SMTP id LAA27278 for ; Mon, 15 Jun 1998 11:18:43 -0400 (EDT) env-from (wildman@sefl.satelnet.org) Message-Id: Date: Mon, 15 Jun 1998 11:18:42 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Wild Man To: Pine Discussion Forum Subject: marking as new MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I need to know how to find out how to mark messages as new messages rather than having the marked as already read, how can I accomplish this? I used to know but didn't make a note. Steve ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 07:58:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA25484 for ; Mon, 15 Jun 1998 07:58:16 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA00609; Mon, 15 Jun 1998 07:58:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA25805; Mon, 15 Jun 1998 07:57:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA78226 for ; Mon, 15 Jun 1998 07:55:16 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA14577 for ; Mon, 15 Jun 1998 07:55:15 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id IAA20650 for ; Mon, 15 Jun 1998 08:55:14 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id IAA23180 for ; Mon, 15 Jun 1998 08:55:11 -0600 Message-Id: Date: Mon, 15 Jun 1998 08:55:11 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: marking as new In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 15 Jun 1998, Wild Man wrote: > I need to know how to find out how to mark messages as new messages rather > than having the marked as already read, how can I accomplish this? I used > to know but didn't make a note. > I'm not sure if you need the "aggregate command" set for this. The command to change flags is *, at least as I have PINE configured. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 08:03:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA25575 for ; Mon, 15 Jun 1998 08:03:11 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id IAA01948; Mon, 15 Jun 1998 08:03:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA26088; Mon, 15 Jun 1998 08:01:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA34522 for ; Mon, 15 Jun 1998 07:59:49 -0700 Received: from mail.delta-ii.de (mail.delta-ii.de [195.180.229.162]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA10923 for ; Mon, 15 Jun 1998 07:59:47 -0700 Received: by mail.delta-ii.de (Smail3.2.0.101/mail.delta-ii.de) via Delta-II from lamia.delta-ii.de with esmtp for mxu2.u.washington.edu id m0ylajR-000aQSC; Mon, 15 Jun 1998 16:59:37 +0200 (MET DST) Received: (from norbert@localhost) by lamia.delta-ii.de (8.8.8/8.7.3) id QAA24454; Mon, 15 Jun 1998 16:59:34 +0200 Message-Id: Date: 15 Jun 1998 16:59:34 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Norbert Koch To: Pine Discussion Forum Subject: Re: marking as new In-Reply-To: Wild Man's message of "Mon, 15 Jun 1998 11:18:42 -0400 (EDT)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-Sender: norbert@delta-ii.de X-To: Wild Man X-Cc: Pine Discussion Forum X-Attribution: viteno X-Organization: Delta Industrie Informatik GmbH X-URL: http://www.delta-ii.de X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Wild Man writes: > I need to know how to find out how to mark messages as new messages > rather than having the marked as already read, how can I accomplish > this? I used to know but didn't make a note. Ummm, a long command ; c a * n (select/current/apply/flag/new) If you want to select more than one message, well don't specify Current. BTW, you must have the 'enable-aggregate-command' flag set (setup/config) L8er, norbert. -- Norbert Koch, Delta Industrie Informatik GmbH, Fellbach, Germany. While I'm in LEVITTOWN I thought I'd like to see the NUCLEAR FAMILY!! From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 08:33:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA25368 for ; Mon, 15 Jun 1998 08:33:25 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id IAA01517; Mon, 15 Jun 1998 08:33:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA05287; Mon, 15 Jun 1998 08:32:04 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA39702 for ; Mon, 15 Jun 1998 08:30:02 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA18024 for ; Mon, 15 Jun 1998 08:30:00 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id KAA24056 for ; Mon, 15 Jun 1998 10:29:55 -0500 Message-Id: Date: Mon, 15 Jun 1998 10:29:54 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: marking as new In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Norbert Koch >Date: 15 Jun 1998 16:59:34 +0200 >Wild Man writes: >>I need to know how to find out how to mark messages as new messages rather >>than having the marked as already read, how can I accomplish this? I used to >>know but didn't make a note. >Ummm, a long command >; c a * n (select/current/apply/flag/new) Too many keystrokes for one message! To change the flag status for the current message, from either the pager or index, "* n" or whatever flag you like. >If you want to select more than one message, well don't specify Current. Suppose you want to change the flags on all read messages: ; s ! n (select status not new) This is confusing: The flag command under select is called status! I hope that his is changed in version 4. To change the flags back to new: a * n (apply flag new) Several flags can be changed: important (proprietary to pine), deleted, or answered. Of course, deleted can be reversed with undelete. pine only sets the "answered" flag when you reply to a message while it's still in you inbox. If you've saved it to a folder, you must set the flag manually. I hope this is fixed for version 4. Can the answered flag be seen by other mail readers, or is this proprietary? Important shows a "*" in the index. But, it gives you more flexibility to select. >BTW, you must have the 'enable-aggregate-command' flag set (setup/config) You also need to activate the option "enable-flag-command". From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 08:40:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA26193 for ; Mon, 15 Jun 1998 08:40:51 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id IAA02970; Mon, 15 Jun 1998 08:40:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA16993; Mon, 15 Jun 1998 08:39:21 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA57396 for ; Mon, 15 Jun 1998 08:37:35 -0700 Received: from mail.delta-ii.de (mail.delta-ii.de [195.180.229.162]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA14896 for ; Mon, 15 Jun 1998 08:37:31 -0700 Received: by mail.delta-ii.de (Smail3.2.0.101/mail.delta-ii.de) via Delta-II from lamia.delta-ii.de with esmtp for mxu2.u.washington.edu id m0ylbJt-000aQOC; Mon, 15 Jun 1998 17:37:17 +0200 (MET DST) Received: (from norbert@localhost) by lamia.delta-ii.de (8.8.8/8.7.3) id RAA24911; Mon, 15 Jun 1998 17:37:14 +0200 Message-Id: Date: 15 Jun 1998 17:37:14 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Norbert Koch To: Pine Discussion Forum Subject: Re: marking as new In-Reply-To: "Adam H. Kerman"'s message of "Mon, 15 Jun 1998 10:29:54 -0500 (CDT)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-Sender: norbert@delta-ii.de X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Attribution: viteno X-Organization: Delta Industrie Informatik GmbH X-URL: http://www.delta-ii.de X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Adam H Kerman writes: >> From: Norbert Koch Date: 15 Jun 1998 16:59:34 >> +0200 >> Wild Man writes: [Adam's good remarks] Hi Adam. Thanks very much for the update - looks like I should have a glimpse into the online help again, I'm way off :-) Cheers, norbert. -- Norbert Koch, Delta Industrie Informatik GmbH, Fellbach, Germany. There's enough money here to buy 5000 cans of Noodle-Roni! From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 09:08:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA27305 for ; Mon, 15 Jun 1998 09:08:37 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA02583; Mon, 15 Jun 1998 09:08:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA18260; Mon, 15 Jun 1998 09:07:23 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA60790 for ; Mon, 15 Jun 1998 09:05:30 -0700 Received: from luomat.peak.org (cc344191-a.ewndsr1.nj.home.com [24.2.83.40]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA22182 for ; Mon, 15 Jun 1998 09:05:29 -0700 Received: by luomat.peak.org (8.9.0/8.9.0) id MAA25858 for pine-info@u.washington.edu; Mon, 15 Jun 1998 12:05:32 -0400 (EDT) Message-Id: <199806151605.MAA25858@luomat.peak.org> Date: Mon, 15 Jun 98 12:05:28 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: wish for 4.0: pgp-awareness References: Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN How about making PINE-4.0 publically available? That's all I'm hoping for at this point, some 3 months after being told that it was "nearing completion". TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 09:20:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA27540 for ; Mon, 15 Jun 1998 09:20:31 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA04374; Mon, 15 Jun 1998 09:20:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA07845; Mon, 15 Jun 1998 09:19:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA49266 for ; Mon, 15 Jun 1998 09:17:31 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA23660 for ; Mon, 15 Jun 1998 09:17:30 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id KAA14216 for ; Mon, 15 Jun 1998 10:17:29 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id KAA59812 for ; Mon, 15 Jun 1998 10:17:25 -0600 Message-Id: Date: Mon, 15 Jun 1998 10:17:24 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: push for 4.0 In-Reply-To: <199806151605.MAA25858@luomat.peak.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 15 Jun 1998, Timothy J Luoma wrote: > How about making PINE-4.0 publically available? That's all I'm > hoping for at this point, some 3 months after being told that it > was "nearing completion". > Don't push. They aren't M$. Pine works now. It's also very cheap. Wanna push for 4.0? Pull some source code an make sure it compiles with no warnings, despite all warnings being enabled on your compiler. Don't let the purple headed chicken eat the hairy fish. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 09:27:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA27319 for ; Mon, 15 Jun 1998 09:26:59 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA03240; Mon, 15 Jun 1998 09:26:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA08484; Mon, 15 Jun 1998 09:26:37 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA27716 for ; Mon, 15 Jun 1998 09:24:39 -0700 Received: from luomat.peak.org (cc344191-a.ewndsr1.nj.home.com [24.2.83.40]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA24585 for ; Mon, 15 Jun 1998 09:24:14 -0700 Received: by luomat.peak.org (8.9.0/8.9.0) id MAA26736 for pine-info@u.washington.edu; Mon, 15 Jun 1998 12:23:46 -0400 (EDT) Message-Id: <199806151623.MAA26736@luomat.peak.org> Date: Mon, 15 Jun 98 12:23:43 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: push for 4.0 In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Wanna push for 4.0? Pull some source code an make sure it compiles > with no warnings, despite all warnings being enabled on your > compiler. I'll be happy if it compiles at all under my OS (OpenStep). My guess is that I will have to compile it under NeXTStep. I've made sure that pine/pico/pilot all compile before, and made them available for those who prefer precompiled binaries. Of course, that's all for 3.9x.... I don't have access to any 4.0 code to see whether or not that compiles. TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 10:14:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA28607 for ; Mon, 15 Jun 1998 10:14:41 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA06132; Mon, 15 Jun 1998 10:14:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA22305; Mon, 15 Jun 1998 10:13:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA78118 for ; Mon, 15 Jun 1998 10:12:33 -0700 Received: from chinet.chinet.com (chinet.chinet.com [206.158.147.18]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA20219 for ; Mon, 15 Jun 1998 10:12:30 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id MAA25789 for ; Mon, 15 Jun 1998 12:12:28 -0500 Message-Id: Date: Mon, 15 Jun 1998 12:12:28 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: status command confusingly named MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I find the command "; s" (select status) confusingly named. The command allows you select messages based on the status of their flags: important, new, deleted, answered (or not flagged thusly). Every other command that referes to flags calls it "*"! Two different names isn't intuitive. Is there a historical reason for this? Or, were there simply two different programmers handling these aspects? ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 10:41:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA19080 for ; Mon, 15 Jun 1998 10:40:59 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA07065; Mon, 15 Jun 1998 10:40:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA04921; Mon, 15 Jun 1998 10:40:25 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA77198 for ; Mon, 15 Jun 1998 10:39:37 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA07147 for ; Mon, 15 Jun 1998 10:39:36 -0700 Received: from helix.mgh.harvard.edu (helix.mgh.harvard.edu [132.183.108.14]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with SMTP id KAA07023 for ; Mon, 15 Jun 1998 10:39:33 -0700 Received: from localhost by helix.mgh.harvard.edu (5.65v4.0/1.1.10.5/02Feb97-1116AM) id AA04638; Mon, 15 Jun 1998 13:39:03 -0400 Message-Id: Date: Mon, 15 Jun 1998 13:39:03 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dennis Gurgul To: Pine Discussion Forum Subject: pinerc files Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Does anyone know what's causing this user to have so many pinerc files in their directory? Running 3.95 on Digital Unix 4.0b. Thanks: -rw------- 1 ma users 0 Jun 9 13:02 pinerc000179 -rw------- 1 ma users 0 Jun 2 16:14 pinerc000487 -rw------- 1 ma users 0 Jun 6 11:10 pinerc000553 -rw------- 1 ma users 0 Jun 9 13:11 pinerc001038 -rw------- 1 ma users 0 Jun 3 11:21 pinerc001192 -rw------- 1 ma users 0 Jun 2 16:00 pinerc002001 -rw------- 1 ma users 0 Jun 9 13:24 pinerc002051 -rw------- 1 ma users 0 Jun 3 11:33 pinerc002238 -rw------- 1 ma users 0 Jun 1 11:13 pinerc002797 -rw------- 1 ma users 0 Jun 2 16:14 pinerc003670 -rw------- 1 ma users 0 May 29 14:10 pinerc003750 -rw------- 1 ma users 0 Jun 4 13:50 pinerc004019 -rw------- 1 ma users 0 May 29 16:27 pinerc004356 -rw------- 1 ma users 0 Jun 9 13:50 pinerc004598 -rw------- 1 ma users 0 Jun 8 15:30 pinerc004715 -rw------- 1 ma users 0 May 29 16:32 pinerc004971 -rw------- 1 ma users 0 Jun 9 13:58 pinerc005314 -rw------- 1 ma users 0 Jun 1 11:36 pinerc005752 -rw------- 1 ma users 0 Jun 4 13:58 pinerc006233 -rw------- 1 ma users 0 Jun 4 09:56 pinerc007570 -rw------- 1 ma users 0 May 29 14:51 pinerc008953 -rw------- 1 ma users 0 Jun 1 14:37 pinerc008966 -rw------- 1 ma users 0 Jun 5 16:40 pinerc009282 -rw------- 1 ma users 0 Jun 3 14:11 pinerc009606 -rw------- 1 ma users 0 May 27 13:45 pinerc009777 -rw------- 1 ma users 0 May 28 15:15 pinerc010106 -rw------- 1 ma users 0 Jun 9 09:35 pinerc010234 -rw------- 1 ma users 0 May 27 16:52 pinerc011079 -rw------- 1 ma users 0 May 29 10:51 pinerc011124 -rw------- 1 ma users 0 Jun 9 09:49 pinerc011618 -rw------- 1 ma users 0 Jun 9 09:55 pinerc012321 -rw------- 1 ma users 0 Jun 9 09:57 pinerc012664 -rw------- 1 ma users 0 May 29 10:19 pinerc012823 -rw------- 1 ma users 0 May 28 14:55 pinerc012869 -rw------- 1 ma users 0 Jun 2 14:28 pinerc012910 -rw------- 1 ma users 0 Jun 9 10:07 pinerc013686 -rw------- 1 ma users 0 Jun 8 16:16 pinerc014780 -rw------- 1 ma users 0 Jun 3 07:59 pinerc015398 -rw------- 1 ma users 0 Jun 9 10:26 pinerc015550 -rw------- 1 ma users 0 Jun 8 14:03 pinerc015723 -rw------- 1 ma users 0 Jun 3 10:55 pinerc016441 -rw------- 1 ma users 0 Jun 8 16:30 pinerc017616 -rw------- 1 ma users 0 Jun 8 09:33 pinerc018859 -rw------- 1 ma users 0 Jun 5 14:58 pinerc018973 -rw------- 1 ma users 0 Jun 10 09:26 pinerc022879 -rw------- 1 ma users 0 Jun 8 14:58 pinerc023031 -rw------- 1 ma users 8192 May 27 16:00 pinerc023401 -rw------- 1 ma users 0 Jun 2 15:04 pinerc024933 -rw------- 1 ma users 0 Jun 9 11:50 pinerc025331 -rw------- 1 ma users 0 Jun 2 09:59 pinerc026271 -rw------- 1 ma users 0 Jun 3 10:24 pinerc026765 -rw------- 1 ma users 0 Jun 10 10:53 pinerc028158 -rw------- 1 ma users 0 Jun 2 15:10 pinerc029845 -rw------- 1 ma users 0 Jun 8 10:47 pinerc029858 -rw------- 1 ma users 0 Jun 10 10:50 pinerc030819 -rw------- 1 ma users 0 Jun 10 10:54 pinerc031145 -rw------- 1 ma users 0 Jun 8 10:14 pinerc031266 -rw------- 1 ma users 0 Jun 10 11:02 pinerc032586 Dennis J. Gurgul Helix System Management 617.724.3169 ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 10:42:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA29091 for ; Mon, 15 Jun 1998 10:42:42 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA05530; Mon, 15 Jun 1998 10:42:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA16973; Mon, 15 Jun 1998 10:42:12 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA24732 for ; Mon, 15 Jun 1998 10:41:42 -0700 Received: from luomat.peak.org (cc344191-a.ewndsr1.nj.home.com [24.2.83.40]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA23451 for ; Mon, 15 Jun 1998 10:41:39 -0700 Received: by luomat.peak.org (8.9.0/8.9.0) id NAA02784 for pine-info@u.washington.edu; Mon, 15 Jun 1998 13:41:38 -0400 (EDT) Message-Id: <199806151741.NAA02784@luomat.peak.org> Date: Mon, 15 Jun 98 13:41:34 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: pinerc files In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: Dennis Gurgul Original-Date: Mon, 15 Jun 1998 13:39:03 -0400 (EDT) Message-ID: > Does anyone know what's causing this user to have so many pinerc files in > their directory? Running 3.95 on Digital Unix 4.0b. Thanks: Could they be at or over their quota? TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 15 Jun 1998 20:24:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA06088 for ; Mon, 15 Jun 1998 20:24:54 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id UAA18710; Mon, 15 Jun 1998 20:24:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA05315; Mon, 15 Jun 1998 20:24:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA32244 for ; Mon, 15 Jun 1998 20:23:16 -0700 Received: from godavari.wipsys.stph.net (godavari.wipsys.stph.net [196.12.37.2]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA14241 for ; Mon, 15 Jun 1998 20:23:08 -0700 Received: from vindhya.wipsys.stph.net (vindhya [196.12.37.134]) by godavari.wipsys.stph.net (8.8.5/8.8.5) with ESMTP id IAA03816 for ; Tue, 16 Jun 1998 08:58:57 GMT Received: from wipsys.stph.net ([192.168.0.32]) by vindhya.wipsys.stph.net (8.9.0/8.9.0) with ESMTP id IAA12877 Message-Id: <3585E577.4331C9EF@wipsys.stph.net> Date: Tue, 16 Jun 1998 08:54:39 +0530 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: pradeep kumar To: Pine Discussion Forum Subject: UNSUBSCRIBE MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 02:54:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA10851 for ; Tue, 16 Jun 1998 02:54:56 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id CAA23293; Tue, 16 Jun 1998 02:54:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id CAA12118; Tue, 16 Jun 1998 02:54:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id CAA87550 for ; Tue, 16 Jun 1998 02:53:55 -0700 Received: from plato.physik.uni-konstanz.de (plato.physik.uni-konstanz.de [134.34.147.28]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA11647 for ; Tue, 16 Jun 1998 02:53:53 -0700 Received: from localhost (flo@localhost) by plato.physik.uni-konstanz.de (8.8.5/8.8.5) with SMTP id LAA26937 for ; Tue, 16 Jun 1998 11:53:49 +0200 Message-Id: Date: Tue, 16 Jun 1998 11:53:49 +0200 (CEST) Reply-To: Florian Kolbe Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Florian Kolbe To: Pine Discussion Forum Subject: Re: pinerc files In-Reply-To: <199806151741.NAA02784@luomat.peak.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 15 Jun 1998, Timothy J Luoma wrote: > Author: Dennis Gurgul > Original-Date: Mon, 15 Jun 1998 13:39:03 -0400 (EDT) > Message-ID: > > > > Does anyone know what's causing this user to have so many pinerc files in > > their directory? Running 3.95 on Digital Unix 4.0b. Thanks: > > Could they be at or over their quota? Or even worse, file system full :) Florian ############################################################################ # Florian Kolbe - Florian.Kolbe@uni-konstanz.de # # Uni Konstanz, P1003, Tel. 88-3859 # ############################################################################ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 03:02:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA08717 for ; Tue, 16 Jun 1998 03:02:53 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id CAA23088; Tue, 16 Jun 1998 02:35:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id CAA11922; Tue, 16 Jun 1998 02:35:33 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id CAA66406 for ; Tue, 16 Jun 1998 02:32:02 -0700 Received: from plato.physik.uni-konstanz.de (plato.physik.uni-konstanz.de [134.34.147.28]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA04307 for ; Tue, 16 Jun 1998 02:32:00 -0700 Received: from localhost (flo@localhost) by plato.physik.uni-konstanz.de (8.8.5/8.8.5) with SMTP id LAA26859 for ; Tue, 16 Jun 1998 11:31:46 +0200 Message-Id: Date: Tue, 16 Jun 1998 11:31:46 +0200 (CEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Florian Kolbe To: Pine Discussion Forum Subject: Re: push for 4.0 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 15 Jun 1998, Raja BrewHaHa wrote: > On Mon, 15 Jun 1998, Timothy J Luoma wrote: > > > How about making PINE-4.0 publically available? That's all I'm > > hoping for at this point, some 3 months after being told that it > > was "nearing completion". > > > > Don't push. They aren't M$. Pine works now. It's also very cheap. > Wanna push for 4.0? Pull some source code an make sure it compiles with no > warnings, despite all warnings being enabled on your compiler. There's a very enlighting article about engineering free software: http://www.kde.org/food/cathedral/cathedral-paper.html I wonder if the pine developers could do it the 'Bazaar' way. Florian ############################################################################ # Florian Kolbe - Florian.Kolbe@uni-konstanz.de # # Uni Konstanz, P1003, Tel. 88-3859 # ############################################################################ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 09:35:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA18371 for ; Tue, 16 Jun 1998 09:35:52 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA00345; Tue, 16 Jun 1998 09:35:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA23641; Tue, 16 Jun 1998 09:34:22 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA44322 for ; Tue, 16 Jun 1998 09:32:56 -0700 Received: from DEFIANT.AMAG.COM ([208.222.108.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA05300 for ; Tue, 16 Jun 1998 09:32:55 -0700 Received: by DEFIANT with Internet Mail Service (5.0.1457.3) id ; Tue, 16 Jun 1998 11:32:55 -0500 Message-Id: Date: Tue, 16 Jun 1998 11:32:52 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jim Hunter To: Pine Discussion Forum Subject: UNSUBSCRIBE MIME-Version: 1.0 Content-Type: text/plain X-To: "'pine-info@u.washington.edu'" X-Priority: 3 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN James A. Hunter Network Manager email: jhunter@amag.com voice: (712) 325-5381 ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 10:02:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA19021 for ; Tue, 16 Jun 1998 10:02:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA01124; Tue, 16 Jun 1998 10:02:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA07706; Tue, 16 Jun 1998 10:01:08 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA44350 for ; Tue, 16 Jun 1998 09:59:58 -0700 Received: from helix.mgh.harvard.edu (helix.mgh.harvard.edu [132.183.108.14]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id JAA13846 for ; Tue, 16 Jun 1998 09:59:57 -0700 Received: from localhost by helix.mgh.harvard.edu (5.65v4.0/1.1.10.5/02Feb97-1116AM) id AA03551; Tue, 16 Jun 1998 12:59:22 -0400 Message-Id: Date: Tue, 16 Jun 1998 12:59:22 -0400 (EDT) Reply-To: Dennis Gurgul Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dennis Gurgul To: Pine Discussion Forum Subject: Re: pinerc files In-Reply-To: <199806151741.NAA02784@luomat.peak.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Timothy J Luoma X-Cc: Pine Discussion Forum , Jon Martinson X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN They were over quota. Actually, that's how we discovered it. The user contacted us about a quota problem. So then this happens when someone goes over quota? Thanks much for the tip. Dennis. Dennis J. Gurgul Helix System Management 617.724.3169 On Mon, 15 Jun 1998, Timothy J Luoma wrote: > Author: Dennis Gurgul > Original-Date: Mon, 15 Jun 1998 13:39:03 -0400 (EDT) > Message-ID: > > > > Does anyone know what's causing this user to have so many pinerc files in > > their directory? Running 3.95 on Digital Unix 4.0b. Thanks: > > Could they be at or over their quota? > > TjL > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 11:00:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA20780 for ; Tue, 16 Jun 1998 11:00:18 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id LAA05576; Tue, 16 Jun 1998 11:00:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA10757; Tue, 16 Jun 1998 10:59:35 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA60560 for ; Tue, 16 Jun 1998 10:58:18 -0700 Received: from quartz.ucs.ualberta.ca (quartz.ucs.ualberta.ca [129.128.5.19]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA20855 for ; Tue, 16 Jun 1998 10:58:17 -0700 Received: from gpu4.srv.ualberta.ca (gpu4.srv.ualberta.ca [129.128.98.18]) by quartz.ucs.ualberta.ca (8.8.8/8.8.8) with ESMTP id LAA36938 for ; Tue, 16 Jun 1998 11:58:15 -0600 Received: from localhost (maldridg@localhost) by gpu4.srv.ualberta.ca (8.8.5/8.8.5) with SMTP id LAA80038 for ; Tue, 16 Jun 1998 11:58:15 -0600 Message-Id: Date: Tue, 16 Jun 1998 11:58:15 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Lea To: Pine Discussion Forum Subject: quota and .pinerc files In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: maldridg@gpu4.srv.ualberta.ca X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 16 Jun 1998, Dennis Gurgul wrote: > They were over quota. Actually, that's how we discovered it. The user > contacted us about a quota problem. So then this happens when someone > goes over quota? Thanks much for the tip. Dennis. I don't know if that's true. I just overloaded one of my accounts and tried to do a few things with Pine. Generated a bunch of quota-related error messages but not one .pinerc123456789 file. Lea ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 19:56:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA29447 for ; Tue, 16 Jun 1998 19:56:10 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id TAA15935; Tue, 16 Jun 1998 19:56:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id TAA19938; Tue, 16 Jun 1998 19:55:56 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id TAA82114 for ; Tue, 16 Jun 1998 19:54:14 -0700 Received: from md2.vsnl.net.in (md2.vsnl.net.in [202.54.6.20]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA01916 for ; Tue, 16 Jun 1998 19:54:11 -0700 Received: from localhost (slfibres@localhost) by md2.vsnl.net.in (8.8.8/8.8.8) with SMTP id IAA06182; Wed, 17 Jun 1998 08:32:49 +0530 (IST) Message-Id: Date: Wed, 17 Jun 1998 08:32:49 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "M/S. SRI LAKSHMI FIBRES" To: Pine Discussion Forum Subject: Re.:pine message scrolling In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Dennis Gurgul X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Pl. explain how to *scroll* pine message instead of using space bar to move page after page to capture the text directly to my computor? K.V.Sivaraman/coimbatore/India From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 20:38:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA29786 for ; Tue, 16 Jun 1998 20:38:19 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id UAA19043; Tue, 16 Jun 1998 20:38:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA21499; Tue, 16 Jun 1998 20:37:37 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA15644 for ; Tue, 16 Jun 1998 20:36:19 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA28723 for ; Tue, 16 Jun 1998 20:36:17 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id VAA13849 for ; Tue, 16 Jun 1998 21:36:16 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id VAA25428 for ; Tue, 16 Jun 1998 21:36:13 -0600 Message-Id: Date: Tue, 16 Jun 1998 21:36:12 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Re.:pine message scrolling In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Pl. explain how to *scroll* pine message instead of using space bar > to move page after page to capture the text directly to my computor? > K.V.Sivaraman/coimbatore/India ...that's two questions I think. I'm not sure about the first one. As far as printing, a "Y" print command is, possibly requiring the "aggregate command set" to be enabled. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 20:41:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA29325 for ; Tue, 16 Jun 1998 20:41:33 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id UAA19087; Tue, 16 Jun 1998 20:41:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA25900; Tue, 16 Jun 1998 20:41:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA36814 for ; Tue, 16 Jun 1998 20:40:07 -0700 Received: from md2.vsnl.net.in (md2.vsnl.net.in [202.54.6.20]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA08894 for ; Tue, 16 Jun 1998 20:40:03 -0700 Received: from localhost (ramchand@localhost) by md2.vsnl.net.in (8.8.8/8.8.8) with SMTP id JAA25117 for ; Wed, 17 Jun 1998 09:18:50 +0530 (IST) Message-Id: Date: Wed, 17 Jun 1998 09:18:50 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "RAMACHANDRAN \"CHIDAMBARAM\"" To: Pine Discussion Forum Subject: Re.:pine message scrolling (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I too wish to have solution. ramchand ---------- Forwarded message ---------- Date: Wed, 17 Jun 1998 08:32:49 +0530 (IST) From: "M/S. SRI LAKSHMI FIBRES" To: Pine Discussion Forum Subject: Re.:pine message scrolling Pl. explain how to *scroll* pine message instead of using space bar to move page after page to capture the text directly to my computor? K.V.Sivaraman/coimbatore/India ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 21:10:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA30042 for ; Tue, 16 Jun 1998 21:09:56 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id VAA16804; Tue, 16 Jun 1998 21:09:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id VAA22322; Tue, 16 Jun 1998 21:09:41 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id VAA39346 for ; Tue, 16 Jun 1998 21:08:13 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA10733 for ; Tue, 16 Jun 1998 21:08:12 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id VAA16785 for ; Tue, 16 Jun 1998 21:08:10 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id WAA14030; Tue, 16 Jun 1998 22:08:08 -0600 Received: (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) id WAA22880; Tue, 16 Jun 1998 22:08:07 -0600 Message-Id: <199806170408.WAA22880@fn2.freenet.edmonton.ab.ca> Date: Tue, 16 Jun 1998 22:08:07 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: brewhaha@freenet.edmonton.ab.ca To: Pine Discussion Forum Subject: Ignored newsgroups header. X-To: pine-info@cac.washington.edu, mail2news@anon.lcs.mit.edu X-Newsreader: TIN [version 1.2 PL2.6] X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've been corresponding on USENET with someone who uses a mail2news gateway. For some reason, when I reply, Pine ignores the newsgroups header in his e-mail, leaving me to put it in. Pine 3.95 also doesn't put a Followup-To: header in. I realize that these should be redundant or useless to software. They are informativ to users though. Does Pine 3.96 use them? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 22:55:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA30568 for ; Tue, 16 Jun 1998 22:55:05 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id WAA17920; Tue, 16 Jun 1998 22:55:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id WAA25168; Tue, 16 Jun 1998 22:54:39 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id WAA69322 for ; Tue, 16 Jun 1998 22:53:09 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA18774 for ; Tue, 16 Jun 1998 22:53:09 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id WAA17902 for ; Tue, 16 Jun 1998 22:53:06 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id XAA47938 for ; Tue, 16 Jun 1998 23:53:05 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id XAA59648 for ; Tue, 16 Jun 1998 23:53:03 -0600 Message-Id: Date: Tue, 16 Jun 1998 23:53:03 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Re.:pine message scrolling In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 17 Jun 1998, M/S. SRI LAKSHMI FIBRES wrote: > I want to see the message *scrolling* & I don't want to see it > page after page. That's what I mean. I just use the arrow keys on my VT102 terminal emulator: telix. Beyond that, there's little I can write for you. I don't even know which version of Pine you're using. > > On Tue, 16 Jun 1998, Raja BrewHaHa wrote: > > > > Pl. explain how to *scroll* pine message instead of using space bar > > > to move page after page to capture the text directly to my computor? > > > K.V.Sivaraman/coimbatore/India > > > > ...that's two questions I think. I'm not sure about the first one. > > > > As far as printing, a "Y" print command is, possibly requiring the > > "aggregate command set" to be enabled. > > > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 16 Jun 1998 23:14:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA30890 for ; Tue, 16 Jun 1998 23:14:45 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA18148; Tue, 16 Jun 1998 23:14:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA18733; Tue, 16 Jun 1998 23:14:24 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA69338 for ; Tue, 16 Jun 1998 23:12:55 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA12247 for ; Tue, 16 Jun 1998 23:12:53 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id BAA17845 for ; Wed, 17 Jun 1998 01:12:51 -0500 Message-Id: Date: Wed, 17 Jun 1998 01:12:51 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: <199806170408.WAA22880@fn2.freenet.edmonton.ab.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: brewhaha@freenet.edmonton.ab.ca >Date: Tue, 16 Jun 1998 22:08:07 -0600 >I've been corresponding on USENET with someone who uses a mail2news >gateway. For some reason, when I reply, Pine ignores the newsgroups header >in his e-mail, leaving me to put it in. You aren't giving sufficient information. You aren't using the gateway? What protocol do you use for Usenet reading? Generally, it doesn't matter if you put in the newsgroups header or not. Pine will ignore it in Mail. Unless a Path header is present, showing the bang path route that the article took to reach your news server, you will not be allowed to post a followup article to News. This is actually one of pine's few well-behaved features related to News. Too many news readers allow mail replies and include headers only applicable to News, and too many mail readers will allow replies to be posted to News instead, even if that wasn't the intent. >Pine 3.95 also doesn't put a Followup-To: header in. I realize that these >should be redundant or useless to software. They are informativ to users >though. Does Pine 3.96 use them? Put it in yourself with Customized-hdrs option in the configuration. Read the context-sensitive help at that option. Again, you can add that to a reply sent to you in Mail, but that won't be sufficient for pine to allow you to post that in News. Followup-To is strictly a News header. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 00:16:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA31307 for ; Wed, 17 Jun 1998 00:16:42 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id AAA18874; Wed, 17 Jun 1998 00:16:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id AAA00548; Wed, 17 Jun 1998 00:16:06 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA66506 for ; Wed, 17 Jun 1998 00:14:14 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA06223 for ; Wed, 17 Jun 1998 00:14:13 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id BAA68062; Wed, 17 Jun 1998 01:14:11 -0600 Received: (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) id BAA73186; Wed, 17 Jun 1998 01:14:11 -0600 Message-Id: <199806170714.BAA73186@fn2.freenet.edmonton.ab.ca> Date: Wed, 17 Jun 1998 01:14:11 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: brewhaha@freenet.edmonton.ab.ca To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@u.washington.edu, mail2news@anon.lcs.mit.edu X-Newsreader: TIN [version 1.2 PL2.6] X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 17 Jun 1998, Adam H. Kerman wrote: > You aren't giving sufficient information. You aren't using the gateway? What > protocol do you use for Usenet reading? In this case, since he's giving me a carbon copy via e-mail, I'm using SMTP. I can and usually do yuuz NNTP. > Generally, it doesn't matter if you put in the newsgroups header or not. Pine > will ignore it in Mail. Unless a Path header is present, showing the bang path > route that the article took to reach your news server, you will not be allowed > to post a followup article to News. Sure I will. I can put the newsgroups header in if Pine doesn't. > This is actually one of pine's few well-behaved features related to News. Too > many news readers allow mail replies and include headers only applicable to > News, and too many mail readers will allow replies to be posted to News instead, > even if that wasn't the intent. In this case, we assume an approval from a moderator, and converse more rapidly than the approval process completes. Pine is well-behaved when an NNTP posting host is available. As far as being well-behaved when deciding whether to post, mail, or both, I'd prefer to have that choice at submission time. If I'M using a mail2news gateway because the number of groups is greater than five and I expect the post to fail, it doesn't really matter--I'll send it to MIT's gateway. The post will fail locally. It's just a bit messy, unless I answer "no" to "post?" at submission time. What I'm saying is that Pine asks the question "post, mail, or both" twice, and it's a little sloppy the second time. In fact, if the post fails, I might not want to mail, because that would mean I should duplicate the mailing on the basis of an incorrect newgroups header alone. That won't even work when sending to duplication-ignoring mailing lists like yours. I think you should let your users use BRAINS to decide when to post or mail, in that order, at submission time. The feature would be especially useful NOW, when my newsreader is LISTING comp.mail.pine, saying that it's invalid, and my sysadmins have the "news-post-without-validation" flag fixed as disabled...exporting to TIN. In the meantime, I guess I can just be notified of articles posted in response to mine, and I'll reply to the post. There's a considerable delay with moderated groups though. I hav no problems with Windows users. I just have problems when they think M$ invented the features in it, made them work together, or doesn't try to cheat on taxes. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 00:45:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA32157 for ; Wed, 17 Jun 1998 00:45:24 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id AAA22370; Wed, 17 Jun 1998 00:45:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id AAA27524; Wed, 17 Jun 1998 00:44:48 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA66432 for ; Wed, 17 Jun 1998 00:41:46 -0700 Received: from luomat.peak.org (cc344191-a.ewndsr1.nj.home.com [24.2.83.40]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA16203 for ; Wed, 17 Jun 1998 00:41:45 -0700 Received: by luomat.peak.org (8.9.0/8.9.0) id DAA05335 for pine-info@u.washington.edu; Wed, 17 Jun 1998 03:41:45 -0400 (EDT) Message-Id: <199806170741.DAA05335@luomat.peak.org> Date: Wed, 17 Jun 98 03:41:41 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: "Adam H. Kerman" Original-Date: Wed, 17 Jun 1998 01:12:51 -0500 (CDT) Message-ID: > Generally, it doesn't matter if you put in the newsgroups header or not. > Pine will ignore it in Mail. Unless a Path header is present, showing the > bang path route that the article took to reach your news server, you will > not be allowed to post a followup article to News. Actually that's not quite true: All you need is the Path: line and something in it. I used to use Path: Bogus path for PINE and that would work. You do have to have a Path: line though, or else it thinks it wasn't a newsgroup message. I find this rather annoying personally. TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 01:02:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA32632 for ; Wed, 17 Jun 1998 01:02:10 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id BAA19659; Wed, 17 Jun 1998 01:02:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id BAA10089; Wed, 17 Jun 1998 01:01:49 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA53960 for ; Wed, 17 Jun 1998 00:59:28 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA16900 for ; Wed, 17 Jun 1998 00:59:27 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id BAA67983 for ; Wed, 17 Jun 1998 01:59:25 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id BAA62210 for ; Wed, 17 Jun 1998 01:59:25 -0600 Message-Id: Date: Wed, 17 Jun 1998 01:59:20 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: <199806170741.DAA05335@luomat.peak.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 17 Jun 1998, Timothy J Luoma wrote: > Path: Bogus path for PINE > and that would work. Yes, and that's specifically what Pine documentation says you don't hav to do and shouldn't do because you don't have to do. Ever wonder why intelligent disobedience IS? > I find this rather annoying personally. Contradictions in what you're told to do to do what you want...and what works are annoying. Hmmm. Now comp.mail.pine is valid. Connection bugs? I remember that Pine didn't try fetching the NG list again last time. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 01:04:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA32694 for ; Wed, 17 Jun 1998 01:04:26 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id BAA19690; Wed, 17 Jun 1998 01:04:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id BAA10148; Wed, 17 Jun 1998 01:04:11 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id BAA81030 for ; Wed, 17 Jun 1998 01:00:01 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA16917 for ; Wed, 17 Jun 1998 01:00:00 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id CAA18748 for ; Wed, 17 Jun 1998 02:59:58 -0500 Message-Id: Date: Wed, 17 Jun 1998 02:59:58 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: <199806170741.DAA05335@luomat.peak.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Timothy J Luoma >Date: Wed, 17 Jun 98 03:41:41 -0400 > Author: "Adam H. Kerman" > Original-Date: Wed, 17 Jun 1998 01:12:51 -0500 (CDT) >>Generally, it doesn't matter if you put in the newsgroups header or not. >>Pine will ignore it in Mail. Unless a Path header is present, showing the >>bang path route that the article took to reach your news server, you will >>not be allowed to post a followup article to News. >Actually that's not quite true: >All you need is the Path: line and something in it. >I used to use >Path: Bogus path for PINE >and that would work. >You do have to have a Path: line though, or else it thinks it wasn't a >newsgroup message. Our friend to whom I was replying won't believe me on this point. Well, I never tried it with a bogus Path. Thanks! I've occassionally copied a Path from another article to get pine to post. >I find this rather annoying personally. Well, it's better than the alternative of some news and mail clients that see the Newsgroups and assume (incorrectly) that the author means to post News. Someone will be sure to post an example of another client that has a better approach, I expect. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 01:18:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA00748 for ; Wed, 17 Jun 1998 01:18:50 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id BAA22957; Wed, 17 Jun 1998 01:18:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id BAA01888; Wed, 17 Jun 1998 01:18:13 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id BAA48122 for ; Wed, 17 Jun 1998 01:15:57 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA24710 for ; Wed, 17 Jun 1998 01:15:56 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id DAA19773 for ; Wed, 17 Jun 1998 03:15:54 -0500 Message-Id: Date: Wed, 17 Jun 1998 03:15:53 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: <199806170714.BAA73186@fn2.freenet.edmonton.ab.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: brewhaha@freenet.edmonton.ab.ca >Date: Wed, 17 Jun 1998 01:14:11 -0600 >On Wed, 17 Jun 1998, Adam H. Kerman wrote: >>Generally, it doesn't matter if you put in the newsgroups header or not. Pine >>will ignore it in Mail. Unless a Path header is present, showing the bang path >>route that the article took to reach your news server, you will not be allowed >>to post a followup article to News. >Sure I will. I can put the newsgroups header in if Pine doesn't. Read what I just wrote a second time. On a reply, posting to News requires more than adding a Newsgroups header. Pine won't inject the reply into the News stream unless it thinks the original was News, not Mail. >In this case, we assume an approval from a moderator, and converse more >rapidly than the approval process completes. Then you have no problem at all. Articles for moderated newsgroups are NEVER injected into the news stream (unless a forgery!) but are mailed to the moderator. So, mail it directly to the moderator's address! >If I'M using a mail2news gateway because the number of groups is greater >than five and I expect the post to fail, it doesn't really matter--I'll >send it to MIT's gateway. The post will fail locally. It's just a bit >messy, unless I answer "no" to "post?" at submission time. Does the gateway require a Newsgroups header? They usually don't. Normally, you put the newsgroup name in the To. That's the whole point of the gateway: to transform an ordinary Mail message into an article. Since Newsgroups isn't a valid Mail header, a well-behaved gateway doesn't expenct to find one. >What I'm saying is that Pine asks the question "post, mail, or both" >twice, and it's a little sloppy the second time. In fact, if the post >fails, I might not want to mail, because that would mean I should >duplicate the mailing on the basis of an incorrect newgroups header alone. You aren't being clear; I'm not following. What second time? >That won't even work when sending to duplication-ignoring mailing lists >like yours. I think you should let your users use BRAINS to decide when to >post or mail, in that order, at submission time. Uh, you aren't on any of MY mailing lists. >The feature would be especially useful NOW, when my newsreader is LISTING >comp.mail.pine, saying that it's invalid, and my sysadmins have the >"news-post-without-validation" flag fixed as disabled...exporting to TIN. Now, what are you talking about? You aren't attempting to post via NNTP? >In the meantime, I guess I can just be notified of articles posted in >response to mine, and I'll reply to the post. There's a considerable delay >with moderated groups though. Notified how? Someone forwards followups? You really are unclear on what you are trying to do. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 08:51:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA31716 for ; Wed, 17 Jun 1998 08:51:14 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id IAA27343; Wed, 17 Jun 1998 08:51:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA15135; Wed, 17 Jun 1998 08:49:12 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA29836 for ; Wed, 17 Jun 1998 08:45:11 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA09376 for ; Wed, 17 Jun 1998 08:45:10 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id KAA07706 for ; Wed, 17 Jun 1998 10:45:08 -0500 Message-Id: Date: Wed, 17 Jun 1998 10:45:08 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Well, it seems I was wrong earlier. In 3.96, when replying to Mail, you CAN get pine to inject an article into the news stream by adding a Newsgroups header. However, no References header will be created and you still MAY NOT add this header in the customized-hdrs option. To add this header, you must postpone the article, and edit mail/postponed-msgs to add it, then continue the postponed message in pine to inject it with the header. I also tried saving News in a mailbox, editing the file to remove the Path header, and then replying in pine. I was NOT allowed to post a followup. Allowing a reply to Mail to be injected into News appears to be new behavior in 3.96. I recall that 3.95 didn't behave this way. Cool! >From: Raja BrewHaHa >Date: Wed, 17 Jun 1998 03:13:03 -0600 (MDT) >Pine or sendmail limits the length of each To address to 180+some characters, >so I must use the Newsgroups header to address over about 8 groups. If you crosspost similar or identical articles to so many newsgroups, you are going to attract the attention of a cancelbot, and your articles will be cancelled on numerous news servers. Generally, you should never crosspost to so many groups; two or three at the very most. >>>What I'm saying is that Pine asks the question "post, mail, or both" >>>twice, and it's a little sloppy the second time. In fact, if the post >>>fails, I might not want to mail, because that would mean I should duplicate >>>the mailing on the basis of an incorrect newgroups header alone. >>You aren't being clear; I'm not following. What second time? >Post, mail, or both?...Both... >Compose message... >Message will be seen by thousands of readers. Really post? >The first question belongs in place of the last, I think, and the option >to mail as well should optionally depend on the post operation. Are you trying to use Pine to post articles in a shell script? Pine really isn't designed for that. You'd have to convince your news administrator that you have a valid need to use inews directly. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 09:34:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA10791 for ; Wed, 17 Jun 1998 09:33:59 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA28730; Wed, 17 Jun 1998 09:33:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA17763; Wed, 17 Jun 1998 09:33:14 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA38774 for ; Wed, 17 Jun 1998 09:30:44 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA05250 for ; Wed, 17 Jun 1998 09:30:43 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id LAA08555 for ; Wed, 17 Jun 1998 11:30:42 -0500 Message-Id: Date: Wed, 17 Jun 1998 11:30:42 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: "Adam H. Kerman" >Date: Wed, 17 Jun 1998 10:45:08 -0500 (CDT) >Well, it seems I was wrong earlier. In 3.96, when replying to Mail, you CAN get >pine to inject an article into the news stream by adding a Newsgroups header. >However, no References header will be created and you still MAY NOT add this >header in the customized-hdrs option. To add this header, you must postpone the >article, and edit mail/postponed-msgs to add it, then continue the postponed >message in pine to inject it with the header. >I also tried saving News in a mailbox, editing the file to remove the Path >header, and then replying in pine. I was NOT allowed to post a followup. >Allowing a reply to Mail to be injected into News appears to be new behavior in >3.96. I recall that 3.95 didn't behave this way. >Cool! I tried another experiment. I posted to a test group and sent a courtesy copy to myself. The courtesy copy, of course, didn't have a Path, but it did have References because I added it as described above. Upon replying to the Mail message, I was allowed to post to News! Even if I removed the References header, I was still allowed to post to News. Only when I removed the News header was I only allowed to reply in Mail. I tried removing various other headers: Return-Path (perhaps because it never left my mail server), Message-ID (was it parsing for a pine message?), and others, but I was always allowed to post a reply to News. I don't understand the difference in behavior between this message, and replying to an article I saved to a mailbox. In the latter case, I was only allowed to reply to News if the Path header remained! What is the critical header in this case? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 09:35:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA10934 for ; Wed, 17 Jun 1998 09:35:52 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA01741; Wed, 17 Jun 1998 09:35:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA15637; Wed, 17 Jun 1998 09:35:25 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA72752 for ; Wed, 17 Jun 1998 09:32:41 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA21145 for ; Wed, 17 Jun 1998 09:32:40 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id LAA08653 for ; Wed, 17 Jun 1998 11:32:38 -0500 Message-Id: Date: Wed, 17 Jun 1998 11:32:38 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Oops. I should have posted the message I was testing with. ---------- Forwarded message ---------- Return-Path: Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id KAA07294 for ; Wed, 17 Jun 1998 10:20:31 -0500 Newsgroups: chi.test Date: Wed, 17 Jun 1998 10:20:27 -0500 (CDT) From: "Adam H. Kerman" Reply-To: "Adam H. Kerman" To: "Adam H. Kerman" Subject: Re: solstice In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 09:49:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA11046 for ; Wed, 17 Jun 1998 09:49:50 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA29243; Wed, 17 Jun 1998 09:49:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA16700; Wed, 17 Jun 1998 09:49:20 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA50414 for ; Wed, 17 Jun 1998 09:47:28 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA07639 for ; Wed, 17 Jun 1998 09:47:22 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id LAA08948; Wed, 17 Jun 1998 11:47:24 -0500 Message-Id: Date: Wed, 17 Jun 1998 11:47:24 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Bug (ID MQ1ZZ): MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1630661997-655933037-898102044=:7885" X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN 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. ---1630661997-655933037-898102044=:7885 Content-Type: TEXT/PLAIN; charset=US-ASCII Sorry about the two previous blank messages. I didn't know that if I answered "yes" to "attach current message" that you would fail to allow me to write text! An error occurs when saving a message to a mailbox when the previous message has no body and no blank line following the headers. The save operation Fails to insert an additional New Line before the "[NL]From " boundary of the message being saved. However, pine still sees the boundary, even though it's not "[NL][NL]From "! If I read the newly-saved message and affect a flag (like open an unread message or flag it answered), the mailbox is rewritten and not one, but two additional New Lines are inserted before the boundary. Obviously, the extra New Line can't cause trouble. Please correct this bug so that whenever a message is saved to a mailbox, the boundary is always preceded by two New Lines regardless of whether the last message has trailing New Lines. ---1630661997-655933037-898102044=:7885 Content-Type: TEXT/PLAIN; name="config.txt" Content-ID: Content-Description: Pine Configuration Data Pine built Tue Dec 30 23:27:35 EST 1997 on host: porky.redhat.com ========== struct pine * ========== ui: login = ahk, full = Adam H. Kerman home = /home/ahk home_dir= /home/ahk hostname= chinet.chinet.com localdom= chinet.com userdom= NULL maildom= chinet.chinet.com cur_cntxt= mail/[] cur_fldr= q actual mbox= /home/ahk/mail/q msgmap: tot=1, cur=1, del=0, hid=0, exld=0, slct=0, sort=Arrival actual inbox= /var/spool/mail/ahk inbox map: tot=333, cur=330, del=0, hid=0, exld=0, slct=0, sort=Arrival term type=vt100, ttyname=/dev/ttyp4, size=24x80, speed=normal ======= Current_val options set ======= personal-name : Adam H. Kerman user-id : ahk nntp-server : news.wwa.com inbox-path : inbox folder-collections : mail/[] : mail/zip/[] news-collections : *{news.wwa.com/nntp}[] default-fcc : "" default-saved-msg-fo : saved-messages postponed-folder : postponed-msgs mail-directory : mail signature-file : .signature address-book : .addressbook feature-list : enable-aggregate-command-set : enable-jump-shortcut : expanded-view-of-addressbooks : expanded-view-of-folders : enable-full-header-cmd : enable-bounce-cmd : enable-suspend : include-text-in-reply : save-will-advance : news-post-without-validation : news-read-in-newsrc-order : delete-skips-deleted : enable-unix-pipe-cmd : enable-flag-cmd : include-header-in-reply : auto-open-next-unread : compose-maps-delete-key-to-ctrl-d : enable-goto-in-file-browser : expanded-view-of-distribution-lists : print-includes-from-line : print-index-enabled : quell-status-message-beeping : select-without-confirm : use-sender-not-x-sender : quell-dead-letter-on-cancel : enable-alternate-editor-cmd : enable-background-sending : preserve-start-stop-characters : include-attachments-in-reply : show-cursor : signature-at-bottom initial-keystroke-li : i : w : ^v default-composer-hdr : To : Cc : Fcc : Subject viewer-hdrs : Resent-From : Reply-To : Message-ID : References : In-Reply-To : To : Resent-To : Cc : Resent-CC : Bcc : Newsgroups : Followup-To : Resent-Date : Subject : Resent-Subject : From : Date saved-msg-name-rule : default-folder fcc-name-rule : default-fcc sort-key : Arrival addrbook-sort-rule : fullname goto-default-rule : most-recent-folder speller : ispell composer-wrap-column : 80 reply-indent-string : > empty-header-message : Undisclosed recipients use-only-domain-name : No printer : attached-to-ansi personal-print-categ : 1 standard-printer : lpr last-time-prune-ques : 98.6 last-version-used : 3.96 bugs-fullname : Pine Developers bugs-address : pine-bugs@cac.washington.edu suggest-fullname : Pine Developers suggest-address : pine-suggestions@cac.washington.edu local-fullname : Local Support local-address : postmaster kblock-passwd-count : 1 alt-addresses : ahk@chinet : ahk@www.chinet.com : ahk@chinet.com : ahk@mail.chinet.com : owner-chi-transportation@chinet.chinet.com : chi-transportation-approval@chinet.chinet.com : Majordomo-Owner@chinet.chinet.com : tra@chinet.chinet.com viewer-overlap : 2 scroll-margin : 0 status-message-delay : 0 mail-check-interval : 150 elm-style-save : no header-in-reply : no feature-level : sapling old-style-reply : no save-by-sender : no ======= Command_line_val options set ======= initial-keystroke-li : i : w : ^v ======= User_val options set (/home/ahk/.pinerc) ======= nntp-server : news.wwa.com folder-collections : mail/[] : mail/zip/[] default-fcc : "" feature-list : enable-aggregate-command-set : enable-jump-shortcut : expanded-view-of-addressbooks : expanded-view-of-folders : enable-full-header-cmd : enable-bounce-cmd : enable-suspend : include-text-in-reply : save-will-advance : news-post-without-validation : news-read-in-newsrc-order : delete-skips-deleted : enable-unix-pipe-cmd : enable-flag-cmd : include-header-in-reply : auto-open-next-unread : compose-maps-delete-key-to-ctrl-d : enable-goto-in-file-browser : expanded-view-of-distribution-lists : print-includes-from-line : print-index-enabled : quell-status-message-beeping : select-without-confirm : use-sender-not-x-sender : quell-dead-letter-on-cancel : enable-alternate-editor-cmd : enable-background-sending : preserve-start-stop-characters : include-attachments-in-reply : show-cursor : signature-at-bottom default-composer-hdr : To : Cc : Fcc : Subject viewer-hdrs : Resent-From : Reply-To : Message-ID : References : In-Reply-To : To : Resent-To : Cc : Resent-CC : Bcc : Newsgroups : Followup-To : Resent-Date : Subject : Resent-Subject : From : Date sort-key : Arrival addrbook-sort-rule : fullname goto-default-rule : most-recent-folder speller : ispell composer-wrap-column : 80 reply-indent-string : > use-only-domain-name : No printer : attached-to-ansi personal-print-categ : 1 last-time-prune-ques : 98.6 last-version-used : 3.96 alt-addresses : ahk@chinet : ahk@www.chinet.com : ahk@chinet.com : ahk@mail.chinet.com : owner-chi-transportation@chinet.chinet.com : chi-transportation-approval@chinet.chinet.com : Majordomo-Owner@chinet.chinet.com : tra@chinet.chinet.com ======= Global_val options set (/usr/lib/pine.conf) ======= inbox-path : inbox default-fcc : sent-mail default-saved-msg-fo : saved-messages postponed-folder : postponed-msgs mail-directory : mail signature-file : .signature address-book : .addressbook saved-msg-name-rule : default-folder fcc-name-rule : default-fcc sort-key : arrival addrbook-sort-rule : fullname-with-lists-last composer-wrap-column : 74 reply-indent-string : > empty-header-message : Undisclosed recipients use-only-domain-name : no printer : attached-to-ansi standard-printer : lpr bugs-fullname : Pine Developers bugs-address : pine-bugs@cac.washington.edu suggest-fullname : Pine Developers suggest-address : pine-suggestions@cac.washington.edu local-fullname : Local Support local-address : postmaster kblock-passwd-count : 1 viewer-overlap : 2 scroll-margin : 0 status-message-delay : 0 mail-check-interval : 150 elm-style-save : no header-in-reply : no feature-level : sapling old-style-reply : no save-by-sender : no ======= Fixed_val options set (/usr/lib/pine.conf.fixed) ======= ========== Feature settings ========== no-allow-talk no-assume-slow-link no-auto-move-read-msgs auto-open-next-unread no-auto-zoom-after-select no-auto-unzoom-after-apply no-compose-cut-from-cursor compose-maps-delete-key-to-ctrl-d no-compose-rejects-unqualified-addrs no-compose-send-offers-first-filter no-compose-sets-newsgroup-without-confirm delete-skips-deleted no-disable-config-cmd no-disable-default-in-bug-report no-disable-busy-alarm no-disable-keyboard-lock-cmd no-disable-keymenu no-disable-password-cmd no-disable-update-cmd no-disable-signature-edit-cmd no-enable-8bit-esmtp-negotiation no-enable-8bit-nntp-posting enable-aggregate-command-set enable-alternate-editor-cmd no-enable-alternate-editor-implicitly enable-background-sending enable-bounce-cmd no-enable-cruise-mode no-enable-cruise-mode-delete no-enable-dot-files no-enable-dot-folders enable-flag-cmd no-enable-flag-screen-implicitly enable-full-header-cmd enable-goto-in-file-browser no-enable-incoming-folders enable-jump-shortcut no-enable-mail-check-cue no-enable-mouse-in-xterm no-enable-newmail-in-xterm-icon enable-suspend no-enable-tab-completion enable-unix-pipe-cmd no-enable-verbose-smtp-posting expanded-view-of-addressbooks expanded-view-of-distribution-lists expanded-view-of-folders no-expunge-without-confirm no-fcc-on-bounce include-attachments-in-reply include-header-in-reply include-text-in-reply no-news-approximates-new-status news-post-without-validation news-read-in-newsrc-order no-pass-control-characters-as-is preserve-start-stop-characters no-print-offers-custom-cmd-prompt print-includes-from-line print-index-enabled no-print-formfeed-between-messages quell-dead-letter-on-cancel no-quell-lock-failure-warnings quell-status-message-beeping no-quell-user-lookup-in-passwd-file no-quit-without-confirm no-reply-always-uses-reply-to no-save-aggregates-copy-sequence no-save-will-quote-leading-froms no-save-will-not-delete save-will-advance select-without-confirm show-cursor no-show-selected-in-boldface signature-at-bottom no-single-column-folder-list no-tab-visits-next-new-message-only no-use-current-dir no-use-function-keys use-sender-not-x-sender no-use-subshell-for-suspend ========== Latest keystrokes ========== RETURN (0x000d) b (0x0062) ESC (0x001b) [ (0x005b) B (0x0042) RETURN (0x000d) ---1630661997-655933037-898102044=:7885 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=q Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: RnJvbSBhaGtAY2hpbmV0LmNoaW5ldC5jb20gIFdlZCBKdW4gMTcgMTA6MjA6 MzEgMTk5OA0KUmV0dXJuLVBhdGg6IDxhaGtAY2hpbmV0LmNoaW5ldC5jb20+ DQpSZWNlaXZlZDogZnJvbSBsb2NhbGhvc3QgKGFoa0Bsb2NhbGhvc3QpDQoJ YnkgY2hpbmV0LmNoaW5ldC5jb20gKDguOC43LzguOC43KSB3aXRoIFNNVFAg aWQgS0FBMDcyOTQNCglmb3IgPGFoa0BjaGluZXQuY2hpbmV0LmNvbT47IFdl ZCwgMTcgSnVuIDE5OTggMTA6MjA6MzEgLTA1MDANCk5ld3Nncm91cHM6IGNo aS50ZXN0DQpEYXRlOiBXZWQsIDE3IEp1biAxOTk4IDEwOjIwOjI3IC0wNTAw IChDRFQpDQpGcm9tOiAiQWRhbSBILiBLZXJtYW4iIDxhaGtAY2hpbmV0LmNo aW5ldC5jb20+DQpSZXBseS1UbzogIkFkYW0gSC4gS2VybWFuIiA8YWhrQGNo aW5ldC5jaGluZXQuY29tPg0KVG86ICJBZGFtIEguIEtlcm1hbiIgPGFoa0Bj aGluZXQuY2hpbmV0LmNvbT4NClN1YmplY3Q6IFJlOiBzb2xzdGljZQ0KSW4t UmVwbHktVG86IDxQaW5lLkxOWC4zLjk2Ljk4MDYxNDE1NTAyNi4xMzQwNUIt MTAwMDAwQGNoaW5ldC5jaGluZXQuY29tPg0KTWVzc2FnZS1JRDogPFBpbmUu TE5YLjMuOTYuOTgwNjE3MTAwMTE1LjY5ODBBLTEwMDAwMEBjaGluZXQuY2hp bmV0LmNvbT4NClJlZmVyZW5jZXM6IDxQaW5lLkxOWC4zLjk2Ljk4MDYxNDE1 NTAyNi4xMzQwNUItMTAwMDAwQGNoaW5ldC5jaGluZXQuY29tPg0KTUlNRS1W ZXJzaW9uOiAxLjANCkNvbnRlbnQtVHlwZTogVEVYVC9QTEFJTjsgY2hhcnNl dD1VUy1BU0NJSQ0KU3RhdHVzOiBSTw0KWC1TdGF0dXM6IA0KDQoNCg== ---1630661997-655933037-898102044=:7885-- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 14:58:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA16773 for ; Wed, 17 Jun 1998 14:58:14 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id OAA10613; Wed, 17 Jun 1998 14:58:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA10143; Wed, 17 Jun 1998 14:57:45 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA86566 for ; Wed, 17 Jun 1998 14:55:44 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA19865 for ; Wed, 17 Jun 1998 14:55:44 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id PAA32719 for ; Wed, 17 Jun 1998 15:55:38 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id PAA47070 for ; Wed, 17 Jun 1998 15:55:36 -0600 Message-Id: Date: Wed, 17 Jun 1998 15:55:36 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 17 Jun 1998, Adam H. Kerman wrote: > I also tried saving News in a mailbox, editing the file to remove the Path > header, and then replying in pine. I was NOT allowed to post a followup. > > Allowing a reply to Mail to be injected into News appears to be new behavior in > 3.96. I recall that 3.95 didn't behave this way. > > Cool! The version of 3.95 I'm using allows follow-ups to e-mail with just the insertion of a newsgroups header: ^R while cursor is in the headers. I've noticed only recently, that it does NOT do the references at ALL. > going to attract the attention of a cancelbot, and your articles will be One cancelbot, it.*, includes followup-to criteria. Fascismo-bot. > >Post, mail, or both?...Both... > >Compose message... > >Message will be seen by thousands of readers. Really post? > > >The first question belongs in place of the last, I think, and the option > >to mail as well should optionally depend on the post operation. > > Are you trying to use Pine to post articles in a shell script? Pine really isn't > designed for that. You'd have to convince your news administrator that you have > a valid need to use inews directly. I hav no shell account. I don't understand why Pine can't do it. It's two questions, actually. Post? Mail? I guess you COULD leave "Both" as an option (gone with the second question). The user would be taking a risk if posting to NGs and a listserv at the same time. This is slightly different from TIN on the system, which checks articles before posting: not to the cancelbot or moderator level of course. I am the son of a TV cartoon baboon. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 18:59:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA20664 for ; Wed, 17 Jun 1998 18:59:31 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id SAA15911; Wed, 17 Jun 1998 18:59:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id SAA15649; Wed, 17 Jun 1998 18:59:04 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id SAA58590 for ; Wed, 17 Jun 1998 18:57:14 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA10577 for ; Wed, 17 Jun 1998 18:57:13 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id TAA73915 for ; Wed, 17 Jun 1998 19:57:11 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id TAA93828 for ; Wed, 17 Jun 1998 19:56:55 -0600 Message-Id: Date: Wed, 17 Jun 1998 19:56:51 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 17 Jun 1998, Adam H. Kerman wrote: > >On Wed, 17 Jun 1998, Adam H. Kerman wrote: > > >>Generally, it doesn't matter if you put in the newsgroups header or not. Pine > >>will ignore it in Mail. Unless a Path header is present, showing the bang path > >>route that the article took to reach your news server, you will not be allowed > >>to post a followup article to News. Actually, if you've read the message first, you'll have to delete Pine's proprietary headers. > Then you have no problem at all. Articles for moderated newsgroups are NEVER > injected into the news stream (unless a forgery!) but are mailed to the > moderator. So, mail it directly to the moderator's address! Will they handle crossposting? I'd still have to put the NGs header in. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 17 Jun 1998 20:20:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA21428 for ; Wed, 17 Jun 1998 20:20:49 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id UAA17017; Wed, 17 Jun 1998 20:20:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA24390; Wed, 17 Jun 1998 20:20:26 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA75406 for ; Wed, 17 Jun 1998 20:18:34 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA05709 for ; Wed, 17 Jun 1998 20:18:29 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id WAA16268 for ; Wed, 17 Jun 1998 22:18:31 -0500 Message-Id: Date: Wed, 17 Jun 1998 22:18:30 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Ignored newsgroups header. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Raja BrewHaHa >Date: Wed, 17 Jun 1998 19:56:51 -0600 (MDT) >On Wed, 17 Jun 1998, Adam H. Kerman wrote: >>Articles for moderated newsgroups are NEVER injected into the news stream >>(unless a forgery!) but are mailed to the moderator. So, mail it directly to >>the moderator's address! >Will they handle crossposting? I'd still have to put the NGs header in. If there's a moderated group in the headers, it's sent to the moderator. If there are multiple moderated groups, it's sent to the first moderator. It's up to the first moderator to inject it into the newsstream. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 18 Jun 1998 06:19:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA30472 for ; Thu, 18 Jun 1998 06:19:00 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id GAA24314; Thu, 18 Jun 1998 06:18:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id GAA06173; Thu, 18 Jun 1998 06:18:05 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id GAA63030 for ; Thu, 18 Jun 1998 06:16:01 -0700 Received: from pump2.york.ac.uk (pump2.york.ac.uk [144.32.128.12]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA13375 for ; Thu, 18 Jun 1998 06:16:00 -0700 Received: from pippin.york.ac.uk (pippin.york.ac.uk [144.32.128.9]) by pump2.york.ac.uk (8.8.7/8.8.7) with SMTP id OAA16308; Thu, 18 Jun 1998 14:15:36 +0100 (BST) Message-Id: <973240.3107168135@pippin.york.ac.uk> Date: Thu, 18 Jun 1998 14:15:35 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Brudenell To: Pine Discussion Forum Subject: Re: pinerc files In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: Dennis Gurgul X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN --On Tue, Jun 16, 1998 12:59 pm -0400 Dennis Gurgul wrote: > They were over quota. Actually, that's how we discovered it. The user > contacted us about a quota problem. So then this happens when someone > goes over quota? Thanks much for the tip. Dennis. I believe this is what should NORMALLY happen (if there is plenty of space): 1. Pine tries to write new version of the preferences file. 2. Pine checks that all the bytes were successfully written out. 3. Pine renames the new version of the file over the old. This sequence prevents you losing or truncating your live settings file if you run out of space during the write operation (which is what would happen if the live preference file's content were simply written over). Of course if, at step 2, Pine discoverd it couldn't write out all the bytes it has to decide what to do with what it HAS managed to write out. Should it delete the (incomplete) file? Or should it leave it in situ so that the user can try and rescue any settings they had altered from out of it? Pine seems to adopt the latter approach. Whilst sensible in general, it might be an idea if Pine 4.00 could stat() the incomplete file and, if it is 0 bytes, delete it? At least this would stop the proliferation of empty "new" files! Cheers, Mike Brudenell -- The Computing Service, University of York, Heslington, York, Yo10 5DD, UK Tel:+44-1904-433811 Fax:+44-1904-433740 http://www.york.ac.uk/~pmb1/ ******* Unsolicited commercial/bulk e-mail is NOT welcome here! ******* From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 18 Jun 1998 10:11:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA01330 for ; Thu, 18 Jun 1998 10:11:42 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA00151; Thu, 18 Jun 1998 10:11:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA27838; Thu, 18 Jun 1998 10:11:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA13034 for ; Thu, 18 Jun 1998 10:09:11 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA19626 for ; Thu, 18 Jun 1998 10:09:11 -0700 Received: from luomat.peak.org (cc344191-a.ewndsr1.nj.home.com [24.2.83.40]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA28181 for ; Thu, 18 Jun 1998 10:09:08 -0700 Received: by luomat.peak.org (8.9.0/8.9.0) id NAA00108 for pine-info@cac.washington.edu; Thu, 18 Jun 1998 13:09:06 -0400 (EDT) Message-Id: <199806181709.NAA00108@luomat.peak.org> Date: Thu, 18 Jun 98 13:09:03 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: another remote pine vunerability (fwd from BugTraq) Content-Type: text/plain MIME-Version: 1.0 X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Begin forwarded message: Approved-By: aleph1@DFW.NET Message-ID: Date: Wed, 17 Jun 1998 16:57:28 +0200 Reply-To: Michal Zalewski Sender: Bugtraq List From: Michal Zalewski Subject: another remote pine vunerability To: BUGTRAQ@NETSPACE.ORG Recently I found silly remote overflow in pine. It's so simple there's no need to describe it: From: Michal Zalewski ...and any attempt of reading this mail will cause: Program received signal SIGSEGV, Segmentation fault. 0x41414141 in ?? () It can be exploited to gain access to remote/local accounts. Fortunately, too long headers are destroyed by sendmail during prescan (maybe there's any way to split long line using encoding tricks): Jun 17 16:49:24 genome sendmail[689]: QAA00689: SYSERR(root): prescan: token too long But other mail daemons aren't so strict - it works. _______________________________________________________________________ Michal Zalewski [lcamtuf@boss.staszic.waw.pl] <= finger for pub PGP key Iterowac jest rzecza ludzka, wykonywac rekursywnie - boska [P. Deutsch] [echo "\$0&\$0">_;chmod +x _;./_] <=------=> [tel +48 (0) 22 813 25 86] From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 19 Jun 1998 16:46:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA31036 for ; Fri, 19 Jun 1998 16:46:50 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id QAA06097; Fri, 19 Jun 1998 16:46:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id QAA24912; Fri, 19 Jun 1998 16:46:14 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id QAA18330 for ; Fri, 19 Jun 1998 16:44:56 -0700 Received: from pop02.globecomm.net (pop02.globecomm.net [207.51.48.186]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA01378 for ; Fri, 19 Jun 1998 16:44:55 -0700 Received: from localhost (207-172-197-103.s40.as2.smf.erols.com [207.172.197.103]) by pop02.globecomm.net (8.8.8/8.8.0) with SMTP id TAA16195; Fri, 19 Jun 1998 19:44:46 -0400 (EDT) Message-Id: <199806192344.TAA16195@pop02.globecomm.net> Date: Fri, 19 Jun 1998 19:44:46 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: HRF To: Pine Discussion Forum Subject: UNSUBSCRIBE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 X-To: brewhaha@freenet.edmonton.ab.ca, pine-info@u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 22 Jun 1998 06:31:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA04193 for ; Mon, 22 Jun 1998 06:31:24 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id GAA17837; Mon, 22 Jun 1998 06:31:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id GAA08896; Mon, 22 Jun 1998 06:29:33 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id GAA10192 for ; Mon, 22 Jun 1998 06:25:50 -0700 Received: from col2.telecom.com.co ([200.21.210.2]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA09218 for ; Mon, 22 Jun 1998 06:25:48 -0700 Received: from col2.telecom.com.co ([200.21.188.26]) by col2.telecom.com.co (8.8.8/8.8.8) with ESMTP id IAA32271 for ; Mon, 22 Jun 1998 08:21:02 -0500 (GMT-0500) Message-Id: <358E7632.467083D2@col2.telecom.com.co> Date: Mon, 22 Jun 1998 08:20:20 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Luis Enrique Delgado Escobar To: Pine Discussion Forum Subject: [Fwd: UNSUBSCRIBE] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------27E32C34A13AF511ECED4496" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Este es un mensaje multipartes en formato MIME. --------------27E32C34A13AF511ECED4496 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Luis Enrique Delgado Escobar e-mail: delgaden@col2.telecom.com.co --------------27E32C34A13AF511ECED4496 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by col2.telecom.com.co (8.8.8/8.8.8) with ESMTP id LAA09565 for ; Tue, 16 Jun 1998 11:32:23 -0500 (GMT-0500) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA29108; Tue, 16 Jun 1998 09:33:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA44322 for ; Tue, 16 Jun 1998 09:32:56 -0700 Received: from DEFIANT.AMAG.COM ([208.222.108.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA05300 for ; Tue, 16 Jun 1998 09:32:55 -0700 Received: by DEFIANT with Internet Mail Service (5.0.1457.3) id ; Tue, 16 Jun 1998 11:32:55 -0500 Message-Id: Date: Tue, 16 Jun 1998 11:32:52 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jim Hunter To: Pine Discussion Forum Subject: UNSUBSCRIBE MIME-Version: 1.0 Content-Type: text/plain X-To: "'pine-info@u.washington.edu'" X-Priority: 3 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN James A. Hunter Network Manager email: jhunter@amag.com voice: (712) 325-5381 ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- --------------27E32C34A13AF511ECED4496-- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 23 Jun 1998 15:58:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA08754 for ; Tue, 23 Jun 1998 15:58:52 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id PAA00983; Tue, 23 Jun 1998 15:58:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA26506; Tue, 23 Jun 1998 15:56:23 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id PAA86620 for ; Tue, 23 Jun 1998 15:53:58 -0700 Received: from zugzug.cfar.UMD.EDU (root@zugzug.cfar.umd.edu [128.8.132.82]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA10384 for ; Tue, 23 Jun 1998 15:53:57 -0700 Received: from cfar.umd.edu by zugzug.cfar.UMD.EDU (8.8.5/UMIACS-0.9/04-05-88) id SAA21627; Tue, 23 Jun 1998 18:53:53 -0400 (EDT) Message-Id: <199806232253.SAA21627@zugzug.cfar.UMD.EDU> Date: Tue, 23 Jun 1998 18:53:52 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Adam Sulmicki To: Pine Discussion Forum Subject: pico "mail" mode. X-To: Pine Discussion Forum X-Cc: adam@cfar.umd.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello I wanted to use pico with an other mailer (MH) in this case I just use it as any other editor. However, the thing I was wondering about is that if I use pico from pine it has ability to automatically format quoted email. That is if I have an email quoted with ">" at beginning of each line and then press ctrl-j to justify it, it does automagically takes care of the ">" chars. How do I enable this feature when MH is calling pico? the only remotely likey option seems be "-t" but it does not quote seems to work. Ideas? ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 23 Jun 1998 16:58:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA09846 for ; Tue, 23 Jun 1998 16:58:35 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id QAA02393; Tue, 23 Jun 1998 16:58:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id QAA28974; Tue, 23 Jun 1998 16:56:19 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id QAA69712 for ; Tue, 23 Jun 1998 16:55:22 -0700 Received: from comet.centenary.edu (comet.centenary.edu [198.137.145.170]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id QAA00626 for ; Tue, 23 Jun 1998 16:48:22 -0700 Received: (qmail 3198 invoked by uid 401); 23 Jun 1998 23:41:55 -0000 Message-Id: Date: Tue, 23 Jun 1998 18:41:55 -0500 (CDT) Reply-To: Son of a Preacherman Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Son of a Preacherman To: Pine Discussion Forum Subject: PCPine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I recently downloaded PCPine, and am thinking about using it as our campus mail client. However, in our computer labs, the person using an individual computer is never the same. The main problem with this is the user-id and personal-name fields need to be changed every time someone logs in. Is there a way to get these to default to the users name on our mailserver without asking the user if that is what he or she wants to do, and without writing it into the pinerc file each time? Thanks for your help. Lee Parker _____________________________________________________________________________ "Oh gaze of love so melt my pride that I may in your house but kneel and in my brokenness to cry spring worship unto thee" --Hymn-by Jars of Clay _____________________________________________________________________________ ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 23 Jun 1998 17:12:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA09750 for ; Tue, 23 Jun 1998 17:12:24 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id RAA29831; Tue, 23 Jun 1998 17:12:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id RAA29533; Tue, 23 Jun 1998 17:10:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id RAA12896 for ; Tue, 23 Jun 1998 17:09:20 -0700 Received: from jeeves.egr.msu.edu (jeeves.egr.msu.edu [35.9.37.127]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id RAA26577 for ; Tue, 23 Jun 1998 17:09:19 -0700 Received: from batradar by jeeves.egr.msu.edu (SMI-8.6/SMI-SVR4) id UAA07365; Tue, 23 Jun 1998 20:09:08 -0400 Received: from localhost by batradar (SMI-8.6/SMI-SVR4) id UAA28521; Tue, 23 Jun 1998 20:09:09 -0400 Message-Id: Date: Tue, 23 Jun 1998 20:09:09 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Chris Schafer To: Pine Discussion Forum Subject: Re: PCPine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Son of a Preacherman X-Cc: Pine Discussion Forum X-Sender: cjs@batradar X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I just wrote a little script to insert the appropriate user information into the pinerc file upon login and the rest is history. No, PCpine doesn't setup as nice as the UNIX version in this situation, but I hope they will change that in the future. Chris. On Tue, 23 Jun 1998, Son of a Preacherman wrote: > I recently downloaded PCPine, and am thinking about using it as our campus > mail client. However, in our computer labs, the person using an > individual computer is never the same. The main problem with this is the > user-id and personal-name fields need to be changed every time someone > logs in. Is there a way to get these to default to the users name on our > mailserver without asking the user if that is what he or she wants to do, > and without writing it into the pinerc file each time? Thanks for your > help. > > Lee Parker > > _____________________________________________________________________________ > > "Oh gaze of love so melt my pride > that I may in your house but kneel > and in my brokenness to cry > spring worship unto thee" > > --Hymn-by Jars of Clay > _____________________________________________________________________________ > > > > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > Christopher James Schafer cjs@egr.msu.edu http://www.egr.msu.edu/~cjs VOX:353.9769 FAX:355.7516 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 23 Jun 1998 19:49:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA11803 for ; Tue, 23 Jun 1998 19:49:56 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id TAA05122; Tue, 23 Jun 1998 19:49:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id TAA11252; Tue, 23 Jun 1998 19:47:50 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id TAA36218 for ; Tue, 23 Jun 1998 19:46:49 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA09304 for ; Tue, 23 Jun 1998 19:46:48 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id VAA03950 for ; Tue, 23 Jun 1998 21:46:39 -0500 Message-Id: Date: Tue, 23 Jun 1998 21:46:38 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: pico "mail" mode. In-Reply-To: <199806232253.SAA21627@zugzug.cfar.UMD.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Adam Sulmicki >Date: Tue, 23 Jun 1998 18:53:52 -0400 >I wanted to use pico with an other mailer (MH) in this case I just use it as >any other editor. However, the thing I was wondering about is that if I use >pico from pine it has ability to automatically format quoted email. . . . >How do I enable this feature when MH is calling pico? The feature is unique to the pine composer. You'll notice that it isn't available when resuming editing on a postponed message. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 23 Jun 1998 20:20:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA11845 for ; Tue, 23 Jun 1998 20:20:30 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id UAA02550; Tue, 23 Jun 1998 20:20:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA12273; Tue, 23 Jun 1998 20:18:24 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA15712 for ; Tue, 23 Jun 1998 20:17:30 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA10963 for ; Tue, 23 Jun 1998 20:17:29 -0700 Received: from D-140-142-189-198.dhcp.washington.edu (D-140-142-189-198.dhcp.washington.edu [140.142.189.198]) by mailhost1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with SMTP id UAA15858; Tue, 23 Jun 1998 20:17:26 -0700 Message-Id: Date: Tue, 23 Jun 1998 20:19:34 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: Re: PCPine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset = US-ASCII X-To: Son of a Preacherman X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN If you set those variables in the pinerc to the null string (i.e. two double quotes) then Pine will not ask the user if they want to save the name/userid to the pinerc file, and each user will be prompted for their own name/id for their session. -teg On Tue, 23 Jun 1998, Son of a Preacherman wrote: > I recently downloaded PCPine, and am thinking about using it as our campus > mail client. However, in our computer labs, the person using an > individual computer is never the same. The main problem with this is the > user-id and personal-name fields need to be changed every time someone > logs in. Is there a way to get these to default to the users name on our > mailserver without asking the user if that is what he or she wants to do, > and without writing it into the pinerc file each time? Thanks for your > help. > > Lee Parker From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 23 Jun 1998 23:38:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA13545 for ; Tue, 23 Jun 1998 23:38:08 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA08009; Tue, 23 Jun 1998 23:38:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA09855; Tue, 23 Jun 1998 23:37:39 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA15862 for ; Tue, 23 Jun 1998 23:35:42 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA22276 for ; Tue, 23 Jun 1998 23:35:41 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id AAA49761; Wed, 24 Jun 1998 00:35:39 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id AAA31642; Wed, 24 Jun 1998 00:35:39 -0600 Message-Id: Date: Wed, 24 Jun 1998 00:35:38 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: pico "mail" mode. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 23 Jun 1998, Adam H. Kerman wrote: > >How do I enable this feature [quote formatting] when MH is calling pico? > > The feature is unique to the pine composer. You'll notice that it isn't > available when resuming editing on a postponed message. > I hav access to two news-readers on this system. The threaded one's called tin. It uses pico, so I have the same question. Is there a switch on pico to enable ^J? I also use pico with Lynx. When using pico with tin or Lynx, and after hitting ^R, using [tab] to complete filenames isn't available either. Is there a switch on pico to enable filename completion? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 23 Jun 1998 23:53:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA13566 for ; Tue, 23 Jun 1998 23:53:28 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA08182; Tue, 23 Jun 1998 23:53:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA24763; Tue, 23 Jun 1998 23:51:59 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA08118 for ; Tue, 23 Jun 1998 23:50:14 -0700 Received: from zugzug.cfar.UMD.EDU (root@zugzug.cfar.umd.edu [128.8.132.82]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA22884 for ; Tue, 23 Jun 1998 23:50:12 -0700 Received: from cfar.umd.edu by zugzug.cfar.UMD.EDU (8.8.5/UMIACS-0.9/04-05-88) id CAA00342; Wed, 24 Jun 1998 02:50:02 -0400 (EDT) Message-Id: <199806240650.CAA00342@zugzug.cfar.UMD.EDU> Date: Wed, 24 Jun 1998 02:50:01 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Adam Sulmicki To: Pine Discussion Forum Subject: Re: pico "mail" mode. In-Reply-To: Your message of "Tue, 23 Jun 1998 21:46:38 CDT." X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum , adam@cfar.umd.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN "Adam H. Kerman" writes: ->>From: Adam Sulmicki ->>Date: Tue, 23 Jun 1998 18:53:52 -0400 -> ->>I wanted to use pico with an other mailer (MH) in this case I just use it as ->>any other editor. However, the thing I was wondering about is that if I use ->>pico from pine it has ability to automatically format quoted email. . . . -> ->>How do I enable this feature when MH is calling pico? -> ->The feature is unique to the pine composer. You'll notice that it isn't ->available when resuming editing on a postponed message. Would make sense, since I did looked into pico source and did not see anything like this, then again I did not look too carefully. This brings question what other Mail-aware editors are out there [1] -Adam [1] Emacs does not count since it is too slow to start each time I want to send an email. It would be ok if it could run in daemon mode in background and starting an extra emacs would just load an extra front-end only. Unfortunatelly it is not what emacs-client does. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 24 Jun 1998 00:16:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA10991 for ; Wed, 24 Jun 1998 00:16:10 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id AAA05300; Wed, 24 Jun 1998 00:16:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id AAA11184; Wed, 24 Jun 1998 00:15:47 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA08072 for ; Wed, 24 Jun 1998 00:13:19 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA19310 for ; Wed, 24 Jun 1998 00:13:17 -0700 Received: from fireball.control-risks.de (port235.koeln.ndh.net [195.94.92.235]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id JAA04933 for ; Wed, 24 Jun 1998 09:13:01 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id JAA04311; Wed, 24 Jun 1998 09:07:45 +0200 Message-Id: <19980624090739.B4297@control-risks.de> Date: Wed, 24 Jun 1998 09:07:39 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: pico "mail" mode. In-Reply-To: <199806240650.CAA00342@zugzug.cfar.UMD.EDU>; from Adam Sulmicki on Wed, Jun 24, 1998 at 02:50:01AM -0400 References: <199806240650.CAA00342@zugzug.cfar.UMD.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Adam Sulmicki (adam@cfar.umd.edu): > "Adam H. Kerman" writes: >>From: Adam Sulmicki > This brings question what other Mail-aware editors are out there [1] Loads of them. At the moment, I`m using vim. It can handle almost anything, except of course (in its default settings) your reply string. Change it. > [1] Emacs does not count since it is too slow to start each time I want to > send an email. It would be ok if it could run in daemon mode in background > and starting an extra emacs would just load an extra front-end only. > Unfortunatelly it is not what emacs-client does. It is. You must be doing something wrong. However, if you`re using Emacs anyway, you might as well use its built-in Mail-/Newsreader Gnus. Robin -- Robin S. Socha M.A. Control Risks Germany Ltd. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 24 Jun 1998 03:15:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA19712 for ; Wed, 24 Jun 1998 03:15:26 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id DAA08072; Wed, 24 Jun 1998 03:15:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id DAA28697; Wed, 24 Jun 1998 03:14:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id DAA74342 for ; Wed, 24 Jun 1998 03:12:46 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA29741 for ; Wed, 24 Jun 1998 03:12:46 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id DAA11239 for ; Wed, 24 Jun 1998 03:12:43 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id EAA54760 for ; Wed, 24 Jun 1998 04:12:42 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id EAA23972 for ; Wed, 24 Jun 1998 04:12:41 -0600 Message-Id: Date: Wed, 24 Jun 1998 04:12:41 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Tagline manager MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've noticed a couple of posts to USENET from offline express. That started out as a shareware FidoNet mailer. I once used it. The thing I miss about it is the tagline manager. If you're not familiar with taglines, they're the same as "signatures", except they're always one line and they usually change from post to post of the same author. That's because the author has a collection they choose from, or let the mailer choose randomly. Currently, I crudely imitate a tagline manager with a small collection of files that I insert after a message. Typically, taglines are the last line, or lines of a post, and they start with an asterisk. That lets you hit one key to steal someone's tagline, which is often a one-liner from Star Trek, the Simpsons, or something about being hooked on roasted, green, bitter beans. ...I write my own...Or fix someone else's... * Articles deemed as polical propaganda, or deemed as for the sale of weapons or prostitutes will be rejected. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 24 Jun 1998 05:27:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA18770 for ; Wed, 24 Jun 1998 05:27:33 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id FAA13026; Wed, 24 Jun 1998 05:27:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id FAA01160; Wed, 24 Jun 1998 05:26:59 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id FAA38678 for ; Wed, 24 Jun 1998 05:24:36 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA07072 for ; Wed, 24 Jun 1998 05:24:34 -0700 Received: from fireball.control-risks.de (port212.koeln.ndh.net [195.94.92.212]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id OAA02549 for ; Wed, 24 Jun 1998 14:24:18 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id OAA05338; Wed, 24 Jun 1998 14:23:04 +0200 Message-Id: <19980624142257.E4599@control-risks.de> Date: Wed, 24 Jun 1998 14:22:57 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Tagline manager In-Reply-To: ; from Raja BrewHaHa on Wed, Jun 24, 1998 at 04:12:41AM -0600 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Raja BrewHaHa (brewhaha@freenet.edmonton.ab.ca): > The thing I miss about it is the tagline manager. If you're not familiar > with taglines, they're the same as "signatures", except they're always one > line and they usually change from post to post of the same author. -- Robin S. Socha M.A. Control Risks Germany Ltd. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 24 Jun 1998 08:26:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA24459 for ; Wed, 24 Jun 1998 08:26:15 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id IAA15938; Wed, 24 Jun 1998 08:26:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA23831; Wed, 24 Jun 1998 08:25:14 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA29802 for ; Wed, 24 Jun 1998 08:23:41 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA20127 for ; Wed, 24 Jun 1998 08:23:40 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id KAA28522 for ; Wed, 24 Jun 1998 10:23:16 -0500 Message-Id: Date: Wed, 24 Jun 1998 10:23:16 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: pico "mail" mode. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Please don't send me duplicates of your replies to the list. >From: Raja BrewHaHa >Date: Wed, 24 Jun 1998 00:35:38 -0600 (MDT) >I hav access to two news-readers on this system. The threaded one's called >tin. It uses pico, so I have the same question. Is there a switch on pico >to enable ^J? To fix the quoting in followups? No. >I also use pico with Lynx. When using pico with tin or Lynx, and after >hitting ^R, using [tab] to complete filenames isn't available either. >Is there a switch on pico to enable filename completion? No. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Wed, 24 Jun 1998 20:42:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA00980 for ; Wed, 24 Jun 1998 20:42:05 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id UAA01228; Wed, 24 Jun 1998 20:42:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA24697; Wed, 24 Jun 1998 20:41:38 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA41082 for ; Wed, 24 Jun 1998 20:39:45 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA08933 for ; Wed, 24 Jun 1998 20:39:44 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id VAA42422 for ; Wed, 24 Jun 1998 21:39:43 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id VAA29446 for ; Wed, 24 Jun 1998 21:39:39 -0600 Message-Id: Date: Wed, 24 Jun 1998 21:39:39 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Tagline manager In-Reply-To: <19980624142257.E4599@control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 24 Jun 1998, Robin S. Socha wrote: > Quoting Raja BrewHaHa (brewhaha@freenet.edmonton.ab.ca): > > > The thing I miss about it is the tagline manager. If you're not familiar > > with taglines, they're the same as "signatures", except they're always one > > line and they usually change from post to post of the same author. > > Nah...that's just the random function of a tagline manager. I didn't use that function of my tagline manager very often. It just wouldn't be the same as splicing into Pine's addressbook code, especially if that code is reasonably reusable. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 25 Jun 1998 00:46:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA07421 for ; Thu, 25 Jun 1998 00:45:59 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id AAA04283; Thu, 25 Jun 1998 00:45:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id AAA03122; Thu, 25 Jun 1998 00:43:21 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA85160 for ; Thu, 25 Jun 1998 00:42:09 -0700 Received: from mail.info.gov.hk (mail.info.gov.hk [202.82.0.205]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA22749 for ; Thu, 25 Jun 1998 00:42:04 -0700 Received: (from kitty@localhost) by mail.info.gov.hk (8.7.1/8.6.6) id PAA17501; Thu, 25 Jun 1998 15:48:11 +0800 (HKT) Message-Id: Date: Thu, 25 Jun 1998 15:48:10 +0800 (HKT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Kitty Kwan To: Pine Discussion Forum Subject: customised message in the mail body MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Just want to know if there are ways to include a customised message in the body of an email message which we may distribute to our mailusers or mailing lists. Kitty. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 25 Jun 1998 06:36:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA13958 for ; Thu, 25 Jun 1998 06:36:13 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id GAA11384; Thu, 25 Jun 1998 06:36:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id GAA07686; Thu, 25 Jun 1998 06:35:11 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id GAA16502 for ; Thu, 25 Jun 1998 06:33:46 -0700 Received: from equake.geol.vt.edu (equake.geol.vt.edu [128.173.184.42]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id GAA20967 for ; Thu, 25 Jun 1998 06:33:46 -0700 Received: from localhost (snoke@localhost) by equake.geol.vt.edu (8.6.9/8.6.9) with SMTP id JAA04399; Thu, 25 Jun 1998 09:33:44 -0400 Message-Id: Date: Thu, 25 Jun 1998 09:33:44 -0400 (EDT) Reply-To: Arthur Snoke Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Arthur Snoke To: Pine Discussion Forum Subject: Extended ISO-8859-1 and Pine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-To: Pine Discussion Forum X-Cc: lizzy@vt.edu, benchoff@vt.edu, Michael Acierno , keiser@clrs1.ciw.edu, Richard T Williams , X-Sender: snoke@equake X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 27 May I sent the Discussion Forum a note describing problems I, as a new PINE user, was having with some characters which were mistranslated, and I thought that the problem was with my configuration of pine not handling the iso-8859-1 character set translation. I was wrong. PINE on my sunos system handles normal iso-8859-1 fine. But I still get some characters mistranslated, and after some sleuthing by myself and John Berthels , I think we have an answer and that it is likely of interest to members of the list and the authors of pine. In the iso-8859-1 8-bit extension of US-ASCII, the first 32 character codes (hex 80-9F) are not used. These ARE used in two "extensions" of the 8-bit character set, one is in the Windows Character Set and in the html which is written by "Save as" to html in clarisworks (and maybe others) and interpreted in Netscape 4 (but not Netscape 3). (HTML v3.2 also does not use those 32 character codes, so Netscape 4 is "nonstandard" in this=20 respect unless there is a more recent "accepted" html character set). Hence if you get mail using pine (or eudora) which was written by a netscape 4.x mailer (or others, perhaps), you will get several characters mistranslated. The most obvious of these is the apostrophe used in contractions like "Physician's". Instead of being transmitted as 39 decimal (27 hex), it comes across as a curly apostrophe with the code decimal 146 (hex 92). Here is a line from my most recent troublesome document:=20 The Physician^=D2s Dilemma: On my xterm window, this comes across as the character with iso-8859-1 code 210 decimal (D2 hex) -- an offset of 64 decimal (40 hex) from what I see when I use my Sun Mailtool and look at the untranslated quoted printable rendition. (John writes concerning the truly unprintable characters hex 0-31, "A common way to print these to screen is as a caret '^' followed by a character. Carriage return (ASCII 13 decimal) is printed as ^M - and the 'M' character is ASCII decimal 77 =3D 13 + 64. So Pine is being helpful and using the same convention for the 'upper control characters' "unprintable" characters is commonly done."=20 Others from among the 32 characters which can be bothersome are smart quotes (single and double), various length dashes and the ... (ellipsis). Assuming we have identified the problem correctly, the question is what to do about it? It may be that some mail server translators (like the one for the PINE List) can or do some renditions in 8-bit translation. (But a recipient using netscape would like to get his curly quotes so might not appreciate any other translation.) As I can see the curly quotes, etc., within Netscape on the same machine I use for pine, there is a font set which knows about them, so maybe pine could not add 64 decimal to these characters but just display them. Or one could put in a simple filter which translates the characters into printable ones -- hex 92 gets changed to hex 27, etc. I (and John) would appreciate comments and suggestions. If someone already has such a filter, please share. If you want references documenting any of the above, we have it. (The PC Character Map and the extended html set are not quite identical, for example.) ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 25 Jun 1998 07:44:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA14927 for ; Thu, 25 Jun 1998 07:44:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA09503; Thu, 25 Jun 1998 07:44:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA10131; Thu, 25 Jun 1998 07:43:32 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA28078 for ; Thu, 25 Jun 1998 07:42:00 -0700 Received: from chinet.chinet.com (chinet.chinet.com [206.158.147.18]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA13327 for ; Thu, 25 Jun 1998 07:41:59 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id JAA28984 for ; Thu, 25 Jun 1998 09:41:55 -0500 Message-Id: Date: Thu, 25 Jun 1998 09:41:55 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Extended ISO-8859-1 and Pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Arthur Snoke >Date: Thu, 25 Jun 1998 09:33:44 -0400 (EDT) >But I still get some characters mistranslated, and after some sleuthing >by myself and John Berthels , I think we have >an answer and that it is likely of interest to members of the list and the >authors of pine. That was fascinating; thank you. >The most obvious of these is the apostrophe used in contractions like >"Physician's". Instead of being transmitted as 39 decimal (27 hex), it comes >across as a curly apostrophe with the code decimal 146 (hex 92). In fact, I was having just such a discussion with someone from Germany a few weeks ago about this very miscoded character! From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 25 Jun 1998 07:57:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA14818 for ; Thu, 25 Jun 1998 07:57:30 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA12795; Thu, 25 Jun 1998 07:57:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA10739; Thu, 25 Jun 1998 07:56:09 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA36184 for ; Thu, 25 Jun 1998 07:55:13 -0700 Received: from helix.mgh.harvard.edu (helix.mgh.harvard.edu [132.183.108.14]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id HAA09912 for ; Thu, 25 Jun 1998 07:55:12 -0700 Received: from localhost by helix.mgh.harvard.edu (5.65v4.0/1.1.10.5/02Feb97-1116AM) id AA07863; Thu, 25 Jun 1998 10:54:17 -0400 Message-Id: Date: Thu, 25 Jun 1998 10:54:17 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dennis Gurgul To: Pine Discussion Forum Subject: Re: Extended ISO-8859-1 and Pine In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE X-To: Arthur Snoke X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I get the same apostrophe problem logging into a DEC unix box via SmartTerm telnet on a W-95 PC. =20 Dennis J. Gurgul Helix System Management 617.724.3169 On Thu, 25 Jun 1998, Arthur Snoke wrote: > On 27 May I sent the Discussion Forum a note describing problems I, as a > new PINE user, was having with some characters which were mistranslated, > and I thought that the problem was with my configuration of pine not > handling the iso-8859-1 character set translation. >=20 > I was wrong. PINE on my sunos system handles normal iso-8859-1 fine. >=20 > But I still get some characters mistranslated, and after some sleuthing > by myself and John Berthels , I think we have > an answer and that it is likely of interest to members of the list and th= e > authors of pine. >=20 > In the iso-8859-1 8-bit extension of US-ASCII, the first 32 character > codes (hex 80-9F) are not used. These ARE used in two "extensions" of th= e > 8-bit character set, one is in the Windows Character Set and in the html > which is written by "Save as" to html in clarisworks (and maybe others) > and interpreted in Netscape 4 (but not Netscape 3). (HTML v3.2 also does > not use those 32 character codes, so Netscape 4 is "nonstandard" in this= =20 > respect unless there is a more recent "accepted" html character set). >=20 > Hence if you get mail using pine (or eudora) which was written by a > netscape 4.x mailer (or others, perhaps), you will get several characters > mistranslated. The most obvious of these is the apostrophe used in > contractions like "Physician's". Instead of being transmitted as 39 > decimal (27 hex), it comes across as a curly apostrophe with the code > decimal 146 (hex 92). Here is a line from my most recent troublesome > document:=20 >=20 > The Physician^=D2s Dilemma: >=20 > On my xterm window, this comes across as the character with iso-8859-1 > code 210 decimal (D2 hex) -- an offset of 64 decimal (40 hex) from what I > see when I use my Sun Mailtool and look at the untranslated quoted > printable rendition. (John writes concerning the truly unprintable > characters hex 0-31, "A common way to print these to screen is as a caret > '^' followed by a character. Carriage return (ASCII 13 decimal) is printe= d > as ^M - and the 'M' character is ASCII decimal 77 =3D 13 + 64. So Pine is > being helpful and using the same convention for the 'upper control > characters' "unprintable" characters is commonly done."=20 >=20 > Others from among the 32 characters which can be bothersome are smart > quotes (single and double), various length dashes and the ... (ellipsis). >=20 > Assuming we have identified the problem correctly, the question is what t= o > do about it? It may be that some mail server translators (like the one > for the PINE List) can or do some renditions in 8-bit translation. (But = a > recipient using netscape would like to get his curly quotes so might not > appreciate any other translation.) As I can see the curly quotes, etc., > within Netscape on the same machine I use for pine, there is a font set > which knows about them, so maybe pine could not add 64 decimal to these > characters but just display them. Or one could put in a simple filter > which translates the characters into printable ones -- hex 92 gets change= d > to hex 27, etc. >=20 > I (and John) would appreciate comments and suggestions. If someone > already has such a filter, please share. If you want references > documenting any of the above, we have it. (The PC Character Map and the > extended html set are not quite identical, for example.) >=20 >=20 >=20 >=20 >=20 >=20 > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- >=20 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 25 Jun 1998 08:32:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA15155 for ; Thu, 25 Jun 1998 08:32:40 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id IAA10581; Thu, 25 Jun 1998 08:32:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA12193; Thu, 25 Jun 1998 08:32:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA80442 for ; Thu, 25 Jun 1998 08:30:43 -0700 Received: from uu7.psi.com (uu7.psi.com [38.8.39.2]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA13431 for ; Thu, 25 Jun 1998 08:30:38 -0700 Received: (from uucp@localhost) by uu7.psi.com (8.8.8/4.0.940727-PSI/PSINet) with UUCP id PAA05259 for pine-info@u.washington.edu; Thu, 25 Jun 1998 15:30:33 GMT Received: by jandr.com (8.6.13/200.19.1.1) id LAA15355; Thu, 25 Jun 1998 11:19:53 -0400 Message-Id: Date: Thu, 25 Jun 1998 11:19:52 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Joe DiBenedetto To: Pine Discussion Forum Subject: Re: customised message in the mail body In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Kitty Kwan X-Cc: Pine Discussion Forum X-Sender: joed@jrmusic X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Kitty, If by "customised" you mean a form letter, there are ways. The simplest is to create the form letter in plain text, and save the file in a public or shared directory. Then users can copy the message to their home direc- tory and read it into the body of their messages using ^R in compose mode. Joe On Thu, 25 Jun 1998, Kitty Kwan wrote: > Just want to know if there are ways to include a customised message in > the body of an email message which we may distribute to our mailusers or > mailing lists. > > Kitty. > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 25 Jun 1998 22:00:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA28557 for ; Thu, 25 Jun 1998 22:00:14 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id WAA02563; Thu, 25 Jun 1998 22:00:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id VAA01627; Thu, 25 Jun 1998 21:59:31 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id VAA18696 for ; Thu, 25 Jun 1998 21:57:31 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA22895 for ; Thu, 25 Jun 1998 21:57:30 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id WAA92133 for ; Thu, 25 Jun 1998 22:57:28 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id WAA20252 for ; Thu, 25 Jun 1998 22:57:25 -0600 Message-Id: Date: Thu, 25 Jun 1998 22:57:25 -0600 (MDT) Reply-To: Raja BrewHaHa Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Extended ISO-8859-1 and Pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-Cc: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 25 Jun 1998, Arthur Snoke wrote: > PINE on my sunos system handles normal iso-8859-1 fine. That would be because it does nothing to it, except for display. > In the iso-8859-1 8-bit extension of US-ASCII, the first 32 character > codes (hex 80-9F) are not used. These ARE used in two "extensions" of the > 8-bit character set, one is in the Windows Character Set and in the html That's code page 850, not iso-8859-1. There have been no changes to iso-8859-1 regarding use of characters below 0x20, or for about 32 characters above 0x80. > which is written by "Save as" to html in clarisworks (and maybe others) > and interpreted in Netscape 4 (but not Netscape 3). (HTML v3.2 also does > not use those 32 character codes, so Netscape 4 is "nonstandard" in this > respect unless there is a more recent "accepted" html character set). As I mentioned, this is code page 850. Yes. NetScape is folowing M$ towards possible backwards incompatibility if the IETF or ISO bodies extend iso-8859-1 and others. > Hence if you get mail using pine (or eudora) which was written by a > netscape 4.x mailer (or others, perhaps), you will get several characters > mistranslated. The most obvious of these is the apostrophe used in > contractions like "Physician's". Instead of being transmitted as 39 > decimal (27 hex), it comes across as a curly apostrophe with the code > decimal 146 (hex 92). Here is a line from my most recent troublesome > document: > > The Physician^Òs Dilemma: Decimal 146 is within an excluded range of iso-8859-1. It's okay for 8bit, as in binary files. It shouldn't be printable. > Assuming we have identified the problem correctly, the question is what to > do about it? It may be that some mail server translators (like the one > for the PINE List) can or do some renditions in 8-bit translation. (But a > recipient using netscape would like to get his curly quotes so might not > appreciate any other translation.) As I can see the curly quotes, etc., In order to do that, you would have to make everyone register with the character set that they use. Asking NetScape to document these non-standards as Content-Type: text/plain; charset=code-page-850 would make more sense. Pine might then know how to translate such characters into printables for display. > within Netscape on the same machine I use for pine, there is a font set > which knows about them, so maybe pine could not add 64 decimal to these > characters but just display them. Or one could put in a simple filter > which translates the characters into printable ones -- hex 92 gets changed > to hex 27, etc. I'm not sure why Pine is adding 64 to characters between 0x80 and 0xBF inclusive. Possibly, those are already used for terminal control, which means that you could change that code in Pine yourself if those characters are printable on your terminal (with that font you mention loaded). From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 25 Jun 1998 22:25:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA28467 for ; Thu, 25 Jun 1998 22:25:02 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id WAA29223; Thu, 25 Jun 1998 22:24:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id WAA02462; Thu, 25 Jun 1998 22:24:41 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id WAA16424 for ; Thu, 25 Jun 1998 22:23:46 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA07776 for ; Thu, 25 Jun 1998 22:23:45 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id XAA47591 for ; Thu, 25 Jun 1998 23:23:44 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id XAA69614 for ; Thu, 25 Jun 1998 23:23:39 -0600 Message-Id: Date: Thu, 25 Jun 1998 23:23:39 -0600 (MDT) Reply-To: Raja BrewHaHa Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: customised message in the mail body In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-No-Archive: YES X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 25 Jun 1998, Kitty Kwan wrote: > Just want to know if there are ways to include a customised message in > the body of an email message which we may distribute to our mailusers or > mailing lists. > > Kitty. > If by "customised" you mean "personalized form letter", you're best off using another program, like WordPerfect, to generate the letters. Just use the "ASCII text printer" printer driver to make it print to a file. While that will speed up creation of the letters a bit, it will also result in one large file. That's fine. If you take a look at your postponed messages file, and make a WordPerfect form that will imitate that file format, you should be able to minimize the necessary work. That should reduce the work to a few key-strokes per message. If you could turn off Pine's display and run a keyboard macro for the purpose, you'd be laughing. As it is, you're stuck with a lot of unnecessary display if you can figure out how to write the keyboard macro. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 26 Jun 1998 04:24:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA03290 for ; Fri, 26 Jun 1998 04:24:45 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id EAA07471; Fri, 26 Jun 1998 04:24:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id EAA21362; Fri, 26 Jun 1998 04:23:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id EAA38690 for ; Fri, 26 Jun 1998 04:21:34 -0700 Received: from lancaster.nexor.co.uk (lancaster.nexor.co.uk [128.243.9.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA20458 for ; Fri, 26 Jun 1998 04:21:32 -0700 Received: from skyhawk.nexor.co.uk by lancaster.nexor.co.uk with SMTP (NEXOR MMTA 2.2); Fri, 26 Jun 1998 12:21:28 +0100 Message-Id: Date: Fri, 26 Jun 1998 12:21:27 +0100 (BST) Reply-To: John Berthels Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: John Berthels To: Pine Discussion Forum Subject: Re: Extended ISO-8859-1 and Pine In-Reply-To: MIME-Version: 1.0 Content-ID: Content-Type: MULTIPART/MIXED; boundary="-559023410-758783491-898859935=:4359" X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ---559023410-758783491-898859935=:4359 Content-ID: Content-Type: TEXT/PLAIN; CHARSET="US-ASCII" > > PINE on my sunos system handles normal iso-8859-1 fine. > > That would be because it does nothing to it, except for display. Almost...see 'control character' bit below. > > In the iso-8859-1 8-bit extension of US-ASCII, the first 32 character > > codes (hex 80-9F) are not used. These ARE used in two "extensions" of the > > 8-bit character set, one is in the Windows Character Set and in the html > > That's code page 850, not iso-8859-1. There have been no changes to > iso-8859-1 regarding use of characters below 0x20, or for about 32 > characters above 0x80. Cool (I didn't know the name for it). Its code page 850. Unfortunately this is what Netscape 4 (at least) will produce and label as text/plain; charset=iso-8859-1 [It and IE also understand these codes as &XXX; 'ampersand tags' in HTML documents.] > As I mentioned, this is code page 850. Yes. NetScape is folowing M$ > towards possible backwards incompatibility if the IETF or ISO bodies > extend iso-8859-1 and others. I'm not sure, but I think this range is already used in iso-8859-1 for non-printable control characters. > Decimal 146 is within an excluded range of iso-8859-1. It's okay for 8bit, > as in binary files. It shouldn't be printable. Yup. But as above, Netscape labels this bodypart as iso-8859-1. Bad netscape. > > Assuming we have identified the problem correctly, the question is what to > > do about it? It may be that some mail server translators (like the one > > for the PINE List) can or do some renditions in 8-bit translation. (But a > > recipient using netscape would like to get his curly quotes so might not > > appreciate any other translation.) As I can see the curly quotes, etc., > > In order to do that, you would have to make everyone register with the > character set that they use. Asking NetScape to document these > non-standards as > > Content-Type: text/plain; charset=code-page-850 > > would make more sense. Pine might then know how to translate such > characters into printables for display. This would be the best solution, naturally. > I'm not sure why Pine is adding 64 to characters between 0x80 and 0xBF > inclusive. Possibly, those are already used for terminal control, which > means that you could change that code in Pine yourself if those characters > are printable on your terminal (with that font you mention loaded). PINE seems to do the same thing for the 80->bf control characters as it does for the 00->1f ones. Namely print a caret '^', followed by a character which has the code of the control character + 64. [e.g. ^M for carriage return. This practice is common - is it standardised anywhere?] Attached is a little perl script which maps a couple of these CP 850 characters to similar glyphs in iso-8859-1. I've installed it with a display-filters=_CHARSET(ISO-8859-1)_ /path/to/the/filter/8859filt line. Seems to work, but I don't get much of this mail. In the spirit of "liberal in what you expect", would a config option to perform similar translations to characters in this illegal range in a iso-8859-1 text be a good thing to add to pine? [Would remove the overhead of running the display filter.] regards, jb -- John Berthels Email: j.berthels@nexor.co.uk X.400: /G=john/S=berthels/O=nexor/P=nexor/A=cwmail/C=gb/ ---559023410-758783491-898859935=:4359 Content-ID: Content-Description: Content-Type: TEXT/PLAIN; CHARSET="US-ASCII"; NAME="8859filt" Content-Transfer-Encoding: base64 IyEvdXNyL2xvY2FsL2Jpbi9wZXJsIC13DQojDQojIFNtYWxsIFBJTkUgZmls dGVyIHRvIGhhbmRsZSBub24taXNvLTg4NTktMSBjaGFyYWN0ZXJzDQojIGlu Y29ycmVjdGx5IHByb2R1Y2VkIGJ5IHNvbWUgbWFpbGVycyAoZWcgTmV0c2Nh cGUgNCkNCiMgKFBJTkUgcHJlc2VudHMgdGhlc2UgY2hhcnMgdG8gdXMgYXMg YSBjYXJldC0oY29kZSArIDY0KSBzZXF1ZW5jZSkNCiMNCiMgdjEuMCwgZ2Vu ZXJhbGx5IHVudGVzdGVkDQojIA0KIyBqamJAbmV4b3IuY28udWssIFRodSBK dW4gMjUgMTg6NDI6MjggQlNUIDE5OTgNCiMNCiMgdGhhbmtzIHRvIEFydGh1 ciBTbm9rZSA8c25va2VAZXF1YWtlLmdlb2wudnQuZWR1PiBmb3INCiMgaWRl YXMgKyBkZXRlcm1pbmF0aW9uDQojDQojIHVzZTogX0NIQVJTRVQoSVNPLTg4 NTktMSlfIC9wYXRoL3RvL2ZpbHRlci84ODU5ZmlsdA0KIyBpbiB5b3VyICdk aXNwbGF5LWZpbHRlcicgc2V0dGluZw0KIw0KDQojDQojIE1hcCBkZWNpbWFs IGNvZGUgZm9yIGNoYXJhY3RlciB0byBpc28tODg1OS0xIHJlcHJlc2VudGF0 aW9uLg0KIw0KJW1hcCA9ICgNCgkiMTMzIiA9PiAiLi4uIiwNCgkiMTQ1IiA9 PiAiJyIsDQoJIjE0NiIgPT4gIiciLA0KCSIxNDciID0+ICJcIiIsDQoJIjE0 OCIgPT4gIlwiIiwNCgkiMTUwIiA9PiAiLSIsDQoJIjE1MSIgPT4gIi0iLA0K KTsNCndoaWxlKCBkZWZpbmVkKCAkY2hhciA9IGdldGMoKSApICkJew0KCWlm KCAkY2hhciBlcSAiXiIgKQl7DQoJCSRjaGFyID0gZ2V0YygpOw0KCQlpZigg ZGVmaW5lZCAkY2hhciApCXsNCgkJCSRudW0gPSAob3JkICRjaGFyKSAtIDY0 Ow0KCQkJaWYoIGV4aXN0cyggJG1hcHskbnVtfSApICkJew0KCQkJCXByaW50 ICRtYXB7JG51bX07DQoJCQl9IGVsc2Ugew0KCQkJCXByaW50ICJeJGNoYXIi Ow0KCQkJfQ0KCQl9IGVsc2Ugew0KCQkJcHJpbnQgIl4iOw0KCQl9DQoJfSBl bHNlIHsNCgkJcHJpbnQgJGNoYXI7DQoJfQ0KfQ0K ---559023410-758783491-898859935=:4359-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 26 Jun 1998 09:40:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA07007 for ; Fri, 26 Jun 1998 09:40:19 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA13066; Fri, 26 Jun 1998 09:40:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA01794; Fri, 26 Jun 1998 09:39:18 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA24758 for ; Fri, 26 Jun 1998 09:37:32 -0700 Received: from campus.cem.itesm.mx (campus.cem.itesm.mx [148.241.32.3]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA05409 for ; Fri, 26 Jun 1998 09:37:30 -0700 Received: from localhost (elavin@localhost) by campus.cem.itesm.mx (8.8.8/8.8.8) with SMTP id LAA14260 for ; Fri, 26 Jun 1998 11:36:40 -0500 (CDT) Message-Id: Date: Fri, 26 Jun 1998 11:36:39 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Eduardo Lavin 5558 To: Pine Discussion Forum Subject: Pine interface MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi! I want to write an application in C using the interface that Pine uses: control keys, move with arrows keys, highlighted text, frames, etc. How can I do that? What libraries I should use and where can I find them? Have a nice day! ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sat, 27 Jun 1998 14:35:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA28780 for ; Sat, 27 Jun 1998 14:35:38 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id OAA04211; Sat, 27 Jun 1998 14:35:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA21601; Sat, 27 Jun 1998 14:34:59 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA53732 for ; Sat, 27 Jun 1998 14:30:29 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA27919 for ; Sat, 27 Jun 1998 14:30:29 -0700 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with SMTP id OAA09157 for ; Sat, 27 Jun 1998 14:30:27 -0700 Received: from localhost by taxa.psyc.missouri.edu (SMI-8.6/SMI-SVR4) id QAA04092; Sat, 27 Jun 1998 16:28:31 -0500 Message-Id: Date: Sat, 27 Jun 1998 16:28:31 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Miller To: Pine Discussion Forum Subject: searching (with Select ';') across multiple folders MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello to all readers! I am not subscribed to this list, so if you have a suggestion, please send it to me directly (in addition to the list, if you like). I love PINE (v. 3.96 on Sun Solaris 2.6) and the Select feature (using the semi-colon) is really superb. My problem is that I often have to find a collection of messages that are in different folders. I end up having to reapply the same command in one folder after another. If only PINE could search across multiple folders simultaneously! Will future versions of PINE have this feature? If not, is there any software out there that can search a collection of mbox files and output another mbox containing all the messages that meet certain criteria? Thanks much! Mike Michael B. Miller, M.S., Ph.D., M.P.E. Department of Psychology 210 McAlester Hall University of Missouri--Columbia Columbia, MO 65211 Phone: (573) 882-5671 Fax: (573) 882-7710 e-mail: mbmiller@taxa.psyc.missouri.edu web: http://taxa.psyc.missouri.edu/~mbmiller/ ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 28 Jun 1998 09:06:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA07909 for ; Sun, 28 Jun 1998 09:06:53 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA21004; Sun, 28 Jun 1998 09:06:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA29859; Sun, 28 Jun 1998 08:52:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA62320 for ; Sun, 28 Jun 1998 08:50:56 -0700 Received: from walnut.asiainter.net (walnut.asiainter.net [202.84.207.5]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA16357 for ; Sun, 28 Jun 1998 08:50:54 -0700 Received: from localhost (ravi@localhost) by walnut.asiainter.net (8.8.8/8.8.6) with SMTP id XAA15102 for ; Sun, 28 Jun 1998 23:50:51 +0800 (HKT) Message-Id: Date: Sun, 28 Jun 1998 23:50:51 +0800 (HKT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ravi To: Pine Discussion Forum Subject: Unsubscribe pine-info MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: walnut.asiainter.net: ravi owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 01:28:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA16205 for ; Mon, 29 Jun 1998 01:28:00 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id BAA01887; Mon, 29 Jun 1998 01:27:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id BAA13788; Mon, 29 Jun 1998 01:26:33 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id BAA79334 for ; Mon, 29 Jun 1998 01:23:53 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA30762 for ; Mon, 29 Jun 1998 01:23:52 -0700 Received: from photon.sckcen.be (photon.sckcen.be [193.190.186.174]) by gluon.zag.si (8.8.6/8.8.6) with SMTP id KAA20556 for ; Mon, 29 Jun 1998 10:23:43 +0200 (CEST) Message-Id: Date: Mon, 29 Jun 1998 10:22:46 +0200 (Romance Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Suggestions for Pine 4.00 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: jank@gluon.zag.si X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ----- Jan Kalin, male, preferred languages: English, Slovene. See http://charm.zag.si/ for contact information ---------- Forwarded message ---------- Date: Thu, 18 Jun 1998 01:28:50 -0700 (PDT) From: UW Email Robot To: Jan Kalin Subject: Re: Suggestions for Pine 4.00 ACKNOWLEDGMENT Your message to the Pine development team has arrived safely in Seattle. As soon as possible, a member of the group will take a look at it. Unfortunately, because we now receive thousands of messages every week from the millions of Pine users around the world, we rarely have the time to answer back, so please don't expect a response (other than this one). If you were seeking information, as opposed to reporting a bug or making a suggestion, here are some alternative sources of assistance: The Pine Information Center: http://www.washington.edu/pine/ The Pine FTP archive: ftp://ftp.cac.washington.edu/pine/ The world-wide Pine newsgroup: comp.mail.pine Thanks for your interest in Pine! From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 01:44:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA17743 for ; Mon, 29 Jun 1998 01:44:07 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id BAA26531; Mon, 29 Jun 1998 01:44:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id BAA13991; Mon, 29 Jun 1998 01:42:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id BAA24802 for ; Mon, 29 Jun 1998 01:41:02 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA26357 for ; Mon, 29 Jun 1998 01:41:00 -0700 Received: from photon.sckcen.be (photon.sckcen.be [193.190.186.174]) by gluon.zag.si (8.8.6/8.8.6) with SMTP id KAA21201 for ; Mon, 29 Jun 1998 10:40:53 +0200 (CEST) Message-Id: Date: Mon, 29 Jun 1998 10:40:00 +0200 (Romance Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Suggestions for Pine 4.00 (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: jank@gluon.zag.si X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi to all from a fresh subscriber to the mailing list! First of all, apologies for the previous letter. It slipped through my fingers (I pressed ^X instead of ^C :) Maybe the keys for "Cancel" and "Send" should be a bit more distant from each other. But that was not what I wanted to write about. I'm delighted to have seen that a new version of Pine is due to be released (I won't ask when :) It is the only mail client I've found up to now that works perfectly in all the environments I work in, Silicon Graphics' Irix 6.2, WinNT, Win95 and Win3.11 (this is also one of the reasons I use vim for editing ASCII files on all these platforms). I was, however, dissapoined to hear that it will not yet have possibility of off-line operation and I believe, in these days of portable computers, that it would be a *major* plus for Pine. What I propose is actually simpler than off-line or disconnected operation. Let me explain what I've done and maybe this will clarify the idea. I have a portable PC with Windows NT and the imap server is a SGI Indy running Irix. Unfortunately, I only have access to Internet during the office hours and I don't have time in the office for the longer letters. Now, since Pine needs to connect to an imap server to compose a message, I've solved the problem by installing a free imap server for WinNT on my portable. Actually it's a complete mail server (Vintra), but it also understands imap. This means that now I can log on to the local server, compose a letter at home and postpone it, then, at the office and using a different .pinerc, log on to the real server and send the letter. I created some folders locally, where I keep copies of correspondence with people with whom I exchange longer letters, otherwise all the folders are on the server. What I believe is a possible and a very simple way of solving (temporarily at least) the lack of off-line or disconnected mode is to incorporate a 'dummy' imap server into Pine itself. If you couldn't log on to a real imap server, you'd be given a choice to use the dummy server and you could then compose and postpone messages but not mail them. The dummy server's INBOX would, of course, be empty (or possibly nonexistent), but at least you'd be able to see local folders. I *know* that you can achieve the same thing by just editing a file in a temporary directory and then reading it into a composition, but it would be more convenient to be able to work like I described. Cheers, Jan ----- Jan Kalin, male, preferred languages: English, Slovene. See http://charm.zag.si/ for contact information ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 01:55:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA17825 for ; Mon, 29 Jun 1998 01:55:55 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id BAA02176; Mon, 29 Jun 1998 01:55:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id BAA18232; Mon, 29 Jun 1998 01:54:33 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id BAA16480 for ; Mon, 29 Jun 1998 01:53:43 -0700 Received: from ashawna.eni.net (firewall-user@chastity.eni.net [206.135.49.2]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA31449 for ; Mon, 29 Jun 1998 01:53:42 -0700 Received: from localhost (drachen@localhost [127.0.0.1]) by ashawna.eni.net (8.8.7/8.8.7) with SMTP id BAA26063 for ; Mon, 29 Jun 1998 01:51:59 -0700 Message-Id: Date: Mon, 29 Jun 1998 01:51:56 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Vinnie Chassot To: Pine Discussion Forum Subject: Pine and Rhapsody In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Anyone know of anyone who has gotten pine to compile on rhapsody? I've got a friend who is trying to do just that and failing rather spectacularly. Ideas? Links? Small furry beasts from betelguese? Vinnie -- drachen@eni.net System Administrator Epoch Internet "It's more than just eye to eye learn the things I could never apply" -- Least Complicated ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 02:18:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA18388 for ; Mon, 29 Jun 1998 02:18:07 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id CAA26881; Mon, 29 Jun 1998 02:18:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id CAA01709; Mon, 29 Jun 1998 02:16:43 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id CAA24700 for ; Mon, 29 Jun 1998 02:15:48 -0700 Received: from ashawna.eni.net (firewall-user@chastity.eni.net [206.135.49.2]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA31993 for ; Mon, 29 Jun 1998 02:15:47 -0700 Received: from localhost (drachen@localhost [127.0.0.1]) by ashawna.eni.net (8.8.7/8.8.7) with SMTP id CAA28154; Mon, 29 Jun 1998 02:13:53 -0700 Message-Id: Date: Mon, 29 Jun 1998 02:13:52 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Vinnie Chassot To: Pine Discussion Forum Subject: Re: Suggestions for Pine 4.00 (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jan Kalin X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > First of all, apologies for the previous letter. It slipped through my > fingers (I pressed ^X instead of ^C :) Maybe the keys for "Cancel" and > "Send" should be a bit more distant from each other. But that was not what > I wanted to write about. I agree with this one! I've embarrased myself one to many times this way. > I *know* that you can achieve the same thing by just editing a file in a > temporary directory and then reading it into a composition, but it would be > more convenient to be able to work like I described. of course, the ultimate in convenience is just to have a machine you can log in remotely too -- and keep everything on it..but then I've always been a bit of a packrat :) Vinnie From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 02:41:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA19280 for ; Mon, 29 Jun 1998 02:41:58 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id CAA27148; Mon, 29 Jun 1998 02:41:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id CAA24333; Mon, 29 Jun 1998 02:40:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id CAA24792 for ; Mon, 29 Jun 1998 02:39:34 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA27971 for ; Mon, 29 Jun 1998 02:39:32 -0700 Received: from photon.sckcen.be (photon.sckcen.be [193.190.186.174]) by gluon.zag.si (8.8.6/8.8.6) with SMTP id LAA23305 for ; Mon, 29 Jun 1998 11:39:27 +0200 (CEST) Message-Id: Date: Mon, 29 Jun 1998 11:38:35 +0200 (Romance Daylight Time) Reply-To: Jan Kalin Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Re: Suggestions for Pine 4.00 (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: jank@gluon.zag.si X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 29 Jun 1998, Vinnie Chassot wrote: > > I *know* that you can achieve the same thing by just editing a file in a > > temporary directory and then reading it into a composition, but it > > would be more convenient to be able to work like I described. > > of course, the ultimate in convenience is just to have a machine you can > log in remotely too -- and keep everything on it..but then I've always > been a bit of a packrat :) Ah, yes, but that implies that you always have access to the network. In fact, the suggestion I sent only came about after I moved temporarily to Belgium. Since I work at nuclear research instutute, where the security is relatively high, I don't have access to my office during weekends and I don't have a phone in my room to hook up to the network. In fact, the *most* important reason why I chose imap and Pine is that I can keep my folders on the server and either run Pine on the server itself or on a PC (depending, for instance, whether I want to attach a file that's on the PC or on the server), and *always* have the same state of folders, no matter where I am. But, as I said, you need to have access to the network for that. Cheers, Jan BTW, what *is* the exotic machine you've mentioned? ----- Jan Kalin, male, preferred languages: English, Slovene. See http://charm.zag.si/ for contact information From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 02:59:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA19376 for ; Mon, 29 Jun 1998 02:59:22 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id CAA02852; Mon, 29 Jun 1998 02:59:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id CAA24597; Mon, 29 Jun 1998 02:58:01 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id CAA24590 for ; Mon, 29 Jun 1998 02:57:05 -0700 Received: from ashawna.eni.net (firewall-user@chastity.eni.net [206.135.49.2]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA10497 for ; Mon, 29 Jun 1998 02:57:05 -0700 Received: from localhost (drachen@localhost [127.0.0.1]) by ashawna.eni.net (8.8.7/8.8.7) with SMTP id CAA32073; Mon, 29 Jun 1998 02:55:16 -0700 Message-Id: Date: Mon, 29 Jun 1998 02:55:15 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Vinnie Chassot To: Pine Discussion Forum Subject: Re: Suggestions for Pine 4.00 (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jan Kalin X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > BTW, what *is* the exotic machine you've mentioned? which? My set up (which is just a linux box that is happily networked) or Rhapsody which is an Apple dev'd unix-type-os for macintosh that officially was stillborn, but rumours abound on it's future. Vinnie From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 04:59:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA21343 for ; Mon, 29 Jun 1998 04:59:58 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id EAA04336; Mon, 29 Jun 1998 04:59:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id EAA20074; Mon, 29 Jun 1998 04:57:45 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id EAA62448 for ; Mon, 29 Jun 1998 04:56:14 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA31532 for ; Mon, 29 Jun 1998 04:56:11 -0700 Received: from photon.sckcen.be (photon.sckcen.be [193.190.186.174]) by gluon.zag.si (8.8.6/8.8.6) with SMTP id NAA27448; Mon, 29 Jun 1998 13:56:01 +0200 (CEST) Message-Id: Date: Mon, 29 Jun 1998 13:55:11 +0200 (Romance Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Re: Suggestions for Pine 4.00 (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Vinnie Chassot X-Cc: Pine Discussion Forum X-X-Sender: jank@gluon.zag.si X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > > > BTW, what *is* the exotic machine you've mentioned? > > which? My set up (which is just a linux box that is happily networked) or > Rhapsody which is an Apple dev'd unix-type-os for macintosh that > officially was stillborn, but rumours abound on it's future. Yes, Rhapsody was what I asked about. ----- Jan Kalin, male, preferred languages: English, Slovene. See http://charm.zag.si/ for contact information From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 05:24:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA21929 for ; Mon, 29 Jun 1998 05:24:38 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id FAA04620; Mon, 29 Jun 1998 05:24:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id FAA20476; Mon, 29 Jun 1998 05:22:31 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id FAA63642 for ; Mon, 29 Jun 1998 05:21:37 -0700 Received: from ashawna.eni.net (firewall-user@chastity.eni.net [206.135.49.2]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA14827 for ; Mon, 29 Jun 1998 05:21:37 -0700 Received: from localhost (drachen@localhost [127.0.0.1]) by ashawna.eni.net (8.8.7/8.8.7) with SMTP id FAA05111; Mon, 29 Jun 1998 05:19:38 -0700 Message-Id: Date: Mon, 29 Jun 1998 05:19:38 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Vinnie Chassot To: Pine Discussion Forum Subject: Re: Suggestions for Pine 4.00 (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jan Kalin X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN oh. well, then rhapsody is just that -- a unix for Macintosh. Vinnie -- drachen@eni.net System Administrator Epoch Internet "It's more than just eye to eye learn the things I could never apply" -- Least Complicated On Mon, 29 Jun 1998, Jan Kalin wrote: > Date: Mon, 29 Jun 1998 13:55:11 +0200 (Romance Daylight Time) > From: Jan Kalin > To: Pine Discussion Forum > Subject: Re: Suggestions for Pine 4.00 (fwd) > > > > > > > BTW, what *is* the exotic machine you've mentioned? > > > > which? My set up (which is just a linux box that is happily networked) or > > Rhapsody which is an Apple dev'd unix-type-os for macintosh that > > officially was stillborn, but rumours abound on it's future. > > Yes, Rhapsody was what I asked about. > > ----- > Jan Kalin, male, preferred languages: English, Slovene. > See http://charm.zag.si/ for contact information > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 05:49:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA22283 for ; Mon, 29 Jun 1998 05:49:56 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id FAA04870; Mon, 29 Jun 1998 05:49:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id FAA20837; Mon, 29 Jun 1998 05:47:48 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id FAA62398 for ; Mon, 29 Jun 1998 05:46:46 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA28597 for ; Mon, 29 Jun 1998 05:46:44 -0700 Received: from fireball.control-risks.de (port242.koeln.ndh.net [195.94.92.242]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id OAA23374 for ; Mon, 29 Jun 1998 14:46:27 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id OAA26688; Mon, 29 Jun 1998 14:42:36 +0200 Message-Id: <19980629144234.A7808@control-risks.de> Date: Mon, 29 Jun 1998 14:42:34 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Suggestions for Pine 4.00 (fwd) In-Reply-To: ; from Vinnie Chassot on Mon, Jun 29, 1998 at 05:19:38AM -0700 References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Vinnie Chassot (drachen@eni.net): > oh. well, then rhapsody is just that -- a unix for Macintosh. *rotfl* Rhapsody is the code-name of Apple's upcoming operating system which will complement Mac OS by providing an advanced environment for servers and software development. While still running the huge library of existing Macintosh programs, Rhapsody also includes a breakthrough software development platform, code-named Yellow Box, for building new classes of reliable, media-rich and cross platform applications. Rhapsody will provide superior Java and Internet support, and is based on the tools used to create revolutionary technologies such as the World Wide Web. In short: MacOS sans bugs (hopefully...) plus a disembowelled NeXTstep. Could have been a killer 3 years ago. Doesn´t stand a bit of a chance against Linux in 1998 if you ask me. Robin -- Robin S. Socha M.A. Control Risks Germany Ltd. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 11:32:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA27509 for ; Mon, 29 Jun 1998 11:32:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id LAA07004; Mon, 29 Jun 1998 11:32:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA26481; Mon, 29 Jun 1998 11:31:21 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA49374 for ; Mon, 29 Jun 1998 11:30:11 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA15094 for ; Mon, 29 Jun 1998 11:30:10 -0700 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with SMTP id LAA06933 for ; Mon, 29 Jun 1998 11:30:08 -0700 Received: from localhost by taxa.psyc.missouri.edu (SMI-8.6/SMI-SVR4) id NAA05199; Mon, 29 Jun 1998 13:28:09 -0500 Message-Id: Date: Mon, 29 Jun 1998 13:28:09 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Miller To: Pine Discussion Forum Subject: Re: searching (with Select ';') across multiple folders In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: PINE-INFO list X-Cc: Edan Idzerda X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I decided that I would take PINE-INFO as daily digests, so I'll post a response to my query on searching across multiple folders using the select command. Great news--Pine 4.00 will include this facility. In the meantime, I did discover a way to get what I wanted using the Unix 'cat' command. I leave Pine, cd to my mail directory, then cat foldernames > newfolder This command will take a collection of folders and it will append them all together into one big folder called "newfolder". "foldernames" could be wildcard name like "sent*" or a series of filenames. The 'newfolder' might be huge, and that is one of the main drawbacks of this method. Then go back into pine, enter the "newfolder" folder, and do the select. It could be slow, but it works. Regards to all, Mike On Mon, 29 Jun 1998, Edan Idzerda wrote: > On Sat, 27 Jun 1998, Mike Miller wrote: > > > collection of messages that are in different folders. I end up having to > > reapply the same command in one folder after another. If only PINE could > > search across multiple folders simultaneously! > > Check out the Pine 4.00 preview, at > > http://www.washington.edu/pine/changes/4.00-preview/ > > It allegedly will this feature. > > > > Will future versions of PINE have this feature? If not, is there any > > software out there that can search a collection of mbox files and output > > another mbox containing all the messages that meet certain criteria? > > That sounds like an interesting program. I often just use 'grep' > and look for something unique. You could use glimpseindex on a > regular basis... > > But I guess Pine 4 will take care of it for you :) > > - edan > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 18:31:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA03008 for ; Mon, 29 Jun 1998 18:31:15 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id SAA17986; Mon, 29 Jun 1998 18:31:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id SAA23106; Mon, 29 Jun 1998 18:30:49 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id SAA24770 for ; Mon, 29 Jun 1998 18:29:40 -0700 Received: from cc344191-b.ewndsr1.nj.home.com (cc344191-b.ewndsr1.nj.home.com [24.2.84.238]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA10387 for ; Mon, 29 Jun 1998 18:29:38 -0700 Message-Id: <199806300129.VAA03471@ocalhost> Date: Mon, 29 Jun 98 21:29:32 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Pine and Rhapsody In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: Vinnie Chassot Date: Mon, 29 Jun 1998 01:51:56 -0700 (PDT) ID: > Anyone know of anyone who has gotten pine to compile on rhapsody? I've got > a friend who is trying to do just that and failing rather spectacularly. > Ideas? Links? Small furry beasts from betelguese? ftp://next-ftp.peak.org/pub/rhapsody/Applications/Unix/Mail/pine-3.96-I-b.tar.gz There's an Intel (binary) version of it... haven't heard of a PowerPC version TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 18:41:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA02011 for ; Mon, 29 Jun 1998 18:41:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id SAA24459; Mon, 29 Jun 1998 18:41:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id SAA01285; Mon, 29 Jun 1998 18:40:43 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id SAA50010 for ; Mon, 29 Jun 1998 18:39:48 -0700 Received: from cc344191-b.ewndsr1.nj.home.com (cc344191-b.ewndsr1.nj.home.com [24.2.84.238]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA03591 for ; Mon, 29 Jun 1998 18:39:44 -0700 Message-Id: <199806300139.VAA03802@ocalhost> Date: Mon, 29 Jun 98 21:39:41 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Rhapsody (was Re: Suggestions for Pine 4.00 (fwd)) In-Reply-To: <19980629144234.A7808@control-risks.de> References: Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: "Robin S. Socha" Date: Mon, 29 Jun 1998 14:42:34 +0200 ID: <19980629144234.A7808@control-risks.de> > In short: MacOS sans bugs (hopefully...) plus a disembowelled NeXTstep. Not really. MacOS with protected memory (ie won't crash/lockup like your Mac) and hopefully with less bugs. The NeXTStep part is difficult... they are keeping most of the Mac GUI which could have been vastly improved on by adding the NeXTStep elements. However, the kernel will be based on BSD4.4, which will actually be significantly better than what NeXTStep had. > Could have been a killer 3 years ago. It could have been extremely killer almost 10 years ago if Apple hadn't decided to cut its wrist by sending Steve Jobs packing.... NeXT, inc's OS together with greater resources would have been a big plus. > Doesn't stand a bit of a chance against Linux in 1998 if you ask me. Apple has killed Intel support (NeXTStep worked on HP/Sparc/NeXT hardware/and Intel) which turned me from optimistic to extremely pessimistic about its future. I'm not sure Linux is the biggest competitor. Anyone who has installed both will tell you that NeXTStep is 100% easier to setup and when you're done you have the beautiful GUI as opposed to a commandline interface trying to get X (blech) running. Anyway, we're way off topic here... there's a Rhapsody discussion list at http://www.omnigroup.com for those who want to know more TjL (NeXTStep user since 1991) From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 22:41:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA04688 for ; Mon, 29 Jun 1998 22:41:38 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id WAA21104; Mon, 29 Jun 1998 22:41:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id WAA06844; Mon, 29 Jun 1998 22:41:07 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id WAA85024 for ; Mon, 29 Jun 1998 22:39:59 -0700 Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id WAA24885 for ; Mon, 29 Jun 1998 22:39:58 -0700 Received: from sushi.uni-bonn.de (131.220.225.85,1600) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Tue, 30 Jun 98 07:40:00 MEZ Received: (from robin@localhost) by sushi.uni-bonn.de (8.8.8/8.8.8) id HAA19474; Tue, 30 Jun 1998 07:20:25 +0200 Message-Id: Date: 30 Jun 1998 07:20:22 +0200 Reply-To: r.socha@control-risks.de Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Rhapsody (was Re: Suggestions for Pine 4.00 (fwd)) In-Reply-To: Timothy J Luoma's message of "Mon, 29 Jun 98 21:39:41 -0400" References: <199806300139.VAA03802@ocalhost> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Timothy J Luoma writes: > "Robin S. Socha" >> Doesn't stand a bit of a chance against Linux in 1998 if you ask >> me. > Apple has killed Intel support (NeXTStep worked on HP/Sparc/NeXT > hardware/and Intel) which turned me from optimistic to extremely > pessimistic about its future. I'm not sure Linux is the biggest > competitor. Anyone who has installed both will tell you that > NeXTStep is 100% easier to setup and when you're done you have the > beautiful GUI as opposed to a commandline interface trying to get > X (blech) running. Well, it's not the Real Thing(tm), but it's damn close in look and feel if you ask me: . And yes, it's OT - reply-to set ;-) Later, Robin -- Robin S. Socha M.A. Control Risks Ltd. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 23:15:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA04730 for ; Mon, 29 Jun 1998 23:14:59 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA21549; Mon, 29 Jun 1998 23:14:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA19878; Mon, 29 Jun 1998 23:14:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA62400 for ; Mon, 29 Jun 1998 23:13:38 -0700 Received: from mail.info.gov.hk (mail.info.gov.hk [202.82.0.205]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA19837 for ; Mon, 29 Jun 1998 23:13:33 -0700 Received: (from kitty@localhost) by mail.info.gov.hk (8.7.1/8.6.6) id OAA09800; Tue, 30 Jun 1998 14:19:53 +0800 (HKT) Message-Id: Date: Tue, 30 Jun 1998 14:19:52 +0800 (HKT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Kitty Kwan To: Pine Discussion Forum Subject: bcc function in pine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Can any anyone kindly tell me if there is a "bcc" function in the pine program? It would certainly help us distribute mails in a much effective way. Thx. Kitty. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 23:30:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA05300 for ; Mon, 29 Jun 1998 23:30:48 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA28076; Mon, 29 Jun 1998 23:30:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA24597; Mon, 29 Jun 1998 23:30:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA49164 for ; Mon, 29 Jun 1998 23:29:17 -0700 Received: from mail.delta-ii.de (mail.delta-ii.de [195.180.229.162]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA09116 for ; Mon, 29 Jun 1998 23:29:16 -0700 Received: by mail.delta-ii.de (Smail3.2.0.101/mail.delta-ii.de) via Delta-II from lamia.delta-ii.de with esmtp for mxu3.u.washington.edu id m0yqtud-000aLRC; Tue, 30 Jun 1998 08:29:07 +0200 (MET DST) Received: (from norbert@localhost) by lamia.delta-ii.de (8.8.8/8.7.3) id IAA00373; Tue, 30 Jun 1998 08:29:00 +0200 Message-Id: Date: 30 Jun 1998 08:29:00 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Norbert Koch To: Pine Discussion Forum Subject: Re: bcc function in pine In-Reply-To: Kitty Kwan's message of "Tue, 30 Jun 1998 14:19:52 +0800 (HKT)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-Sender: norbert@delta-ii.de X-To: Kitty Kwan X-Cc: Pine Discussion Forum X-Attribution: viteno X-Organization: Delta Industrie Informatik GmbH X-URL: http://www.delta-ii.de X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Kitty Kwan writes: > Can any anyone kindly tell me if there is a "bcc" function in the > pine program? It would certainly help us distribute mails in a much > effective way. Thx. Short answer: Yes, I can tell you that there is :-) Longer one: In compose mode, while being in the header region, type ^R (rich header) and find the field :-) l8er, norbert. -- Norbert Koch, DELTA Industrie Informatik GmbH, Fellbach, Germany. YOW: Th' PINK SOCK... soaking... soaking... soaking... Th' PINK SOCK... washing... washing... washing... Th' PINK SOCK... rinsing... rinsing... rinsing... From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 29 Jun 1998 23:31:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA05157 for ; Mon, 29 Jun 1998 23:31:27 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA21810; Mon, 29 Jun 1998 23:31:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA20224; Mon, 29 Jun 1998 23:31:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA49282 for ; Mon, 29 Jun 1998 23:30:14 -0700 Received: from ashawna.eni.net (firewall-user@chastity.eni.net [206.135.49.2]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA09164 for ; Mon, 29 Jun 1998 23:30:13 -0700 Received: from localhost (drachen@localhost [127.0.0.1]) by ashawna.eni.net (8.8.7/8.8.7) with SMTP id XAA07135; Mon, 29 Jun 1998 23:28:19 -0700 Message-Id: Date: Mon, 29 Jun 1998 23:28:19 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Vinnie Chassot To: Pine Discussion Forum Subject: Re: bcc function in pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Kitty Kwan X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN when sending, arrow up into the header section and hit ctrl-R Vinnie -- drachen@eni.net System Administrator Epoch Internet "It's more than just eye to eye learn the things I could never apply" -- Least Complicated On Tue, 30 Jun 1998, Kitty Kwan wrote: > Date: Tue, 30 Jun 1998 14:19:52 +0800 (HKT) > From: Kitty Kwan > To: Pine Discussion Forum > Subject: bcc function in pine > > Can any anyone kindly tell me if there is a "bcc" function in the pine > program? It would certainly help us distribute mails in a much effective > way. Thx. > > Kitty. > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 01:03:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA31578 for ; Tue, 30 Jun 1998 01:03:44 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id BAA22881; Tue, 30 Jun 1998 01:03:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id BAA09082; Tue, 30 Jun 1998 01:03:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA62340 for ; Tue, 30 Jun 1998 00:52:28 -0700 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA23475 for ; Tue, 30 Jun 1998 00:52:27 -0700 Received: from ccz004.ust.hk ([143.89.102.4]:1421 "HELO CCZ004.ust.hk" ident: "NO-IDENT-SERVICE") by uxmail.ust.hk with SMTP id <626377-8784>; Tue, 30 Jun 1998 15:51:22 +0800 Message-Id: <000e01bda3fb$e3b12c80$0466598f@ust.hk> Date: Tue, 30 Jun 1998 15:51:28 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Patrick Leung" To: Pine Discussion Forum Subject: RE: bcc function in pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Cc: "Patrick Leung" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0518.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From message compose window, press "control r" while your cursor is in message header area, you will find the "bcc" header line. > -----Original Message----- > From: PINE-INFO-owner@u.washington.edu > [mailto:PINE-INFO-owner@u.washington.edu]On Behalf Of Kitty Kwan > Sent: Tuesday, June 30, 1998 2:20 PM > To: Pine Discussion Forum > Subject: bcc function in pine > > > Can any anyone kindly tell me if there is a "bcc" function in the pine > program? It would certainly help us distribute mails in a much effective > way. Thx. > > Kitty. > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 06:22:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA03664 for ; Tue, 30 Jun 1998 06:22:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id GAA03429; Tue, 30 Jun 1998 06:22:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id GAA14656; Tue, 30 Jun 1998 06:21:52 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id GAA32138 for ; Tue, 30 Jun 1998 06:20:01 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA23671 for ; Tue, 30 Jun 1998 06:20:00 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id GAA27070 for ; Tue, 30 Jun 1998 06:19:58 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id HAA67601 for ; Tue, 30 Jun 1998 07:19:56 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id HAA58170 for ; Tue, 30 Jun 1998 07:19:46 -0600 Message-Id: Date: Tue, 30 Jun 1998 07:19:42 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Binary MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Your editor's behaviour of wrapping long lines is especially annoying when trying to transfer files in 8bit binary mode....The wrapping will inevitably cause errors. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 07:47:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA14228 for ; Tue, 30 Jun 1998 07:47:42 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA28517; Tue, 30 Jun 1998 07:47:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA09825; Tue, 30 Jun 1998 07:47:04 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA54936 for ; Tue, 30 Jun 1998 07:45:44 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA18184 for ; Tue, 30 Jun 1998 07:45:44 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA04712 for ; Tue, 30 Jun 1998 07:45:42 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id IAA79912 for ; Tue, 30 Jun 1998 08:45:34 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id IAA56064 for ; Tue, 30 Jun 1998 08:45:24 -0600 Message-Id: Date: Tue, 30 Jun 1998 08:45:24 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 30 Jun 1998, Robin S. Socha wrote: > Quoting Raja BrewHaHa (brewhaha@freenet.edmonton.ab.ca): > > Your editor's behaviour of wrapping long lines is especially annoying when trying to transfer files in 8bit binary mode....The wrapping will inevitably cause errors. > > Tell me, Raja - what`s it like, talking to yourself in front of an entire > mailing list? I address it to a group of people, developers included. One copy of it comes back to me. I know who sent it, and it wasn't me. Maybe it's to me if I can answer it. If that bothers you, I'll go with "Pico's behaviour" when I know that there isn't a switch to turn this line-warping off, or when I know who has final say in how Pico behaves. As far as I can tell, no one has final say, or it'll be the same in Version 4.0. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 07:56:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA14284 for ; Tue, 30 Jun 1998 07:56:14 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id HAA04958; Tue, 30 Jun 1998 07:56:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA04947; Tue, 30 Jun 1998 07:55:38 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA57966 for ; Tue, 30 Jun 1998 07:54:38 -0700 Received: from cc344191-b.ewndsr1.nj.home.com (cc344191-b.ewndsr1.nj.home.com [24.2.84.238]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA18934 for ; Tue, 30 Jun 1998 07:54:37 -0700 Message-Id: <199806301454.KAA20915@ocalhost> Date: Tue, 30 Jun 98 10:54:36 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Your editor's behaviour of wrapping long lines is especially annoying when > trying to transfer files in 8bit binary mode....The wrapping will > inevitably cause errors. A) Why are you sending binaries via email rather than ftp? B) Why are you opening binaries in an editor rather than just attaching them (in the headers of PINE)? Wrapping *SHOULD* be done on the text of a message, but not the attachments. If you aren't attaching them, this is pilot error (ie you) If you are attaching them (using the Attchmnt: header) then it is a PINE error, but I've transferred binaries this way when I had to and there was no problem. TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 08:10:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA14524 for ; Tue, 30 Jun 1998 08:10:37 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id IAA05344; Tue, 30 Jun 1998 08:10:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA11056; Tue, 30 Jun 1998 08:09:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA25542 for ; Tue, 30 Jun 1998 08:07:55 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA17312 for ; Tue, 30 Jun 1998 08:07:54 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id JAA90745 for ; Tue, 30 Jun 1998 09:07:53 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id JAA29364 for ; Tue, 30 Jun 1998 09:07:42 -0600 Message-Id: Date: Tue, 30 Jun 1998 09:07:42 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: <199806301454.KAA20915@ocalhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 30 Jun 1998, Timothy J Luoma wrote: > > Your editor's behaviour of wrapping long lines is especially annoying when > > trying to transfer files in 8bit binary mode....The wrapping will > > inevitably cause errors. > > A) Why are you sending binaries via email rather than ftp? Because not everyone has filespace for me to SEND to. > B) Why are you opening binaries in an editor rather than just attaching them > (in the headers of PINE)? > > Wrapping *SHOULD* be done on the text of a message, but not the attachments. > If you aren't attaching them, this is pilot error (ie you) If I attach them, Pine puts them in Base 64 beyond my control, which isn't as universal as JustSend8, or 8bitmime, especially with old mailers. Attachments certainly require human knowledge of MIME, which is more common. Why bother going through the trouble of telling someone how to get and use a base64 tool, when an 8bit binary will do the trick 9 times out of 10. I've also received several (about 10) messages where the paragraphs were NOT wrapped. Pine wrapped them correctly in the viewer. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 08:26:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA14731 for ; Tue, 30 Jun 1998 08:26:58 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id IAA05792; Tue, 30 Jun 1998 08:26:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA01815; Tue, 30 Jun 1998 08:26:25 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA58098 for ; Tue, 30 Jun 1998 08:25:16 -0700 Received: from cc344191-b.ewndsr1.nj.home.com (cc344191-b.ewndsr1.nj.home.com [24.2.84.238]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA19107 for ; Tue, 30 Jun 1998 08:25:15 -0700 Message-Id: <199806301525.LAA22416@ocalhost> Date: Tue, 30 Jun 98 11:25:10 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > >A) Why are you sending binaries via email rather than ftp? > > Because not everyone has filespace for me to SEND to. Then put it on a webpage and let those who want it download it. You needn't make it publically available, make a directory like 'privatestuff' touch 'index.html' and put the file in that directory. Tell those who want it where to find it. Email is the wrong method of sending binaries no matter how man people use it. See 'man uuencode' for a good look at how inefficient it is (25 or 35% IIRC) > If I attach them, Pine puts them in Base 64 beyond my control, What kind of file is it? Have you tried (g)zip-ping it (depending on who you are sending it to) TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 09:08:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA15879 for ; Tue, 30 Jun 1998 09:08:07 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA00747; Tue, 30 Jun 1998 09:08:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA13751; Tue, 30 Jun 1998 09:05:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA21510 for ; Tue, 30 Jun 1998 09:04:23 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA05317 for ; Tue, 30 Jun 1998 09:04:22 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id MAA03537; Tue, 30 Jun 1998 12:04:18 -0400 (EDT) Received: from rock.me.mtu.edu (root@rock.me.mtu.edu [141.219.25.31]) by mtu.edu (8.8.8/8.8.8) with ESMTP id MAA08445; Tue, 30 Jun 1998 12:04:17 -0400 (EDT) Received: from hanky.me.mtu.edu (hanky.me.mtu.edu [141.219.25.130]) by rock.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with SMTP id MAA18682; Tue, 30 Jun 1998 12:04:09 -0400 (EDT) Message-Id: Date: Tue, 30 Jun 1998 12:03:55 -0400 (EDT) Reply-To: Edan Idzerda Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Raja BrewHaHa X-Cc: Pine Discussion Forum X-Sender: edan@hanky.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 30 Jun 1998, Raja BrewHaHa wrote: > > A) Why are you sending binaries via email rather than ftp? > Because not everyone has filespace for me to SEND to. Ah, but they have mail spool space? Ok, whatever--I don't think FTP is the answer either. > If I attach them, Pine puts them in Base 64 beyond my control, which isn't as universal as JustSend8, or 8bitmime, especially with old mailers. Attachments certainly require human knowledge of MIME, which is more common. I think it's odd that these people with old mailers have modern mail delivery programs, but again, not the point. It sounds like in your daily practice you don't have a problem with mailers stripping out your high bit from under you. You bring up a good point; it might be a nice feature if Pine gave you a choice of encodings. > Why bother going through the trouble of telling someone how to get and use a base64 tool, when an 8bit binary will do the trick 9 times out of 10. I believe that Pico has a limitation of 255 character lines. There is no motivation to extend that limitation, because it is a simple text editor. If you wish to include binary files directly in your messages, you'll need to use Pine's "alternate editor" facility. I personally use "enable-alternate-editor-implicitly" to invoke it automatically. - edan From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 09:31:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA16280 for ; Tue, 30 Jun 1998 09:31:00 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA01499; Tue, 30 Jun 1998 09:30:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA03866; Tue, 30 Jun 1998 09:30:00 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA12994 for ; Tue, 30 Jun 1998 09:28:52 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA26103 for ; Tue, 30 Jun 1998 09:28:51 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id KAA67790 for ; Tue, 30 Jun 1998 10:28:50 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id KAA49096 for ; Tue, 30 Jun 1998 10:28:40 -0600 Message-Id: Date: Tue, 30 Jun 1998 10:28:40 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: <199806301525.LAA22416@ocalhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 30 Jun 1998, Timothy J Luoma wrote: If your girlfriend asked you for a binary, would you make it public? > Email is the wrong method of sending binaries no matter how man people use > it. See 'man uuencode' for a good look at how inefficient it is (25 or 35% > IIRC) That's over 8bit. 8bit, MIME or not, is just as efficient as binary FTP, maybe a little bit more efficient, counting overhead--definitely more efficient if you count the overhead in the assumption that your recipient even HAS ftp access. They could be on FidoNet. > > If I attach them, Pine puts them in Base 64 beyond my control, > > What kind of file is it? Have you tried (g)zip-ping it (depending on who > you are sending it to) My version of Pine puts HTML attachments in Base 64. I don't see any place in the mimetypes file for changing that. Basically, my question is this: Why can't I make a binary into the main message instead of making it an attachment? Pine won't necessarily document the font correctly in that case, and who will care? On another viewpoint, there's these paragraphs that Pine warps into lines. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 09:50:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA17085 for ; Tue, 30 Jun 1998 09:50:40 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA08439; Tue, 30 Jun 1998 09:50:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA15303; Tue, 30 Jun 1998 09:50:03 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA14670 for ; Tue, 30 Jun 1998 09:49:04 -0700 Received: from fn1.freenet.edmonton.ab.ca (0@fn1.freenet.edmonton.ab.ca [198.161.206.8]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA19788 for ; Tue, 30 Jun 1998 09:49:03 -0700 Received: from fn2.freenet.edmonton.ab.ca (6782@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by fn1.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id KAA42595; Tue, 30 Jun 1998 10:49:01 -0600 Received: from localhost (brewhaha@localhost) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id KAA41052; Tue, 30 Jun 1998 10:48:51 -0600 Message-Id: Date: Tue, 30 Jun 1998 10:48:49 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Raja BrewHaHa To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Edan Idzerda X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 30 Jun 1998, Edan Idzerda wrote: > I think it's odd that these people with old mailers have modern mail > delivery programs, but again, not the point. It sounds like in > your daily practice you don't have a problem with mailers stripping > out your high bit from under you. Let's assume I'm talking FidoNet then. They adopted 8bit last decade. That makes them both modern and old. Then again, I might not be talking about FidoNet, since only DEC provides an 8bit (JustSend8) SMTP mailer "PATCH" in compliance with RFC 821. I've had no problems with the 8th bit being stripped from foreign language messages, even with intermediary SMTP. > I believe that Pico has a limitation of 255 character lines. There is > no motivation to extend that limitation, because it is a simple text > editor. If it remains a simple text editor and only SMTP compatible, Pine and Pico will eventually die and be supplanted by MH or something that does X.400. As far as that 255 character line length limitation, if I ever bother to adjust Pine myself the second thing I'll do is make that limit 2^16 or 2^32. 8bit software went out with the Apple ][. > If you wish to include binary files directly in your messages, you'll > need to use Pine's "alternate editor" facility. I personally use > "enable-alternate-editor-implicitly" to invoke it automatically. Well...if there's an editor which doesn't give command-line or low-level programming language facilities, and it's as convenient as Pine, I'll test it for stability and recommend it to my sysop. ...If everyone does that, then who would waste time developing Pico? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 11:19:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA18624 for ; Tue, 30 Jun 1998 11:19:27 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id LAA11603; Tue, 30 Jun 1998 11:19:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA08687; Tue, 30 Jun 1998 11:18:37 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA57900 for ; Tue, 30 Jun 1998 11:17:14 -0700 Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id LAA00217 for ; Tue, 30 Jun 1998 11:17:13 -0700 Received: from sushi.uni-bonn.de (131.220.225.99,3863) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Tue, 30 Jun 98 20:17:16 MEZ Received: (from robin@localhost) by sushi.uni-bonn.de (8.8.8/8.8.8) id TAA22613; Tue, 30 Jun 1998 19:13:16 +0200 Message-Id: Date: 30 Jun 1998 19:13:14 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: Raja BrewHaHa's message of "Tue, 30 Jun 1998 10:28:40 -0600 (MDT)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-To: Raja BrewHaHa X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Raja BrewHaHa writes: (blablabla) > Basically, my question is this: Why can't I make a binary into > the main message instead of making it an attachment? Pine won't > necessarily document the font correctly in that case, and who > will care? man uuencode -- Robin S. Socha M.A. Control Risks Ltd. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 12:11:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA19459 for ; Tue, 30 Jun 1998 12:11:16 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id MAA13168; Tue, 30 Jun 1998 12:11:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA17440; Tue, 30 Jun 1998 12:10:26 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA41036 for ; Tue, 30 Jun 1998 12:09:10 -0700 Received: from peace.netnation.com (dave@ns1.netnation.com [204.174.223.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA21672 for ; Tue, 30 Jun 1998 12:09:09 -0700 Received: from localhost (dave@localhost) by peace.netnation.com (8.8.8/8.8.8) with SMTP id MAA00588 for ; Tue, 30 Jun 1998 12:09:09 -0700 Message-Id: Date: Tue, 30 Jun 1998 12:09:09 -0700 (PDT) Reply-To: Dave Hirsch Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dave Hirsch To: Pine Discussion Forum Subject: loading messages into memory MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Dear Pine-info, I have several folders with +1000 messages in them. When I open the folder, it takes several minutes and about 60megs of memory to load. Is there anyway for pine to ONLY load the index screen (message header info) into memory? Once the message is selected for opening, only that message would be read into memory. PS Partitioning the folders into several smaller folders is not a feasible option for the nature of my system. best regards, ---------------------- Dave Hirsch support@netnation.com NetNation Tech Support ---------------------- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 12:26:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA19733 for ; Tue, 30 Jun 1998 12:26:35 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id MAA05911; Tue, 30 Jun 1998 12:26:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA18332; Tue, 30 Jun 1998 12:25:32 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA55868 for ; Tue, 30 Jun 1998 12:24:23 -0700 Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id MAA11717 for ; Tue, 30 Jun 1998 12:24:22 -0700 Received: from sushi.uni-bonn.de (131.220.225.111,4221) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Tue, 30 Jun 98 21:24:16 MEZ Received: (from robin@localhost) by sushi.uni-bonn.de (8.8.8/8.8.8) id UAA23130; Tue, 30 Jun 1998 20:36:57 +0200 Message-Id: Date: 30 Jun 1998 20:36:53 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: Raja BrewHaHa's message of "Tue, 30 Jun 1998 10:48:49 -0600 (MDT)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Raja BrewHaHa writes: > On Tue, 30 Jun 1998, Edan Idzerda wrote: Hello, Troll... (...) >> If you wish to include binary files directly in your messages, you'll >> need to use Pine's "alternate editor" facility. I personally use >> "enable-alternate-editor-implicitly" to invoke it automatically. > Well...if there's an editor which doesn't give command-line or > low-level programming language facilities, and it's as convenient > as Pine, I'll test it for stability and recommend it to my sysop. Dear Raja, thank you for playing. Really, it's ok. We got your message. Yes, we feel sorry for you. Let me assure you that it'll go away when you grow up. Really... > ....If everyone does that, then who would waste time developing > Pico? *sigh* *plonk* *sigh* Robin -- Robin S. Socha M.A. Control Risks Ltd. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 13:21:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA21263 for ; Tue, 30 Jun 1998 13:21:08 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA15200; Tue, 30 Jun 1998 13:21:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA03498; Tue, 30 Jun 1998 13:20:39 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA57532 for ; Tue, 30 Jun 1998 13:19:39 -0700 Received: from cc344191-b.ewndsr1.nj.home.com (cc344191-b.ewndsr1.nj.home.com [24.2.84.238]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA17490 for ; Tue, 30 Jun 1998 13:19:38 -0700 Message-Id: <199806302019.QAA01206@ocalhost> Date: Tue, 30 Jun 98 16:19:34 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > >I believe that Pico has a limitation of 255 character lines. There is > >no motivation to extend that limitation, because it is a simple text > >editor. > > If it remains a simple text editor and only SMTP compatible, Pine and Pico > will eventually die and be supplanted by MH or something that does X.400. There are other mailers out there already. PINE and PICO have the advantage of being simple and easy to use. If you want something more, there are other options for you rather than forcing all the PINE/PICO users in the world to put up with code bloat for a feature only you seem to care about. > As far as that 255 character line length limitation, if I ever bother to > adjust Pine myself the second thing I'll do is make that limit 2^16 or > 2^32. Go for it. That's the nice thing about having source. > Well...if there's an editor which doesn't give command-line or low-level > programming language facilities, and it's as convenient as Pine, I'll test > it for stability and recommend it to my sysop. pine/pico are stable and convenient because they do what they do in a very simple way. > My version of Pine puts HTML attachments in Base 64. Mine puts HTML files as text/plain. There ain't no way to put an attachment in the body of the message, other than uuencode. If your recipients really don't have access to the web and you really don't have a web page, and you really can't get around this using zip or gzip (which would make the attachment smaller anyway) then I think you are SOL as far as using PINE for this. TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 14:11:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA14779 for ; Tue, 30 Jun 1998 14:11:24 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id OAA16589; Tue, 30 Jun 1998 14:11:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA27922; Tue, 30 Jun 1998 14:10:15 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA25574 for ; Tue, 30 Jun 1998 14:09:04 -0700 Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id OAA01723 for ; Tue, 30 Jun 1998 14:09:03 -0700 Received: from sushi.uni-bonn.de (131.220.225.99,4374) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Tue, 30 Jun 98 23:09:04 MEZ Received: (from robin@localhost) by sushi.uni-bonn.de (8.8.8/8.8.8) id VAA23592; Tue, 30 Jun 1998 21:42:29 +0200 Message-Id: Date: 30 Jun 1998 21:42:28 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: loading messages into memory In-Reply-To: Dave Hirsch's message of "Tue, 30 Jun 1998 12:09:09 -0700 (PDT)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Dave Hirsch writes: > Dear Pine-info, I have several folders with +1000 messages in them. > When I open the folder, it takes several minutes and about 60megs of > memory to load. Is there anyway for pine to ONLY load the index screen > (message header info) into memory? Once the message is selected for > opening, only that message would be read into memory. Not that I know of. > PS Partitioning the folders into several smaller folders is not a > feasible option for the nature of my system. Could you elaborate on that? Robin -- Robin S. Socha M.A. Control Risks Ltd. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 15:20:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA21723 for ; Tue, 30 Jun 1998 15:20:52 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id PAA18636; Tue, 30 Jun 1998 15:20:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA00876; Tue, 30 Jun 1998 15:20:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id PAA57430 for ; Tue, 30 Jun 1998 15:19:03 -0700 Received: from orca.ucd.ie (orca.ucd.ie [137.43.4.16]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id PAA09544 for ; Tue, 30 Jun 1998 15:19:01 -0700 Received: (qmail 11474 invoked by uid 532); 30 Jun 1998 22:19:00 -0000 Message-Id: Date: Tue, 30 Jun 1998 23:19:00 +0100 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Finbarr O'Kane \(Sysadmin\)" To: Pine Discussion Forum Subject: Re: loading messages into memory In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Robin S. Socha" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 30 Jun 1998, Robin S. Socha wrote: {} * Dave Hirsch writes: {} {} > Dear Pine-info, I have several folders with +1000 messages in them. {} > When I open the folder, it takes several minutes and about 60megs of {} > memory to load. Is there anyway for pine to ONLY load the index screen {} > (message header info) into memory? Once the message is selected for {} > opening, only that message would be read into memory. {} {} Not that I know of. {} {} > PS Partitioning the folders into several smaller folders is not a {} > feasible option for the nature of my system. {} {} Could you elaborate on that? {} {} Robin {} {} -- {} Robin S. Socha M.A. {} Control Risks Ltd. {} excuse this newbie post to the list , but isnt that what , in principal IMAP does :) fin From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 19:07:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA16360 for ; Tue, 30 Jun 1998 19:07:18 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id TAA15204; Tue, 30 Jun 1998 19:07:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id TAA07522; Tue, 30 Jun 1998 19:06:52 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id TAA57434 for ; Tue, 30 Jun 1998 19:05:28 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA28943 for ; Tue, 30 Jun 1998 19:05:27 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id WAA23119; Tue, 30 Jun 1998 22:05:20 -0400 (EDT) Received: from rock.me.mtu.edu (root@rock.me.mtu.edu [141.219.25.31]) by mtu.edu (8.8.8/8.8.8) with ESMTP id WAA11345; Tue, 30 Jun 1998 22:05:19 -0400 (EDT) Received: from rock.me.mtu.edu (edan@rock.me.mtu.edu [141.219.25.31]) by rock.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with SMTP id WAA24252; Tue, 30 Jun 1998 22:05:16 -0400 (EDT) Message-Id: Date: Tue, 30 Jun 1998 22:05:15 -0400 (EDT) Reply-To: Edan Idzerda Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Raja BrewHaHa X-Cc: Pine Discussion Forum X-Sender: edan@rock.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > If it remains a simple text editor and only SMTP compatible, Pine and Pico will eventually die and be supplanted by MH or something that does X.400. As far as that 255 character line length limitation, if I ever bother to adjust Pine myself the second t hing I'll do is make that limit 2^16 or 2^32. Hah hah, sure, the people who use Pine with Pico are going to switch to MH. In general, there's no point to extending Pico's editing capabilities to enable binary files. It doesn't make it a "stupid" program; the Pine designers intend for you to use file attachments. For most of the internet, I think that's reasonable. Pico is a line editor, not a binary editor. Besides, you don't want to *edit* binary files, correct? You just don't want them to be encoded, which Pine enforces with an iron base64 fist. It could be more useful in your case, if Pine allowed you to select your encoding method. (It doesn't because sending 8bit files directly is generally thought of as a bad idea.) > Well...if there's an editor which doesn't give command-line or low-level programming language facilities, and it's as convenient as Pine, I'll test it for stability and recommend it to my sysop. > > ...If everyone does that, then who would waste time developing Pico? Not everyone uses a different editor. Changing NLINE and NSTRING in pico/estruct.h to support longer line lengths seems to be enough. I wouldn't recommend 2^32, though. Good luck with your peculiar situation. - edan From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 20:05:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA26482 for ; Tue, 30 Jun 1998 20:05:44 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id UAA15908; Tue, 30 Jun 1998 20:05:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA16211; Tue, 30 Jun 1998 20:05:18 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA36142 for ; Tue, 30 Jun 1998 20:04:27 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA18750 for ; Tue, 30 Jun 1998 20:04:26 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id WAA01034 for ; Tue, 30 Jun 1998 22:04:22 -0500 Message-Id: Date: Tue, 30 Jun 1998 22:04:22 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN What is your problem? Despite your complaint about pico breaking lines longer than 254 characters, you have no trouble annoying me by sending lines in text messages longer than 80 characters. The reason one doesn't send binaries in text messages is because mail transport is known to corrupt long lines, given that it was never designed not to. It is irrelevant if you can make it leave your own system intact. It is unlikely to arrive intact on the far end. >From: Raja BrewHaHa >Date: Tue, 30 Jun 1998 09:07:42 -0600 (MDT) >On Tue, 30 Jun 1998, Timothy J Luoma wrote: >>A) Why are you sending binaries via email rather than ftp? >Because not everyone has filespace for me to SEND to. If they don't have space for it, what the hell do you expect them to do with it once they receive it? >If I attach them, Pine puts them in Base 64 beyond my control, which isn't as >universal as JustSend8, or 8bitmime, especially with old mailers. Attachments >certainly require human knowledge of MIME, which is more common. The pine developers feel that Base 64 encoding tends to survive mail transport better than other methods. I'll take their word for it, unless you intend to make a supportable argument to the contrary. uuencode is extremely common, and is the tool to deal with Base 64. >Why bother going through the trouble of telling someone how to get and use a >base64 tool, when an 8bit binary will do the trick 9 times out of 10. So that the attachment arrives intact. That's a good reason. >I've also received several (about 10) messages where the paragraphs were NOT >wrapped. Pine wrapped them correctly in the viewer. Bully for you. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 21:06:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA26915 for ; Tue, 30 Jun 1998 21:06:38 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id VAA24808; Tue, 30 Jun 1998 21:06:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id VAA28769; Tue, 30 Jun 1998 21:05:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id VAA69230 for ; Tue, 30 Jun 1998 21:04:52 -0700 Received: from md2.vsnl.net.in (md2.vsnl.net.in [202.54.6.20]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA03701 for ; Tue, 30 Jun 1998 21:04:48 -0700 Received: from localhost (slfibres@localhost) by md2.vsnl.net.in (8.8.8/8.8.8) with SMTP id JAA04950; Wed, 1 Jul 1998 09:43:44 +0530 (IST) Message-Id: Date: Wed, 1 Jul 1998 09:43:44 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "M/S. SRI LAKSHMI FIBRES" To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Raja BrewHaHa X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN can anybody guide me to download files directly to my computpr instead of my ISprovider? what software I should have to do so ? pl. help Thanks/K.V.Sivaraman/India From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 21:08:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA27873 for ; Tue, 30 Jun 1998 21:08:06 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id VAA16758; Tue, 30 Jun 1998 21:08:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id VAA05279; Tue, 30 Jun 1998 21:06:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id VAA15406 for ; Tue, 30 Jun 1998 21:06:09 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA03786 for ; Tue, 30 Jun 1998 21:06:08 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id AAA01860; Wed, 1 Jul 1998 00:06:04 -0400 (EDT) Received: from rock.me.mtu.edu (root@rock.me.mtu.edu [141.219.25.31]) by mtu.edu (8.8.8/8.8.8) with ESMTP id AAA18807; Wed, 1 Jul 1998 00:06:04 -0400 (EDT) Received: from rock.me.mtu.edu (edan@rock.me.mtu.edu [141.219.25.31]) by rock.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with SMTP id AAA24701; Wed, 1 Jul 1998 00:06:00 -0400 (EDT) Message-Id: Date: Wed, 1 Jul 1998 00:05:59 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Sender: edan@rock.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 30 Jun 1998, Adam H. Kerman wrote: > uuencode is extremely common, and is the tool to deal with Base 64. Call me a chatterbox today, but uudecode deals with the "uuencode" format--not base64. Dealing with base64 when you don't have a MIME-compliant mail reader can be a pain. - edan From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 22:33:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA28500 for ; Tue, 30 Jun 1998 22:33:07 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id WAA17760; Tue, 30 Jun 1998 22:33:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id WAA19338; Tue, 30 Jun 1998 22:32:42 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id WAA60720 for ; Tue, 30 Jun 1998 22:31:46 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA21574 for ; Tue, 30 Jun 1998 22:31:45 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id AAA02956 for ; Wed, 1 Jul 1998 00:31:41 -0500 Message-Id: Date: Wed, 1 Jul 1998 00:31:41 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Edan Idzerda >Date: Wed, 1 Jul 1998 00:05:59 -0400 (EDT) >On Tue, 30 Jun 1998, Adam H. Kerman wrote: >>uuencode is extremely common, and is the tool to deal with Base 64. >Call me a chatterbox today, but uudecode deals with the "uuencode" >format--not base64. POSIX-compliant uuencode -m encodes base64. The formats are rather similar. Today, aren't all uuencodes using base64? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 23:26:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA28591 for ; Tue, 30 Jun 1998 23:26:40 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA26444; Tue, 30 Jun 1998 23:26:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA13192; Tue, 30 Jun 1998 23:25:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA60466 for ; Tue, 30 Jun 1998 23:23:56 -0700 Received: from bay2.bjt.net (root@mailhost.bjt.net [209.237.0.15]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA24360 for ; Tue, 30 Jun 1998 23:23:55 -0700 Received: from bay1.bjt.net (kstevens@bay1.bjt.net [209.237.0.8]) by bay2.bjt.net (8.8.5/8.8.5) with ESMTP id XAA09050; Tue, 30 Jun 1998 23:22:45 -0700 Received: from localhost (kstevens@localhost) by bay1.bjt.net (8.7.5/8.7.5) with SMTP id XAA25092; Tue, 30 Jun 1998 23:22:45 -0700 Message-Id: Date: Tue, 30 Jun 1998 23:22:45 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Stevens To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Edan Idzerda X-Cc: Pine Discussion Forum X-Authentication-Warning: bay1.bjt.net: kstevens owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Do you know of any tool that can deal with base-64 format? Ken On Wed, 1 Jul 1998, Edan Idzerda wrote: > On Tue, 30 Jun 1998, Adam H. Kerman wrote: > > > uuencode is extremely common, and is the tool to deal with Base 64. > > Call me a chatterbox today, but uudecode deals with the "uuencode" > format--not base64. Dealing with base64 when you don't have a > MIME-compliant mail reader can be a pain. > > - edan > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 23:42:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA29068 for ; Tue, 30 Jun 1998 23:42:47 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA26610; Tue, 30 Jun 1998 23:42:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA08616; Tue, 30 Jun 1998 23:41:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA74284 for ; Tue, 30 Jun 1998 23:40:30 -0700 Received: from chinet.chinet.com (ahk@chinet.chinet.com [206.158.147.18]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA04624 for ; Tue, 30 Jun 1998 23:40:29 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.8.7/8.8.7) with SMTP id BAA03774 for ; Wed, 1 Jul 1998 01:40:26 -0500 Message-Id: Date: Wed, 1 Jul 1998 01:40:25 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Ken Stevens >Date: Tue, 30 Jun 1998 23:22:45 -0700 (PDT) >Do you know of any tool that can deal with base-64 format? uuencode/uudecode -m on Linux; you may need to invoke a different option on your unix. And, of course, pine. Attachments encoded in base64 are automatically decoded. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 23:43:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA29126 for ; Tue, 30 Jun 1998 23:43:45 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA26619; Tue, 30 Jun 1998 23:43:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA21093; Tue, 30 Jun 1998 23:42:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA57458 for ; Tue, 30 Jun 1998 23:40:39 -0700 Received: from lamia.delta-ii.de (norbert@apollonius.delta-ii.de [195.180.229.163]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA25103 for ; Tue, 30 Jun 1998 23:40:37 -0700 Received: (from norbert@localhost) by lamia.delta-ii.de (8.8.8/8.8.8) id IAA05508; Wed, 1 Jul 1998 08:40:25 +0200 Message-Id: Date: 01 Jul 1998 08:40:25 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Norbert Koch To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: Ken Stevens's message of "Tue, 30 Jun 1998 23:22:45 -0700 (PDT)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-Sender: norbert@lamia.delta-ii.de X-To: Ken Stevens X-Cc: Pine Discussion Forum X-Attribution: viteno X-Organization: Delta Industrie Informatik GmbH X-URL: http://www.delta-ii.de X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Ken Stevens writes: > Do you know of any tool that can deal with base-64 format? Ken Hmm, which platform? What do you want to do? Pine can handle it (that's what the discussion is about, partly, I guess). XEmacs :-) mmencode (UNIX) I think, Netscape is also able to handle it. That is: All of these tools should be able to extract the data contained in base64 encoded text. L8er, norbert. -- Norbert Koch, DELTA Industrie Informatik GmbH, Fellbach, Germany. YOW: A wide-eyed, innocent UNICORN, poised delicately in a MEADOW filled with LILACS, LOLLIPOPS & small CHILDREN at the HUSH of twilight?? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 30 Jun 1998 23:44:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA26804 for ; Tue, 30 Jun 1998 23:44:11 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA26622; Tue, 30 Jun 1998 23:44:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA08713; Tue, 30 Jun 1998 23:42:55 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA36204 for ; Tue, 30 Jun 1998 23:41:21 -0700 Received: from mailhost2.u.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA04660 for ; Tue, 30 Jun 1998 23:41:21 -0700 Received: from D-140-142-189-195.dhcp.washington.edu (D-140-142-189-195.dhcp.washington.edu [140.142.189.195]) by mailhost2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with SMTP id XAA15944 for ; Tue, 30 Jun 1998 23:41:20 -0700 Message-Id: Date: Tue, 30 Jun 1998 23:43:39 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: Re: Binary In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset = US-ASCII X-To: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Raja BrewHaHa > > If I attach them, Pine puts them in Base 64 beyond my control, which > isn't as universal as JustSend8, or 8bitmime, especially with old > mailers. Attachments certainly require human knowledge of MIME, which > is more common. I'm not quite sure that the "is more common" refers to, but Base 64 is in fact the principal encoding scheme of MIME. As others have mentioned, there are good reasons for encoding attachments --if you care about them arriving intact-- but it is also true that if you turn on Pine's feature to enable esmtp negotiation *and* you have an ESMTP capable MTA that supports 8BITMIME, then Pine will negotiate the use of 8BITMIME rather than Base64 MIME. -teg