On Thu, Aug 17, 2017 at 07:25:14PM -0500, Scott Cheloha wrote: > Spotted these when customizing my prompt. > > I think "may differ from" is better than "could be different from," > and you're free to (heh) differ, but in either case we get the > > to -> from >
morning. > -- > Scott Cheloha > > Index: bin/ksh/ksh.1 > =================================================================== > RCS file: /cvs/src/bin/ksh/ksh.1,v > retrieving revision 1.192 > diff -u -p -r1.192 ksh.1 > --- bin/ksh/ksh.1 11 Aug 2017 23:10:55 -0000 1.192 > +++ bin/ksh/ksh.1 18 Aug 2017 00:19:35 -0000 > @@ -1614,16 +1614,15 @@ in > .Ev PS1 . > .It Li \e# > The current command number. > -This could be different to the current history number, > -if > +This may differ from the current history number if what's there now is ok, and what you propose is ok. so the difference is really taste. in cases like that, i don;t think changing the text is worth it, unless you can see a clear improvement. as to your point about to -> from, "different to" is in use. my student dictonary notes that "In British English, people sometimes say that one thing is different to another. Some people consider this use to be incorrect". but then the reverse is seemingly true of "different than". i would just leave it. > .Ev HISTFILE > contains a history list from a previous session. > .It Li \e$ > -The default prompt i.e.\& > -.Sq # \& > +The default prompt character i.e.\& > +.Sq #\& > if the effective UID is 0, > otherwise > -.Sq $ \& . > +.Sq $\& . > Since the shell interprets > .Sq $ > as a special character within double quotes, > i haven;t tested the space issue, but if it's correct i guess it needs fixing. however in that case the "\&" escaping is not needed. jmc
