[Bug report] abbr_init on OpenBSD

[lebel]

Is there an existing issue for this?

• I have searched the existing issues

Update the issue title

• I have updated the title

Expected Behavior

No "errors" when I log on my shell.

Actual Behavior

I get the following when loading the zsh-abbr.zsh module:

+/home/lebel/.zim/modules/zsh-abbr/zsh-abbr.zsh:1887> _abbr_init
+_abbr_init:1> emulate -LR zsh
head: unknown option -- c
usage: head [-count | -n count] [file ...]

on OpenBSD 7.6.

The abbr command still works just fine, it is only displaying this when I log on my account. To catch the log I added a

exec 2>trace.log
set -x

at the top of my .zshrc.

Steps To Reproduce

No response

Environment

OpenBSD 7.6 with Zsh 5.9 with pkg_add.

Installation method

Plugin manager

Installation method details

Using zimfw.

Anything else?

No response

[olets]

Thanks for the report!

Ok that's coming from zsh-job-queue (this line).

I see OpenBSD's head doesn't have a way to select a certain number of bytes. cut might work as a replacement. What do you get if you run

'command' 'cat' /dev/urandom | 'command' 'base64' | 'command' 'tr' -dc '0-9a-zA-Z' | 'command' 'cut' -b 1-36

(it will be different every time, I just need one)

[lebel]

It doesn't work. The line never returns. Ven 28 mars 2025, à 20:22, Henry Bley-Vroman a écrit :

…

Thanks for the report! Ok that's coming from zsh-job-queue (this line <https://github.com/olets/zsh-job-queue/blob/e98ed2acae2c47395596e2af229319266678b000/zsh-job-queue.zsh#L207>). I see OpenBSD's `head` doesn't have a way to select a certain number of bytes. `cut` might work as a replacement. What do you get if you run 'command' 'cat' /dev/urandom | 'command' 'base64' | 'command' 'tr' -dc '0-9a-zA-Z' | 'command' 'cut' -b 1-36 (it will be different every time, I just need one) — Reply to this email directly, view it on GitHub <#168 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAF7PRGCKIUI2OAJUNV23GT2WXRUFAVCNFSM6AAAAAB2AUGZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRSHEZDIMJUG4>. You are receiving this because you authored the thread.Message ID: ***@***.***> olets*olets* left a comment (olets/zsh-abbr#168) <#168 (comment)> Thanks for the report! Ok that's coming from zsh-job-queue (this line <https://github.com/olets/zsh-job-queue/blob/e98ed2acae2c47395596e2af229319266678b000/zsh-job-queue.zsh#L207>). I see OpenBSD's `head` doesn't have a way to select a certain number of bytes. `cut` might work as a replacement. What do you get if you run 'command' 'cat' /dev/urandom | 'command' 'base64' | 'command' 'tr' -dc '0-9a-zA-Z' | 'command' 'cut' -b 1-36 (it will be different every time, I just need one) — Reply to this email directly, view it on GitHub <#168 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAF7PRGCKIUI2OAJUNV23GT2WXRUFAVCNFSM6AAAAAB2AUGZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRSHEZDIMJUG4>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[lebel]

In the meantime, I implemented the uuidgen so it doesn't get to the head part from
https://www.bsdhowto.ch/uuid.html

[olets]

Good workaround.

I don't currently have an OpenBSD environment to test on. If anyone else runs into this, I'd be glad for fix suggestions.