Subject: Another modest modification to Pine...

From: "Michael C. Newell" <[email-masked]>
Date: Mon, 18 Apr 1994 14:45:53 -0400 (EDT)

One thing that is a bit of a problem I've noticed is the "Send" key ("^X") 
is RIGHT NEXT to the "Cancel" key ("^C").  Some people (well, at least 
me!) get into the habit of typing fast, and sometimes miss a key..  Then 
you type "Y" automatically and *POOF* there goes your message...

Perhaps using another key to initiate send might be nice??

Thanks,

Mike

+--------------------------------------+------------------------------------+
|Mike Newell                           | The opinions expressed herein are  |
|NASA Science Internet Network Systems | my own, and do not necessarily     |
[email-masked]                | reflect those of the NSI program,  |
|+1-202-434-8954                       | NASA, my employer, or anyone else. |
+--------------------------------------+------------------------------------+

---

From: David L Miller <[email-masked]>
Date: Mon, 18 Apr 1994 13:00:13 -0700 (PDT)

This has been pointed out a few times, but unfortunately it is far too 
late to make that kind of fundamental change in the user interface.  We 
already got burned pretty bad on what we thought was a pretty minor 
change for the prYnt command...

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

---

From: Omi Chandiramani <[email-masked]>
Date: Mon, 18 Apr 1994 16:03:19 -0400 (EDT)

> Perhaps using another key to initiate send might be nice??

	I used to have the same problem a few months ago and then I just
got used to pressing Return after pressing ^X. If I had successfully
pressed X then the message would be sent, the default for Send being to
send the message, and if i had pressed C by mistake I'd be back into
compose mode, the default action for Cancel being NOT to cancel the
message. 

Pico without ^X, would be like Emacs without ^X^C; it just wouldnt be the 
same again! 

Omi Chandiramani
[email-masked]

---

From: David L Miller <[email-masked]>
Date: Mon, 18 Apr 1994 13:09:43 -0700 (PDT)

Mike,

That is another user-support nightmare we don't want to get any where near. 
If anything programmable definitions are even more of a support nightmare
than a static change... 

Thanks for the followup!

--DLM

On Mon, 18 Apr 1994, Michael C. Newell wrote:

> I figured as much... However, would it be possible (well, probable...) 
> to include programmable key definitions in some future release?  That way 
> a user with exceedingly fat fingers (like me) could customize the 
> interface around things like this while leaving the vanilla interface alone.
> 
> Thanks for a great product!
> 
> Mike
> 
> On Mon, 18 Apr 1994, David L Miller wrote:
> 
> >

---

From: "Michael C. Newell" <[email-masked]>
Date: Mon, 18 Apr 1994 16:00:26 -0400 (EDT)

Mike

---

From: Gene Trantham <[email-masked]>
Date: Mon, 18 Apr 1994 15:14:05 -0500 (CDT)

On Mon, 18 Apr 1994, Michael C. Newell wrote:
> is RIGHT NEXT to the "Cancel" key ("^C").  

> Perhaps using another key to initiate send might be nice??

Like, maybe, ^S (S for "send")?  Be careful when you start mucking about 
with key bindings like that.  We had a problem on our campus with new 
unix (and pine) users hitting ^S, and subsequently complaining that their 
sessions just "locked up".  ^S, you may recall, is normally the XOFF 
character, which is _SUPPOSED_ to "lock up" the terminal.  And ^Q is 
bound to XON....... Most of the rest of the function keys already have 
bindings within pine.  What would you suggest they move it to?  Or 
perhaps you should consider starting pine with the switch (I forget 
which one it is) that maps essential functions to F keys.

--
Gene Trantham
University of Arkansas

---

From: Richard Lee <[email-masked]>
Date: Mon, 18 Apr 1994 16:08:42 -0500 (CDT)

> Perhaps using another key to initiate send might be nice??

	Oh, let's not change those keystrokes too often.  Now people are 
used to ^X as send.  If they change it now, that will confuse everyone 
else and we'll have to get used to something else (e,g, ^S, which will 
lock up some folks' keyboards, or ^O (for get that *O*ut of here), which 
some people will think should postpone the message) etc.

--

Dr. Richard Lee                         [email-masked]
Department of Philosophy Old Main 318   [email-masked]
University of Arkansas                  phone: 501-575-5826
Fayetteville, AR 72701