all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xue Fuqiao <xfq.free@gmail.com>
To: raman <raman@google.com>
Cc: 21834@debbugs.gnu.org
Subject: bug#21834: 25.0.50; Info Node On Lexical Vars Ends Abruptly
Date: Thu, 5 Nov 2015 13:39:53 +0800	[thread overview]
Message-ID: <CAAF+z6HfoVdnvoR2rFxy9DjKYMkZ9vCjZM4ci4DDWqA68t=qQw@mail.gmail.com> (raw)
In-Reply-To: <p91pozpxkhx.fsf@google.com>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

On Thu, Nov 5, 2015 at 10:12 AM, raman <raman@google.com> wrote:
> Ends like so:
> <cite>
> interprets this as an indication that this is a variable known not to be
> </cite> in node
> File: elisp.info,  Node: Using Lexical Binding,  Prev: Lexical Binding,  Up: Variable Scoping
>

Cannot reproduce here.  On my Emacs build, the last paragraph is:
<cite>
   (To silence byte-compiler warnings about unused variables, just use
a variable name that start with an underscore.  The byte-compiler
interprets this as an indication that this is a variable known not to
be used.)
</cite>

A screenshot is also attached.

> In GNU Emacs 25.0.50.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll bars)
>  of 2015-10-21
> Repository revision: 6e3bac85d032eccd81454e4f6630fac7d829d88d

My build:

In GNU Emacs 25.0.50.4 (x86_64-apple-darwin15.0.0, NS appkit-1404.13
Version 10.11.1 (Build 15B42))
 of 2015-10-24
Repository revision: 7836e422e46721290c076969b87e277aa264ceca

$ makeinfo --version
makeinfo (GNU texinfo) 4.8

[-- Attachment #2: screenshot.png --]
[-- Type: image/png, Size: 266860 bytes --]

  reply	other threads:[~2015-11-05  5:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05  2:12 bug#21834: 25.0.50; Info Node On Lexical Vars Ends Abruptly raman
2015-11-05  5:39 ` Xue Fuqiao [this message]
2016-12-07 20:03   ` Glenn Morris

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='CAAF+z6HfoVdnvoR2rFxy9DjKYMkZ9vCjZM4ci4DDWqA68t=qQw@mail.gmail.com' \
    --to=xfq.free@gmail.com \
    --cc=21834@debbugs.gnu.org \
    --cc=raman@google.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.