unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Martin Edstrom" <meedstrom@runbox.eu>
Cc: 72420@debbugs.gnu.org
Subject: bug#72420: set-goal-column misbehaves with a line-prefix and visual-line-mode
Date: Wed, 07 Aug 2024 15:19:56 +0300	[thread overview]
Message-ID: <865xsco783.fsf@gnu.org> (raw)
In-Reply-To: <E1sbfSD-0007Kv-H4@rmmprod05.runbox> (meedstrom@runbox.eu)

> From: "Martin Edstrom" <meedstrom@runbox.eu>
> CC: "72420" <72420@debbugs.gnu.org>
> Date: Wed, 07 Aug 2024 14:07:45 +0200 (CEST)
> 
> But, it's odd that visual-line-mode does not affect it for you - it does for me. 
> 
> If I leave visual-line-mode off, then I get the behavior I expect (i.e. set-goal-column at column 2 is treated as column 6), which is useful.  Turning it on causes the command to behave in a way that is not useful, as I described.

If you leave visual-line-mode off, then type C-p twice from "z", don't
you see point go to the 3rd "*" of the line "**** h4"?  And if so,
isn't that what you meant by "the goal column actually seems to be
offset in some way influenced by the line prefix"?  Or did I
misunderstand what you consider a problem in the existing behavior?





  reply	other threads:[~2024-08-07 12:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 10:35 bug#72420: set-goal-column misbehaves with a line-prefix and visual-line-mode Martin Edström
2024-08-04  8:47 ` Eli Zaretskii
2024-08-06 14:10   ` Martin Edstrom
2024-08-07 11:01     ` Eli Zaretskii
2024-08-07 12:07       ` Martin Edstrom
2024-08-07 12:19         ` Eli Zaretskii [this message]
2024-08-07 14:03           ` Martin Edstrom
2024-08-07 14:29             ` Eli Zaretskii
2024-08-07 14:53               ` Martin Edstrom
2024-08-06 14:24 ` Martin Edstrom
2024-08-07 11:04   ` Eli Zaretskii
2024-08-20  8:28 ` Martin Edström
2024-08-20 12:24   ` Eli Zaretskii
2024-08-22 14:33     ` Eli Zaretskii
2024-09-07  7:16       ` 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=865xsco783.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72420@debbugs.gnu.org \
    --cc=meedstrom@runbox.eu \
    /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).