From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: Problem with org-entities-user Date: Sun, 23 Sep 2012 08:18:31 -1000 Message-ID: References: <87k3vtgnhy.fsf@gmail.com> <87sjaeduh5.fsf@gmail.com> <7CC1FB98-B071-429C-A230-B91D461104FD@gmail.com> <87d31idn1v.fsf@gmail.com> <2A730922-8F3C-4CEC-ACFA-AF04E6FF7DAB@gmail.com> <87zk4kdi0e.fsf@gmail.com> <8AE329E8-EE0F-45CB-B8FE-96A98EDEBE9E@gmail.com> <87sjaacucx.fsf@gmail.com> <87mx0hb0q5.fsf@gmail.com> <0FD2FC08-F999-4CE7-A5D4-E86CD2CF9436@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:51433) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TFqlL-0006sb-Oz for emacs-orgmode@gnu.org; Sun, 23 Sep 2012 14:18:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TFqlK-0000Hb-MM for emacs-orgmode@gnu.org; Sun, 23 Sep 2012 14:18:39 -0400 Received: from oproxy9.bluehost.com ([69.89.24.6]:55580) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1TFqlK-0000HU-CB for emacs-orgmode@gnu.org; Sun, 23 Sep 2012 14:18:38 -0400 In-Reply-To: <0FD2FC08-F999-4CE7-A5D4-E86CD2CF9436@gmail.com> (Carsten Dominik's message of "Sun, 23 Sep 2012 12:01:53 +0200") 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: Carsten Dominik Cc: Org-mode , Nicolas Goaziou Carsten Dominik writes: > On 23.9.2012, at 10:30, Nicolas Goaziou wrote: > >> Hello, >> >> Carsten Dominik writes: >> >>> On 22.9.2012, at 10:52, Nicolas Goaziou wrote: >>>> If the LaTeX command doesn't require an argument, you can always add it >>>> to `org-entities-user'. >>> >>> Yes, even though this is not very clean by itself. >> >> This is debatable. Entities are perfectly integrated into Org and are, >> by essence, multiple-back-end friendly. > > I only mean in the sense that entities are made to insert symbols and > characters, not to execute commands. It certainly can be used to that, > but this is not the intention of this mechanism. > Yes, this is the essence of the mismatch. The mechanism is designed to work with entities, but the regular expression catches all LaTeX commands, whose names don't distinguish entities from other constructs AFAIK. >> >>>> Anyway this is a minor point. I guess it will be swept under the rug of >>>> historical reasons, after all. >>> >>> Maybe not. I can go along with your arguments for cleanness. Would you >>> object to keeping this feature in as an option, turned off be default, >>> so that it is at least easy to keep lengthy files working? >> >> I'd rather leave it as it is, then. This option would require to >> maintain two versions of the parser: one without LaTeX commands and >> another one with them. That would defeat the whole point of removing >> them. >> >>> The way I understand it, the new exporter will be default in 8.0, so >>> this is the time to make some incompatible changes. >> >> Indeed. I will preserve my quota of backward-incompatible changes for >> other things. > > > OK. > Two versions of the parser! Yikes, that doesn't sound good. Links still provide a path to handle arbitrary LaTeX commands and have them send sensible output to the different backends. They don't look so great in the Org buffer, but that is an aesthetic issue, not functional. Thanks, Nicolas, for the new LaTeX exporter. All the best, Tom -- Thomas S. Dye http://www.tsdye.com