getprogname(3) manpage fix

Index: getprogname.3 === RCS file: /cvs/src/lib/libc/gen/getprogname.3,v retrieving revision 1.4 diff -u -p -r1.4 getprogname.3 --- getprogname.3 31 Jul 2013 16:43:27 - 1.4 +++ getprogname.3 4 May 2015 20:34:35 -00

Re: Rewording mbstowcs(3), wcrtomb(3) and wcstombs(3)

On Thu, Mar 19, 2015 at 03:58:16PM +0100, Stefan Sperling wrote: > > Perhaps the following diff would make everyone happy again? Thanks Stefan, it looks good for me. > > Index: mbstowcs.3 > === > RCS file: /cvs/src/lib/libc/locale/

Re: Rewording mbstowcs(3), wcrtomb(3) and wcstombs(3)

On Thu, Mar 19, 2015 at 01:36:45PM +0001, Jason McIntyre wrote: > On Thu, Mar 19, 2015 at 03:32:52PM +0200, Kaspars Bankovskis wrote: > > Is that really accurate to say that elements are stored in a pointer? > > > > no idea. it's why i asked stsp to look it over.

Re: Rewording mbstowcs(3), wcrtomb(3) and wcstombs(3)

Is that really accurate to say that elements are stored in a pointer? On Thu, Mar 19, 2015 at 12:41:48PM +0001, Jason McIntyre wrote: > On Wed, Mar 18, 2015 at 03:32:40PM -0400, Andre Smagin wrote: > > Hello. > > > > mbstowcs(3), wcrtomb(3) and wcstombs(3) use a bit awkward wording - > > "the fi

mg(1) segfaults on scroll-down

Hi, to reproduce the issue: (1) start mg and press Enter, until you fill up the screen and it goes on to the next screen. (2) type in at least one character (3) press M-v (or execute command scroll-down) (4) mg core dumps. (gdb) bt #0 0x16b305e0e014 in update (modelinecolor=2) at /usr/src/

mg(1): typo in manpage

Index: mg.1 === RCS file: /cvs/src/usr.bin/mg/mg.1,v retrieving revision 1.89 diff -u -p -r1.89 mg.1 --- mg.13 Nov 2014 14:53:22 - 1.89 +++ mg.117 Mar 2015 13:27:17 - @@ -86,7 +86,7 @@ Backup files have a

arithmetic(6) range patch

Using better tool for the job. Index: arithmetic.c === RCS file: /cvs/src/games/arithmetic/arithmetic.c,v retrieving revision 1.18 diff -u -p -r1.18 arithmetic.c --- arithmetic.c29 Aug 2013 20:22:09 - 1.18 +++ arithm

comment fix for mg

There's no ifdef for STARTUP. Index: Makefile === RCS file: /cvs/src/usr.bin/mg/Makefile,v retrieving revision 1.28 diff -u -p -r1.28 Makefile --- Makefile31 May 2013 18:03:43 - 1.28 +++ Makefile4 Jan 2015 19:08:47 -0

mail(1) and chdir command

Due to the order in commands table, "c" maps to "copy", not "chdir" as man page says. "cd" and "ch" work instead. Two alternative fixes: either man page or the order of commands - leaving for you to decide. IMHO better to update man page than muscle memory of old time users. Index: mail.1

Re: wc(1) and -m flag

I agree, it's better this way - with the prospect that the locale support might be added some day. On Fri, Jan 02, 2015 at 12:03:31PM +0100, Ingo Schwarze wrote: > Hi, > > i'm certainly not known for enthusiasm with respect to multibyte > character support, but wc(1) is one example of a program

Re: wc(1) and -m flag

On Thu, Jan 01, 2015 at 10:28:44PM +0001, Jason McIntyre wrote: > it's not exactly that we updated wc knowing that it was not posix > conformant. i think the general explanation is that the current > implementation of obsd treats characters and bytes the same, but they > might not on other systems,

wc(1) and -m flag

Correct me if I'm wrong, but it seems to me that the manual for wc(1) has been updated to be compliant with the standard but implementation not. -m and -c both set dochar=1 and I can't see any difference in further execution. They're not "mutually exclusive" either (opposed to manual) as it's the s

Re: intro(2) update regarding file names

Forgot to mention - the sentence I changed is based on FreeBSD version of the same manpage. On Mon, Dec 15, 2014 at 01:22:21PM +0200, Kaspars Bankovskis wrote: > As there are no file name restrictions for ASCII characters, I assume > this requirement might be outdated. Is that correct? >

intro(2) update regarding file names

As there are no file name restrictions for ASCII characters, I assume this requirement might be outdated. Is that correct? Index: intro.2 === RCS file: /cvs/src/lib/libc/sys/intro.2,v retrieving revision 1.53 diff -u -p -r1.53 intro.2

swapctl(2) manpage cleanup

The last sentence in HISTORY perhaps made sense before forking from Nx, but imho it's not relevant afterwards, especially since it mentions a header file which didn't come to Ox. .In and .An macro fixes, while there. Index: swapctl.2

