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: Thu, 03 Mar 2011 11:18:06 +0100	[thread overview]
Message-ID: <87mxlco6ch.fsf@gnu.org> (raw)
In-Reply-To: <4d5c35ef.0ae9640a.3fc9.0852@mx.google.com> (Darlan Cavalcante Moreira's message of "Wed, 16 Feb 2011 17:39:08 -0300")

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.

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

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



Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.

  reply	other threads:[~2011-03-03 10:18 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 [this message]
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
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=87mxlco6ch.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).