all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Kevin Ryde <user42_kevin@yahoo.com.au>
Cc: 19812@debbugs.gnu.org
Subject: bug#19812: 24.4; suggest `shell-mode' not interactive
Date: Sat, 03 Aug 2019 13:11:40 +0200	[thread overview]
Message-ID: <87a7cqld03.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87v9vf2kdw.fsf@blah.blah> (Kevin Ryde's message of "Sat, 03 Aug 2019 09:54:51 +1000")

Kevin Ryde <user42_kevin@yahoo.com.au> writes:

> Maybe :interactive, just to write it in the positive sense.  The default
> must be t for compatibility.

That makes sense, and is easy to implement in this case.  We usually
treat the absence of a parameter the same as nil (since Emacs Lisp isn't
Common Lisp), but we don't have to do that here.

> A couple of words in the docs could note that special modes usually
> should be nil.

True, but I don't think we need to limit the interactivity here, though.
When there's little chance of confusion, having the mode be interactive
isn't that big a deal (and might be useful for somebody, sometime).

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-08-03 11:11 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 [this message]
2019-08-03  7:22   ` Eli Zaretskii
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=87a7cqld03.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=19812@debbugs.gnu.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.