From: Matthew Lundin <firstname.lastname@example.org> To: Nicolas Goaziou <email@example.com> Cc: "Gustav Wikström" <firstname.lastname@example.org>, "Org Mode List" <email@example.com> Subject: Re: [Bug] org-store-link should not insert a document level ID property Date: Wed, 13 May 2020 08:26:07 -0500 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Nicolas Goaziou <firstname.lastname@example.org> writes: > Matthew Lundin <email@example.com> writes: > >> What I was thinking of in terms of configuration is being able to >> preserve path-based links (instead of IDs) if creating a link above the >> first headline. This is the behavior that existed in the past when >> org-id-link-to-org-use-id was set to t or >> 'create-if-interactive-and-no-custom-id. > > I don't understand what is the meaning of an ID property for a whole > document. > > 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. 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). But in other ways they are more fragile than paths, since a :PROPERTIES: drawer at the top of a file looks like clutter and is *very* tempting to delete: ---- beginning of file :PROPERTIES: :ID: d4ef67e6-ffcd-4df3-b821-b92c0138eb9c :END: #+FILETAGS: work inbox #+CATEGORY: work ---- file continues... That said, I'm happy to hack together a personal solution by advising org-id-store-link if we decide not to allow users to customize this behavior. Best, Matt
next prev parent reply other threads:[~2020-05-13 13:26 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-04 22:13 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 [this message] 2020-05-13 16:45 ` Nicolas Goaziou 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [Bug] org-store-link should not insert a document level ID property' \ /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
Code repositories for project(s) associated with this 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).