From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Some projects Date: Sun, 25 Oct 2015 17:11:54 +0100 Message-ID: <87fv0z9bcl.fsf@nicolasgoaziou.fr> References: <87wpub9jts.fsf@nicolasgoaziou.fr> <87mvv7ypot.fsf@wmi.amu.edu.pl> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41299) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqNs6-0003qI-Dt for emacs-orgmode@gnu.org; Sun, 25 Oct 2015 12:10:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZqNs5-0001RL-Ic for emacs-orgmode@gnu.org; Sun, 25 Oct 2015 12:10:14 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:38820) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqNs5-0001RH-CB for emacs-orgmode@gnu.org; Sun, 25 Oct 2015 12:10:13 -0400 In-Reply-To: <87mvv7ypot.fsf@wmi.amu.edu.pl> (Marcin Borkowski's message of "Sun, 25 Oct 2015 15:43:21 +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: > That sounds interesting, though I don't really see much difference > between this and plain simple comments. 1. you cannot simply inline comments (you need to create a new link type or some such); 2. you cannot mark exactly where the comment applies. >> ** Backslash escaping >> >> Allowing to escape some symbols in plain text (e.g., emphasis markers, >> square brackets...) would remove a limitation in verbatim/code objects. >> As a small benefit, it would also permit to implement mid-word markup: >> b*o*ld. >> >> There are some gotchas, however. > > And this one is probably the most interesting to me. If I can help > (testing, suggestions, maybe coding - I'm in the process of transferring > copyright for my Emacs/Org-mode/AUCTeX contributions to the FSF), please > let me know. Here, I don't even have clear specifications. So the first step would be to define them. 1. It should be unintrusive, i.e., you only need to escape ambiguous cases. E.g., \[1] makes sure that [1] will not be treated as a footnote reference, but \[*] is equivalent to [*]. 2. It should allow to insert "=" within verbatim and "~" within code markup. 3. It should only be used in paragraphs, verse blocks or table cells. E.g., there is no escaping in #+NAME: ... or in node properties. Assuming you can escape #, :, |, [, {, <, *, +, _, ^, /, ~, =, you only need to escape \ if it is followed by any of the previous characters. So, \\= means \= but \\! means \\!. Unfortunately, there is a special entity, "\_ " which is incompatible with the previous definition. Implementation-wise, I think it is enough to resolve backslash escaping when parsing a paragraph (or equivalent). Regards,