stumpwm-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [STUMP] That c-encoding problem again


From: Rohan Nicholls
Subject: Re: [STUMP] That c-encoding problem again
Date: Tue, 24 Mar 2009 10:41:10 +0100

Sorry guys, got busy and so reading lists went by the board.

I actually ended up installing xubuntu due to other issues with
ubuntu, actually more with gnome in various details, but especially
with the stopping of reading .gnomerc, which mean't that stumpwm was
no longer being loaded properly.

On xubuntu everything is working perfectly.  The home directory is
unchanged, and both Eterm and xfterminal are working perfectly.  I
have not had a crash since I made this change.

On Fri, Jan 30, 2009 at 5:01 PM, Jay Belanger <address@hidden> wrote:
>
> Christophe Rhodes <address@hidden> writes:
>
>> Rohan Nicholls <address@hidden> writes:
>>
>>> Seems I have found a solution, more like stumbled on it.  If you set
>>> the LC_ALL and LANG variables before starting sbcl to "UTF-8", it
>>> handles everything properly.
>>
>> This doesn't seem likely to me, I'm afraid.
>
> Regardless of whether or not it should work, I'm wondering if it does
> work.  I switched from sbcl to clisp because the c-encoding problem kept
> causing stumpwm to crash; I have a similar problem with clisp, but at
> least I only get errors and not crashes.
>
>> I'm fairly sure that this is in fact backwards, assuming you meant
>> en_US.UTF-8.
>
> So, Rohan, is it still working?  And did you mean en_US.UTF-8?

Yes, but due to the change above, it is hard to tell what is more
responsible, but I had mean't 'UTF-8', and not the other, which
according to Christophe reverted everything back to 'C', but it did
lead to far fewer crashes.  I am sure Christophe is correct and that
there is a lot more than that going on, but the encoding/LC_* stuff is
such a nightmare, that the less I run into it, the better.  I have
enough problem navigating the unicode/string brokenness in python at
work (seriously, what the hell was Guido van Rossum thinking?). :(

I am wondering if maybe gnome or ubuntu or both were trying to be too
clever, and as a result were making a mess of things for sbcl.  I do
know that a lot of other things that were quirky with gnome are
working perfectly now that I don't have a desktop that tries to
override the various system settings, such as keyboard etc. and makes
such a mess of sound (pulseaudio: yes, we can compound the already
fraught world of linux sound even further!).

Looking at the output from locale, it seems that en_US.UTF-8 is the
standard:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

I know I have stripped all the setting of the LC_* variables in my
xinitrc.stumpwm as well.

I wish I had something more informative to say, but the whole LC_*
world is somewhat beyond me.

Thanks for all the responses,

Rohan




reply via email to

[Prev in Thread] Current Thread [Next in Thread]