From: Tim Cross <firstname.lastname@example.org>
Subject: Re: [WDYT] org-attach-sync better remove an empty attachment directory?
Date: Thu, 08 Jul 2021 10:34:43 +1000 [thread overview]
Message-ID: <email@example.com> (raw)
Marco Wahl <firstname.lastname@example.org> writes:
> org-attach-sync can be used to "Synchronize the current outline node
> with its attachments." Which is great AFAICT.
> What do you think about letting org-attach-sync remove the attachment
> directory if it's empty?
> Rationale: Nobody needs an empty attachment directory.
This seems pretty reasonable to me provided it only removes an
attachments directly which was created by org-attach-sync. If the
directory existed or was created by something external, then removing it
probably should not be done.
Likely this is something which should be controllable via a custom
next prev parent reply other threads:[~2021-07-08 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 20:15 [WDYT] org-attach-sync better remove an empty attachment directory? Marco Wahl
2021-07-08 0:34 ` Tim Cross [this message]
2021-07-08 7:45 ` Marco Wahl
2021-07-08 7:56 ` Tim Cross
2021-07-08 8:28 ` Colin Baxter
2021-07-08 17:36 ` Marco Wahl
2021-07-08 18:53 ` Marco Wahl
2021-07-08 19:28 ` Tim Cross
2021-07-09 6:15 ` Colin Baxter
2021-07-09 19:18 ` Marco Wahl
2021-07-10 13:20 ` Colin Baxter
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).