From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Re: Feature Request: attach link type
Date: Fri, 04 Mar 2011 22:56:41 +0100 [thread overview]
Message-ID: <8062rymtwm.fsf@somewhere.org> (raw)
In-Reply-To: 4d712b0e.1838640a.4d18.ffffa691@mx.google.com
Hi Darlan and Bastien,
Darlan Cavalcante Moreira wrote:
>> > 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).
Just to comment on that point: reworking the filename is exactly what Gnus do
with attachment files, once you want to save them. It (optionally) do whatever
is needed to make them better, such as removing spaces, replacing accents,
etc...
Best regards,
Seb
--
Sébastien Vauban
next prev parent reply other threads:[~2011-03-04 21:56 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 [this message]
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:
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=8062rymtwm.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).