From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: dalanicolai Newsgroups: gmane.emacs.bugs Subject: bug#43463: 27.1; Elisp manual error, printed text in Interaction buffer Date: Sun, 20 Sep 2020 18:24:48 +0200 Message-ID: References: <8d15246b145ad2b7aa616aedd7b28c4d6b40f1d4.camel@gmail.com> <834knw7c97.fsf@gnu.org> <83o8m0zfsm.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000d99a3905afc12c44" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1251"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 43463@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Sep 20 18:27:36 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kK2Bc-0000DH-1a for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 20 Sep 2020 18:27:36 +0200 Original-Received: from localhost ([::1]:51980 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kK2Bb-000171-1G for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 20 Sep 2020 12:27:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35738) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kK2A6-00086A-19 for bug-gnu-emacs@gnu.org; Sun, 20 Sep 2020 12:26:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40926) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kK2A5-0008SJ-Nx for bug-gnu-emacs@gnu.org; Sun, 20 Sep 2020 12:26:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kK2A5-0005P9-Jo for bug-gnu-emacs@gnu.org; Sun, 20 Sep 2020 12:26:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: dalanicolai Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 20 Sep 2020 16:26:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43463 X-GNU-PR-Package: emacs Original-Received: via spool by 43463-submit@debbugs.gnu.org id=B43463.160061910620710 (code B ref 43463); Sun, 20 Sep 2020 16:26:01 +0000 Original-Received: (at 43463) by debbugs.gnu.org; 20 Sep 2020 16:25:06 +0000 Original-Received: from localhost ([127.0.0.1]:52472 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kK29C-0005Nx-4b for submit@debbugs.gnu.org; Sun, 20 Sep 2020 12:25:06 -0400 Original-Received: from mail-ua1-f44.google.com ([209.85.222.44]:46900) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kK29B-0005NN-B8 for 43463@debbugs.gnu.org; Sun, 20 Sep 2020 12:25:05 -0400 Original-Received: by mail-ua1-f44.google.com with SMTP id z46so3523323uac.13 for <43463@debbugs.gnu.org>; Sun, 20 Sep 2020 09:25:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+PJTNANI0a+WGodhr/yAc8kUoKdgklFKK5Y09orM2/I=; b=nVbRMteIuoBc2daZ8gHQ5PFSN4zD61AQLg1FU8t1NxanX0Uf6OWZKTifKdKZSUyCiq SqaxVTcCfdvwp+ghHtiSt3ZI4sRNUdFFou4erLPoRM+oXfU6d9hb5oXH449akra/jObd alAtKNmcd3iUfE7G+e/ParRUlwMbwAXmGz9XzeObZioievVC/nDDivQghazAJ78lCaPr YhkRZP1bP+jH+dbPzNgfBMg+RKBr8YcKmCUAbWtTXVXzBem5PKt8E2SlCacEbKGHww1j QP9ea7BuGPPt+yPGJsKBB9jD3qrfo7WvS3ryPZC3isWTWPCFrPY0SGumK34qxdsGviyk U9yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+PJTNANI0a+WGodhr/yAc8kUoKdgklFKK5Y09orM2/I=; b=p3V35CpN6iUk9qCxRB9e2CGFxh2Xo1CEBTyhQ4bRjMSeztqcUHbIYus1/UeNQS6RBy QbcgXu6W/pSTT0uhoSLci7p7qGwIc1rdD44ACdK3uaUr/Iq0xglYlKOPo9z6sw5lMWQU bfpZFSXWjKaCCoyyGEPLP1qoUOszj5R/MczaV6+fJztuXXk8rgDihwN/PenRoO9GEf3N Rims47wT6LiFORaRpfrv/L31/l/xBeJ0aR4evQhVhITJFXjfFSo4GOhIHC3qrh2/rKAn bsf06Q4b0ZswninsnRBT9IBrlM4xSuvMwYNNx6ecmdplJeDLFbgr6a8jf6vU6KtNNM8B 2XgQ== X-Gm-Message-State: AOAM533Ck/HpYw2flP6R/0wiRh0O7eZ//op6Dp7rSWftgzrQzrrih2SQ xgSbCZew/k10PdXrNM8Fu3h9zoOCUPCAoAcRS0g= X-Google-Smtp-Source: ABdhPJyKBMGyQXiQ3uChUVmW0OQW1sMisqi4DWUu3puVBLsGkeHLidKYD1la3R/mMAX39/jJYdISAzed//vwu1RTViE= X-Received: by 2002:ab0:5495:: with SMTP id p21mr9174565uaa.109.1600619099559; Sun, 20 Sep 2020 09:24:59 -0700 (PDT) In-Reply-To: <83o8m0zfsm.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:188516 Archived-At: --000000000000d99a3905afc12c44 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ah okay thanks, will use reply all then. Yes indeed, I think adding only that would make it less confusing because the word "execute" is somewhat ambiguous here. Then people get a hint and can look it up (looking a bit more I think the C-j functionality is "not really over-advertised"). Of course the part "execute example code" could link to section 27.7 of the Elisp manual and/or in a "Lisp Interaction buffer" could become a link to section 27.10. It might be a little excessive, but the excessive documentation is one of the aspects that makes Emacs my favorite editor. But otherwise just adding the few words would make it much clearer for me already. Thanks again for your great work! On Sun, 20 Sep 2020 at 16:25, Eli Zaretskii wrote: > [Please use Reply All to reply, so that the discussion gets recorded > by the bug tracker.] > > > From: dalanicolai > > 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 =E2=80=98*scratch*=E2=80=99), 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? > --000000000000d99a3905afc12c44 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ah okay thanks, will use reply all then.
Ye= s indeed, I think adding only that would make it less confusing because the= word "execute" is somewhat ambiguous here. Then people get a hin= t and can look it up (looking a bit more I think the C-j functionality is &= quot;not really over-advertised"). Of course the part "execute example code" could link to section 27.7 of the= Elisp manual and/or in a "Lisp Interaction buffer" could become = a link to section 27.10. It might be a little excessive, but the excessive = documentation is one of the aspects that makes Emacs my favorite editor. Bu= t otherwise just adding the few words would make it much clearer for me alr= eady.
Thanks again for your g= reat work!

On Sun, 20 Sep 2020 at 16:25, Eli Zaretskii <= eliz@gnu.org> wrote:
[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 pl= acing 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 s= hould get printed within the *scratch*
> buffer itself:
>
> "If you execute example code in a Lisp Interaction buffer (such a= s the
> buffer =E2=80=98*scratch*=E2=80=99), the printed text is inserted into= the buffer."

Would it be enough to say

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

IOW, how to "execute the code in the buffer" was not explained, a= nd we
need to explain it.=C2=A0 Right?
--000000000000d99a3905afc12c44--