unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16497@debbugs.gnu.org
Subject: bug#16497: 24.3.50; `move-to-column' ignores invisible text at the beginning of the line,	which create problems when using string-rectangle
Date: Mon, 20 Jan 2014 17:50:25 +0100	[thread overview]
Message-ID: <87fvoilhri.fsf@bzg.ath.cx> (raw)
In-Reply-To: <83d2jmirt1.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 20 Jan 2014 17:41:46 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Before we design the interface, can we please define what is the job
> to be done here?

I don't know what needs to be done, but what's confusing is that both
`move-to-column' and `line-move-to-column' ignore invisible characters
within the line, but `line-move-to-column' goes back to real beginning
of the line while `move-to-column' goes back to the visual beginning
of the line.

> If it's just to get to Nth character from bol, aren't there easier
> ways of doing that?

Sure.  If `string-rectangle' can do the right thing with no change
in such internals, that's good -- but I trust Stefan when he says
that there may be cases where you want `string-rectangle' to behave
as it does now.

Another probably related quirk:

emacs -Q
M-: (insert "abc") RET
C-a
M-: (put-text-property (point) (1+ (point)) 'invisible t) RET
C-a
C-a
C-a

... !  See the point moving from b to c and back again.
Probably some heisenbug since edebug-defun'ing move-beginning-of-line
and stepping through it does not have the bug.

Such a contrived example does not deserve a bug report, but i thought
maybe this is related to the current discussion.

-- 
 Bastien





  reply	other threads:[~2014-01-20 16:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 16:26 bug#16497: 24.3.50; `move-to-column' ignores invisible text at the beginning of the line, which create problems when using string-rectangle Bastien Guerry
2014-01-19 17:11 ` Eli Zaretskii
2014-01-20  9:22   ` Bastien
2014-01-20 15:38     ` Eli Zaretskii
2014-01-20 16:25       ` Bastien
     [not found]     ` <<83eh42iry6.fsf@gnu.org>
2014-01-20 18:10       ` Drew Adams
2014-01-19 20:48 ` Stefan Monnier
2014-01-20  9:11   ` Bastien
2014-01-20 15:41     ` Eli Zaretskii
2014-01-20 16:50       ` Bastien [this message]
2014-01-20 18:14         ` Stefan Monnier
2014-01-20 18:22           ` Bastien
2014-01-20 19:10             ` Stefan Monnier
2014-01-20 20:55               ` Bastien
2014-01-20 19:19           ` Eli Zaretskii
     [not found] <<87ob38gcp1.fsf@bzg.ath.cx>

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=87fvoilhri.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=16497@debbugs.gnu.org \
    --cc=eliz@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).