From: Carsten Dominik <carsten.dominik@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: footnote bugs
Date: Wed, 14 Apr 2010 16:48:13 +0200 [thread overview]
Message-ID: <077D75A3-2217-4A76-B8B0-95C75312C65A@gmail.com> (raw)
In-Reply-To: <y2m20524da71004061939u73662084kffb778d8aff0816a@mail.gmail.com>
Hi Samuel,
On Apr 7, 2010, at 4:39 AM, Samuel Wales wrote:
> (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].
ASCII export of anonymous footnotes works fine for me. here is an
example for your text above:
The following text
Some text[fn::text] with note
is exported like this:
Some text[1] with note
[1] text
Also, when inserting a footnote, I can eave the label empty - the
fact that this is not working for you must mean that you have some
completion setup that takes over the generic function
`completing-read'.
>
> ===
>
> [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.
I guess you can hack the paragraph... regexps to make \par
a separator.
>
> [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.
It is very difficult for org to find footnotes if there
are several definitions in a buffer for the same footnote label.
But I can follow you argument, so the definition is now search up
in the buffer, before looking down.
>
> ===
>
> [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.
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-04-14 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 2:39 footnote bugs Samuel Wales
2010-04-14 14:48 ` Carsten Dominik [this message]
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=077D75A3-2217-4A76-B8B0-95C75312C65A@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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).