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

Hi Darlan,

Darlan Cavalcante Moreira <darcamo@gmail.com> writes:

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

I just introduced `org-confirm-elisp-link-not-regexp' which allows the
user to avoid confirmation step for elisp code matching a regexp.  Hope
that helps in your case.

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

I've been working a bit on your idea, it's possible to create a function
and to use it to rename a file when the user is attaching it - but there
are problems: for example, if this function changes, then there will be
*several* attachements for the same file...  we don't want that.

So, renaming the file belongs elsewhere IMHO.

>> >  - 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
> intended?

Yes.  Since the file is now also available as an attachment, a link to
the source file might be useful, while a link to the attached file is a
bit redundant with what org-attach allows you to do (get the file).

Does that make sense?



  parent reply	other threads:[~2011-03-05  9:14 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
2011-03-04 21:56     ` Sébastien Vauban
2011-03-04 22:10       ` Darlan Cavalcante Moreira
2011-03-05  9:14     ` Bastien [this message]
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=87aahaj5ee.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=darcamo@gmail.com \
    --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).