From: aaermolov@gmail.com
To: Rainer M Krug <Rainer@krugs.de>, emacs-orgmode@gnu.org
Subject: Re: Defining directory tree structure from org-attach to reflect headers
Date: Sun, 16 Oct 2016 18:41:42 +0300 [thread overview]
Message-ID: <878ttoz4g9.fsf@laptoptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <m2h98g5qdk.fsf@krugs.de>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
I'm not completely up to topic, but it seems to me that org-attach
machinery is more about a content-addressable storage, so it makes
little sense for what you want this way.
But those who know more, can obviously correct me.
cheers,
Alex
Rainer M Krug <Rainer@krugs.de> writes:
> Hi
>
> I have effectively the same question as Adm here:
> [http://emacs.stackexchange.com/questions/26412/human-readable-directory-tree-with-org-attach]
>
> I would like to have the directory tree of the attachments managed by
> org-attach to reflect the document structure as defined by the
> headlines.
>
> To quote from his question:
>
> ,----
> | * This headline
> | ** This sub-headline 1
> | ** This sub-headline 2
> | * This second headline
> |
> | matches to the directory structure:
> |
> | - This headline
> | - This sub-headline 1
> | - This sub-headline 2
> | - This second headline
> `----
>
> I started using to set the directories, but for this I need the
> additional step of defining it per subtree. Is there a way to configure
> org-attach to automatically use the header name instead of the uuid?
>
> Thanks,
>
> Rainer
>
>
> --
> Rainer M. Krug
> email: Rainer<at>krugs<dot>de
> PGP: 0x0F52F982
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
prev parent reply other threads:[~2016-10-16 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 13:29 Defining directory tree structure from org-attach to reflect headers Rainer M Krug
2016-10-16 15:41 ` aaermolov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ttoz4g9.fsf@laptoptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=aaermolov@gmail.com \
--cc=Rainer@krugs.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.