Re: [Ebib-users] Ebib 0.25 released!
Brought to you by:
joostkremers
From: Steve Y. <st...@sx...> - 2006-08-19 07:09:07
|
* Joost Kremers <joo...@fa...> writes: > Hi list, Hi list-owner! :-) > The new version incorporates two suggestions made by Jesse: first, > the command keys are now customisable. In what way were they not customisable before? > Note that the key definitions are now all in .ebibrc. That means > that if you install the new version, you must also copy the new > ebibrc to your HOME dir (or at least copy the key definitions to > your existing .ebibrc), otherwise no command keys will be defined. Wow, this is an incredibly _bad_ idea. Why are you leaving the responsibility of default key bindings up to the user? What happens to the poor user that downloads the Ebib dist tarball, installs, and then deletes the tarball. Then one day, disaster strikes and he blows away his ${HOME}[1]... I also don't see any benefit or point to the `ebib-key' macro. Isn't... (define-key ebib-foo-map [(control c) x] #'foo-function) ...good enough? > I've added a few key bindings, so that C-p, C-n and M-p, M-n now > do what one would expect in Emacs. That's great, except you haven't defined M-p/M-n, you've defined A-p/A-n. Alt !=3D Meta. They quite often are the same key, but not necessarily. (define-key ebib-foo-map [(meta n)] #'foo-function) Is a totally different binding than... (define-key ebib-foo-map [(alt n)] #'foo-function) You can even use them both in the one binding... (define-key ebib-foo-map [(alt meta n)] #'foo-function) > Jesse made a few other suggestions, that I'm considering > incorporating. One thing I think I won't do, is to use Emacs' > standard customisation interface (M-x customize) for Ebib. I'm not sure how much of Ebib is customisable, but I think this is a mistak= e. > Personally, I don't really like this interface, Neither do I. > and the elisp code it generates is so cluttered that it can hardly be > modified by hand.=20 The type of user that relies on `M-x customize' is most likely _not_ the type of user to look at, or want to modify what it generates. :-) > Plus, I feel that the little customisation that Ebib might need > can easily be handled through .ebibrc.=20 OK, I'm heading off on a bit of a tangent here, but, from what I can see, there isn't anything in .ebibrc that couldn't be left in ebib.el. I don't see the need to have an rc file. Couldn't you just state in the manual... "if you want to add your own entry types, put (defentry foo-entry (...)) into your init.el/.emacs" ? Actually, I'd be inclined to turn those `defentry's into `defcustom's, although I'm not quite sure how hard that would be. :-) > (I'm of course open to counter-arguments on this point, so please > let me know if you feel differently.) The counter argument is that _all_ user-configurable variables should be defined with `defcustom'. One last tangent before I finish... Why oh why isn't the manual in Texinfo format? From there you could generate your PDF and HTML, while the rest of us can read the Ebib manual inside our emacs in info. :-) Footnotes:=20 [1] Don't laugh, I've done it. :-( =2D-=20 |---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---| | I am Dyslexic of Borg. |=20 | Fusistance is retile. Your arse will be laminated. | |------------------------------------<st...@sx...>---| |