From: Kenichi Handa <handa@m17n.org>
Cc: jsbien@mimuw.edu.pl
Subject: Re: problem of display property [Re: list-charset-chars and unicode-bmp]
Date: Thu, 30 Jan 2003 13:26:43 +0900 (JST) [thread overview]
Message-ID: <200301300426.NAA18495@etlken.m17n.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1030129162559.20453D-100000@is> (message from Eli Zaretskii on Wed, 29 Jan 2003 16:27:05 +0200 (IST))
In article <Pine.SUN.3.91.1030129162559.20453D-100000@is>, Eli Zaretskii <eliz@is.elta.co.il> writes:
> On Wed, 29 Jan 2003, Kenichi Handa wrote:
>> By the way, I found that current-column, move-to-column,
>> etc. don't take display properties into acount. I vaguely
>> remember that once there was a discussion about using
>> display engine to calculte column numbers.
> That discussion revealed a problem with this approach: sometimes you need
> to compute columns in a portion of a buffer that isn't displayed, so it
> doesn't appear in the glyph matrices.
Of course we can't reuse the existing glyph matrics, but,
was it the conclusion that we can't use `struct it' without
a glyph matrics?
For instance, it seems to me that doing this is possible.
(1) call init_iterator with ROW == NULL
(2) call reseat with POS == (line-beginning-position)
(3) call move_it_to with TO_CHARPOS == (point)
(4) it->hpos is the current column.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-01-30 4:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87u1g3atvf.fsf@mimuw.edu.pl>
[not found] ` <200301210831.RAA03126@etlken.m17n.org>
[not found] ` <871y35kej4.fsf@mimuw.edu.pl>
[not found] ` <rzqsmvjtrnx.fsf@albion.dl.ac.uk>
2003-01-28 11:29 ` problem of display property [Re: list-charset-chars and unicode-bmp] Kenichi Handa
2003-01-28 12:35 ` Gerd Moellmann
2003-01-29 7:39 ` Kenichi Handa
2003-01-29 12:45 ` Gerd Moellmann
2003-01-29 13:15 ` Kenichi Handa
2003-01-29 14:27 ` Eli Zaretskii
2003-01-30 4:26 ` Kenichi Handa [this message]
2003-01-30 20:07 ` Eli Zaretskii
2003-01-30 20:26 ` Stefan Monnier
2003-01-30 20:56 ` Gerd Moellmann
2003-01-31 13:21 ` Dave Love
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=200301300426.NAA18495@etlken.m17n.org \
--to=handa@m17n.org \
--cc=jsbien@mimuw.edu.pl \
/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).