From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: orgtbl-mode and markdown Date: Fri, 21 Dec 2012 11:53:27 +0100 Message-ID: <950BEDE9-836D-41C2-BEBE-3D92DBD5B245@gmail.com> References: <1ssj73bvzr.fsf@voll.uninett.no> <1sbodrbhsl.fsf@voll.uninett.no> <66FAEC7A-9437-4ACD-A61E-4841AB8668EF@gmail.com> <87a9tbi6r0.fsf@Rainer.invalid> <417EF3F0-EB5E-4EE2-B800-FA2C9C7B6E43@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59319) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tm0EW-0001wA-QG for emacs-orgmode@gnu.org; Fri, 21 Dec 2012 05:53:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tm0EQ-0007Mp-Rx for emacs-orgmode@gnu.org; Fri, 21 Dec 2012 05:53:40 -0500 Received: from mail-ee0-f51.google.com ([74.125.83.51]:39961) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tm0EQ-0007MX-Li for emacs-orgmode@gnu.org; Fri, 21 Dec 2012 05:53:34 -0500 Received: by mail-ee0-f51.google.com with SMTP id d4so2262319eek.38 for ; Fri, 21 Dec 2012 02:53:32 -0800 (PST) In-Reply-To: <417EF3F0-EB5E-4EE2-B800-FA2C9C7B6E43@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org 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 = wrote: >=20 > On 18.12.2012, at 18:56, Achim Gratz wrote: >=20 >> 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. >>=20 >> Stefan Monnier advises the opposite (quote from >> http://article.gmane.org/gmane.emacs.bugs/68688 ): >>=20 >> --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? >>=20 >> 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--- >=20 > I am sure that Stefan would consider backward-delete-charater > such an exception, if you ask him directly. >=20 > - Carsten >=20 >>=20 >>=20 >> Regards, >> Achim. >> --=20 >> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ >>=20 >> SD adaptation for Waldorf rackAttack V1.04R1: >> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada >>=20 >>=20 >=20 --=20 The graveyard is filled with indispensible people. -- Julia Sweeney's = mother