From: "Paul W. Rankin" <hello@paulwrankin.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emulating Scrivener's binder feature
Date: Wed, 03 Apr 2019 19:34:14 +1000 [thread overview]
Message-ID: <m2wokbl9ex.fsf@paulwrankin.com> (raw)
In-Reply-To: <530ddfc1-e38e-4e7b-864d-e6cc1d1ccb76@default>
On Tue, Apr 02 2019, Drew Adams wrote:
>> Before I go to far,
>
> Please _do_ go far into this. Such effort is never wasted, IMO.
>
>> Question 1: Has someone already made something like this?
>> I don't want to reinvent the wheel...
>
> There is not only one wheel. Wheels often need reinventing.
Thanks Drew, I appreciate the encouragement :)
> FYI, here is something similar, but it does not correspond
> to everything you describe:
>
> 1. You can create a Dired buffer that has any combination
> of files and directories that you like. This feature
> is not very well known, but it's always been there.
>
> If you use library Dired+ then it's a bit easier to
> create such buffers interactively (and you can
> interactively create Dired buffers as unions etc. of
> other Dired buffers, and add arbitrary files and dirs
> to an existing Dired buffer).
>
> However, it is not possible (until someone implements
> it!) to sort such a Dired buffer with ad hoc entries.
I am a big fan of the `i' key in Dired. I will check out Dired+.
> 2. If you use library Bookmark+ then you can bookmark Dired
> buffers, including those just described (i.e., with ad
> hoc entries from anywhere). Jumping to such a bookmark
> restores the Dired buffer, including all of its markings
> omitted files, `ls' switches, inserted subdirs, etc.
>
> This gives you a persistent way to record and restore
> the files and dirs of a project, for example. You can
> also create different bookmark display lists or different
> bookmark files, so you can list only the bookmarks for
> a given project or have different views of a project or
> parts of a project. You can also bookmark Emacs desktops,
> and quickly switch among them, to flip between different
> projects or different views of a project.
>
> You can also bookmark a Dired tree. This gives you a
> set of Dired bookmarks that represent a hierarchy and
> are opened together.
>
> Bookmark+ also lets you tag bookmarks (and so bookmarked
> files and directories) with arbitrary strings or even
> Lisp key-value pairs. This gives you another way to
> access/view/define sets of bookmarks (thus files & dirs).
Excellent! I think Bookmarks+ will offer a lot of clues on a good
implementation, as essentially it will be a case of "bookmarking" all
the files in the project directory in a specific order and
tagging/annotating them. The other half of things is navigating around
the project hierachy from the project files themselves (e.g.
next/previous). Thanks :)
--
https://www.paulwrankin.com
next prev parent reply other threads:[~2019-04-03 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 8:09 Emulating Scrivener's binder feature Paul W. Rankin
2019-04-01 15:06 ` Drew Adams
2019-04-03 9:34 ` Paul W. Rankin [this message]
2019-04-01 15:27 ` Skip Montanaro
2019-04-01 16:57 ` Marcin Borkowski
2019-04-03 9:59 ` Paul W. Rankin
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wokbl9ex.fsf@paulwrankin.com \
--to=hello@paulwrankin.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).