unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ian Nehera <delta29@shaw.ca>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 51171@debbugs.gnu.org
Subject: bug#51171: 27.2; `forward-word' w/arg bug in narrowed buffer
Date: Thu, 14 Oct 2021 12:22:50 +0300	[thread overview]
Message-ID: <83v920kljp.fsf@gnu.org> (raw)
In-Reply-To: <31D3ED6E-A1EB-4214-901F-FB62BF2A6922@shaw.ca> (message from Ian Nehera on Tue, 12 Oct 2021 17:17:14 -0700)

> From: Ian Nehera <delta29@shaw.ca>
> Date: Tue, 12 Oct 2021 17:17:14 -0700
> 
> To reproduce from 'emacs -Q /path/to/dcl.c’ (file attached):
>    1. M-x `subword-mode' (side question: should C-c C-w still use the
>       obsolete alias `c-subword-mode'?).
>    2. Navigate to the function 'int dirdcl(void)' and use
>       `narrow-to-defun' (C-x n d).
>    3. From the top of the buffer, use `forward-word' with an arg greater
>       than 1 (like C-u 2 M-f).
>    4. Repeat this with C-x z z z z... until you get an error around the
>       start of the while loop (2nd to last message in list below).
>    5. Moving point forward then trying the same command again will yield
>        the last message with a number greater than `point-max' (5741).
> 
> Other notes:
>       - The bug dissapears with a widened buffer or when narrowing to
>         earlier functions.
>       - `backward-word’ doesn’t seem to have the same problem.
>       - I'm reporting this from OSX 10.14.6 (homebrew), but it also occurs on
>         Arch Linux (emacs being installed from the standard pacman repos).

Stefan, any suggestions wrt this?





  reply	other threads:[~2021-10-14  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13  0:17 bug#51171: 27.2; `forward-word' w/arg bug in narrowed buffer Ian Nehera
2021-10-14  9:22 ` Eli Zaretskii [this message]
2022-09-12 12:02   ` 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=83v920kljp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51171@debbugs.gnu.org \
    --cc=delta29@shaw.ca \
    --cc=monnier@iro.umontreal.ca \
    /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).