From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: user42_kevin@yahoo.com.au, 19812@debbugs.gnu.org
Subject: bug#19812: 24.4; suggest `shell-mode' not interactive
Date: Sat, 03 Aug 2019 10:22:44 +0300 [thread overview]
Message-ID: <83tvayemrf.fsf@gnu.org> (raw)
In-Reply-To: <87v9vfmjke.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Fri, 02 Aug 2019 21:52:17 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 02 Aug 2019 21:52:17 +0200
> Cc: 19812@debbugs.gnu.org
>
> As you point out, there's a lot of modes that only make sense in certain
> limited contexts, and having them be interactive isn't very helpful.
> I'm not sure it's that much of a problem in general, but it is a
> particular an issue with `shell-mode', since I'd guess that a lot of
> people type that instead of `M-x shell-script-mode' when starting to
> write new shell scripts.
>
> The following fixes this particular issue. Would something like this be
> welcome?
Are there no valid use cases where invoking shell-mode interactively
makes sense? If there are such use cases, we cannot disallow them
now.
next prev parent reply other threads:[~2019-08-03 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 4:07 bug#19812: 24.4; suggest `shell-mode' not interactive Kevin Ryde
2019-08-02 19:52 ` Lars Ingebrigtsen
2019-08-02 23:54 ` Kevin Ryde
2019-08-03 11:11 ` Lars Ingebrigtsen
2019-08-03 7:22 ` Eli Zaretskii [this message]
2019-08-03 11:08 ` Lars Ingebrigtsen
2019-08-04 19:11 ` Juri Linkov
2019-08-05 8:54 ` Kevin Ryde
2019-08-05 21:59 ` Juri Linkov
2019-08-07 6:46 ` Kevin Ryde
2019-08-23 0:59 ` Lars Ingebrigtsen
2019-08-27 22:13 ` Juri Linkov
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=83tvayemrf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19812@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=user42_kevin@yahoo.com.au \
/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.