From: Michael Brand <michael.ch.brand@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>,
Christian Moe <mail@christianmoe.com>,
John Kitchin <jkitchin@andrew.cmu.edu>,
Eric S Fraga <esflists@gmail.com>,
org-mode-email <Emacs-orgmode@gnu.org>, ST <smntov@gmail.com>
Subject: Re: Structured links to headings with endless depth
Date: Tue, 7 May 2019 16:39:00 +0200 [thread overview]
Message-ID: <CALn3zogde71Gr143mMp=fHPVMW8UJQ7JTJk8S3T3yW4ADBa+4A@mail.gmail.com> (raw)
In-Reply-To: <874l67eyif.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me>
Hi Ihor
On Tue, May 7, 2019 at 5:27 AM Ihor Radchenko <yantar92@gmail.com> wrote:
> I am wondering why you are strictly against ID properties.
To me this looks like a misunderstanding. I use the ID often but my
weighting of the different advantages is not the same in all cases.
Some situations where no ID can be seen as an advantage: Looking at
the raw view (for example visible-mode during ediff), looking at the
raw file (when in the other world outside of Org mode), the time it
can take to not find an ID in all the ID files when the target file or
ID is not accessible, etc. There must be good reasons why some more
users than just me sometimes prefer the format B over A:
#+name: A
#+begin_src org
- [[id:8e5c5d87-291e-469b-a8e4-15704610c82c][The heading name]]
,* The heading name
:PROPERTIES:
:ID: 8e5c5d87-291e-469b-a8e4-15704610c82c
:END:
#+end_src
#+name: B
#+begin_src org
- [[*The heading name]]
,* The heading name
#+end_src
Michael
next prev parent reply other threads:[~2019-05-07 14:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 10:09 Structured links to headings with endless depth ST
2018-03-12 10:29 ` Eric S Fraga
2018-03-12 10:39 ` ST
2018-03-12 13:08 ` Christian Moe
2018-03-12 13:46 ` ST
2018-03-12 14:10 ` Nicolas Goaziou
2018-03-12 15:08 ` ST
2018-03-14 3:49 ` John Kitchin
2018-03-14 6:58 ` Michael Brand
2019-05-06 16:34 ` Michael Brand
2019-05-07 3:26 ` Ihor Radchenko
2019-05-07 14:39 ` Michael Brand [this message]
2019-05-18 10:44 ` Ihor Radchenko
2018-03-14 10:10 ` ST
2018-03-14 13:26 ` Nicolas Goaziou
2018-03-14 18:11 ` ST
2018-03-14 18:32 ` Nicolas Goaziou
2018-03-14 18:46 ` ST
2018-03-14 14:15 ` John Kitchin
2018-03-14 18:07 ` ST
2018-03-12 12:43 ` ST
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='CALn3zogde71Gr143mMp=fHPVMW8UJQ7JTJk8S3T3yW4ADBa+4A@mail.gmail.com' \
--to=michael.ch.brand@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=esflists@gmail.com \
--cc=jkitchin@andrew.cmu.edu \
--cc=mail@christianmoe.com \
--cc=mail@nicolasgoaziou.fr \
--cc=smntov@gmail.com \
--cc=yantar92@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).