From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17779@debbugs.gnu.org
Subject: bug#17779: 24.4.50; (elisp) `Using Interactive'
Date: Mon, 05 Aug 2019 11:29:27 +0200 [thread overview]
Message-ID: <87blx4dkp4.fsf@mouse.gnus.org> (raw)
In-Reply-To: <83r260dfbb.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Aug 2019 20:13:28 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> 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.
I hadn't read that section before, and I just found it an odd thing to
talk about in that context -- as if there was something in particular
about code in the interactive spec that has to be extra careful about
buffer contents changing, when that's a general issue with points.
> 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.
Emacs has great documentation, but it (as everything else) can be
improved. The argument you're making here seems to veer into the "well,
everything is subjective, so let's not even try" territory, which I know
you don't mean. While going through these doc clarification bug
reports, I do close the ones I don't think are not worth doing and only
bring up the ones I think could benefit from some consideration.
But you think the text here is fine, so I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-05 9:29 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 [this message]
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=87blx4dkp4.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=17779@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 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.