From: Arthur Miller <arthur.miller@live.com>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs-Devel List <emacs-devel@gnu.org>
Subject: Re: Friendlier dired experience [CODE INCLUDED]
Date: Thu, 05 Nov 2020 13:54:27 +0100 [thread overview]
Message-ID: <VI1PR06MB4526536A89758CB5AA069C3B96EE0@VI1PR06MB4526.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <20201105092232.fk4r5dexnay3eyln@E15-2016.optimum.net> (Boruch Baum's message of "Thu, 5 Nov 2020 04:22:32 -0500")
[-- Attachment #1: diredc-bookmark.png --]
[-- Type: image/png, Size: 35513 bytes --]
[-- Attachment #2: Type: text/plain, Size: 5049 bytes --]
Boruch Baum <boruch_baum@gmx.com> writes:
> On 2020-11-05 09:05, Arthur Miller wrote:
>> I hope that Boruch does not take it as personal critique
>
> Not at all. It was a good read; here's some feedback.
>
>> I don't use Sunrise
>
> My memory from looking at it years ago was that it was non-functioning
> abandon-ware.
No idea if it is abandon-ware; I don't use it; I used some year ago and it
was quite competent.
Looking at github, it seems like last commit was ~6 month ago:
https://github.com/sunrise-commander/sunrise-commander
>> Unfortunately for some features, as I read the diredc code; I would
>> probably be annoyed if they were in dired. Particularly if dired asked
>> yes/no if I really wish to bookmark a place and if I wish to start
>> diredc. If user bothered to press a 4-letter combination, then I think
>> we can be sure the user wish to create that bookmark; it is really
>> unnecessary to ask if I am really sure :-). Just my opinion.
>
> You read that snippet of code incorrectly. No such prompt.
Ok, sure I was just skimming and saw those yes/no questions. I have
downloaded and tested it now and her are few questions:
How do you do bookmarks? I just bookmarked
a folder with your shortcut C-c b a; and the bookmark does not show in
bookmarks list. furthermore, when I use C-c b j; it seems to show some byte
code, you can see it in the attached screenshot.
Another quick impression: opening new frame in the bacgkround is not
really the best feel. It didn't got neither raised nor focused.
Also my original frame got resized and centered on the screen, and
diredc took place of the original frame (but in background and not focused).
The dual pane wasn't so resilient; at least not to Gnus (nothing is
:-)). After switching to Gnus and back I was left with a single window.
I am not sure if I understand the docs correctly: is it supposed to
restore window layout and buffers automatically or do I need to take an
action? It didn't happened automatically so I tried diredc-restore. I
was than ask a question to choose between starting a new or choosing two
panes or something else. I choose two-pane, but I wasn't left with same
buffers after it executed.
After I switched to the mail to continue writing it again switched to
just one window. When I switched back it was still just one window. I
then tried running again diredc (C-x 5 d); it just moved my cursor back
to old frame. Running again diredc moved cursor back to second frame but
it never switched back to dual pane nor to original buffers I had in
diredc. I am sure I am using it wrong, but I don't see in the
accompanying docs how to switch between buffers and go back to dual-pane
and original buffers.
In connection to this, looking at those predefined variables; I am not
sure I find it really useful; you can see below what diredc exported
when I run it for the first time:
export d1="~/repos/emacs-related/emacs-diredc/" d2="" f1="~/repos/emacs-related/emacs-diredc/README.md" f2="" t1="(/home/arthur/repos/emacs-related/emacs-diredc/README.md)" t2="nil"
sh-5.0$ sh-5.0$ sh-5.0$
Documentation says they are useful dired values - but in which way are they
useful? Do I really need to export a shortcut to a README file if I am
already using Emacs? Am I supposed to open current file from the shell
in new Eamcs instance, or what was the intended workflow?
Sorry if I am obnoxious; these are just questions I was left with after
tryimg it.
Something positive:
I like your C-c C-k and '; I'll steal it for my own hack of term-toggle,
thanks! :-). I have eshell on F2 and term on F1, but ' was really nice;
I think I'll use it instead of F2.
>> History handling: can it not be handled by recentf/winner modes already?
>
> I've been a long-time happy user of winner, and found the answer to be
> no. Winner operates on all windows of a frame, not just the current
> dired buffer. Thus, if you had in your window configuration history
> temporary quick-shell buffer-windows or quick-file-view buffer-windows,
> they would pop in and out if you were using winner-undo to navigate
> sequentially in your dired history. Also, does winner-mode have a
> quick-jump to a specific history element?
>
>> I am not particulary against custom history handling, but recentf
>> already does it and winner has undo/redo stack maybe they can be reused?
>
> When I had tried recentf years ago, I was disappointed that its only
> interface was the ncurses menu. Is that still the case? In any event,
> a recentf menu will include ALL recently visited items, so that list
> will be a mixture of emacs files and dired buffers and who knows what
> else; a user would need to visually filter out the path-names ending
> with a file from those ending with a directory ...
We have Helm + fuzzy search to filter those out ...
>> Other functionality I would like to see is some from dired-hacks: toggle
>> and filters.
>
> What do you mean by "toggles and filters"?
https://github.com/Fuco1/dired-hacks#dired-subtree
https://github.com/Fuco1/dired-hacks#dired-filter
next prev parent reply other threads:[~2020-11-05 12:54 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 10:43 Friendlier dired experience [CODE INCLUDED] Boruch Baum
2020-11-03 10:54 ` Jean Louis
2020-11-03 11:15 ` Boruch Baum
2020-11-03 11:32 ` Joost Kremers
2020-11-03 12:22 ` Boruch Baum
2020-11-03 16:07 ` Jean Louis
2020-11-03 17:12 ` Boruch Baum
2020-11-03 19:31 ` Jean Louis
2020-11-03 21:13 ` Boruch Baum
2020-11-04 8:10 ` Jean Louis
2020-11-04 8:54 ` Boruch Baum
2020-11-04 9:57 ` Jean Louis
2020-11-04 10:39 ` Jean Louis
2020-11-04 13:17 ` Boruch Baum
2020-11-04 15:32 ` Joost Kremers
2020-11-04 15:58 ` Stefan Monnier
2020-11-04 17:23 ` Jean Louis
2020-11-04 17:15 ` Jean Louis
2020-11-04 15:28 ` Eli Zaretskii
2020-11-03 11:24 ` Boruch Baum
2020-11-03 15:10 ` Stefan Kangas
2020-11-03 16:10 ` Jean Louis
2020-11-03 17:16 ` Boruch Baum
2020-11-03 17:59 ` Michael Albinus
2020-11-03 19:10 ` Boruch Baum
2020-11-03 19:49 ` Jean Louis
2020-11-04 6:08 ` Pankaj Jangid
2020-11-04 19:57 ` Michael Albinus
2020-11-04 20:18 ` Yuri Khan
2020-11-04 20:29 ` Michael Albinus
2020-11-05 8:54 ` Boruch Baum
2020-11-05 10:11 ` Jean Louis
2020-11-05 13:31 ` Eli Zaretskii
2020-11-04 19:28 ` Stefan Kangas
2020-11-04 19:39 ` Boruch Baum
2020-11-05 15:00 ` Stefan Kangas
2020-11-06 9:34 ` Boruch Baum
2020-11-04 18:07 ` Stefan Monnier
2020-11-04 18:32 ` Boruch Baum
2020-11-04 18:55 ` Stefan Monnier
2020-11-05 8:05 ` Arthur Miller
2020-11-05 9:22 ` Boruch Baum
2020-11-05 12:54 ` Arthur Miller [this message]
2020-11-05 13:34 ` Jean Louis
2020-11-05 14:38 ` Boruch Baum
2020-11-05 15:05 ` Stefan Monnier
2020-11-05 15:34 ` Arthur Miller
2020-11-05 15:45 ` Stefan Monnier
2020-11-05 16:18 ` Adam Porter
2020-11-05 17:02 ` Stefan Monnier
2020-11-05 17:09 ` Drew Adams
2020-11-05 17:08 ` Drew Adams
2020-11-05 16:19 ` Arthur Miller
2020-11-05 17:56 ` Jean Louis
2020-11-05 17:08 ` Drew Adams
2020-11-06 9:15 ` Boruch Baum
2020-11-06 14:14 ` Stefan Monnier
2020-11-06 16:28 ` Drew Adams
2020-11-06 19:43 ` Adam Porter
2020-11-06 20:24 ` Drew Adams
2020-11-06 20:57 ` Adam Porter
2020-11-07 0:30 ` Daniel Martín
2020-11-08 9:36 ` Boruch Baum
2020-11-08 12:09 ` Arthur Miller
2020-11-08 12:40 ` Boruch Baum
2020-11-08 13:37 ` Jean Louis
2020-11-08 16:48 ` Drew Adams
2020-11-08 18:26 ` on hyperlinks (bookmarks) Jean Louis
2020-11-08 19:47 ` Drew Adams
2020-11-08 20:26 ` Jean Louis
2020-11-08 13:45 ` Friendlier dired experience [CODE INCLUDED] Arthur Miller
2020-11-08 16:48 ` Drew Adams
2020-11-08 17:37 ` Boruch Baum
2020-11-08 19:24 ` Drew Adams
2020-11-05 15:29 ` Arthur Miller
2020-11-05 16:25 ` Adam Porter
2020-11-05 16:47 ` Arthur Miller
2020-11-05 18:00 ` Jean Louis
2020-11-05 18:56 ` Adam Porter
2020-11-05 19:33 ` Jean Louis
2020-11-06 4:55 ` Arthur Miller
2020-11-06 9:49 ` Boruch Baum
2020-11-06 9:42 ` Boruch Baum
2020-11-05 14:21 ` Stefan Monnier
2020-11-05 9:56 ` Jean Louis
2020-11-05 17:07 ` Drew Adams
2020-11-08 19:46 ` Juri Linkov
2020-11-08 19:50 ` Sv: " arthur miller
2020-11-09 22:45 ` Mathias Dahl
2020-11-09 23:20 ` Stefan Monnier
2020-11-10 0:05 ` Drew Adams
2020-11-10 2:31 ` T.V Raman
2020-11-10 6:47 ` Jean Louis
2020-11-11 19:23 ` Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2020-11-04 17:28 Boruch Baum
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=VI1PR06MB4526536A89758CB5AA069C3B96EE0@VI1PR06MB4526.eurprd06.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=boruch_baum@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.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).