[STUMP] Re: Problems with SCIM et al` (A.W.)

[A . W .]

Suddenly it started working.
The popup widget...doesn't, but I think I tried disabling that last session.
In any case, it works, but not from startx...on sidux.
scim is very non-standard in the way different distros implement it.
Ubuntu(which prides itself on internationalisation) is notably harder
to get working with it, and much clumsier in implementation.
My point is, there's not one clear solution to dealing with this, sadly.

I'll probably write up a wiki entry on making a stumpwm.desktop file
etc. just for such occasions.


On Sun, May 18, 2008 at 11:25 PM, A. W. <address@hidden> wrote:
> I've eliminated problems related to using startx VS KDM by adding a
> (detailed, and nearly identical) entry for stumpwm in my available
> window managers for KDM.
> I've reset the machine to eliminate... well, I'm not sure, but when
> all else fails.
> xorg has been reconfigured by dpkg, so that's not it, either.
>
> scim either exits abnormally, segfaults, or fails to start a front end
> and then fails entirely. Awesome worked with it, and I had no problems
> with big, fat(but fun) KDE either.
>
> *shrug*
>
> I can only guess as to what would cause it, but, well, I figured I'd
> let you know. This isn't a deal-breaker for me, as I can always do a
> mad dash of emails etc in an Awesome session,
> ;;Gushing
>  but I much(MUCH!) prefer StumpWM, from the configuration method to
> the more sophisticated (if less instantly fancy) frame management. The
> ability to use Java applications is a big plus over other tiling
> WMs(if caused by a bug in the JVM...) as well.
> ;;rationale for caring so much
> This will be a deal breaker for people in Asian countries, however.
> Possibly other regions as well, but I'm not sure. Their keyboard
> layouts etc are unknown to me.
> Without the ability to easily switch between coding(standard 'roman'
> characters and punctuation) and communicating (native language input)
> they're unlikely to use it.
>