wireguard-openbsd/bin/ed/ed.1, branch jd/queueboosts

In addresses, consistently use "+" rather than ".+1".

2019-07-30T09:23:35Z

Both have the same meaning, but the former is explicitly defined in this manual page as "the next line" whereas the latter requires combining various pieces of information for understanding. Unification suggested and patch OK'ed by martijn@.

1. Correct the description of the g command to match POSIX and our

2019-07-20T15:28:54Z

implementation; it was oversimplified and arguably incorrect. 2. Explicitely compare the behaviour of empty command lists for g, empty command lists for G, and empty commands because these subtle differences are quite confusing. 3. Say more precisely what the v and V commands do, avoiding the fuzzy wording "similar". All these issues were first pointed out by martijn@. Feedback and OK martijn@; "diff reads ok" jmc@ on an earlier version.

Explain in which circumstances trailing slashes can be omitted after

2019-07-15T17:57:48Z

the g and G commands, and polish the wording a bit explaining empty command lists. Closing a gap in the manual reported by . OK jmc@ martijn@

Minor polishing:

2019-07-12T19:28:48Z

* Delete a stray blank from the command line synopsis and add the missing .Ar markup to it. * Do not mention the terminating newline for the empty command since it isn't mentioned for any other command either. * Make the description of the empty command easier to understand. Joint work with martijn@ and jmc@.

document the dropping of the second / and ? in line address REs;

2019-07-10T13:35:51Z

thread started by mazocomp; diff from ropers, shortened by me; ok martijn schwarze

Make ed's 'l' command end lines with a '$' and make sure that literal

2018-04-26T12:18:54Z

'$' characters are escaped, so that we are POSIX compliant. The omission of trailing '$' was originally hidden behind a BACKWARDS flag. This flag was most likely introduced to be compatible with 4.4BSD. Thanks to naddy@ for pointing me to the 4.4BSD ed implementation. I tried to trace the origin and enabling of the BACKWARDS flag, since both FreeBSD and NetBSD have the flag, but only FreeBSD doesn't have it enabled. Both projects had an alm@ working on ed during 1993-1995 during which he added this flag to both projects and only enabled it on NetBSD, but I wasn't able to reach him on any known address. Thanks to Ed Schouten (ed@freebsd), and Michael W. Lucas of the ed Mastery book for helping me trying to locate Andrew Moore. Problem originally prodded by garzon.lucero@gmail.com and later independently re-requested by n.reusse@hxgn.net. OK tb@, guenther@, and mwl@mwl.io

nits about trailing punctuation found with mandoc -Tlint

2017-07-05T12:23:46Z

remove the note about the list command (l) displaying a --More--

2016-09-23T06:17:43Z

prompt for huge lines (according to otto this happens only when BACKWARDS is not defined); ok otto

honestly i think you should just zap that paragraph - it doesn;t make

2015-11-20T20:13:32Z

sense to document that posix more or less says something should happen, and that it does. jmc

make ed restore the user defined prompt (specified with -p) when it was turned

2015-11-20T08:53:28Z

off and then on again with 'P'. ok daniel@