all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dalanicolai <dalanicolai@gmail.com>
Cc: 43463@debbugs.gnu.org
Subject: bug#43463: 27.1; Elisp manual error, printed text in Interaction buffer
Date: Sun, 20 Sep 2020 17:25:13 +0300	[thread overview]
Message-ID: <83o8m0zfsm.fsf@gnu.org> (raw)
In-Reply-To: <CACJP=3n8rJ0prugJd5K+Y3jcLP38E1qH8NdF14hk1a48Un6J-Q@mail.gmail.com> (message from dalanicolai on Sun, 20 Sep 2020 15:59:03 +0200)

[Please use Reply All to reply, so that the discussion gets recorded
by the bug tracker.]

> From: dalanicolai <dalanicolai@gmail.com>
> Date: Sun, 20 Sep 2020 15:59:03 +0200
> 
> I copy the example text into a *scratch* buffer, and evaluate it by placing the cursor behind the code and
> press C-x C-e, the text is then printed in the echo-area.
> However the following line from Section 1.3.4 suggests to me that it should get printed within the *scratch*
> buffer itself:
> 
> "If you execute example code in a Lisp Interaction buffer (such as the
> buffer ‘*scratch*’), the printed text is inserted into the buffer."

Would it be enough to say

  "If you execute ... by typing C-j after the closing parentheses, the
  printed text is inserted ..."

IOW, how to "execute the code in the buffer" was not explained, and we
need to explain it.  Right?





  parent reply	other threads:[~2020-09-20 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17  4:19 bug#43463: 27.1; Elisp manual error, printed text in Interaction buffer dalanicolai
2020-09-17 13:40 ` Eli Zaretskii
     [not found]   ` <CACJP=3n8rJ0prugJd5K+Y3jcLP38E1qH8NdF14hk1a48Un6J-Q@mail.gmail.com>
2020-09-20 14:25     ` Eli Zaretskii [this message]
2020-09-20 16:24       ` dalanicolai
2020-09-20 16:39         ` Eli Zaretskii

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=83o8m0zfsm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=43463@debbugs.gnu.org \
    --cc=dalanicolai@gmail.com \
    /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.