OK, I withdraw my opposition to fixing this issue in org - by my criticism toward the way markdown.el defines this hook remains.
- Carsten On 20 dec. 2012, at 09:01, Carsten Dominik <[email protected]> wrote: > > On 18.12.2012, at 18:56, Achim Gratz <[email protected]> wrote: > >> Carsten Dominik writes: >>> Well this is very safe - but if you have to assume that every elisp >>> command does change match data behind your back, you would have to >>> create a lot of extra code. >> >> Stefan Monnier advises the opposite (quote from >> http://article.gmane.org/gmane.emacs.bugs/68688 ): >> >> --8<---------------cut here---------------start------------->8--- >>> Okay. On second though: it wouldn't be very useful to use the match >>> data set by these functions. Why not save the match-data here once so >>> that no caller has to ever worry about it? Is there a general policy >>> that this kinda thing shouldn't be done? >> >> Yes, the general policy is: all functions should be presumed to trash >> the match-data, except for a very few exceptions. >> --8<---------------cut here---------------end--------------->8--- > > I am sure that Stefan would consider backward-delete-charater > such an exception, if you ask him directly. > > - Carsten > >> >> >> Regards, >> Achim. >> -- >> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ >> >> SD adaptation for Waldorf rackAttack V1.04R1: >> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada >> >> > -- The graveyard is filled with indispensible people. -- Julia Sweeney's mother
