From: Bastien Guerry <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: [Accepted] Prevent creation of duplicate footnote sections.
Date: Thu, 17 Mar 2011 09:24:36 +0100 (CET) [thread overview]
Message-ID: <20110317082436.9F7C86523@myhost.localdomain> (raw)
In-Reply-To: 87zkozi2j5.fsf@fastmail.fm
Patch 679 (http://patchwork.newartisans.com/patch/679/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C87zkozi2j5.fsf%40fastmail.fm%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O] Prevent creation of duplicate footnote sections.
> Date: Fri, 11 Mar 2011 18:49:06 -0000
> From: Matt Lundin <mdl@imapmail.org>
> X-Patchwork-Id: 679
> Message-Id: <87zkozi2j5.fsf@fastmail.fm>
> To: Org Mode <emacs-orgmode@gnu.org>
>
> * lisp/org-footnote.el: (org-footnote-create-definition): Allow for
> footnote sections above the current footnote insertion point.
>
> Fixes bug in which org-mode will create a new footnote section if the
> current footnote section is not beneath the current insertion point.
>
> ---
> lisp/org-footnote.el | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/lisp/org-footnote.el b/lisp/org-footnote.el
> index 0524b41..2ce6668 100644
> --- a/lisp/org-footnote.el
> +++ b/lisp/org-footnote.el
> @@ -291,6 +291,7 @@ or new, let the user edit the definition of the footnote."
> ;; No section, put footnote into the current outline node
> nil
> ;; Try to find or make the special node
> + (goto-char (point-min))
> (setq re (concat "^\\*+[ \t]+" org-footnote-section "[ \t]*$"))
> (unless (or (re-search-forward re nil t)
> (and (progn (widen) t)
>
prev parent reply other threads:[~2011-03-17 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 13:49 [PATCH] Prevent creation of duplicate footnote sections Matt Lundin
2011-03-17 8:24 ` Bastien Guerry [this message]
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=20110317082436.9F7C86523@myhost.localdomain \
--to=bzg@altern.org \
--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).