[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43587: move-to-column behaves differently when text has invisible pr
From: |
Eli Zaretskii |
Subject: |
bug#43587: move-to-column behaves differently when text has invisible property |
Date: |
Tue, 29 Sep 2020 19:50:07 +0300 |
[Please use Reply All to CC the bug address as well.]
> From: Christoph Arenz <tiga.arenz@web.de>
> Date: Tue, 29 Sep 2020 18:29:22 +0200
>
>
> On 29.09.20 18:22, Eli Zaretskii wrote:
> >> From: Christoph Arenz <tiga.arenz@web.de>
> >> Date: Tue, 29 Sep 2020 17:56:45 +0200
> >>
> >> Digging deeper into bug 43587, it seems to be related to move-to-column
> >> behaving slightly different when the
> >> text in a line has the invisible property set.
> >>
> >> Here is how to recreate. According to the documentation for
> >> move-to-column, I would not expect any
> >> difference between the two lines:
> >>
> >>> Optional second argument FORCE non-nil means if COLUMN is in the middle
> >>> of a tab character, change
> >> it to spaces.
> >>
> >> For the first line, the tab has not been changed to spaces...
> >>
> >> Am I overlooking something?
> > Yes, move-to-column skips invisible text.
> Given that there is no invisible text in columns 0 to 7 in the provided
> example, but only thereafter(!), I do not understand what 'skips' means
> in this context when moving to column 7...
Sorry, I've misunderstood what you were asking. I thought you were
asking whether move-to-column is affected by invisible text, and
answered that question.