Path: utzoo!attcan!uunet!snorkelwacker!apple!rutgers!att!cbnewsu!mark From: mark@cbnewsu.att.com (Mark Horton) Newsgroups: comp.mail.mush Subject: Re: mush bugs Summary: so that's the secret! Message-ID: <1990Oct4.212140.11006@cbnewsu.att.com> Date: 4 Oct 90 21:21:40 GMT References: <1990Oct2.170734.17606@cbnewsu.att.com> <143274@sun.Eng.Sun.COM> Organization: AT&T Bell Laboratories Lines: 66 In article <143274@sun.Eng.Sun.COM>, argv@turnpike.Eng.Sun.COM (Dan Heller) writes: > alts * !cory.berkeley.edu!dheller !ora.ora.com!danh !comp-sources-x Aha! That's the secret. Silly me, I figured that since all the mail addresses on my Sun are user@domain format, that putting the exact-string-match user@domain in the alternates list would do it. I flipped them around and stuck a ! on the front and now it works! Thanks! > 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... This seems like a reasonable thing to do since user@host is the standard format that most people use these days. > > 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. Somehow mailtool manages to do it. > > 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 > If the button is also disabled, then we have a problem. Yes, works, it just wasn't obvious that I should press it. You view as meaning "pop up the compose window", I view it as meaning "I want to send a new piece of mail". I suspect users are more likely to make the latter interpretation. > > 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 seem to get mush's pager no matter what I ask for. But that's OK - I don't really want a separate pager, it takes too long to start up. I just want the built-in pager to do something reasonable (not just beep) when I type a mush command at it. I realize this is hard to do if you use your own pager, but for the built-in one that I get anyway it should be easy. > > 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. Are there bugs in screen scrolling on the BSD curses? Or is it just slow to scroll backwards? I think even the BSD curses will scroll the whole screen forward a line if you set scrollok to true. Mark