moody

Plan 9 only alt of @moody

Last Notes

2026-08-06 21:58:49 UTC

- reply

@nprofile…650u The cursor may show on screen while its prompting for you to set a mouse port, accepting the default of 'ps2' or using 'ps2intellimouse' should work.

2026-08-06 21:34:39 UTC

- reply

@nprofile…650u The qcow2 images are specifically designed to use a console by default with because for virtual machines you really would much prefer to be using drawterm. You can give that a go or grab the iso and boot that up in qemu.

2026-08-06 20:54:55 UTC

- reply

@nprofile…sj2w Just wanted to double check to common pitfalls, thanks for that.
Can you try booting the kernel with usbdebug=-d in plan9.ini? That should cause udb debug to be spit out on the kernel console, you can grab it from /dev/kmesg and webpaste it. I can pass that off (but you sending a mail to the ML might be easier so I dont have to be the go between, I've been lucky enough to avoid touching the usb code)

2026-08-06 20:43:43 UTC

- reply

@nprofile…sj2w Ok perfect that is exactly as it should be. Then just the usb issue, just wanna make sure you did update your kernel when updating yeah? You need to make sure to build userspace first, then the kernel since the kernel bundles parts of userspace in the paqfs. I just checked the git log and some things were tweaked with nusb in this release in particular to the disk.
if that all checks out, could you send a mail to the 9front mailing list as a bug report?

2026-08-06 20:24:45 UTC

- reply

@nprofile…sj2w When was the last time you updated your machine? The first indicate an issue with dns resolution/ndb in general, the later of which seems to potentially be a bug in usb although not a ton of usb work happened between the last release and now.
We also had an issue with the git cache for a while that can bit when large updates are done all at once, try the following:
bind -a /dist/9front /
cd /
rm .git/INDEX9
git/diff -s /
This should only show files you've manually modified.

2026-08-06 20:13:25 UTC

- reply

@nprofile…sj2w can you provide more details?

2025-02-24 20:31:23 UTC

- reply

@nprofile…vc7v The command exactly like that could be added to the end of /sys/lib/kbmap/it (or whichever you use specifically) or you can put it in your profile manually, either or works. The kbmap files are just a collection of these commands.

2025-02-24 20:18:15 UTC

- reply

@nprofile…vc7v Look at kbdfs(8) manual page for details about how the keyboard maps work, evdump just gives you the scan code. For making shift+space work you'd something like:
echo shift 57 0x1c >> /dev/kbmap

2025-02-23 10:55:49 UTC

- reply

@nprofile…vc7v I did port neatroff, and I would like to try replace our troff with it, but from my understanding for neatroff we need our pdf display program to handle embedded ttf, and currently our gs can not. So all of this is pending the rendering/font stuff being fixed on the display side first.

2025-02-23 10:53:55 UTC

- reply

@nprofile…vc7v You can try out evdump(1).

2025-02-23 00:21:34 UTC

- reply

@nprofile…vc7v It's a bit of a hack, you put things between the Jp font, and then you have to use -mnihongo which will generate a bitmap. At the default ppi of 100 it's a bit hard to read but 200 works a bit better. It sucks a bit.

2025-02-23 00:18:55 UTC

- reply

@nprofile…vc7v The kbmap might use the literal control character. It's in there on the 9th line. It depends on the physical keyboard you have. You're going need to mess around a bit and just set whatever you want to emit that control character.

2025-02-20 23:54:53 UTC

- reply

@nprofile…vc7v Ctrl-\ should output character 0x1C, what is it generating? That is how it is by default perhaps you've modified your kbmap to output something else? You can modify kbmap to generate 0x1C from any sort of key combination.

2025-02-20 20:26:39 UTC

- reply

@nprofile…vc7v You launch it like so:
ktrans /dev/kbdtap
Then you input Ctrl+n to switch to Japanese hiragana input. Completion is then done using Ctrl+\, candidates will show up in the graphical window. All of this is described in the manual page.

2025-02-20 19:51:21 UTC

- reply

@nprofile…vc7v Did you read the manual for ktrans? It is fairly explicit how it works. What is not happening how you expect it to?

2025-01-10 22:55:57 UTC

- reply

@nprofile…vc7v The ktrans(1) manual page goes over the details of how to input the Kanji characters, I would refer there. The issue with our troff is that they do not use the same font files as the rest of the system, they use Postscript type-1 fonts, which are a bit of a relic at this point. I recall I did help someone get Chinese working within out troff but it required converting their own font (with something like font forge) and was a bit involved. We want to use neatroff but the work isn't done

2025-01-10 19:06:36 UTC

- reply

@nprofile…vc7v Unicode within the troff that 9font uses is not great right now, we have a hack (see mnihongo(6)) for embedding Japanese in troff documents but it does not support all of CJK. Japanese input in general is handled through ktrans(1).

2024-05-24 22:46:10 UTC

- reply

@npub1ufm…qhp4 Yeah watching this remake has been a bit disappointing. I was optimistic at first but stuff like this makes it feel more like a cheap cash grab.