emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Karl Voit <devnull@Karl-Voit.at>
Cc: Karl Voit <news1142@Karl-Voit.at>, emacs-orgmode@gnu.org
Subject: Re: Scanning for duplicate IDs of whole buffer when exporting a sub-heading
Date: Thu, 11 Feb 2016 18:23:54 +0100	[thread overview]
Message-ID: <87fuwz5ff9.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <2016-02-11T16-02-01@devnull.Karl-Voit.at> (Karl Voit's message of "Thu, 11 Feb 2016 16:13:15 +0100")

Hello,

Karl Voit <devnull@Karl-Voit.at> writes:

> What is the policy of merging changes from master to maint? Does
> this happen only for major issues? Only before releases?

Usually maint contains either very important or trivial fixes. To put it
differently, fixes that might not go in maint are invasive changes that
solve non-critical issues. I believe this one fell in the latter
category.

However, as you can tell, there is usually no clear cut.

> Sorry, I'm a bit confused here. Does this mean that id-links are
> replaced by something new or do you assume that the id-links in my
> document are not important (because it ought to be only a small
> file for a presentation)?
>
> If it's the latter: my Org-mode file is quite large and contains
> hundreds of id-links I want to keep. The sub-heading of the
> presentation I want to export is only a tiny fraction of the file.
>
> My whole digital life is managed in a dozen Org-mode files with a
> quarter million lines and approximately ninety percent is within
> five files. Therefore I love narrowing down to sub-headings for
> editing and exporting.

Export process happens in a copy of your documents. You can safely
remove id links there (since they get in the way ATM) using hooks.

Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2016-02-11 17:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 16:16 Scanning for duplicate IDs of whole buffer when exporting a sub-heading Karl Voit
2016-02-10 17:28 ` Nicolas Goaziou
2016-02-10 17:48   ` Samuel Wales
2016-02-10 18:08   ` Karl Voit
2016-02-10 23:04     ` Nicolas Goaziou
2016-02-11 15:13       ` Karl Voit
2016-02-11 17:23         ` Nicolas Goaziou [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=87fuwz5ff9.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=devnull@Karl-Voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /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).