[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: info invisible changes
From: |
Richard Stallman |
Subject: |
Re: info invisible changes |
Date: |
Wed, 13 Nov 2002 23:09:41 -0500 |
1) it doesn't test for `invisible' properties, so it happily processes
invisible text when deciding the (visible) width of the lines,
The TODO item about making filling handle fonts ought to include this
as well.
2) it doesn't test for `display' properties, so if a part of the buffer
text is hidden and visibly replaced with some other text (or an
image), the hidden (rather than the visible) text is used for
filling, and
I guess it ought to include this as well.
3) when the fill code inserts a newline to wrap the text, it may
insert that newline in an invisible part of the buffer,
If this is a significant case, I guess we would want to handle this
case too.
For the immediate issue of *info*, if you are going to fill the buffer
text anyway, the other changes may as well be made by editing the buffer
rather than with text properties.
- Re: info invisible changes, (continued)
- Re: info invisible changes, Miles Bader, 2002/11/12
- Re: info invisible changes, Kim F. Storm, 2002/11/12
- Re: info invisible changes, Robert J. Chassell, 2002/11/12
- Re: info invisible changes, Kim F. Storm, 2002/11/13
- Re: info invisible changes, Robert J. Chassell, 2002/11/13
- Re: info invisible changes, Richard Stallman, 2002/11/14
- Re: info invisible changes, Kim F. Storm, 2002/11/14
- Re: info invisible changes, Stefan Monnier, 2002/11/12
- Re: info invisible changes, Kim F. Storm, 2002/11/13
- Re: info invisible changes, Kim F. Storm, 2002/11/13
- Re: info invisible changes,
Richard Stallman <=
Re: info invisible changes, Karl Berry, 2002/11/14