From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: Bastien <bzg@altern.org>
Cc: "Gustav Wikström" <gustav.erik@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Attachments and refiling
Date: Wed, 24 Aug 2011 11:56:37 -0300 [thread overview]
Message-ID: <4e55112c.a1beec0a.51eb.751f@mx.google.com> (raw)
In-Reply-To: <87fwkqublv.fsf@altern.org>
At Wed, 24 Aug 2011 16:12:01 +0200,
Bastien <bzg@altern.org> wrote:
>
> Hi Darlan,
>
> Darlan Cavalcante Moreira <darcamo@gmail.com> writes:
>
> > At Fri, 19 Aug 2011 10:46:26 +0200,
> > Bastien <bzg@altern.org> wrote:
> >
> > What about org-add-link-type?
>
> Mmhh.. yes. We should be able to use something like:
>
> (org-add-link-type "attach" 'org-attach-open 'org-attach-export)
>
> > However, I could not make the the "export" part work because I can't use
> > org-attach-expand in it. Therefore, I don't know how to get the attach
> > directory inside a function that I can pass to org-add-link-type as the
> > export function.
>
> That's not possible for now. That's something we can keep in mind
> while working an a new export engine: exporting part of the content
> should be done in a context-aware fashion, where it's possible to
> get the value of org-attach-dir.
Thanks for the confirmation Bastien. At least for me the export part is not
very important right now. A context aware export engine would make this
easy to achieve with org-add-link-type and probably open up many other
possibilities, but I understand it is a lot of work.
>
> > Unfortunately, my elisp skills are very limited to go any further for
> > now.
>
> Even with good elisp skills I'm afraid we cannot achieve this for
> the moment.
>
> HTH,
>
> --
> Bastien
--
Darlan
prev parent reply other threads:[~2011-08-24 14:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 11:06 Attachments and refiling Gustav Wikström
2011-07-15 11:16 ` Bastien
2011-07-15 14:55 ` Gustav Wikström
2011-07-16 15:50 ` Darlan Cavalcante Moreira
2011-07-19 12:17 ` Gustav Wikström
2011-07-24 20:00 ` Bastien
2011-07-25 0:14 ` Brian van den Broek
2011-07-25 7:10 ` Gustav Wikström
2011-07-25 7:45 ` Bastien
2011-07-25 15:55 ` Darlan Cavalcante Moreira
2011-07-28 7:51 ` Bastien
2011-07-28 10:38 ` suvayu ali
2011-07-28 13:46 ` Nick Dokos
2011-07-28 13:49 ` suvayu ali
2011-07-28 14:33 ` Nick Dokos
2011-07-28 17:31 ` Darlan Cavalcante Moreira
2011-07-28 18:04 ` Bernt Hansen
2011-07-29 7:27 ` Gustav Wikström
2011-08-02 4:02 ` Matt Lundin
2011-08-29 12:04 ` Gustav Wikström
2011-07-24 20:07 ` Bastien
2011-07-25 7:21 ` Gustav Wikström
2011-07-29 8:33 ` Gustav Wikström
2011-07-29 20:58 ` Darlan Cavalcante Moreira
2011-08-18 17:33 ` Bastien
2011-08-18 20:37 ` Darlan Cavalcante Moreira
2011-08-19 8:46 ` Bastien
2011-08-19 16:29 ` Darlan Cavalcante Moreira
2011-08-24 14:12 ` Bastien
2011-08-24 14:56 ` Darlan Cavalcante Moreira [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
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=4e55112c.a1beec0a.51eb.751f@mx.google.com \
--to=darcamo@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=gustav.erik@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).