Nicholas Marriott <nicholas.marri...@gmail.com> wrote: > If you start PWD with it already in the environment, it is marked as > exported - this is the same as any other variable:
Ah, ok. Anyway it shows that ksh uses $PWD as any other shell, even though it doesn't export it by default. > For your use, you want to be able to add * to > update-environment. Particularly if that included PWD too. > > * should match anything, -* should remove anything in the new but not > global environment add an unset (-FOO) for anything that is in the > global environment but not the new. Ok, that sounds reasonable. So you're suggesting to extend update-environment to include a filter (i.e. removing elements from the environment for a session). But there would also be a different list of environment variables to be updated for new sessions than for attaching to an existing session. For the $PWD part: you'd suggest to use $PWD instead of all the cwd member? This would also mean that windows have their own environment as the PWD should not be changed. What about the default-path option? Imo it is just redundant to the global PWD value or the session PWD value. Do you agree that the value of $PWD should be copied from the surrounding environment, if it points to the correct directory? ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
