Ihor Radchenko <yanta...@posteo.net> writes: > David Masterson <dsmaster...@gmail.com> writes: > >> It's taking awhile to get through my hard head, but I think I'm >> beginning to understand the directory structure of attachments. >> >> org-attach-id-dir/IDx/attachment-file >> >> I don't understand the value of IDx. I would think that "attachment:" >> could simply reference 'org-attach-id-dir' (drop 'id'?) unless >> overridden by a DIR property. I think I'm missing something that would >> help my understanding of attachments. Am I? > >> Is there a section of the Org manual that talks about IDs? > > 10.2.2 Attachment options > > ‘org-attach-id-to-path-function-list’ > When ‘ID’ is used for attachments, the ID is parsed into a part of > a directory-path. See ‘org-attach-id-uuid-folder-format’ for the > default function. Define a new one and add it as first element in > ‘org-attach-id-to-path-function-list’ if you want the folder > structure in any other way. All functions in this list will be > tried when resolving existing ID's into paths, to maintain backward > compatibility with existing folders in your system. > > For IDs, we use `org-attach-id-uuid-folder-format' by default - it puts > attachments under > > <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. -- David Masterson
