Re: Adding -p to pr(1)

2021-01-04 Thread Andras Farkas
Ping. I'm hoping someone can review the diff adding -p to pr(1). On Fri, Dec 11, 2020 at 9:54 PM Andras Farkas wrote: > > Hi! > > After seeing the diff for cat -n earlier today, and just browsing Unix > stuff on my own, I noticed OpenBSD's pr(1) command has no -p option > de

Re: Adding -p to pr(1)

2020-12-13 Thread Andras Farkas
On Sun, Dec 13, 2020 at 4:44 PM Jason McIntyre wrote: > On Sun, Dec 13, 2020 at 04:30:06PM -0500, Andras Farkas wrote: > > Was the diff I sent adding -p support not good? Or is -p just > > something undesired in general? Just trying to understand and learn > > from this.

Re: Adding -p to pr(1)

2020-12-13 Thread Andras Farkas
On Sun, Dec 13, 2020 at 10:40 AM Jason McIntyre wrote: > hi. > > it's an oversight on my part - the posix page for pr renders poorly on > lynx, and -p is difficult to spot. i have added a note to say that -p is > unsupported. if anyone chooses to add support, we can easily fix it. I see! Was the

Re: Adding -p to pr(1)

2020-12-11 Thread Andras Farkas
On Fri, Dec 11, 2020 at 10:23 PM Andras Farkas wrote: > Also, I think the line: > ttyinf = stdin; > is almost certainly unnecessary. But I'd like someone else more > versed in programming to confirm this. I don't think ttyinf's value > of stdin is ever used, as it gets set next

Re: Adding -p to pr(1)

2020-12-11 Thread Andras Farkas
Also, I think the line: ttyinf = stdin; is almost certainly unnecessary. But I'd like someone else more versed in programming to confirm this. I don't think ttyinf's value of stdin is ever used, as it gets set next to /dev/tty On Fri, Dec 11, 2020 at 9:54 PM Andras Farkas wrote: > &

Adding -p to pr(1)

2020-12-11 Thread Andras Farkas
Hi! After seeing the diff for cat -n earlier today, and just browsing Unix stuff on my own, I noticed OpenBSD's pr(1) command has no -p option despite pr.1 stating: > The pr utility is compliant with the IEEE Std 1003.1-2008 ("POSIX.1") > specification. https://man.openbsd.org/pr.1 This part of

diff: fixing a few broken links on 68.html, and other minor things

2020-10-21 Thread Andras Farkas
Hello! While reading 68.html I noticed some of the man page links pointed to the man pages in the wrong section of the manual. (at least, given the manual section numbers listed next to them in the 68.html text) I decided to fix these. While there, I also made the fixed links point at 6.8 man

vi.beginner diff and analysis (vi.advanced to follow)

2020-05-23 Thread Andras Farkas
I went through vi.beginner. It works both with vi's regular settings, and with the settings applied via EXINIT in vi.tut.csh. I have a diff attached. I was mostly light and gentle with my changes, but I indeed did change some outdated info and incorrect info. I seriously doubt vi.tut.csh's

httpd diff (fixes single instance of XHTML-style element)

2020-05-20 Thread Andras Farkas
Hello! Today I noticed, when looking at an autoindex page on my own website, that despite the page being HTML (as evidenced by being used rather than further down, and also by the page being served as text/html) there was a single instance of an XHTML-style element: Notice the second to last

Re: correction for insque.3

2020-04-24 Thread Andras Farkas
I have an alternative to insque3difflarge.txt as for clarifying the wording: simply removing the word "respectively", so the end of the sentence is just "in the queue." (that said, I have a preference for what I actually sent as a diff) On Thu, Apr 23, 2020 at 5:48 PM Andras

correction for insque.3

2020-04-23 Thread Andras Farkas
I was reading the thread about STAILQ and SIMPLEQ and thought it was interesting, so I then read a little about sys/queue.h and search.h I noticed an error in insque.3: https://man.openbsd.org/insque.3 The words "next" and "previous" are swapped, as it is the first pointer that points to the next

a POSIXy diff for what(1)

2020-04-18 Thread Andras Farkas
I don't use what often, but I do use it sometimes. Today I noticed the format of what's output on OpenBSD was different than that of what on FreeBSD. Looking in what.1: https://man.openbsd.org/what I noticed OpenBSD's what is documented as abiding by POSIX:

