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: Thu, 18 Aug 2011 17:37:06 -0300 [thread overview]
Message-ID: <4e4d77f7.1136650a.10fc.73a6@mx.google.com> (raw)
In-Reply-To: <87pqk2lj4e.fsf@altern.org>
Hello Bastien,
I'm glad to help (even if such a small contribution).
The downside of this hack is that it does not work when you export the
buffer. If you use the file: link type then the link will works when you
export the org buffer, but you have to type the whole path of the attached
file. Therefore, there is this trade-off for now.
There is probably a way to make the attach link type also work when
exporting the org buffer, but since I don't need this right now I didn't
search how to do it.
--
Darlan
At Thu, 18 Aug 2011 19:33:37 +0200,
Bastien <bzg@altern.org> wrote:
>
> Hi Darlan,
>
> Darlan Cavalcante Moreira <darcamo@gmail.com> writes:
>
> > I requested this some time ago [1]. While there is not a built-in attach
> > link type, org provides you with ways to easily create this functionality.
> >
> > In the setup part in my org-files I put
> > #+LINK: attach elisp:(org-open-file (org-attach-expand "%s"))
> >
> > Now I can use the "attach" link type, but org will ask me if I want to
> > allow executing the elisp code. To avoid this you can even set
> > org-confirm-elisp-link-function to nil (I don't like this because it allows
> > any elisp code in links) or you can set org-confirm-elisp-link-not-regexp
> > appropriately.
> >
> > In my case I use
> > : (setq org-confirm-elisp-link-not-regexp "org-open-file")
> >
> > This works very well.
>
> This is a nice and useful hack -- I added it to Worg/org-hacks.org.
>
> Thanks!
>
> --
> Bastien
next prev parent reply other threads:[~2011-08-18 20:37 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 [this message]
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
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=4e4d77f7.1136650a.10fc.73a6@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).