122 reputation
5
bio website
location
age
visits member for 2 years, 2 months
seen Dec 10 at 12:50

Dec
10
accepted calling Bash Function from alias definition
Dec
10
comment calling Bash Function from alias definition
While I think that I will go for the subshell option (seems best), the solution you suggest ommits the case where I run ise and analyzer. It only removes one alias, meaning the script will get sourced a second time if i run those two commands one after another.
Dec
9
comment calling Bash Function from alias definition
So how do I work arround the subshell issue? After all I want the addition to the list to be executed. I think adding the iseAlias will help me to get arround the subshell but in general how do I do something like VAR=resultOfFunction X where I execute the resultOfFunction in the same bash but only at definition time?
Dec
9
awarded  Commentator
Dec
9
comment calling Bash Function from alias definition
@HaukeLaging: fixed the typo. will check the updated answer now.
Dec
9
revised calling Bash Function from alias definition
added 2 characters in body
Dec
9
comment calling Bash Function from alias definition
I think I sort of get the problem with iseRemoveSetup beeing empty at the time analyzer is defined. However I do not know why iseRemoveSetup also shows as empty on the bash after freshly starting it (it should update?). While I might invesitgate arrays (I am new to bash scripting), I wonder if I can then call a function from the alias to do the cleanup of alias when the alias is invoked. The funciton would be called at the time I execute the alias if I put it as litteral text, right?
Dec
9
comment calling Bash Function from alias definition
I do need the unalias, since it basically turns source /setupscript/;tool into tool. otherwise a second start of the tool would source the setup script again.
Dec
9
comment calling Bash Function from alias definition
@HaukeLaging: I only need to run source /home/ted/... once after that my path is fixed to include the tools. Therefore just running analyzer is enough, no need to source again. The script also adds older libraries to the linker path and some programs cant deal with these older libraries.
Dec
9
asked calling Bash Function from alias definition
Dec
9
comment Extend one alias in second alias
why not use alias ls instead of alias -p|grep '^alias ls='?
Oct
8
revised less does not show expected output after sourcing a script in .cshrc
added relevant text from external site
Oct
8
awarded  Scholar
Oct
8
comment less does not show expected output after sourcing a script in .cshrc
I have to accept this awnser unchecked since I no longer work on the relevant system or have access to it. I took the freedom to quote the link. Cheers
Oct
8
accepted less does not show expected output after sourcing a script in .cshrc
Oct
8
suggested approved edit on less does not show expected output after sourcing a script in .cshrc
Jul
26
awarded  Student
Apr
3
awarded  Supporter
Mar
31
comment less does not show expected output after sourcing a script in .cshrc
However I don't see why my souricngtriggers this behaviour
Mar
31
revised less does not show expected output after sourcing a script in .cshrc
added 1641 characters in body