| Re: Permanently changing shell [message #37411 is a reply to message #37241] |
Fri, 12 December 2003 17:50  |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Fri, 12 Dec 2003 17:49:06 -0700, Patrick Ford wrote:
> Reimar Bauer <R.Bauer@fz-juelich.de> wrote in message
> news:<br1e7r$bk86$1@zam602.zam.kfa-juelich.de>...
>> Patrick Ford wrote:
>>> Greetings:
>>>
>>> I upgraded to MacOS 10.3 (Panther) last night and IDL got trashed. In
>>> the processed of reinstalling it, including all the Unix config
>>> files/scripts, I discovered that the shell had be changed to bash
>>> from the tsch that it had been. Since my Unix skills are limited and
>>> since the info pages at rsinc.com are written for the tsch shell I am
>>> at an impass.
>>>
>>> I need to know how to reset the default shell and get the scripts
>>> reset. I think I do the latter by editing the .cshrc and .tcshrc
>>> file in the Users/MyDir/ to include:
>>>
>>> source RSI-DIR/idl_6.0/bin/idl_setup
>>>
>>>
>>> and/or find out where .bashrc file is and how to set its script for
>>> the equivalent of the above command.
>>>
>>>
>>> Thanks
>>>
>>> Patrick Ford
>>
>> Dear Patrick
>>
>> on linux I have always to use ksh (pdksh) to run this install scripts.
>>
>> If you know it runs with tsch you could run it by
>>
>>> tsch RSI-DIR/idl_6.0/bin/idl_setup
>>
>> If this is the only reason to change the shell I think this is not
>> necessary.
>>
>> Reimar
>>
>> --
>> Reimar Bauer
>>
>> Institut fuer Stratosphaerische Chemie (ICG-I) Forschungszentrum
>> Juelich
>> email: R.Bauer@fz-juelich.de
>> ------------------------------------------------------------ -------
>> a IDL library at ForschungsZentrum Juelich
>> http://www.fz-juelich.de/icg/icg-i/idl_icglib/idl_lib_intro. html
>> ============================================================ =======
>
>
> I thought I would give the bash shell a try. (Please keep in mind that I
> am a unix novice or, in other words, I don't know what I am doing.) Both
> methods on how to alter the shell permanently work. Thanks!
>
> Going back the the bash shell, the suggestes cmd line does the
> following:
>
> $ tsch RSI-DIR/idl_6.0/bin/idl_setup
> -bash: tsch: command not found
>
> idl does have a bash script at idl_6.0/bin
>
>
> Patrick-Fords-Computer:/idl_6.0/bin patrickford$ more idl_setup.bash #
> Bash shell commands to define IDL environment variables and aliases. # #
> This script can be used by IDL users who use Bash as their interactive
> shell
> # to define the environment variables and aliases required by IDL #
> related commands (idl, idlde, idlhelp, idldemo) if the symbolic links to
> # the default directory (/usr/local/rsi/idl) are not being used. # #
> Bash users should run idl_setup from their .profile file # using the
> following command:
> #
> # . /usr/local/rsi/idl_6.0/bin/idl_setup.bash #
> RSI_DIR=/usr/local/rsi
> IDL_DIR=/usr/local/rsi/idl_6.0
> export IDL_DIR RSI_DIR
> alias rsilicense=$IDL_DIR/bin/rsilicense alias idl=$IDL_DIR/bin/idl
> alias idlde=$IDL_DIR/bin/idlde
> alias idldeclient=$IDL_DIR/bin/idldeclient alias
> idlhelp=$IDL_DIR/bin/idlhelp
> alias idlman=$IDL_DIR/bin/idlman
> alias idlrpc=$IDL_DIR/bin/idlrpc
> alias idldemo=$IDL_DIR/bin/idldemo
> ___________________________________
>
> Trying a variety of different paths to run it, I get the same basic
> message:
> $ idl_setup.bash
> -bash: idl_setup.bash: command not found
>
> Usually this turns out to be some trivial solution, but I don't yet know
> what I am doing wrong here. I thought I could invoke a script by typing
> in its name into the shell while I was in that directory.
>
> Clues appreciated. Thanks in advance.
This isn't a script, its just a list of commands. In bash and other
Bourne-like-shells you can "source" (i.e. run) this list of commands
using ".", i.e.
$ . idl_setup.bash
Shell scripts start with "#!/bin/bash", or something like this; think of
it like the distinction in IDL between files you can "@" and files you
can ".run".
A better method might be to make your own set of aliases and environment
variables in a .bashrc or the equivalent startup file. I also like to
make IDL_DIR just be "idl" which is a symbolic link to idl_6.0, etc.
This facilitates running multiple versions of IDL in the "probation"
period when new releases come out.
Good luck,
JD
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
