From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Some projects Date: Sun, 25 Oct 2015 17:37:33 +0100 Message-ID: <87io5uewfm.fsf@nicolasgoaziou.fr> References: <87wpub9jts.fsf@nicolasgoaziou.fr> <87eggjar5u.fsf@ucl.ac.uk> <87io5uzzv6.fsf@mbork.pl> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46162) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqOGs-00016Q-T2 for emacs-orgmode@gnu.org; Sun, 25 Oct 2015 12:35:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZqOGs-0007bG-3F for emacs-orgmode@gnu.org; Sun, 25 Oct 2015 12:35:50 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:54840) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqOGr-0007bC-SX for emacs-orgmode@gnu.org; Sun, 25 Oct 2015 12:35:50 -0400 In-Reply-To: <87io5uzzv6.fsf@mbork.pl> (Marcin Borkowski's message of "Sun, 25 Oct 2015 17:18:48 +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: Marcin Borkowski Cc: Org Mode List Marcin Borkowski writes: > Since your point is quite valid - and OTOH, I would like to put anything > (or almost anything) in =code= markup, for instance (my use case: Emacs > keybindings, try =C-x ,= - Org won't recognize it as code!). I could > mess up with org-emphasis-regexp-components in e.g. file local > variables, but this is far from clean. I cannot think of any bad consequence if we tailor "border" in `org-emphasis-regexp-components' to allow everything but white spaces. > Maybe a good solution would be to allow two syntaxes for markup: > "short", like *bold* or =code=, and "long", like \textbf{bold} and > \verb|code|. If it is decided that such LaTeX-like syntax is fine, we > could only introduce escaping of backslash and curly braces, which seems > a decent compromise. I don't think LaTeX-like syntax is good. It doesn't belong to lightweight markup. Besides, Org already supports LaTeX macros so it would probably be ambiguous. I suggest to keep as close as possible to the existing markup. Regards,