#dired is a tool that seems super powerful, but I don't use it often enough to stay familiar with the features. This sounds like a great fix to that issue!
The original announcement from the package author:
I missed #KDE#Dolphin's filtering ability in #Emacs#Dired. The dired-goto-file works when you aim at one single file, but it is not enough when you have tens of files and you want to "narrow" your view to files that match certain pattern (regex, glob, or fixed string).
Turns out there is a nice package called dired-narrow that does exactly that with very handy defaults.
@apublicimage I haven't installed consult. Does it also allow you to interact with the dired buffer while typing the filtering pattern? dired-narrow allows to interact with directories and open then while the point is still at the minibuffer, which is quite handy, plus if you treat dired buffer as a text buffer (as occur does), you will lose context if you have inserted subdirectories (using i).
Introducing Cleandesk.el, a small collection of functions to rapidly rename and process files in Dired.
Pictures, PDFs and many other kinds of files frequently end up on my Desktop. In the past, I used Hazel and/or Devonthink (both macOS only) to automatically rename and refile. Cleandesk offers an alternative (manual) approach for these tasks from within #Emacs. It draws on #Dired and #fd.
To be sure, vanilla Dired probably can do most of this. But perhaps neither as convenient nor as swift. 😉
Ever since I found out that #emacs#dired allows me to use S to symlink exactly how C and R can be used to copy/rename, I try to always do my symlinks in dired in emacs and not in the terminal.
No one can keep ln -s straight because depending on the specifics, the way your brain deals with sentence ordering can change. From/to, source/destination, all get muddled with here/there. Does it mean that what's here points to what's there or does what's there point to what's here? What's the original which I should not delete gets confusing.
@harish Ah. So the thing is the original and the where is the other place it will show up at? That's a nice way to think. I would still prefer the emacs way, but this might be useful. I'll keep it in mind.
My Elisp package for history in Dired was added to MELPA
repository. 🎂
I added alternative implementation of history with tab-line
mode. 🤹 This implementation work perfect, fast and able to work
under root console or any terminal. ⌘
I also solved in Dired:
selection by region selection, not by marks ●
customization of opening file in other window ●
I am going to write article about configuration of Emacs as a
file manager.
🏄
@sping@publicvoit I was a bit confused when I first read that article, because I thought consult-buffer can do all that and was even mentioned in the article. So now I think the author simply was unaware. Or am I still missing something?
I posted request to MELPA repository for my new package for Dired
filemanger in Emacs. 🐾💜😊
Emacs has is very advanced filemanager (Dired) it is like
MidnightCommander and FarManager, but much better, because it
is customizable as beyond imagination.
Even Vim don't have modern fast navigation, that is why my
package is awesome. 😈
Now I don't need OS Environment, all I need is Emacs, console
and browser. File manager now is in Emacs. ⛅
Thunar was very good, but too simple. ☄️
Maybe my package will became quickly very popular. 💅
#Emacs people: what is the canonical way to read a list of filenames? #Dired and completing-read-multiple can be both be used but are both clumsy when most of the times only one wants to choose on or two files. I am asking because of https://codeberg.org/rahguzar/filechooser
@rahguzar@sqrtminusone A dialog that allows you to mark files already exist in Emacs, dired. Soyounjzst need to write a function tgat operates on these marked files. You gave many examples on how to do that: other fired functions.
@holgerschurig@sqrtminusone this is already implemented and is pretty good for selecting a large number of files. When I want to choose only 1 or 2 I always end up wishing I was dealing with read-file-name and almost always I want only one file.
The buffer becomes editable, so you can do all sorts of fun things quickly. I like using macros to do file renames, especially when it would take me longer to figure out the regex/pattern than it would for me to record the keystrokes I want effected.
Ich hatte gehofft, mir könnte der in #emacs integrierte Dateimanager #dired genügen. Leider nicht, denn jeder Verzeichniswechsel öffnet einen neuen Buffer. Bedeutet, durch 10 Verzeichnisse navigiert und 9 weitere Buffer sind im Hintergrund aktiv. Keine Ahnung, wie man auf die Idee kommt, dies könnte eine gute sein. In meinen Augen Schwachsinn. Muss ich mich doch mit #nerdtree oder ähnliches befassen.
@sqrtminusone 👍 dired-subtree is great. I wonder why you don't have 'hide details', bound to "(" interactively, enabled though. Doesn't the stuff bother you?
@ctietze No, I guess I'm just used to it. And I often find the details useful, e.g. I immediately see that a file created by some Docker container has wrong ownership, or that some elisp file or log file is much larger than the rest.
Besides, I use EXWM, and I rarely have more than 2 windows of Dired side by side, so there isn't any space lost. My following splits are all horizontal if I need more.