Re: Problem wih characters (was Problem with IME)

From: Bart Mathias (mathias_at_hawaii.edu)
Date: 02/27/05 

Date: Sun, 27 Feb 2005 01:35:11 GMT

jim_breen@hotmail.com wrote:
> [...]
> OK. Two possibilities:

I have an idea these are the same things Timmy Douglas suggested, except
I understand it a little better stated as follows.

> (a) use the "env" utility, i.e. put something like:
>
> /usr/bin/env LANG=ja_JP.UTF-8 /usr/bin/mozilla
>
> in the Command box;

OK, that worked nicely. I would never have been able to figure it out
for myself; I've been using Linux for almost two years now, and never
even *heard* of an "env" utility. (I have now looked at the manual;
apparently I can run any program I could start from the shell in a
LANG=ja_JP.UTF-8 environment, although I suspect it wouldn't have any
effect on most. [I'd better save this before I experiment with ~$ env
LANG=ja_JP.UTF-8 vi.] OK, I didn't think vi would like Japanese. But
it didn't work with AbiWord either, in spite of the fact that any .doc
attachment I open from Mozilla brings AbiWord up in broken Japanese!)

I'm also so ignorant that I have no idea how to do the following, or it
would have been my first choice.

> (b) write a little script like:
>
> #!/bin/bash
> LANG=ja_JP.UTF-8 /usr/bin/mozilla
>
> and put its name in the Command box.

I don't get what the first line could do. Doesn't the "#" cause it to
be ignored? (I guess not! When I tried running it in a shell, it came
out like this:

bart@AmigaOne:~$ #!/bin/bash
bash: !/bin/bash: event not found

The "!" looks like what I've been using to start Mozilla from the shell:
 "!L<return>."

Neither my Unix manual (which doesn't know anything about environments
but "set") nor my Linux manual (which doesn't even index "env" or
"environment") is very informative about where I should put a script
file after I write it.

But I am going to study Tobias Diedrich's suggestion very hard. I just
hope I live long enough to understand it.

Thanks, Jim (and Timmy and Tobias),

Bart

Relevant Pages

  • Re: Call for input on comp.unix.shell FAQ
    ... SHELL needs to be in the environment. ...
    (comp.unix.shell)
  • Re: how to view environment variables
    ... > sysutils/fusefs-ntfs/files/README.FreeBSD refers to various environment> variables, ... current shell. ... It does indeed print environment variables set with 'env VAR=foo prog' but as I've now understood from previous replies the program doesn't set variables, it uses them if they are already set, otherwise uses defaults. ...
    (freebsd-questions)
  • Re: define and assignment
    ... which draws environment models as the user types ... Memory locations are the addresses of objects. ... void define(symbol sym, expression expr, environment env) ... location set!(symbol sym, expression expr, environment env) ...
    (comp.lang.scheme)
  • Re: Windows env-Bug?
    ... Tcl could initialize::env from the system environment ... forward informations to subprocesses and change information on current ... The "current process level" arguments is discussed controversly, ...
    (comp.lang.tcl)
  • Re: Process Understanding
    ... their environment, especially env variables. ... the that one user has a bash shell while the other has no shell ... The environment variables are read by software commands. ... Now when you execute the source command again, ...
    (Fedora)