Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!ogicse!schaefer
From: schaefer@ogicse.ogi.edu (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: mush bugs
Message-ID: <12573@ogicse.ogi.edu>
Date: 3 Oct 90 05:00:43 GMT
References: <1990Oct2.170734.17606@cbnewsu.att.com> <1990Oct3.025026.3297@mlb.semi.harris.com>
Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR
Lines: 56

In article <1990Oct2.170734.17606@cbnewsu.att.com> mark@cbnewsu.att.com (Mark Horton) writes:
} I notice the following problems in MUSH:
} 
} 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 probably have $metoo set.  Mush will continue to include you in
replies if that variable is set.

} General gripe: in curses mode, the interface looks and feels very much
} like rn, but many things that work in rn that could reasonably work in
} mush don't.  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.

That's because mush doesn't have any sophisticated pager built in.
You get either an extremely simple pager (the code is about 30 lines)
or your usual pager process (more, less, pg, etc.).  Obviously, you
can't issue mush commands from the middle of a forked-off paging
process, so it would be confusing to allow it from the built-in pager.

} 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.)

Problem: Many curses implementations do not perform scrolling properly,
even if the terminal supports "scrolling regions", which many don't.
Mush would have to redraw the whole screen when the j passed the bottom
or the k passed the top.  Since this can be rather slow (depending on
baud rates) mush doesn't want to do it "accidentally" if you happen
to hit j or k one or two times more often than is necessary to get you
to the message you want.

In article <1990Oct3.025026.3297@mlb.semi.harris.com> del@thrush.mlb.semi.harris.com (Don Lewis) writes:
} In article <1990Oct2.170734.17606@cbnewsu.att.com> mark@cbnewsu.att.com (Mark Horton) writes:
} >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!  I
} >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.
} 
} I get bitten by this occasionally, too.  I find it annoying to discover
} that I never sent out the message that I composed several hours ago.
} An easier way to get the compose frame back is to hit the Compose button.
} Mush will whine that you have to finish your first letter and will pop
} up the compose frame.

We've discussed having a variable or some such that would send when
you close the frame, automatically.  But there are times when you might
*want* to close the frame without sending ... sorry if it isn't obvious
enough that hitting <Compose> again will bring back the window ... I
suppose supplying some kind of compose window icon would be better.
-- 
Bart Schaefer						schaefer@cse.ogi.edu