unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52163@debbugs.gnu.org, iung@autistici.org
Subject: bug#52163: 28.0.60; visual-line-mode breaks C-a and C-e in extreme case
Date: Sat, 15 Jan 2022 14:08:22 +0100	[thread overview]
Message-ID: <87v8yltad5.fsf@gnus.org> (raw)
In-Reply-To: <83fsrgw6mu.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 28 Nov 2021 19:07:53 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> * Reproducing
>> - Case 1:
>>    emacs -Q
>>    C-u 999 a
>>    visual-line-mode
>>    C-p C-a
>>    C-e C-a
>
> What are the problems you see in this recipe?  Please be specific,
> because it could be that what you see on your system we cannot see on
> ours.
>
> Also, please show all the information about your build collected by
> report-emacs-bug, it could be important while investigating this
> issue.

More information was requested, but no response was given within a
month, so I'm closing this bug report.  If the problem still exists,
please respond to this email and we'll reopen the bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-01-15 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 14:49 bug#52163: 28.0.60; visual-line-mode breaks C-a and C-e in extreme case iung--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-28 17:07 ` Eli Zaretskii
2022-01-15 13:08   ` Lars Ingebrigtsen [this message]
2022-01-15 22:53     ` Phil Sainty
2022-01-16  7:22       ` Eli Zaretskii
2022-01-16  9:58         ` Phil Sainty
2022-01-16 10:18           ` Eli Zaretskii
2022-01-16 10:23             ` Eli Zaretskii
2022-01-16 11:08               ` Phil Sainty
2022-01-16 10:55             ` Phil Sainty
2022-01-16 11:03               ` Eli Zaretskii

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=87v8yltad5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=52163@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=iung@autistici.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).