#watanabeshell — Public Fediverse posts

I'm not the only person to provide a full off-line browsable HTML guide to my softwares in the box, also. (-:

In case anyone else hits it: The version of xgettext in #NetBSD 10.1 is old enough (0.16) that it breaks the #WatanabeShell build. You need the one that is in pkgsrc (0.22).

#UnixShells #nosh

I've just upgraded the Watanabe shell to version 2.61 on my machines.

I think that the #WatanabeShell is the first shell to really run with the idea of having no dot files in my home directory. All of its files are under ~/.local or ~/.config , no compatibility symbolic links being required in order to force this. And there are no dots in the remaining pathname components.

https://github.com/jdebp/slashpackage/commit/9671a9018a8cf8012affdbddd2fa942888b788ae

#UnixShells #slashpackage #XDG

It turns out that this is an easy fix. Ironically, if termcap actually knows about an enter key, ncurses returns the actual key code for it, that yash then fails to handle. The fix is 1 extra line in lineeditor/keymap.c:

Set(Key_enter,cmd_accept_line);

#yash #WatanabeShell
@magicant

There's an interesting problem with terminal types that use @8 in termcap to define an enter key.

Ironically, doing so *stops* the enter key from being recognized as an accept action in the line editor. I haven't got to the bottom of that yet.

#yash #WatanabeShell
@magicant

I built directly from source. It turns out that taking out the declaration and putting in #include <stdio.h> is exactly the patch that Christian Weisgerber had to do in ports:

https://cgit.freebsd.org/ports/tree/shells/yash/files/patch-configure

#yash #WatanabeShell
@magicant

It turns out that getting #yash, the #WatanabeShell, version 2.54 to compile on FreeBSD needs only 1 correction so far.

It doesn't detect ncurses properly because of, ironically, an error in one of the test programs used by ./configure .

In one ncurses test program it correctly #includes <stdio.h>. But in another it erroneously tries to declare int putchar(int) itself. putchar() is a macro in BSD libc, and the declaration breaks the test program, thereby failing to find <term.h>.

@magicant