Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!sparkyfs!hercules!fernwood!portal!atari!imagen!sun!argv From: argv@turnpike.Eng.Sun.COM (Dan Heller) Newsgroups: comp.mail.mush Subject: Re: mush bugs Message-ID: <143274@sun.Eng.Sun.COM> Date: 2 Oct 90 22:54:32 GMT References: <1990Oct2.170734.17606@cbnewsu.att.com> Sender: news@sun.Eng.Sun.COM Organization: O'Reilly && Associates Lines: 84 In article <1990Oct2.170734.17606@cbnewsu.att.com> mark@cbnewsu.att.com (Mark Horton) writes: > The "alternates" feature does not seem to work. If I say ":alternates" > in curses mode it lists them from my .mushrc correctly, but when I reply > all it still sends a copy to me. You're not specific enough. It does work, you're just not setting the right alternates values :-). Let me give an example of what I do for myself (my .mushrc). alts * !cory.berkeley.edu!dheller !ora.ora.com!danh !comp-sources-x The * implies "argv everywhere". That is, if I reply to a message and it sees "argv" as a user name, it gets removed no matter where it's going. The next case: !cory.berkeley.edu!dheller indicates that I have an account on cory.berkeley.edu with the login of dheller. So, no matter what the path is, if it *ends up* at that host and machine, then remove it from the list. The leading ! implies that any path up to cory is irrelevant. The same thins is true for and ora.ora.com!danh. In the last case, !comp-sources-x means any mail addressed to that user no matter what the path... Since I am the moderator for comp.sources.x, people that mail to me will have that address, not "argv". I can reply to them and not send myself a copy of the message. In patch #3 that will soon be available, you will be able to specify the @-style format such as: dheller@cory.berkeley.edu This is a "convenience" for the user -- it'll just internally use the bang-formats discussed above. I think bart and I are also planning on supporting *user to imply the same thing as !user now... > When using mushtool, when I press "done" it closes the window down OK, > but it moves the current message to the last preserved message, marking > it read. I have to manually preserve it each time I open the window. There has always been a bunch of bantering about back and forth on what to do about "preserve". I'll let bart answer this one. I agree that its an inconvenience.... all things considered, this is not a trivial problem to solve. > When replying, if I forget to press "send" (or miss it) and then press > "close", the reply window goes away and so does the reply button! You can still hit the button, can't you? That's just there to bring up the compose window -- not necessarily to invoke a new composition. This should have the same effect that your workaround provides: > found that by getting a menu on any random message and selecting "reply" > I can get it back (although it won't reply) but there's no visible icon > or any other normal way to get it back. If the button is also disabled, then we have a problem. > General gripe: in curses mode, the interface looks and feels very much > like rn, Really?! Ugh, then there *IS* a bug! :-) (seriously, that was never intentional -- it could be just the way you've set things up). > In particular, when I'm paging through a long message and > have a "more" at the bottom, I would like to be able to issue commands > like "n" or "r" without having to "q" first. I can do this in mushtool > but not in curses mode. The disadvantage to "rn" is that you have to use *their* pager. I hate that and I think most will agree that it is better for you to specify your own pager (more, less, pg, etc..) than to not be given a choice. Thus, you are never going to have the capability you are asking for here. *However* there is something almost as good. When you are paging the message and the pager is done (you've hit 'q'), and you are given a "...continue..." prompt, you *can* issue a new curses mode command and you do not have to return to the toplevel menu. > Sure would be nice if, in curses mode at the main message menu, j and k > would work at the bottom and top of the screen ala vi. Currently I > have to z or Z- which is inconvenient (and inconsistent from vi.) This is true, but vi is tuned to take full advantage of the capabilties of the screen. Mush just uses those curses(3X) commands that are most portable across all versions of unix (that we've found). We cannot do reverse scrolling reliably (which would give you your desired effect) and be assured that it works everywhere. -- dan ---------------------------------------------------- O'Reilly && Associates argv@sun.com / argv@ora.com Opinions expressed reflect those of the author only.