From: pillule <pillule@riseup.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pillule <pillule@riseup.net>,
poenikatu@fastmail.co.uk, stefan@marxist.se,
15069@debbugs.gnu.org
Subject: bug#15069: [PATCH] Bug: 15069: Correct functioning in the *scratch* buffer
Date: Mon, 24 May 2021 15:48:20 +0000 [thread overview]
Message-ID: <87bl903zgb.fsf@host.localdomain> (raw)
In-Reply-To: <83pmxjl1jo.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> It says "install the functions", which means they should be
> evaluated
> or loaded, and that tells you the Lisp code should already be
> available in some Lisp buffer, whether it's *scratch* or some
> *.el
> file.
>
> So why did you think it speaks about the text in the Info
> buffer?
> That's not the intent of the text, and the text says as much.
That is what I have done when studying this manual, I don't
remember well,
but I may have been comforted in this habit by the following
sections :
(info "(eintr) How to Evaluate")
« In addition to typing keyboard commands, we have seen a second
way to
evaluate an expression: by positioning the cursor after a list and
typing ‘C-x C-e’. This is what we will do in the rest of this
section.
There are other ways to evaluate an expression as well; these will
be
described as we come to them.»
(info "(eintr) Buffer Names")
« If you are reading this in Info inside of GNU Emacs, you can
evaluate
each of the following expressions by positioning the cursor after
it and
typing ‘C-x C-e’.»
Finally the section :
(info "(eintr) count-words-in-defun")
« Now we can try out ‘count-words-defun’: install both
‘count-words-in-defun’ and ‘count-words-defun’, and set the
keybinding,
and then place the cursor within the following definition:»
^_____________________________^
So I can understand one may be confused to discover that in this
case,
he or she must instead copy the following definition in a separate
file,
then call the command `count-words-in-defun' within it.
> So I'm not sure we should install this fix. Any other opinions?
>
> In any case:
>
> . just talking about *scratch* is too restrictive
> . the commit log message is not according to our conventions
> (see
> CONTRIBUTE)
Yes please don't.
--
next prev parent reply other threads:[~2021-05-24 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 11:32 bug#15069: Introduction to Elisp 14.3: Function 'count-words-defun' does not work as described Sian Mountbatten
2013-08-11 11:47 ` bug#15069: Bug: 15069: Correct functioning in the *scratch* buffer Sian Mountbatten
2021-05-21 19:39 ` bug#15069: [PATCH] " pillule
2021-05-22 6:34 ` Eli Zaretskii
2021-05-24 15:48 ` pillule [this message]
2021-08-21 13:44 ` bug#15069: Introduction to Elisp 14.3: Function 'count-words-defun' does not work as described Lars Ingebrigtsen
2021-08-30 20:02 ` Trust me I am a Doctor
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl903zgb.fsf@host.localdomain \
--to=pillule@riseup.net \
--cc=15069@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=poenikatu@fastmail.co.uk \
--cc=stefan@marxist.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).