emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Marco Wahl <marcowahlsoft@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [rfc] org-dired
Date: Sun, 12 Nov 2017 17:38:38 +0100	[thread overview]
Message-ID: <87mv3r1mgh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <84bmk7ttkh.fsf@gmail.com> (Marco Wahl's message of "Sun, 12 Nov 2017 16:17:34 +0100")

Hello,

Marco Wahl <marcowahlsoft@gmail.com> writes:

> org-dired (https://github.com/marcowahl/org-dired) is a experimental
> little tool to ease attaching files to org subtrees via dired.
>
> Actually I use this feature quite often.
>
> Up to now org-dired-attach-hardlinked-to-next-best-orgee is the only
> function available.
>
> The flow goes like so
>
>     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".

> Thanks for your time,

Thank you for your work.

Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2017-11-12 16:38 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 [this message]
2017-11-12 17:53   ` Marco Wahl
2017-11-15 11:07   ` Marco Wahl
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=87mv3r1mgh.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=marcowahlsoft@gmail.com \
    /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

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