david wrote: > I added a welcome message when nmh detects that its version > changed. You'll you see it the first time after checking out > the welcome branch (and 1.7, assuming we want to keep this). > > It doesn't happen if stdin or stdout isn't connect to a terminal, > or for any of these commands: > > mhbuild, mhfixmsg, mhparam, mhpath, prompter, whatnow, whom > > or any of the libexec commands: > > ap, dp, fmtdump, mhl, mkstemp, post, rcvdist, rcvpack, rcvstore, > rcvtty, slocal, spost, viamail > > Here's the message, printed on stderr:
nice. is there a "press enter to continue?" prompt? if not, many commands which bring up an editor will tromp on that text before it can be read. paul > > ======================================================================= > Welcome to nmh version 1.6+dev > > See the release notes in /home/levine/lib/nmh/share/doc/nmh/NEWS . > > Send bug reports, questions, suggestions, and patches to > [email protected]. That mailing list is relatively quiet, so user > questions are encouraged. Users are also encouraged to subscribe, and > view the archives, at https://lists.gnu.org/mailman/listinfo/nmh- > workers . > > This message will not be repeated until nmh is next updated. > ======================================================================= > > Thought the message will be repeated if the nmh command failed. > > It's implemented by adding a Version: string to the user's context. > > OK? > > David > > _______________________________________________ > Nmh-workers mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/nmh-workers > =---------------------- paul fox, [email protected] (arlington, ma, where it's 51.8 degrees) _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
