all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 17779@debbugs.gnu.org
Subject: bug#17779: 24.4.50; (elisp) `Using Interactive'
Date: Sun, 4 Aug 2019 19:05:28 -0700 (PDT)	[thread overview]
Message-ID: <7b436413-02f5-4516-87b4-04e2aba06124@default> (raw)
In-Reply-To: <87o9159k6k.fsf@mouse.gnus.org>

I don't even think it should say:

 "Usually this form will call various functions to read
  input from the user, most often through the minibuffer (*note
  Minibuffers::) or directly from the keyboard (*note Reading
  Input::)."

It can say that the form can read input etc. -
that's fine.  But I don't see the point of saying
"usually".  The point is that IF some argument
needs to be obtained by getting user input then
it that CAN be done by the form, e.g. reading from
the minibuffer etc.

But that's a nit.  ("Often" is better than "usually",
if you really want to stress that this is done often.)

> Yes, I think you're right -- the text starting with "Providing point or
> the mark" until the end of the example seems like very confusing text
> to
> include in an introduction to `interactive'.  The failure modes (if you
> can call it that) are hyper-specific to a very obscure case, and (as
> Drew says) what the user should do here depends on what the user wants.
> 
> So I think that bit should just be removed from the manual.
> 
> Any objections?

No objection from me, at least.  Thanks for
working on this.





  parent reply	other threads:[~2019-08-05  2:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 15:50 bug#17779: 24.4.50; (elisp) `Using Interactive' Drew Adams
2019-08-04 12:41 ` Lars Ingebrigtsen
2019-08-04 17:13   ` Eli Zaretskii
2019-08-05  9:29     ` Lars Ingebrigtsen
2019-08-05 16:25       ` Eli Zaretskii
2019-08-05  2:05   ` Drew Adams [this message]
2019-08-06  3:20     ` Richard Stallman

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=7b436413-02f5-4516-87b4-04e2aba06124@default \
    --to=drew.adams@oracle.com \
    --cc=17779@debbugs.gnu.org \
    --cc=larsi@gnus.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.