emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Orgmode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Feature Request: attach link type
Date: Fri, 04 Mar 2011 15:10:18 -0300	[thread overview]
Message-ID: <4d712b0e.1838640a.4d18.ffffa691@mx.google.com> (raw)
In-Reply-To: <87mxlco6ch.fsf@gnu.org>

At Thu, 03 Mar 2011 11:18:06 +0100,
Bastien <bzg@altern.org> wrote:
> Hi Darlan,
> Darlan Cavalcante Moreira <darcamo@gmail.com> writes:
> > Using the functions already provided by org-attach I could get
> > #+LINK: attach elisp:(org-open-file (org-attach-expand "%s"))
> > However, I always have to confirm the execution of the elisp code. 
> You want to set `org-confirm-elisp-link-function' to nil.

Thanks Bastien.

I knew there was some variable to control this for all elisp links. I would
prefer not to set this to nil, since I like the confirmation for other
elisp links and since links for attached files are common for me I thought
it could be a "built-in link". But that's OK.

> > Other useful things (just random thoughts) could be:
> >  - Perform some operation when a file is attached, such as replacing
> >    white-spaces in the file-name by underscores
> IMHO this goes beyond what org-attach.el should do: attach files.
> Besides, that would require even more confirmation steps.

My common use scenario for org-attach is to store files associated to a
sub-tree. For instance, when I receive a file by E-mail that I need to read
I create a task for it and attach the file. I usually need to change the
file name, since I don't like spaces and If would be practical if I could
attach the file as it is and know that org-attach would store it the way I
like. Is there a hook I could use to do this myself then? (I'm not a lisp
programmer, but think I can google tips about how to do this).

> >  - When a file is attached a link to it could be stored in the kill ring,
> >    in case the user want to insert it in the current text. Alternatively,
> >    an interactive function to insert a link to an attached file (using the
> >    same completions we already get for opening attached files) would also
> >    be very handy.
> Yes, good idea.
> From latest git, set `org-attach-store-link-p' to `t' if you want a link
> to be stored in `org-stored-links' when attaching a file.

This is even better then storing it in the kill ring. I noticed that the
link points to the location of the original file and not to the location
where it was attached (which is what thought it would do). Is this what you

> Thanks,
> -- 
>  Bastien


  reply	other threads:[~2011-03-04 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 20:39 Feature Request: attach link type Darlan Cavalcante Moreira
2011-03-03 10:18 ` Bastien
2011-03-04 18:10   ` Darlan Cavalcante Moreira [this message]
2011-03-04 21:56     ` Sébastien Vauban
2011-03-04 22:10       ` Darlan Cavalcante Moreira
2011-03-05  9:14     ` Bastien
2011-03-09 18:23       ` Darlan Cavalcante Moreira
2011-03-10 10:24         ` Bastien
2011-03-10 14:52           ` 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:

  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=4d712b0e.1838640a.4d18.ffffa691@mx.google.com \
    --to=darcamo@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \


* 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).