From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Q: Attachments and IDs?
Date: Fri, 12 Jul 2024 20:34:21 -0700 [thread overview]
Message-ID: <LV8P223MB092069EC8BC8EBD66F49F3D9A2A72@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87le2859eg.fsf@localhost> (Ihor Radchenko's message of "Thu, 11 Jul 2024 13:46:15 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> David Masterson <dsmasterson@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
next prev parent reply other threads:[~2024-07-13 3:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 22:34 Q: Attachments and IDs? David Masterson
2024-07-11 13:46 ` Ihor Radchenko
2024-07-13 3:34 ` David Masterson [this message]
2024-07-13 13:35 ` Ihor Radchenko
2024-07-14 4:18 ` David Masterson
2024-07-14 10:16 ` Ihor Radchenko
2024-07-14 17:16 ` David Masterson
2024-07-11 16:18 ` Daniel Fleischer
2024-07-13 3:09 ` David Masterson
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=LV8P223MB092069EC8BC8EBD66F49F3D9A2A72@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).