From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Christian Barthel <bch@online.de>,
John Kitchin <jkitchin@andrew.cmu.edu>,
Ihor Radchenko <yantar92@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-attach a directory?
Date: Thu, 10 Jun 2021 14:01:21 +0000 [thread overview]
Message-ID: <87h7i5lsy6.fsf@posteo.net> (raw)
In-Reply-To: <87r1h999q8.fsf@online.de> (Christian Barthel's message of "Thu, 10 Jun 2021 14:37:19 +0200")
This only works when you create the attach folder manually, but not when
you want org-attach to generate the attach directory for the current
node.
If I have to stay with a workaround that covers many scenarios, I would
stay with Ihor's snippet, which seems to me simpler than the patch that
I suggested before, and you don't need to define new attach
commands/methods. I would vote for a patch in that direction (Ihor's
code).
Best regards,
Juan Manuel
Christian Barthel writes:
> On Thu, Jun 10 2021, Ypo wrote:
>
>> C-c C-a
>>
>> s
>>
>> (not "S" like in the video, but "s")
>
> Thanks, that is an interesting workaround:
> Setting the directory twice and using the copy/delete action
> accordingly.
>
> Does anyone know if there is a workaround to attach a file and
> delete the old one (or move the file) or do I need to write a
> small elisp function for that?
next prev parent reply other threads:[~2021-06-10 14:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 19:35 org-attach a directory? Ypo
2021-06-09 23:39 ` John Kitchin
2021-06-10 3:54 ` Ypo
2021-06-10 3:56 ` Ypo
2021-06-10 12:37 ` Christian Barthel
2021-06-10 12:39 ` John Kitchin
2021-06-10 12:54 ` Christian Barthel
2021-06-10 14:01 ` Juan Manuel Macías [this message]
2021-06-10 16:13 ` Juan Manuel Macías
-- strict thread matches above, loose matches on Subject: below --
2021-06-10 16:50 Ypo
2021-06-08 15:49 John Kitchin
2021-06-08 16:21 ` Henrik Frisk
2021-06-08 20:41 ` John Kitchin
2021-06-09 1:38 ` Ihor Radchenko
2021-06-11 1:43 ` stardiviner
2021-06-11 16:35 ` John Kitchin
2021-06-11 17:10 ` Juan Manuel Macías
2021-06-15 12:45 ` stardiviner
2021-06-15 20:22 ` Henrik Frisk
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=87h7i5lsy6.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=bch@online.de \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=yantar92@gmail.com \
/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).