unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 31137@debbugs.gnu.org
Subject: bug#31137: 27.0.50; `Info-find-node-2': Pass STRICT-CASE in last 2 `Info-find-node' calls?
Date: Thu, 12 Apr 2018 11:14:37 -0700 (PDT)	[thread overview]
Message-ID: <f509df90-e9de-48df-a3ff-389e939a1ae5@default> (raw)

At the end of `Info-find-node-2' we see this in the second
part of `unwind-protect':

;; If we did not finish finding the specified node,
;; go back to the previous one or to the Top node.
(unless (or Info-current-node no-going-back)
  (if Info-history
     (let ((hist (car Info-history)))
        (setq Info-history (cdr Info-history))
        (Info-find-node (nth 0 hist) (nth 1 hist) t)
        (goto-char (nth 2 hist)))
    (Info-find-node Info-current-file "Top" t)))))

Shouldn't those calls to `Info-find-node' pass along the
received value of arg STRICT-CASE?



In GNU Emacs 27.0.50 (build 3, x86_64-w64-mingw32)
 of 2018-03-21 built on CIRROCUMULUS
Repository revision: e70d0c9e66d7a8609450b2889869d16aeb0363b5
Windowing system distributor 'Microsoft Corp.', version 6.1.7601
Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Read-Only mode enabled in current buffer
Mark saved where search started
Mark set
Quit
Quit
Configured using:
 'configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install -C 'CFLAGS=-O2 -static -g3''

Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
TOOLKIT_SCROLL_BARS THREADS LCMS2





             reply	other threads:[~2018-04-12 18:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 18:14 Drew Adams [this message]
2018-04-12 18:46 ` bug#31137: 27.0.50; `Info-find-node-2': Pass STRICT-CASE in last 2 `Info-find-node' calls? Eli Zaretskii
2021-02-04 10:23   ` Lars Ingebrigtsen

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=f509df90-e9de-48df-a3ff-389e939a1ae5@default \
    --to=drew.adams@oracle.com \
    --cc=31137@debbugs.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 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).