I guess I interpreted this differently. Just to be clear, do you mean you are connecting to a remote computer, where GRASS resides, from your Mac? Or do you mean your Mac login & home is on a remote OSX server (LDAP), and GRASS is on the local Mac?
If it's a remote connection to GRASS, then it's as Glynn says. You will also have to make sure that the X11 aplication is running. I don't know if you can run it from a Terminal, you may need to use an xterm from X11. Note also that OSX now defaults to the bash shell, so it would be .bashrc/.bash_profile.
If it's an LDAP login, then that doesn't matter. There may be some things to put in the .bash_profile (DISPLAY, PATH), but if you use the OSX .app build of GRASS, this is taken care of for you. GRASS 6.3 has this, and I've ported it over for my 6.2 OSX binaries. It also takes care of making sure that X11 is running and starts the Terminal for you. Just double-click GRASS.app.
With a generic unix build, you'll have to start X11 yourself, and at least "export DISPLAY=:0.0" should be in your .bash_profile.
The X11 frowarding capability brings up an interesting point - when the Python gui is default, and NVIZ doesn't need X11, breaking the ties to X11 (on OSX at least), this won't be possible. A more indirect method, like VNC, will have to be used.
On Aug 21, 2007, at 8:34 AM, Hamish wrote:
Hi Gretchen,
Off and on, for a number of years, I have trying to use GRASS on the
Mac. (I became a little familiar with GIS when ESRI still made
ArcView for the Mac, and created some data that I still need, and
need a better way to update it.) I am again trying to use GRASS (but
it does not come up in the GUI). I need to deal with the fact that my
login is remote from the computer I use. I know that I need to set a
PATH variable somewhere to make GRASS work, but I have virtually no
Unix understanding. I am capable of creating/editing a .tcshrc file
or .cshrc file, but I don't really know what to put in it.
If you are trying to use the GUI remotely from a Mac you might try using -Y:
ssh -Y user@hostname
'xeyes' is a good test if X will get passed over the remote connection.
As long as the remote host is set up correctly I don't think you have to bother
with any PATH or .grass.bashrc / .grass.cshrc files.
Hamish
____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"Time is an illusion - lunchtime doubly so."
- Ford Prefect