On Sun, Mar 18, 2007 at 01:05:37PM +0000, Tuomo Valkonen wrote: > On 2007-03-18, Joerg van den Hoff <[EMAIL PROTECTED]> wrote: > > that's how `mutt' dynamically adjusts it's help pages. I think that is good, > > but even better would be augmenting this by parenthesis a la "(changed from > > default definition xxx)" so that one could incrementally restore default > > bindings easily if need be. > > It's not doable reliably in the function call based configuration of > Ion. You'd have to work with a fixed set of command instead, and define > a command for every action that the user might want to do, in addition > to providing the scripting API. It's extra work that I don't want at > this point, the Ion architechture being what it is, although the menu > system does already have some "commands".
I do not quite understand (or not at all?): even if one can in principle use the function call based configuration to do 'arbitrary' things, as it stands, it seems not illegitimate for a user to read the files in ~/.ion3 as "static config-files with a strange syntax". my point is simply that at least for a start it does not harm to approach it in that way and tell the new user: "if you want to change shortcut x, modify the corresponding line in file y". so what exactly do you mean by 'not doable reliably'? could it not at least be done in a "justifable" way? > > Now, if someone wants to provide an alternative configuration system > on top of the scripting API, go ahead... for ion3plus perhaps. Although, > the proper place for such command sets is Vis... [1] > > > I agree: scratchpad as the sole location is no good for this. but why not > > make > > it available instead of the ion3-manpage with MOD1-F1? the manpage everyone > > will be able to access otherwisei -- be it via F1 (where it is the default > > anyway), be it via some xterm. > > Maybe you want to improve the man page? I have no real issue with the manpage in its present form, although it is _very_ terse and probably not that helpful for first time users (afterwards it serves as a memo for forgotten keyboard shortcuts). I thought the discussion related to where one should put additional documentation/tutorial stuff. but of course one could put that in the manpage as well (the 'bash approach'). I'm not sure whether that's the best way. joerg
