$PATH word too long

[Erik Wanta]

I am using tcsh. If I have all the Cadence streams and other tools in
$PATH it gets very long and I am running into "word too long"
messages. Does anyone have any advice on how best to deal with this?
---
Erik

 

[Dave]

Erik,

1) Run the tools in smaller groups, with a separate shell for each group.
This will avoid unexpected interactions between two tools that really don't
need to be running in the same shell.
2) Use a script to switch from one setup to another. I can send you the one
I use. It sets up aliases for every setup I need. Type 'cds' and it lists
all the aliases. Type 'cds446' and it strips out all previous Cadence
paths, and adds the new ones for this particular release. Type 'cdsxxx'
<new cds_root> and you can even set a new path "on the fly". This can be
repeated as many times as you like.
3) Use the Cadence Stream Manager. I have never used this, because I'm
happy with my script, and I don't like big "black boxes".

Note: The script is useful, even if you go with strategy 1.

- Dave MacQuigg
macquigg@$$$nospam$$$ece.arizona.edu

"Erik Wanta" <erikwanta@starband.net> wrote in message
news:84018314.0310030705.847979f@posting.google.com...

I am using tcsh. If I have all the Cadence streams and other tools in
$PATH it gets very long and I am running into "word too long"
messages. Does anyone have any advice on how best to deal with this?
---
Erik