You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and plain Internal Server Error results in the browser.
As a workaround, I start with RUBYOPT="-KU -E utf-8:utf-8" kdwatch or LC_ALL="en_GB.UTF-8" kdwatch or LC_ALL="C.UTF8: kdwatch, which makes things work better. (Setting LC_ALL to en_US.UTF-8 was insufficient, probably because that locale is not built on my system).
I think that my work environment is all set up for UTF-8 (which, really, all system should have been for ages):
Operating system is Debian GNU/Linux sid, in a setup that only builds the en_GB.UTF-8 (and a few selected other) locales.
I think that this is related to the ENV["LANG"]="en_US.utf-8" workaround on top of bin/kdwatch -- this sets the default to some (on my system), which I can override by setting LC_ALL.
Quite possibly, the workaround has become obsolete anyway; if it has not, C.UTF-8 might be a suitable replacement (as it should be available no matter which locales are built).
The text was updated successfully, but these errors were encountered:
(Proposed resolution at the end, full story for reference)
On my system I get errors like this:
and plain Internal Server Error results in the browser.
As a workaround, I start with
RUBYOPT="-KU -E utf-8:utf-8" kdwatch
orLC_ALL="en_GB.UTF-8" kdwatch
orLC_ALL="C.UTF8: kdwatch
, which makes things work better. (Setting LC_ALL to en_US.UTF-8 was insufficient, probably because that locale is not built on my system).I think that my work environment is all set up for UTF-8 (which, really, all system should have been for ages):
Operating system is Debian GNU/Linux sid, in a setup that only builds the en_GB.UTF-8 (and a few selected other) locales.
I think that this is related to the
ENV["LANG"]="en_US.utf-8"
workaround on top of bin/kdwatch -- this sets the default to some (on my system), which I can override by setting LC_ALL.Quite possibly, the workaround has become obsolete anyway; if it has not,
C.UTF-8
might be a suitable replacement (as it should be available no matter which locales are built).The text was updated successfully, but these errors were encountered: