On 11/05/2014 01:53 PM, Siteshwar wrote: > If you fork a new fish process it will have different environment > then it's parent process for e.g. local and global variables which > are not exported are not available to new fish process. So this > approach may or may not work depending on user requirements. You can > add it to the bug report if you like.
Good point. A new fish shell (process) will not be able to share all shell variables: Unexported variables will be invisible to a new fish process. Exported variables will be visible to a new fish process, but any changes made to them in the child process will not affect the parent process. Universal fish variables would be able to be shared in both directions, I think. My suggestion is intended as a work-around rather than an ideal solution. ------------------------------------------------------------------------------ _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
