From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 17779@debbugs.gnu.org
Subject: bug#17779: 24.4.50; (elisp) `Using Interactive'
Date: Sun, 04 Aug 2019 20:13:28 +0300 [thread overview]
Message-ID: <83r260dfbb.fsf@gnu.org> (raw)
In-Reply-To: <87o9159k6k.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Sun, 04 Aug 2019 14:41:55 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 04 Aug 2019 14:41:55 +0200
> Cc: 17779@debbugs.gnu.org
>
> 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'.
It isn't an introduction, it's a full description of how to use
'interactive'. And I find nothing confusing about that part of the
text, I think that single paragraph with 2 examples to illustrate the
issue is quite appropriate here.
Please just leave this alone. I object in principle to making
significant changes in the manuals based on hair-splitting arguments,
not in the least because someone will always come back later and claim
that the new text is worse, or less clear, or whatever.
At least in the docs, let's please avoid making changes for reasons
that are so minuscule that they need a magnifying glass to see. We
should not waste our energy making "limit-cycle" kind of changes.
next prev parent reply other threads:[~2019-08-04 17:13 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 [this message]
2019-08-05 9:29 ` Lars Ingebrigtsen
2019-08-05 16:25 ` Eli Zaretskii
2019-08-05 2:05 ` Drew Adams
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=83r260dfbb.fsf@gnu.org \
--to=eliz@gnu.org \
--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.