search for: _parameter_

...uture). It should also accept 1 optional parameter to turn it on >> or off. When not present, it should turn the new behavior on. >> >> -- >> -Gene > > > What exactly do you mean with "When not present, it should turn the > new behavior on"? When the _parameter_ is not present. -- -Gene

...parameter to turn it on >>> or off. When not present, it should turn the new behavior on. >>> >>> -- >>> -Gene >> >> >> What exactly do you mean with "When not present, it should turn the >> new behavior on"? > > When the _parameter_ is not present. I just saw this and thought I should kibitz. How about have a way to explicitly map keys to behaviors and just default the keys to their current behavior. The implementation would be an extra table lookup (no matter the mapping) it gives power to accomodate everyone's peculia...

On 09/22/2014 07:03 PM, Eric W. Biederman wrote: >>> >>> What exactly do you mean with "When not present, it should turn the >>> new behavior on"? >> >> When the _parameter_ is not present. > > I just saw this and thought I should kibitz. > > How about have a way to explicitly map keys to behaviors and just > default the keys to their current behavior. > > The implementation would be an extra table lookup (no matter the > mapping) it gives po...

> On Thu, Sep 11, 2014 at 4:09 PM, Ady <ady-sf at hotmail.com> wrote: > > >> Since keystrokes were brought up, this seems like a reasonable time to > >> make the following seemingly simple-to-implement feature request: > >> > >> Navigating a multi-level menu structure seems to require use of > >> UP/DOWN/ENTER/ESC. It would be easier to

On Thu, Sep 11, 2014 at 4:09 PM, Ady <ady-sf at hotmail.com> wrote: >> Since keystrokes were brought up, this seems like a reasonable time to >> make the following seemingly simple-to-implement feature request: >> >> Navigating a multi-level menu structure seems to require use of >> UP/DOWN/ENTER/ESC. It would be easier to quickly search/navigate if it >>