On Wed, 30 Jul 2008 16:29:29 -0500 Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx> wrote: > Wow. F10 works now. Thanks. I'd forgotten to update the CONFIGURATION document. For a "complex" binding, you do not have to use <custom command> stuff any more, but can simply enter stuff in the action field. > Your question about variables becoming external is moving towards the > lines of setenv. > My environment uses env variables in places for tools and processes. So > now I have > to leave FM2 and set the environment (using xterm) and then open FM2 again. My previous post was not entirely clear. The added 'set'-related commands set/clear variables in the shell in which e2 is running (it can be run as a daemon, not sure if that affects things). The question then becomes: should e2 still support internal variables (for reasons other than backward-compatibility, anyway). Regards Tom > > On another matter you raised, svn code now handles commands: > > set, set A B, set A=B, set A, set A= > > with optional whitespace around any '='. > > > > I need to think about whether an internal variable should automatically > > also become an external one, or even whether to abandon internal ones > > completely, in which case whether to discard the 'set' syntax again. -- Users can unsubscribe from the list by sending email to emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by logging into the web interface.