Help tracking down a shell problem

Andre Garzia andre at
Thu Oct 20 16:12:07 EDT 2011


The terminal and the shell command are different beasts. On your mac, you
can check some hidden files:


For example, my .profile changes my locale $LANG var.

I think that .profile always load but .bash_profile and .bashrc only loads
then you launch a terminal, but I am guessing. Its been a while since I last
played this kind of game.

Anyway, the shell() executes stuff in "Mac OS X" graphical land, the
terminal is different. For example, IIRC applescript is not available when
the old engine was running on the terminal but was available if you shell().
Its the little things...

On Thu, Oct 20, 2011 at 6:02 PM, Pete <pete at> wrote:

> Posted this a couple of days ago and have also been working with LC support
> on it but no joy.
> If you have a few minutes and are on a Mac, could you execute the following
> code and let me know the results:
> *put* line 1 of shell("defaults read .GlobalPreferences AppleLocale") into
>  $LANG
> *put* uniDecode(uniEncode(shell("locale -k LC_NUMERIC"), "utf8"))
> I'm getting different results in LC than executing the same shell commands
> in Terminal. I get:
> decimal_point="."
> thousands_sep=
> grouping="0"
> If I execute the same locale command in Terminal, the output looks like:
> decimal_point="."
> thousands_sep=","
> grouping="3;3"
> If you could let me know the OS X and LC versions too, that would be great.
> I'm on OS X 10.6.8 and LC 4.6.3
> Thanks,
> Pete
> Molly's Revenge <>
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

-- -- All We Do Is Code. -- minimalist url shortening service.

More information about the Use-livecode mailing list