The relationship between /usr/bin/scratch and /usr/bin/squeak is somewhat confused. /usr/bin/scratch has some code to handle VMOPTIONS but it is not actually passed to /usr/bin/squeak. But then if /usr/bin/scratch was passing those to /usr/bin/squeak, that shell script does not handle them. I'd think it might be good to copy the LD_LIBRARY_PATH part of /usr/bin/squeak to /usr/bin/scratch, and the latter does not deal with the former.
What do you guys think?
On Mon, May 16, 2016 at 10:14 AM, Yoshiki Ohshima Yoshiki.Ohshima@acm.org wrote:
On Mon, May 16, 2016 at 10:06 AM, Yoshiki Ohshima Yoshiki.Ohshima@acm.org wrote:
On Mon, May 16, 2016 at 10:04 AM, tim Rowledge tim@rowledge.org wrote:
Forgive me if I’m being hopelessly naive here, but does this text input mechanism work for other languages too? Would it, for example, be usable as an on-screen keyboard for theRaspberry Pi lcd touchscreen?
It should work for any other languages that ibus or scim can handle. Yes, it will be usable with the on-screen keyboard.
So I wrote about two possible options on changes to /usr/bin/scratch; I think that the option that uses the XMODIFIERS environment variable, or some other ways to tell that there is an input method running, is more suitable for this purpose.
-- -- Yoshiki