search for: _clear_

...dering that there is no "new" proposed action, breaking the > current behavior would be questionable for users that are already > taking advantage of it. > I am not against changing behaviors (sometimes, it is worth), but > IMHO breaking a current behavior has to bring a very _clear_ gain, > while such change should be as less traumatic as possible for current > users. In my opinion, this would be better addressed with a conditional directive than an outright change in current behavior. Since it only affects (vesa)menu.c32, it should begin with "MENU ", perhap...

...quot;new" proposed action, breaking the > > current behavior would be questionable for users that are already > > taking advantage of it. > > > I am not against changing behaviors (sometimes, it is worth), but > > IMHO breaking a current behavior has to bring a very _clear_ gain, > > while such change should be as less traumatic as possible for current > > users. > > In my opinion, this would be better addressed with a conditional > directive than an outright change in current behavior. Since it only > affects (vesa)menu.c32, it should begin...

...on the menu level. The Syslinux command line interface has its own (different) behavior for (these and other) keys. See http://www.syslinux.org/wiki/index.php/Cli#Keystrokes . I am not against changing behaviors (sometimes, it is worth), but IMHO breaking a current behavior has to bring a very _clear_ gain, while such change should be as less traumatic as possible for current users. Regards, Ady.

...osed action, breaking the >> > current behavior would be questionable for users that are already >> > taking advantage of it. >> >> > I am not against changing behaviors (sometimes, it is worth), but >> > IMHO breaking a current behavior has to bring a very _clear_ gain, >> > while such change should be as less traumatic as possible for current >> > users. >> >> In my opinion, this would be better addressed with a conditional >> directive than an outright change in current behavior. Since it only >> affects (vesa)men...

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 could be done with fingers stationed on the arrow keys so that the eyes can stay focused on the screen. Current

...g the >>> > current behavior would be questionable for users that are already >>> > taking advantage of it. >>> >>> > I am not against changing behaviors (sometimes, it is worth), but >>> > IMHO breaking a current behavior has to bring a very _clear_ gain, >>> > while such change should be as less traumatic as possible for current >>> > users. >>> >>> In my opinion, this would be better addressed with a conditional >>> directive than an outright change in current behavior. Since it only >&g...

...ere's absolutely no reason in the world -- none! -- that you can't have _clarity_ and _user_convenience_... indeed, i see those two as working hand-in-hand... the easiest thing for the user to handle is a clear model. the hardest thing is to juggle two ambiguous models. even juggling two _clear_ models is somewhat difficult. but one clear model, especially a simple one? _easy_. > Another problem is that the majority of Markdown.pl > derivatives are implemented as a long series of > global substitutions running on the full document i have done things that way. it...