Re: FAQ4.html Commit Revert

2020-01-02 Thread Andras Farkas
For me, faq4.html displays fine in Firefox, lynx, and Chromium, both with and without the CSS. On Thu, Jan 2, 2020 at 10:47 AM Oleg Pahl wrote: > > Hi @All, > > > > could you be so kind to revert this commit in FAQ 4? > >

Re: ksh: support "function name()"

2019-12-28 Thread Andras Farkas
On Sat, Dec 28, 2019 at 10:08 AM Mark Kettenis wrote: > [snip] > Are there other ksh implementations that have this "feature"? As for this question, I can at least confirm that no version of ksh93 has it.

Re: ksh: support "function name()"

2019-12-28 Thread Andras Farkas
If this diff gets accepted, in ksh's man page, you'll probably have to change the following line as it's not entirely disambiguous how a function would behave if it had both 'function' and '()' where it was defined: "Functions defined with the function reserved word are treated differently in the

Re: Clarify drand48() return values

2019-12-19 Thread Andras Farkas
, unless they really do mean their upper bound is inclusive) On Thu, Dec 19, 2019 at 10:48 PM Andras Farkas wrote: > > On Thu, Dec 19, 2019 at 10:05 PM Theo de Raadt wrote: > > It's a mathematical notation that anyone using this page should > > understand because it comes with the te

Re: Clarify drand48() return values

2019-12-19 Thread Andras Farkas
On Thu, Dec 19, 2019 at 10:05 PM Theo de Raadt wrote: > It's a mathematical notation that anyone using this page should > understand because it comes with the territory. > [snip] > > I think understanding the landscape's notation is a requirement, and we > don't need to say things a 2nd time in

Re: un-boolean_t ANSIfy ddb(4) for hppa & sparc64

2019-11-20 Thread Andras Farkas
On Wed, Nov 20, 2019 at 9:38 AM Theo de Raadt wrote: > Kernel environment cannot use userland includes. On Wed, Nov 20, 2019 at 12:18 PM Todd C. Miller wrote: > Changing from int -> bool is error prone since you inevitably have > code that use true, false and -1. Finding those outliers that

Re: un-boolean_t ANSIfy ddb(4) for hppa & sparc64

2019-11-20 Thread Andras Farkas
Out of curiosity, why not just use stdbool.h if these are actually meant to be booleans? Wouldn't that be more readable? I wonder if there's something I'm not understanding. On Tue, Nov 5, 2019 at 8:05 AM Martin Pieuchot wrote: > > ok? > > Index: arch/hppa/hppa/db_disasm.c >

add errata66 to security.html

2019-10-28 Thread Andras Farkas
This diff adds a link to https://www.openbsd.org/errata66.html on https://www.openbsd.org/security.html I noticed this when reading the 6.6 announcement email. Index: security.html === RCS file: /cvs/www/security.html,v retrieving

fix acme manpage link in faq/upgrade66.html

2019-10-24 Thread Andras Farkas
Diff attached, changes bad link: https://man.openbsd.org/OpenBSD-6.6/acme-client.5 to https://man.openbsd.org/OpenBSD-6.6/acme-client.conf.5 on this page: https://www.openbsd.org/faq/upgrade66.html Do documentation-related diffs like this belong in tech, bugs, or misc? Index: upgrade66.html

Re: Fix a segmentation fault in awk

2019-08-12 Thread Andras Farkas
On Mon, Aug 12, 2019 at 3:45 PM Frederic Cambus wrote: > Hi tech@, > Here is a diff to fix a segmentation fault in awk, from upstream > version 20121220 [1]. Upstream fix didn't check for strdup return value > so I added the check. I've always been curious, why isn't the latest version of awk,

Re: printf(1) man page has a small omission

2019-08-02 Thread Andras Farkas
On Thu, Aug 1, 2019 at 5:54 PM Ingo Schwarze wrote: > please do not cross-post on OpenBSD lists, choose whatever list fits > best. I trimmed bugs@ for this followup. Ah, my bad. I just found it unclear which list to send documentation issues to. I've normally sent them to bugs@ in the past,

Re: printf(1) man page has a small omission

