From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [Out-of-Thread] Re: [RFC] Org syntax (draft) Date: Mon, 18 Mar 2013 22:24:37 +0100 Message-ID: <87ppywpfje.fsf@pank.eu> References: <6449B53A-997D-411D-8E13-AAFAE6D81397@gmail.com> <87mwu0n371.fsf@riseup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:53813) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UHhY3-00037n-Q6 for emacs-orgmode@gnu.org; Mon, 18 Mar 2013 17:24:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UHhY2-0004xQ-Kw for emacs-orgmode@gnu.org; Mon, 18 Mar 2013 17:24:51 -0400 Received: from plane.gmane.org ([80.91.229.3]:59721) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UHhY2-0004xE-EE for emacs-orgmode@gnu.org; Mon, 18 Mar 2013 17:24:50 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UHhYN-0007vY-SH for emacs-orgmode@gnu.org; Mon, 18 Mar 2013 22:25:11 +0100 Received: from dynamic-adsl-94-39-221-9.clienti.tiscali.it ([94.39.221.9]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 18 Mar 2013 22:25:11 +0100 Received: from rasmus by dynamic-adsl-94-39-221-9.clienti.tiscali.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 18 Mar 2013 22:25:11 +0100 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: emacs-orgmode@gnu.org Carsten Dominik writes: > The reason why the emphasis regexp components were made configurable > in the first place is because when the feature was introduced, I had > no idea what would work, and I redesigned this part several times > over. Emphasis is a very heuristic system, the character that are > allowed before and after the markers are necessarily a compromise, and > we will always find people for who the chosen selection will not work. > That is why I would like to argue for keeping this part hackable, even > if I agree that the official definition should be fixed. Keeping this > variable a customize variable invites changes also by people who do > not really know what they are doing. Turning it into a defvar or > defconst and somewhere document how to hack around the restriction if > you really need to sounds like a good solution for me. To some extend I disagree, I think. Well, a contrib library is of course OK, but I think it's not the right way to go about it. . . Would it be possible to make it easier to make 'custom' highlights? In a previous thread a [cite:key] syntax was suggested. Perhaps, a better way for custom emphasis would be [type:value] allowing for custom functions for each type. E.g. [TYPE:value] would run function a function org-type-keys-TYPE which returns value formatted with a special face. Perhaps this is more cumbersome and perhaps it is no more 'structured' than using customized emphases. –Rasmus -- El Rey ha muerto. ¡Larga vida al Rey!