emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: [dev] footnotes improvements
Date: Wed, 11 May 2011 21:02:29 +0200	[thread overview]
Message-ID: <871v05f4ca.fsf@gmail.com> (raw)

Hello,

I'd like to submit a branch for testing:

          git://github.com/ngz/org-mode-lists.git footnote-fix

Here are the changes so far:

- recognize and export inlined footnotes holding links in their definition,
- recognize and export two or more footnotes in a row,
- don't chock at footnotes or partial footnotes inside comments in Org buffer,
- export calls to already defined footnotes in LaTeX,
- export footnotes before first heading (LaTeX),
- export footnotes when selecting a subtree not holding their
  definition (LaTeX),
- fontify more consistently footnotes in the org buffer (only labels
  are "fontified" or fn in the case of an anonymous footnote).

The following snippet demonstrates most of these changes:

----------------------------------------------------------------------
#+title: Footnotes test

Some text before first headline[fn:1].

* First headline

# [fn::fake footnote

  Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
  eiusmod tempor incididunt ut labore et dolore magna
  aliqua[fn::inline1][1].

* Second headline

  Duis aute irure dolor in reprehenderit in voluptate velit esse
  cillum dolore eu fugiat nulla pariatur[fn:inlabel:an inline
  footnote][fn:inlabel2:[[http://www.google.com][google]] this].

  Call an already defined inline footnote[fn:inlabel].

* Footnotes

[fn:1] first footnote.

[1] End of first section.
------------------------------------------------------------------------

There are probably mischievous bugs. So, thanks in advance for any
feedback.

Regards,

-- 
Nicolas Goaziou

             reply	other threads:[~2011-05-11 19:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 19:02 Nicolas Goaziou [this message]
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
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

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=871v05f4ca.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).