2019-07-29 Thread Andras Farkas
I have a diff attached which fixes the man page. On Mon, Jun 3, 2019 at 2:12 PM Andras Farkas wrote: > > https://man.openbsd.org/man1/printf.1 > The section on the b format (%b) neglects to mention that for that > format, it's \0num rather than \num > Because of the way OpenBSD's

Re: ksh "clear-screen" editing command

2019-04-02 Thread Andras Farkas
On Tue, Apr 2, 2019 at 11:32 AM Klemens Nanni wrote: > On Tue, Apr 02, 2019 at 05:20:19PM +0200, Theo Buehler wrote: > > Yes, ^L is printed in vi insert mode. The text you quoted is about vi > > command mode which does indeed redraw the current line on ^L. I agree > > with jca, no need for a

Re: [vi] moving by sentences is inconsistent

2018-10-08 Thread Andras Farkas
On Mon, Oct 8, 2018 at 11:04 AM Theo de Raadt wrote: > You only checked the clones? You need to compare to the past. What you're implying is right: a comment (the one with the AB CD example) in https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr.bin/vi/vi/v_sentence.c implies that this

Re: [Patch] mg(1) tutorial: no columns :(

2018-05-25 Thread Andras Farkas
On Fri, May 25, 2018 at 7:43 AM, Leonid Bobrov wrote: > Index: tutorial > === > RCS file: /cvs/src/usr.bin/mg/tutorial,v > retrieving revision 1.17 > diff -u -p -u -p -r1.17 tutorial > --- tutorial30 May

Re: manpage text width

2018-03-31 Thread Andras Farkas
On Fri, Mar 30, 2018 at 11:23 AM, Chris Bennett wrote: > This is very important. Our brains just are not good at working with > long lines. This is hard-wired. If anyone doesn't believe me, try > setting your browser window to a narrower width or use reader mode.

Re: [PATCH] usr.bin/calendar/calendars/calendar.uk - Burns' Night -> Burns Night

2018-01-12 Thread Andras Farkas
On Fri, Jan 12, 2018 at 3:11 PM, Jason McIntyre wrote: > hilariously, i just realised the apostrophe in the quote above is in the > wrong place! maybe it should be "Burns Hog Weighing Method" ;) I'd also like to note that while some people would do: Burns' Hog Weighing Method

Re: README patch

2017-11-13 Thread Andras Farkas
On Mon, Nov 13, 2017 at 8:16 AM, Sebastian Benoit wrote: > http://ftp.openbsd.org/pub/OpenBSD/6.2/README Much more minor, but "This is our 43nd release." should be "This is our 43rd release." Also, "For further details, please visit https://OpenBSD.org/faq; actually ends up

Re: Mistake in flex man page

2016-12-23 Thread Andras Farkas
On Fri, Dec 23, 2016 at 11:14 PM, Philip Guenther wrote: > Many options to cc are position sensitive, including the -l > option. Oh wow, I see. You're absolutely right. Thank you!

Mistake in flex man page

2016-12-23 Thread Andras Farkas
Afternoon! The attached flexdiff changes flex.1 to be accurate about how flex currently works: -lfl does not provide yywrap() by default. Attached also are two lex files I used to find out that the man page wasn't correct. The man page says one can either use %option noyywrap or link with -lfl

Re: netcat service lookup

2016-06-01 Thread Andras Farkas
Oh, someone pointed the possible problem out to me: I'm running OpenBSD 5.9 instead of current. Sorry. On Thu, Jun 2, 2016 at 3:58 AM, Andras Farkas <deepbluemist...@gmail.com> wrote: >> Andras - your original diff does not apply to -current as mailed, and >> you also have

Re: netcat service lookup

2016-06-01 Thread Andras Farkas
Andras - your original diff does not apply to -current as mailed, and you also have a bug when the -v option is used, because you end up putting port names in the portlist array instead of numbers and so -v doesn't work right. Try this instead: Thank you, I was trying to look for bugs and

Re: netcat service lookup

2016-05-31 Thread Andras Farkas
Ah, okay. > I don't see how it makes it easier. There are a number of netcat > versions out there, mostly trying to be somewhat compatible. On a > whim, this introduces an incompatibility --> scripts become less > portable.

netcat service lookup

2016-05-31 Thread Andras Farkas
Evening! This diff allows users to use the name of a service in /etc/services instead of a port number when using netcat. Hopefully, this will make using netcat easier for some users. ? nc Index: nc.1 === RCS file: