-
IndyJoenz
tsoome_: LANG=C.UTF-8.. LC_CTYPE="C.UTF-8" etc
-
IndyJoenz
tsoome_: as in, like this:
0x0.st/XVcl.png
-
IndyJoenz
-
IndyJoenz
you can see the unicode blocks showing up as M instead
-
tsoome_
I asked, because LC_* varaibles will override LANG. However, what does stty -a report?
-
IndyJoenz
-
IndyJoenz
tsoome_: xterm on top, xfce4-terminal on bottom
-
IndyJoenz
Oh, interesting. It's not working in durdraw, but the characters work if I cat a unicode file
-
IndyJoenz
Hmm. Durdraw uses python curses
-
IndyJoenz
Yep. Must be something with how durdraw is using curses and/or python.
0x0.st/XVmX.png
-
ptribble
Hm. Does that need ncursesw as opposed to regular ncurses?
-
IndyJoenz
Hmm. Maybe. :) It shouldn't really, though I'm not sure what happens if you try to use wide characters in regular curses. durdraw will draw wide charaters, but isn't aware of them
-
IndyJoenz
the calls should be just to regular curses, through the python stdlib
-
IndyJoenz
but it is using some panels features that aren't in older curses versions
-
IndyJoenz
that said, I probably developed it against ncursesw
-
tsoome_
IndyJoenz thats output from gnu stty, what does /bin/stty show?
-
IndyJoenz
-
tsoome_
ok, so terminal lines should pass data as expected...
-
tsoome_
we could also check that with dtrace but given stty output should be sufficient...
-
ptribble
Yep, it needs ncursesw - just built a temporary copy for testing
-
IndyJoenz
ptribble: nice :)
-
ptribble
Which means it would work in other distributions, which explicitly enable ncursesw, but Tribblix always starts with whatever upstream ships as defaults and only changes them when a problem shows up
-
IndyJoenz
Ahh. I was wondering why the system python build wasn't sufficient
-
ptribble
I think python just looks for some curses library and isn't too bothered about the details
-
ptribble
But anyway I'll switch ncurses to ncursesw and we'll see how much else I have to fix
-
jperkin
there shouldn't be too much, I did the switch recently in pkgsrc, and most of that was mechanical to support NetBSD's native curses
-
ptribble
What I meant was breakage without rebuilding, as the docs says that wide and non-wide aren't binary compatible
-
jperkin
ah, that's a foreign concept to me ;)
-
gitomat
[illumos-gate] 15279 lex: clang build error -- Toomas Soome <tsoome⊙mc>
-
gitomat
[illumos-gate] 16687 iasl: storing the address of local variable -- Toomas Soome <tsoome⊙mc>
-
gitomat
[illumos-gate] 16684 Solaris 10 zones and libproc broken by new parameter to fcntl -- Robert Mustacchi <rm⊙fo>
-
alanc
btw, the thread starting at
lists.gnu.org/archive/html/autoconf/2024-08/msg00006.html is about illumos ksh93 not playing nicely with GNU autoconf
-
andyf
Thanks alanc. It's reported on a pre illumos 13405 system so I expect current systems are okay but I'll offer to help them test if the OP doesn't volunteer. (fenix)
-
fenix
FEATURE 13405: ksh93 update to 2012-08-01 (Closed)
-
fenix
-
rmustacc
Thanks for taking a look, Andy.
-
-
jclulow_
alanc: lol
-
jclulow_
I suppose that's how you know you've had a good idea, at least
-
richlowe
if you combine both .Xr and .Lk in a SEE ALSO, it kind gets difficult to read. Do we have an idiomatic way to put a line break in to tidy things up?
-
richlowe
I've used regular old `.sp`, but it feels weird in mdoc
-
andyf
.Pp ?
-
richlowe
I think that's a full paragraph break, rather than just a newline?
-
andyf
mandoc.bsd.lv/mdoc/appendix/markup.html has some notes but it's hard to interpret. `.br` is mentioned
-
richlowe
well, it works as well as `.sp`, and it was mentioned, so I'll do that. thanks!