[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: info invisible changes
From: |
Stefan Monnier |
Subject: |
Re: info invisible changes |
Date: |
Tue, 12 Nov 2002 13:49:17 -0500 |
> 1) it doesn't test for 'invisible properties, so it happily processes
> invisible text when deciding the (visible) width of the lines,
Are you sure ? It uses current-column which does pay attention
to `invisible' properties.
> 3) when the fill code inserts a newline to wrap the text, it may
> insert that newline in an invisible part of the buffer, so it has
> no visible effect (i.e. displaying one very long line rather than
> two normal width lines).
You can fix this easily. See fill-nobreak-predicate.
Stefan
- Re: info invisible changes, (continued)
- Re: info invisible changes, Miles Bader, 2002/11/06
- Re: info invisible changes, Richard Stallman, 2002/11/07
- Re: info invisible changes, Kim F. Storm, 2002/11/12
- 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 <=
- 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, 2002/11/13
Re: info invisible changes, Karl Berry, 2002/11/14