unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61781@debbugs.gnu.org, Spencer Baugh <sbaugh@janestreet.com>
Subject: bug#61781: 28.2; (setq-default indent-tabs-mode nil) causes weird next-line behavior in *Help*
Date: Mon, 11 Sep 2023 18:03:03 -0700	[thread overview]
Message-ID: <CADwFkm=xgnXafR4Xn1QvjKQZ6kH8Xv6s8-DvSuVT6Nhwq8SMTA@mail.gmail.com> (raw)
In-Reply-To: <83h6vaktsj.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 25 Feb 2023 10:56:12 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Date: Fri, 24 Feb 2023 17:32:09 -0500
>>
>> >From emacs -Q:
>>
>> 1. M-: (setq-default indent-tabs-mode nil) RET
>> 2. Open up a help buffer, e.g. C-x 4 C-h
>> 3. Move point to the link for the first binding (find-file-other-window)
>> 4. C-n
>> 5. Observe that in addition to moving down, point also moves back one
>>    column (as if we had hit C-b).
>>
>> Without indent-tabs-mode set to nil, next-line stays in the same column.
>
> I can reproduce this in Emacs 28.2, but not in Emacs 29, since
> describe-prefix-bindings in Emacs 29 no longer heeds indent-tabs-mode,
> it always inserts tabs.  So if this problem still exists in Emacs 29,
> you or someone else will have to come up with a different reproducer.

Ping.  Specer, is this an issue for you in Emacs 29?  If so, could you
come up with a different reproducer?  Thanks in advance.





  reply	other threads:[~2023-09-12  1:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 22:32 bug#61781: 28.2; (setq-default indent-tabs-mode nil) causes weird next-line behavior in *Help* Spencer Baugh
2023-02-25  8:56 ` Eli Zaretskii
2023-09-12  1:03   ` Stefan Kangas [this message]
2023-09-12 13:10     ` Spencer Baugh
2023-09-12 13:51       ` Stefan Kangas

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='CADwFkm=xgnXafR4Xn1QvjKQZ6kH8Xv6s8-DvSuVT6Nhwq8SMTA@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=61781@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=sbaugh@janestreet.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 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).