eb@LUCID.COM (Eric Benson) (10/01/88)
I've been using rmail for about three years now, having used ZMail and MM previously. For the most part I've been happy with it, but there are a few things I find annoying. These might be taken as suggestions for Version 19. I would like to see something analogous to the ZMail "Examine" command, to permit reading an rmail file read-only. The behavior I would like occurs when the file is not writable by me; I would like to be able to specify that behavior even if the file is writable. I would prefer to have each "mail" or "reply" command create a new *mail* buffer, even if a buffer already exists and the message has been sent. It's easy enough to kill buffers and it's nice to be able to look at messages previously sent during the same session. It's also convenient to be able to respond quickly to a message while in the middle of composing a longer message. I know this is a simple hack; I put it in my init file. I think it is useful enough to be the default. Messages are marked "answered" as soom as the "reply" command is used. This is misleading if the reply is never sent. It would be preferable wait until the reply is sent before marking the message as answered. It might be useful to have another attribute to indicate that a reply is being composed.
rlk@THINK.COM (Robert L. Krawitz) (10/01/88)
Date: Fri, 30 Sep 88 12:33:30 pdt From: Eric Benson <eb@lucid.com> I would like to see something analogous to the ZMail "Examine" command, to permit reading an rmail file read-only. The behavior I would like occurs when the file is not writable by me; I would like to be able to specify that behavior even if the file is writable. This is something I never quite got around to doing... I would prefer to have each "mail" or "reply" command create a new *mail* buffer, even if a buffer already exists and the message has been sent. It's easy enough to kill buffers and it's nice to be able to look at messages previously sent during the same session. It's also convenient to be able to respond quickly to a message while in the middle of composing a longer message. I know this is a simple hack; I put it in my init file. I think it is useful enough to be the default. We have a local hack to do this... Messages are marked "answered" as soom as the "reply" command is used. This is misleading if the reply is never sent. It would be preferable wait until the reply is sent before marking the message as answered. It might be useful to have another attribute to indicate that a reply is being composed. This is a problem; it's difficult to fix this for reasons I'd explain if it were not for the fact that today's been too much of a mess... harvard >>>>>> | Robert Krawitz <rlk@think.com> bloom-beacon > |think!rlk topaz >>>>>>>> . rlk@a.HASA.disorg