emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eric Danan <eric.danan@u-cergy.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-attach: Allow attaching file from visited buffer
Date: Thu, 21 Jun 2018 17:47:30 +0200	[thread overview]
Message-ID: <87y3f8cfal.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAMBH+RZ7KkA0ws_uC5csMMmjXEH47a+nSjOs4JbALNm1E0a2vw@mail.gmail.com> (Eric Danan's message of "Thu, 21 Jun 2018 16:27:12 +0200")

Hello,

Eric Danan <eric.danan@u-cergy.fr> writes:

> When the file to attach is already open in emacs, it is generally
> faster to select it from the buffer list than navigating to it through
> the file system. This patch adds a `b' command to the attach
> dispatcher that reads a buffer and writes it in the attachment
> directory.

Thank you.

One issue is that we're losing the method choice (symlink, copy,
hardlink).

However, `org-attach-attach' already offers to start file system
navigation from a Dired side buffer, if any. We may extend this idea: if
there is a buffer currently displayed in another window, but no Dired
buffer, offer its default directory as a start for completion.

Another idea is to create a new function that will attach the current
file to the subtree in another window. See
`org-attach-dired-to-subtree', for example.

If you haven't signed FSF papers, you need to add TINYCHANGE at the end
of the commit message.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2018-06-21 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21 14:27 [PATCH] org-attach: Allow attaching file from visited buffer Eric Danan
2018-06-21 15:47 ` Nicolas Goaziou [this message]
2018-06-25 13:04   ` Eric Danan
2018-11-02  9:24     ` Nicolas Goaziou
2018-11-02 13:14       ` Eric Danan

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=87y3f8cfal.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric.danan@u-cergy.fr \
    /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).