emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Greg Minshall <minshall@umich.edu>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: including one double quote in an anonymous footnote?
Date: Sat, 26 Feb 2022 19:20:44 +0000	[thread overview]
Message-ID: <87h78le8oj.fsf@posteo.net> (raw)
In-Reply-To: <3396628.1645887607@apollo2.minshall.org> (Greg Minshall's message of "Sat, 26 Feb 2022 07:00:07 -0800")

Greg Minshall writes:

> Juan Manuel,
>> I can confirm that behavior. One possible solution is to use an entity
>> (M-x org-entities-help):
> thanks very much -- that does the trick for my case.

In any case, I don't know if that behavior should be considered a bug. I
say this because other constructions with an unbalanced element,
although org does not fontify them well, they are exported correctly:

this is a test[fn::(this is an inline footnote]

this is a test[fn::{this is an inline footnote]

== LaTeX ==>

this is a test\footnote{(this is an inline footnote}

this is a test\footnote{\{this is an inline footnote}

Instead, if you do <M-: (org-element-context)> on your example,
org-element-context doesn't recognize this as a footnote reference:

this is a test[fn::"this is an inline footnote]

Looking at `org-element-footnote-reference-parser', I'd say the problem
is with:

(with-syntax-table org-element--pair-square-table
		       (ignore-errors (scan-lists (point) 1 0)))

If there is an unbalanced double quote inside a bracket construction,
that expression returns nil and not the position after the final
bracket. But I don't know how to go on :-(.

Best regards,

Juan Manuel 

  reply	other threads:[~2022-02-26 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26 14:33 including one double quote in an anonymous footnote? Greg Minshall
2022-02-26 14:47 ` Juan Manuel Macías
2022-02-26 15:00   ` Greg Minshall
2022-02-26 19:20     ` Juan Manuel Macías [this message]
2022-02-28 14:47       ` Nicolas Goaziou
2022-02-28 18:36         ` Greg Minshall
2022-02-28 20:57           ` Juan Manuel Macías

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h78le8oj.fsf@posteo.net \
    --to=maciaschain@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=minshall@umich.edu \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).