From: Matt Lundin <firstname.lastname@example.org>
To: Org Mode List <email@example.com>
Subject: Re: [dev] footnotes improvements
Date: Sun, 15 May 2011 11:47:30 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Nicolas Goaziou's message of "Sun, 15 May 2011 16:59:46 +0200")
Nicolas Goaziou <firstname.lastname@example.org> writes:
>> First, a general consideration: my vote would be for highlighting the
>> entire footnote label, including the brackets. IMO, leaving the brackets
>> in the default face makes it more difficult to scan the buffer.
>> (Similarly, I think it might be nice to fontify the entire contents of
>> inline footnotes.)
> I tend to disagree here:
> - if we fontify the whole contents, it may override any special
> fontification inside the inlined footnote (i.e. links, emphasis).
> Moreover, it would look ugly with multi-lines footnotes (white spaces
> at the beginning of the line are also fontified).
Yes, I can see how overriding the fontification of links might be an
issue. FWIW, auctex/font-latex provides a nice example of the behavior I
have in mind. The face inside of the footnote macro overrides some
faces, but not others. Leading whitespace indented, multi-line footnotes
is not fontified.
> - if we fontify the label and the brackets, it might be difficult to
> distinguish when two or more footnotes are bound together. In the case
> of a single inline footnote, the closing bracket would look silly when
> fontified alone in the middle of the text.
> - fontifying only labels is enough to spot quickly a footnotes, and is
> useful when you want to reuse an already defined label.
Could we perhaps provide an option to fontify the brackets, if only to
preserve the traditional behavior? I use footnotes that look like
this.[fn:6592605c] I find them much easier to scan visually when the
brackets and "fn:" are also highlighted.
> That being said, I agree that the actual fontification process needs to
> be tweaked a bit more (i.e. is buggy and not in is final state). Let me
> improve this during the next week, then, if needed, we will discuss
> again about it.
>> Square brackets containing digits inside of footnotes cause some issues.
>> The primary use for such brackets would be to include LaTeX cite macros
>> inside of footnotes. I imagine this might be tricky to fix, as 
>> looks exactly like a footnote label.
>  isn't recognized as a footnote label, as LaTeX macros have
> precedence over footnotes (`org-footnote-at-reference-p' dismisses any
> footnote matching a part of a LaTeX macro). The problem is that, at the
> moment, footnote contents are not protected from further processing.
> Alas, unprotected macros are not seen as macros by LaTeX exporter. One
> solution would be to protect the contents, but I have first to look at
> the HTML exporter, as the reason might be different there.
Indeed. It was the html exporter that treated the brackets as a
footnote. The LaTeX exporter, by contrast, escaped the curly brackets.
> Again, I will have a look at all of this during the week to come. Stay
> tuned !
next prev parent reply other threads:[~2011-05-15 15:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 19:02 Nicolas Goaziou
2011-05-12 7:19 ` Christian Moe
2011-05-12 8:10 ` Aankhen
2011-05-12 10:04 ` Nicolas Goaziou
2011-05-12 10:48 ` Christian Moe
2011-05-14 8:44 ` Nicolas Goaziou
2011-05-14 18:22 ` Christian Moe
2011-05-14 13:42 ` Matt Lundin
2011-05-15 14:59 ` Nicolas Goaziou
2011-05-15 15:47 ` Matt Lundin [this message]
2011-05-26 19:49 ` Nicolas Goaziou
2011-05-26 20:56 ` Samuel Wales
2011-05-26 23:41 ` suvayu ali
2011-05-15 15:52 ` Samuel Wales
2011-06-27 18:29 ` Nicolas Goaziou
2011-06-27 20:07 ` Christian Moe
2011-06-27 20:24 ` Nicolas Goaziou
2011-06-27 22:45 ` Christian Moe
2011-06-28 9:59 ` Bastien
2011-06-30 6:14 ` Samuel Wales
2011-06-30 9:15 ` Bastien
2011-06-30 17:36 ` Nicolas Goaziou
2011-07-04 23:26 ` Samuel Wales
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 \
* 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).