From: "Philip K." <philip@warpmail.net>
To: emacs-devel@gnu.org
Subject: Updating dired-guess-shell-alist-default
Date: Tue, 07 Jul 2020 10:50:31 +0200 [thread overview]
Message-ID: <87imezhfoo.fsf@warpmail.net> (raw)
Hi,
I wonder if anyone else shares my point of view: while useful,
dired-do-shell-command seems somewhat outdated. Certain file formats
haven't changed much, and their handling is still ok (.patch, .tar.*,
.sig) but especially image, video files and documents suggest tools
that don't seem to be installed by default on most systems (xloadimage,
xpdf, ...).
Of course this can be mitigated by using dired-guess-shell-alist-user,
but I think that this shouldn't be necessary. I usually just map all
images, videos and documents to xdg-open, and changing the values to
something like this wouldn't be bad a bad idea, if you ask me
(especially because xdg-open doesn't block).
So if not xdg-open (at least on GNU/Linux and other XDG-compliant
systems), should the default value be changed to something that makes
dired-do-shell-command more useful, out of the box?
--
Philip K.
next reply other threads:[~2020-07-07 8:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 8:50 Philip K. [this message]
2020-07-07 14:19 ` Updating dired-guess-shell-alist-default Eli Zaretskii
2020-07-07 16:10 ` Philip K.
2020-07-07 18:37 ` Eli Zaretskii
2020-07-07 19:05 ` Philip K.
2020-07-07 19:24 ` Eli Zaretskii
2020-07-07 19:48 ` Stefan Monnier
2020-07-08 2:25 ` Eli Zaretskii
2020-07-08 4:12 ` Stefan Monnier
2020-07-07 19:52 ` Yuri Khan
2020-07-08 2:26 ` Eli Zaretskii
2020-07-08 2:48 ` Michael Welsh Duggan
2020-07-08 7:52 ` tomas
2020-07-07 20:38 ` Philip K.
2020-07-08 2:28 ` Eli Zaretskii
2020-07-08 4:15 ` Stefan Monnier
2020-07-08 14:21 ` Eli Zaretskii
2020-07-08 15:08 ` Stefan Monnier
2020-07-08 8:28 ` Philip K.
2020-07-08 14:24 ` Eli Zaretskii
2020-07-08 14:33 ` Philip K.
2020-07-09 16:21 ` Philip K.
2020-07-11 10:07 ` Eli Zaretskii
2020-07-11 11:07 ` Philip K.
2020-07-11 11:15 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imezhfoo.fsf@warpmail.net \
--to=philip@warpmail.net \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.