comp.lang.idl-pvwave archive - RDF feed
type: channel
description: Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
items: Re: Solarsoft and idlwave?

Re: Solarsoft and idlwave?
type: item
description: BG wrote: > Hey all, > > Just discovering all that is wonderful about idlwave, but running into > a problem. > > My current machine is runs bash. > > My group uses Solarsoft, which has init scripts for IDL that are all > written in csh. > > If I'm sitting on the (Unix) command line, I do something like: > > csh ssw_startup > > Which calls the scripts just fine and I get a SSW> prompt in IDL. > > However, if I feed a script into idlwave as my startup file (e.g.: > > (setq idlwave-shell-explicit-file-name "~/shortcuts/ssw_workaround") > > where ssw_workaround is just a script file that just does this: > > csh ssw_startup > > > Then when I start the IDL shell in Emacs/IDLWAVE I get this: > > > Process idl exited abnormally with code 1 > It works for me, but my solarsoft startup script looks like this: ----------------------------------------------- #!/bin/csh -f # setenv SSW /proj/DataCenter/ssw/ setenv SSW_INSTR "gen hinode xrt sxt hxt bcs trace eit binaries chianti hessi spex xray" source $SSW/gen/setup/setup.ssw # start sswidl sswidl ------------------------------------------------ Maybe you can try something like that and see if it works. Ciao, Paolo > > And my IDL process is toast. > > > Any ideas about this? I think it all has to do with the fact that the > environmental variables in my csh init scripts aren't persisting...but > I haven't been able to come up with a good workaround. > > Cheers, > > Brian
creator: pgrigis
date: 2008-05-23T13:40:43-00:00

Re: Solarsoft and idlwave?
type: item
description: As usual, the simplest thing is the one that works. Thanks! -BG On May 23, 6:40 am, pgri...@gmail.com wrote: > BG wrote: >> Hey all, > >> Just discovering all that is wonderful about idlwave, but running into >> a problem. > >> My current machine is runs bash. > >> My group uses Solarsoft, which has init scripts for IDL that are all >> written in csh. > >> If I'm sitting on the (Unix) command line, I do something like: > >> csh ssw_startup > >> Which calls the scripts just fine and I get a SSW> prompt in IDL. > >> However, if I feed a script into idlwave as my startup file (e.g.: > >> (setq idlwave-shell-explicit-file-name "~/shortcuts/ssw_workaround") > >> where ssw_workaround is just a script file that just does this: > >> csh ssw_startup > >> Then when I start the IDL shell in Emacs/IDLWAVE I get this: > >> Process idl exited abnormally with code 1 > > It works for me, but my solarsoft startup script looks like this: > > ----------------------------------------------- > #!/bin/csh -f > # > > setenv SSW /proj/DataCenter/ssw/ > setenv SSW_INSTR "gen hinode xrt sxt hxt bcs trace eit binaries > chianti hessi spex xray" > source $SSW/gen/setup/setup.ssw > > # start sswidl > sswidl > ------------------------------------------------ > > Maybe you can try something like that and see if it works. > > Ciao, > Paolo > > > >> And my IDL process is toast. > >> Any ideas about this? I think it all has to do with the fact that the >> environmental variables in my csh init scripts aren't persisting...but >> I haven't been able to come up with a good workaround. > >> Cheers, > >> Brian
creator: BG
date: 2008-05-23T18:25:34-00:00