Subject: Bug? #pine.20556#, ~/dead.letter, pico -k

From: Hussam Husain Qasem <[email-masked]>
Date: Thu, 27 Mar 1997 13:17:18 -0500

Hi!

I found couple of things that really annoies me about pine.

I like the idea of "dead.letter" and "dead.article", but I
don't like their names or where they are placed, so I was
wondering if you can set a global $VARIABLE that Pine will
read the file name from (with full path). ie: 
setenv DEADLETTER $HOME/doc/.dead.letter
or something like that. I've read the enitre pinerc and I
couldn't find anything.

Also while composing a message once (and having umask 022),
I found that Pine created a tmp file in ~/#pine.20556# and
it was world-readable, so anybody could've read my message
while composing it! :(
Was that a bug? I couldn't re-produce the problem, and I
don't remember on what architecture it was.

Also, I found the `-k' option for `pico' to be extremely
useful. Can I apply this to pine? Is there something I have
to set?

I would really appreciate if you can reply back by e-mail as
well.

Thanks a lot,

Hussam

---

From: Robin S Socha <[email-masked]>
Date: Thu, 27 Mar 1997 22:01:28 +0100 (CET)

-----BEGIN PGP SIGNED MESSAGE-----

On Thu, 27 Mar 1997, Hussam Husain Qasem wrote:

  >I like the idea of "dead.letter" and "dead.article", but I don't like
  >their names or where they are placed, so I was wondering if you can set a
  >global $VARIABLE that Pine will read the file name from (with full path).
  >ie: setenv DEADLETTER $HOME/doc/.dead.letter or something like that. I've
  >read the enitre pinerc and I couldn't find anything.

Since noone has uttered this request before, you might UTSL. From a quick
glance at the source, it looks like a pretty straight-forward thing.

  >Also while composing a message once (and having umask 022), I found that
  >Pine created a tmp file in ~/#pine.20556# and it was world-readable, so
  >anybody could've read my message while composing it! :( Was that a bug? I
  >couldn't re-produce the problem, and I don't remember on what
  >architecture it was.

We've had this "problem" before and didn't come up with a solution within
pine. You might alter umask in your .<shell>rc, you might alter permissions
on your dirs, or (probably the easiest solution) use another editor.
Pico isn't _the_ editor, anyway.

  >Also, I found the `-k' option for `pico' to be extremely useful. Can I
  >apply this to pine? Is there something I have to set?

I don't have -k for pico:

Syntax
       pico [-f] [+n] [-nn] [-t] [-v] [-w] [-z] [file]
       
What does it do?

Later,
Robin
- -----
Robin S. Socha,
Political Science Dept., Bonn University, Bonn
Key fingerprint = 7F F2 84 73 CF E9 2C 92  F6 6E F9 B4 8F FE AC 1E
To get my pgp public key, send an e-mail with the subject "get pgp-key"

GMC d++ s+:+ a- C++ UL++$>+++$ P+>++$ E>+ W- N+ o@ w--- M-- PS--- PE+++ Y+
PGP++>+++ t+() 5-- tv++(+) b+++ DI++ D+(++) G++>+++ e++>+++ h r++>+++ y+**

---

From: "Steve \"Stevers!\" Coile" <[email-masked]>
Date: Thu, 27 Mar 1997 16:34:12 -0500 (EST)

On Thu, 27 Mar 1997, Robin S Socha wrote:
[...]

>From "man pico" (from Pine 3.95 distribution):

       -k     Causes "Cut Text" command to remove characters from
              the  cursor  position to the end of the line rather
              than remove the entire line.

--
    Steve Coile           P a t r i o t  N e t      Systems Engineering
 [email-masked]      Patriot Computer Group        (703) 277-7737

---

From: Hussam Husain Qasem <[email-masked]>
Date: Sun, 30 Mar 1997 16:15:51 -0500 (EST)

> glance at the source, it looks like a pretty straight-forward thing.

You're right, but unfortunately, that'll affect other users.
Or I might do it specificly for me, "hqasem" == $USER then
put it wherever I want to! :)

> Pico isn't _the_ editor, anyway.

I prefer to keep my umask as 022, but would like to know
more about the problem, and when does it occur.

>        pico [-f] [+n] [-nn] [-t] [-v] [-w] [-z] [file]

Someone had followed this message with an answer, but here
it is again:
     -k   Causes "Cut Text" command to remove characters from the
          cursor  position  to  the  end  of the line rather than
          remove the entire line.

In fact, I found it in pine! I needed to add
"compose-cut-from-cursor" to my feature-list.

Thanks a lot!

Hussam

---

From: Robin S Socha <[email-masked]>
Date: Sun, 30 Mar 1997 23:50:46 +0200 (CEST)

-----BEGIN PGP SIGNED MESSAGE-----

On Sun, 30 Mar 1997, Hussam Husain Qasem wrote:
  >> On Thu, 27 Mar 1997, Hussam Husain Qasem wrote [excerpt]:

  >You're right, but unfortunately, that'll affect other users. Or I might
  >do it specificly for me, "hqasem" == $USER then put it wherever I want
  >to! :)

Get the source, hack it and put pine in ~/bin. Or do I get sth wrong?

Later,
Robin

- -----
Robin S. Socha,