RE: Readings for an emacs package maintainer ?

["Drew Adams" <drew.adams@oracle.com>]

> > There are other tips in the Elisp manual, node Coding
> > Conventions. These, for instance:
...
> It's funny that I pointed Xavier to this very node in March 2008 when
> reporting such a bug in color-theme (see https://gna.org/bugs/?9494)
> which overwrites `replace-in-string' in an incompatible way which
> breaks Gnus, Muse, emacs-jabber, etc.  Unfortunately Xavier didn't fix
> this up to now, AFAIK.

Dunno about that particular context, but I like to remember that guidelines are,
well just guidelines. They are meant to help, and they help more if reasons are
provide, so people can understand them.

My feeling is that advice should be freely given, with nothing expected in
return. It is unreasonable to expect someone to follow some advice you give, no
matter how well intentioned you are, and no matter how good the advice might be.
If there is such an expectation, then it is not advice that you give, but
something else.

I myself do redefine some Emacs functions, and I occasionally do use `defadvice'
(though I avoid it). I have my reasons. But I have no problem with someone
giving me advice not to do so. And I agree with the manual's guidelines.

They are only guidelines, however, which means (1) They are likely to be helpful
_in general_. (2) Use your own judgment: use them when you want to; ignore them
when you want to.