From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [rfc] org-dired
Date: Wed, 15 Nov 2017 12:07:08 +0100 [thread overview]
Message-ID: <84inebztpf.fsf@gmail.com> (raw)
In-Reply-To: 87mv3r1mgh.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> Prepare
>> - In a dired buffer mark files or have the cursor on a file.
>> - Have also an org mode window open.
>> - Place the cursor in an orgee. (Orgee is short for org subtree.)
>> Act
>> - M-x org-dired-attach-hardlinked-to-next-best-orgee
>> Enjoy
>
> Why is hard linking mandatory? Couldn't this function obey to
> `org-attach-method'?
>
>> - Find the files attached to the orgee.
>>
>> Feel free to play with the implementation.
>>
>> WDYT?
>
> According to this description, I think it could be implemented as
> a function within "org-attach.el" instead of a new library.
>
> Also, in the context of Org, an "org subtree" is simply a "subtree".
> I prefer "subtree" over "orgee".
I just pushed the functionality to master.
With the lines
(add-hook
'dired-mode-hook
(lambda ()
(define-key dired-mode-map (kbd "C-c C-x a") #'org-attach-dired-attach-to-next-best-subtree)
(define-key dired-mode-map (kbd "C-c C-x c") #'org-attach-dired-attach-to-next-best-subtree-cp)
(define-key dired-mode-map (kbd "C-c C-x m") #'org-attach-dired-attach-to-next-best-subtree-mv)
(define-key dired-mode-map (kbd "C-c C-x l") #'org-attach-dired-attach-to-next-best-subtree-ln)
(define-key dired-mode-map (kbd "C-c C-x s") #'org-attach-dired-attach-to-next-best-subtree-lns)))
in the config file dired gets the functionality on the respective keys.
Critique and improvements welcome, as always, thanks,
Marco
next prev parent reply other threads:[~2017-11-15 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 15:17 [rfc] org-dired Marco Wahl
2017-11-12 16:38 ` Nicolas Goaziou
2017-11-12 17:53 ` Marco Wahl
2017-11-15 11:07 ` Marco Wahl [this message]
2017-11-15 11:38 ` Nicolas Goaziou
2017-11-15 13:54 ` Marco Wahl
2017-11-21 22:48 ` Nicolas Goaziou
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=84inebztpf.fsf@gmail.com \
--to=marcowahlsoft@gmail.com \
--cc=emacs-orgmode@gnu.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).