Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!ogicse!schaefer From: schaefer@ogicse.ogi.edu (Barton E. Schaefer) Newsgroups: comp.mail.mush Subject: Re: mush bugs Message-ID: <12635@ogicse.ogi.edu> Date: 4 Oct 90 18:37:40 GMT References: <1990Oct2.170734.17606@cbnewsu.att.com> <12573@ogicse.ogi.edu> <1990Oct3.172900.28233@cbnewsu.att.com> <143274@sun.Eng.Sun.COM> <1990Oct4.062156.24647@mlb.semi.harris.com> Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR Lines: 123 In article <1990Oct3.172900.28233@cbnewsu.att.com> mark@cbnewsu.att.com (Mark Horton) writes: } Bart - thanks for the fast response! } } In article <12573@ogicse.ogi.edu>, schaefer@ogicse.ogi.edu (Barton E. Schaefer) writes: } > } The "alternates" feature does not seem to work. } > You probably have $metoo set. Mush will continue to include you in } > replies if that variable is set. } } I popped up the "options" button and it says "metoo" is "false". } Yet every reply still goes to any alias even though it's me. In article <143274@sun.Eng.Sun.COM> argv@turnpike.Eng.Sun.COM (Dan Heller) writes: } 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 If you're still having problems after trying Dan's examples, send me the alternates line from your .mushrc. Back to mark@cbnewsu.att.com (Mark Horton): } rn uses a built-in pager (public domain code - you could snarf it) which } apparently pops you out to the top level for unrecognized commands. Actually, thinking about it, it wouldn't be very difficult to add to mush. Try this. The following lines are from misc.c (7.1.2 version): 555 while ((c = getchar()) >= 0 && c != CTRL('D') && !isspace(c) && 556 c != '\n' && c != '\r' && lower(c) != 'q' && lower(c) != 'd') 557 bell(); Change line 557 to: if (iscurses) { m_ungetc(c); c = 'q'; } else bell(); and let me know how that works. } I have "set PAGER=/usr/ucb/more" in both my .mushrc and .mailrc, but yet } I seem to get the built-in pager when I use mush -C. That's odd. Oh, wait! Mush doesn't have a local variable named PAGER. It recognizes the *environment* variable PAGER and the local variable pager. So you need either set pager=/usr/ucb/more or setenv PAGER /usr/ucb/more in your .mushrc. } > } 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. } > } > Problem: Many curses implementations do not perform scrolling properly, } > even if the terminal supports "scrolling regions", which many don't. } } You have -DSYSV to tell at compile time whether you have the System V } curses, which can scroll efficiently, or the Berkeley curses, which can't. That's not quite good enough. There are other systems besides SVR2 that use the SYSV define, that have curses packages just as messed up as Berkeley's. } (Of course, mush won't compile with -DSYSV on a Sun, it's apparently never } been tested under /usr/5bin/cc - this needs to be taken care of.) We just got mail from someone who compiled it under SysV on the Sun. Hm. I don't think I saved the message. Anyway, /usr/5bin/cc at least on pre- 4.x suns has a badly broken preprocessor, which can't handle some of the #if constructs that are handled correctly by every other SysV mush has been compiled on (which is most of them). We aren't going to go through the major effort required to rewrite all our preprocessing directives for that one case when the alternative of /bin/cc is available. } (I wish space went on to the next message ala } n, and or or something put you back in the top level menu.) bind ' ' display-next unbind '\n' unbind '\E' } An icon for the compose window would be a big improvement. As Don Lewis mentioned, it probably isn't possible, because the compose window is not its own process -- its just a child window in its own frame. In article <1990Oct4.062156.24647@mlb.semi.harris.com> del@thrush.mlb.semi.harris.com (Don Lewis) writes: } In article <1990Oct3.172900.28233@cbnewsu.att.com> mark@cbnewsu.att.com (Mark Horton) writes: } >I note that mushtool makes you confirm lots of other things, such as sending } >out a message in the first place, or saving it to a file. Closing the } >compose window without pressing send first is unusual and ought to require } >a confirmation. Personally I would prefer to turn off these confirmations - } >have automatically the compose window, and not bother with } } Maybe the same with too. Does ask for confirmation? Hmm. (Can you tell I don't use a Sun very often?) Anyway, in 7.1.2 (as opposed to 7.1.1, which I think Mark still has) the variable "verify" has become multi-valued, and has a field "save" that controls whether you are asked about saves to a file. The others could be added as well, we'll consider it. } >Another general comment: I spend a lot of time with my mouse in mushtool } >carefully positioning it all over the place - lots of wasted motion, and } >lots of energy keeping it on that tiny little diamond when I'm paging through } >a message. A button near would be very nice, even } >better if hitting space in the same window had the same effect. That's sort of wryly amusing, because there used to be such a button, but we removed it when the scrollbars went in. As Don says, though: } Try j, k, ^d, ^u, ^f, ^b, the up and down arrow keys, R7 and R13. Sorry, } no space though. -- Bart Schaefer schaefer@cse.ogi.edu