emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: footnote bugs
Date: Tue, 6 Apr 2010 19:39:24 -0700	[thread overview]
Message-ID: <y2m20524da71004061939u73662084kffb778d8aff0816a@mail.gmail.com> (raw)

(setf org-footnote-auto-label 'confirm)
(setf org-footnote-section nil)

* top
*** an article
sadfkaj sdnfklaj nsfklandsf
asd flkajnd sfa
*** an article.  exporting this to ascii does not export anonymous footnotes
I sometimes[fn:3] mix regular[fn:1] footnotes and inline
[fn:: There are issues here.  For example, I have to type
them in manually.  You cannot leave empty; it won't accept
it.  Maybe it has to do with my ido setup.  Exporting this
to ASCII seems to silent fail.  I tried "fn:: text" and
"fn::text".] ones[fn:2].

===

[fn:1] ordinary.  note that if you put point here and do c-c
c-c, you will get sent to the next article, which is
disconcerting.  i expected it to go up to the thing that
points to it.  this situation, where you have duplicate
footnote numbers in the same file, but different org
entries, is very common when you refile an article.
\par
don't know how to separate paragraphs in a footnote in
a way that fill-paragraph with filladapt will understand.
would be nice if a way were possible, imo.

[fn:2] another

[fn:3] a third
# a comment
*** another article
ordinary [fn:1], inline[fn:This is a test.], and
regular[fn:2] footnotes.

===

[fn:1] regular

[fn:2] usual
*** another article
asdfj alkdfn akljdn fklajdf
askdfn al;ksjnf lajdnf klajdnf
skjdhflakjdnf klajnf [fn:1]

[fn:1] test
*** another article
asdknf lakjdnf ak
asdkjfn aldjf


Thanks.

             reply	other threads:[~2010-04-07  2:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07  2:39 Samuel Wales [this message]
2010-04-14 14:48 ` footnote bugs Carsten Dominik
2010-04-14 16: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=y2m20524da71004061939u73662084kffb778d8aff0816a@mail.gmail.com \
    --to=samologist@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).