Re: Support showenv output as shell code

2013-08-12 Thread Aaron Schrab
At 16:59 +1200 13 Aug 2013, Jan Larres wrote: >I use this code in zsh to do the same thing without having to patch >tmux. The preexec variable is an array of functions that get called >before each interactive command execution. I don't think such a variable >exists in bash, but you could hack some

Re: Support showenv output as shell code

2013-08-12 Thread Jan Larres
On 13/08/13 11:56, Aaron Schrab wrote: > Commands running in tmux windows have the values for the variables that > were set when the command was started, but those values can change such > as when a new tmux client attaches. > > My main use case for this is that I run mutt inside of tmux to read my

Re: Support showenv output as shell code

2013-08-12 Thread Aaron Schrab
At 00:11 +0100 13 Aug 2013, Thomas Adam wrote: >On Mon, Aug 12, 2013 at 04:01:46PM -0400, Aaron Schrab wrote: >> Add -s option to the shown-environment command which will alter the >> output format to Bourne shell commands, allowing import of the >> environment into current shell with: > >What use

Re: [PATCH] Support showenv output as shell code

2013-08-12 Thread Thomas Adam
On Mon, Aug 12, 2013 at 04:01:46PM -0400, Aaron Schrab wrote: > Add -s option to the shown-environment command which will alter the > output format to Bourne shell commands, allowing import of the > environment into current shell with: What use-case is this for? Note that "current shell" is reall

[PATCH] Support showenv output as shell code

2013-08-12 Thread Aaron Schrab
Add -s option to the shown-environment command which will alter the output format to Bourne shell commands, allowing import of the environment into current shell with: eval `tmux showenv -s` --- cmd-show-environment.c | 59 ++-- tmux.1