emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Q: Attachments and IDs?
Date: Sat, 13 Jul 2024 13:35:05 +0000	[thread overview]
Message-ID: <877cdpqut2.fsf@localhost> (raw)
In-Reply-To: <LV8P223MB092069EC8BC8EBD66F49F3D9A2A72@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM>

David Masterson <dsmasterson@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.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-07-13 13:34 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
2024-07-13 13:35     ` Ihor Radchenko [this message]
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=877cdpqut2.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dsmasterson@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).