Re: [dev] noice and NetBSD curses

2018-08-07 Thread Cág
Silvan Jegen wrote: > I thought that maybe one of the programs is linked against the > non-"...w" variant of the curses library (i. e. "libncurses" instead > of "libncursesw") but it turns out that NetBSD's curses library does > not have this separation at all. Interesting stuff. Some programs, l

Re: [dev] noice and NetBSD curses

2018-08-07 Thread Cág
Silvan Jegen wrote: > I thought that maybe one of the programs is linked against the > non-"...w" variant of the curses library (i. e. "libncurses" instead > of "libncursesw") but it turns out that NetBSD's curses library does > not have this separation at all. Interesting stuff. It can handle wi

Re: [dev] noice and NetBSD curses

2018-08-07 Thread Silvan Jegen
On Sun, Aug 5, 2018 at 4:56 PM, Cág wrote: > Silvan Jegen wrote: > >> I have the same locale set up (LANG=en_US.UTF-8) and on my (Linux) >> machine, both rover and noice (compiled from tip) show the "früh.mp3" >> filename correctly without me having to set LC_ALL=C. > > Keep in mind, this is NetBS

Re: [dev] noice and NetBSD curses

2018-08-05 Thread Cág
Silvan Jegen wrote: > I have the same locale set up (LANG=en_US.UTF-8) and on my (Linux) > machine, both rover and noice (compiled from tip) show the "früh.mp3" > filename correctly without me having to set LC_ALL=C. Keep in mind, this is NetBSD with its own curses library. It was suggested that

Re: [dev] noice and NetBSD curses

2018-08-02 Thread Silvan Jegen
On Wed, Aug 1, 2018 at 11:55 PM, Cág wrote: > Silvan Jegen wrote: > >> What does running 'locale' print on both machines? > > Mine's are all en_US.UTF-8, except for LC_COLLATE. I don't set anything > other than LANG in profile. I have the same locale set up (LANG=en_US.UTF-8) and on my (Linux) ma

Re: [dev] noice and NetBSD curses

2018-08-01 Thread Cág
Silvan Jegen wrote: > What does running 'locale' print on both machines? Mine's are all en_US.UTF-8, except for LC_COLLATE. I don't set anything other than LANG in profile. -- caóc

Re: [dev] noice and NetBSD curses

2018-08-01 Thread Cág
Hiltjo Posthuma wrote: > Maybe setlocale(LC_CTYPE, ""), not sure if that is correct. You could > technically mix different locales in filenames or use (almost) any byte > sequence though. rover, which I mentioned in the OP, has it too: https://github.com/lecram/rover/blob/master/rover.c#L405 --

Re: [dev] noice and NetBSD curses

2018-08-01 Thread Silvan Jegen
On Wed, Aug 01, 2018 at 05:29:14PM +0200, Hiltjo Posthuma wrote: > On Wed, Aug 01, 2018 at 11:57:38AM +0200, Silvan Jegen wrote: > > On Wed, Aug 01, 2018 at 09:55:16AM +0200, Hiltjo Posthuma wrote: > > > On Tue, Jul 31, 2018 at 04:35:30PM -0500, Cág wrote: > > > > Hey, > > > > > > > > The thread i

Re: [dev] noice and NetBSD curses

2018-08-01 Thread Hiltjo Posthuma
On Wed, Aug 01, 2018 at 11:57:38AM +0200, Silvan Jegen wrote: > On Wed, Aug 01, 2018 at 09:55:16AM +0200, Hiltjo Posthuma wrote: > > On Tue, Jul 31, 2018 at 04:35:30PM -0500, Cág wrote: > > > Hey, > > > > > > The thread is here[0], and I guess this is more of curses problem, but > > > since I firs

Re: [dev] noice and NetBSD curses

2018-08-01 Thread Silvan Jegen
On Wed, Aug 01, 2018 at 09:55:16AM +0200, Hiltjo Posthuma wrote: > On Tue, Jul 31, 2018 at 04:35:30PM -0500, Cág wrote: > > Hey, > > > > The thread is here[0], and I guess this is more of curses problem, but > > since I first noticed it with noice, here it is. > > > > The question: what do rover

Re: [dev] noice and NetBSD curses

2018-08-01 Thread Hiltjo Posthuma
On Tue, Jul 31, 2018 at 04:35:30PM -0500, Cág wrote: > Hey, > > The thread is here[0], and I guess this is more of curses problem, but > since I first noticed it with noice, here it is. > > The question: what do rover and noice do differently, that the former > displays Unicode filenames right, a

[dev] noice and NetBSD curses

2018-07-31 Thread Cág
Hey, The thread is here[0], and I guess this is more of curses problem, but since I first noticed it with noice, here it is. The question: what do rover and noice do differently, that the former displays Unicode filenames right, and the latter only under the LC_ALL=C local. P.S. 2f30 guise pleas