Ihor Radchenko <yanta...@posteo.net> writes: > David Masterson <dsmaster...@gmail.com> writes: > >>> <org-attach-id-dir>/<first two letters of ID>/<the rest of ID>/attached-file >> >> Hmm. I'm still misunderstanding the *value* of an ID (value in the sense >> of why is it useful for me). This suggests to me that, under >> org-attach-id-dir, you could have a tree of attachments, but what is an >> example of why that's a good thing (particularly for a newbie)? >> ... Since >> the documentation on attachments starts out mentioning an ID, it's >> helpful to understand why it's useful. Basically, I guess the above >> mentions "folder structure" without defining what is trying to be >> achieved with this more complicated folder structure instead of just one >> attachment directory where all attachments are dumped. > > You can attach files to multiple headings. > Using the heading ID to construct the attachment location makes sure > that we do not dump all the attachments together. > Isn't it obvious? I am genuinely surprised.
I'm getting old, but I think I'm seeing it now. I think the word "entry" in 10.2 threw me for awhile (entry as in a task hierarchy as opposed to a particular attachment). Maybe an Appendix for these generic words (entry, ID, header, task, ...) that explains their special meaning in Org for reference? Not sure. Thanks for putting with me. -- David Masterson
