From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Matthew Lundin <mdl@imapmail.org>
Cc: "Gustav Wikström" <gustav@whil.se>,
"Org Mode List" <emacs-orgmode@gnu.org>
Subject: Re: [Bug] org-store-link should not insert a document level ID property
Date: Wed, 13 May 2020 18:45:20 +0200 [thread overview]
Message-ID: <87tv0jbx7j.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878shw6k5s.fsf@fastmail.fm> (Matthew Lundin's message of "Wed, 13 May 2020 08:26:07 -0500")
Matthew Lundin <mdl@imapmail.org> writes:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>>
>> AFAIK, ID is associated to a file name, and possibly a location in it.
>> In this case, the ID is strictly equivalent to the file name, so why
>> bother?
>
> I'm not sure I understand the question. Are you asking: Why bother
> generating IDs at the top level of a file (which was the change Gustav
> introduced)? Or why bother turning off that behavior? I can't address
> the former question but I will address the latter.
Sorry for not being clear. This was the first question. I don't
understand why we are generating an ID for the whole file.
> The main reason is that I find these IDs redundant and visually
> distracting. I can see how file IDs would be useful if one is
> constantly renaming files (or perhaps writing custom functions that
> convert files to entries and vice versa).
IIUC, currently, renaming the file breaks the association between the ID
and the file name. IOW, the ID is useless if you rename the file.
Regards,
next prev parent reply other threads:[~2020-05-13 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 22:13 [Bug] org-store-link should not insert a document level ID property Matt Lundin
2020-04-04 23:07 ` Gustav Wikström
2020-04-05 15:50 ` Gustav Wikström
2020-04-10 8:08 ` Gustav Wikström
2020-05-07 21:41 ` Matthew Lundin
2020-05-13 8:33 ` Nicolas Goaziou
2020-05-13 13:26 ` Matthew Lundin
2020-05-13 16:45 ` Nicolas Goaziou [this message]
2020-05-14 19:27 ` Gustav Wikström
2020-05-14 21:20 ` Nicolas Goaziou
2020-05-14 22:06 ` Gustav Wikström
2020-05-14 19:11 ` Gustav Wikström
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=87tv0jbx7j.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=gustav@whil.se \
--cc=mdl@imapmail.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).