unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "63875@debbugs.gnu.org" <63875@debbugs.gnu.org>
Subject: bug#63875: 26.3; Doc of `dired-guess-shell-alist-user'
Date: Sat, 3 Jun 2023 17:20:14 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488C421224574543A1D4F5BF34FA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83v8g47bmd.fsf@gnu.org>

> > But it would be good, I think, to add that it's
> > not just about shell commands.  Some users will
> > not recognize that they can invoke executable
> > programs this way.
> 
> Shell commands are a super-set of executable programs, so I see no
> reason to change anything here.  The variable is used to invoke
> commands via a shell, so "shell command" is exactly right.

Yes, but many Emacs users won't know that.

Unless they're programmers or they are used to
GNU or Unix or Linux, some users won't guess
that they can use this user option to associate
applications (executable binaries) with file
names for Emacs.

MS Windows, for example, may know how to create
default file associations for programs invoked
normally (for Windows), but Emacs users on
Windows might well not guess that they can
associate files with programs for Emacs.

If you disagree that this is the case, fine.
But if you agree then maybe you'll consider
explicitly mentioning this use of the option.





  reply	other threads:[~2023-06-03 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03 16:08 bug#63875: 26.3; Doc of `dired-guess-shell-alist-user' Drew Adams
2023-06-03 16:14 ` Drew Adams
2023-06-04 16:44   ` Juri Linkov
2023-06-03 16:16 ` Eli Zaretskii
2023-06-03 16:21   ` Drew Adams
2023-06-03 16:24     ` Eli Zaretskii
2023-06-03 16:26     ` Drew Adams
2023-06-03 16:29       ` Eli Zaretskii
2023-06-03 17:20         ` Drew Adams [this message]
2023-06-03 18:50           ` Eli Zaretskii
2023-06-03 19:29             ` Drew Adams

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=SJ0PR10MB5488C421224574543A1D4F5BF34FA@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=63875@debbugs.gnu.org \
    --cc=eliz@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 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).