pcap(3) manpage fixes

Function arguments in synopsis for pcap_inject and pcap_sendpacket are a bit messed up by comma. Types updated from actual code. And some .An and .In macro fixes while there. Index: pcap.3 === RCS file: /cvs/src/lib/libpcap/pcap.3,v

Re: no allocbuf in buffercache

On Thu, Dec 11, 2014 at 02:31:32PM +, Jason McIntyre wrote: > fixed, but couple of comments inline: OK, thanks for corrections, will keep in mind.

no allocbuf in buffercache

allocbuf was removed in 1.88 of sys/kern/vfs_bio.c but not from manpages Index: distrib/sets/lists/comp/mi === RCS file: /cvs/src/distrib/sets/lists/comp/mi,v retrieving revision 1.1117 diff -u -p -r1.1117 mi --- distrib/sets/lists/c

Re: cleanup of return values in section 2 manpages

I think these two are good for the change as well: Index: getrlimit.2 === RCS file: /cvs/src/lib/libc/sys/getrlimit.2,v retrieving revision 1.24 diff -u -p -r1.24 getrlimit.2 --- getrlimit.2 20 Nov 2014 03:19:23 - 1.24 +++ ge

dup(2) manpage fix

Index: dup.2 === RCS file: /cvs/src/lib/libc/sys/dup.2,v retrieving revision 1.17 diff -u -p -r1.17 dup.2 --- dup.2 31 Aug 2014 01:42:36 - 1.17 +++ dup.2 10 Dec 2014 12:20:09 - @@ -129,6 +129,7 @@ is zero then

cleanup of return values in section 2 manpages

On Wed, Dec 10, 2014 at 12:18:44AM -0700, Philip Guenther wrote: > CVSROOT: /cvs > Module name: src > Changes by: guent...@cvs.openbsd.org2014/12/10 00:18:44 > > Modified files: > lib/libc/sys : bind.2 intro.2 kill.2 > > Log message: > Prefer .In and .Rv -std More of thi

typos

Index: vfs_bio.c === RCS file: /cvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.163 diff -u -p -r1.163 vfs_bio.c --- vfs_bio.c 8 Oct 2014 07:33:14 - 1.163 +++ vfs_bio.c 9 Dec 2014 21:25:27 - @@ -86,7 +86,7 @@ long

Re: assert(3) manpage tweaks

On Sun, Dec 07, 2014 at 02:33:29AM +0100, Ingo Schwarze wrote: > By the way, i just grepped v6 for "assert" and came up empty-handed. > Anybody knows whether the statement is even correct? Didn't it > rather first appear in v7? If we can rely on the files that we get from tuhs, yes - it's not in

Re: assert(3) manpage tweaks

Ingo Schwarze wrote: > Hi Kaspars, > > Kaspars Bankovskis wrote on Sat, Dec 06, 2014 at 11:07:50PM +0200: > > > macro fixes, mostly. > > Committed with the following exception. > > Thanks, > Ingo > > > Index: assert.3 > > ==

getrusage(2) manpage update

One flag was undocumented + some cleanup. Index: getrusage.2 === RCS file: /cvs/src/lib/libc/sys/getrusage.2,v retrieving revision 1.15 diff -u -p -r1.15 getrusage.2 --- getrusage.2 17 Jul 2013 05:42:11 - 1.15 +++ getrusage.2

typo

Small typo fix, for the sake of correctness. Index: kern_time.c === RCS file: /cvs/src/sys/kern/kern_time.c,v retrieving revision 1.88 diff -u -p -r1.88 kern_time.c --- kern_time.c 15 May 2014 04:36:33 - 1.88 +++ kern_time.c

assert(3) manpage tweaks

Hi, macro fixes, mostly. Index: assert.3 === RCS file: /cvs/src/share/man/man3/assert.3,v retrieving revision 1.8 diff -u -p -r1.8 assert.3 --- assert.35 Jun 2013 03:42:03 - 1.8 +++ assert.36 Dec 2014 19:23:45 -

stdarg(3) manpage tweaks

Hi, I'm proposing the following changes to stdarg(3). Moved description of return values to its own section + macro cleanup. Index: stdarg.3 === RCS file: /cvs/src/share/man/man3/stdarg.3,v retrieving revision 1.18 diff -u -p -r1.18

mg(1) and no-tab-mode

Hi, I was just mislead by mg(1) manpage, which mentions no-tab-mode as an available command. But you get it only if you look at source and manually compile with -DNOTAB. Last time the topic was touched here: http://marc.info/?l=openbsd-tech&m=133727367821401&w=2 > no-tab-mode looks a bit buggy.

Re: em(4) fix for Intel I218 chip

spotted a small typo in a comment. 1Gpbs -> 1Gbps On Sun, Oct 12, 2014 at 09:53:28PM +0200, Claudio Jeker wrote: > This seems to be enough to help em(4) in modern laptops like the X240 to > no longer generate watchdog timeouts on high throughput. > This should only affect I218 but tests on differe