There are some small mistakes in the Elisp manual's description of
`remove-list-of-text-properties'. I think the description should look
like this:
--- text.texi 07 Mar 2005 16:48:51 +0100 1.95
+++ text.texi 11 Mar 2005 08:34:59 +0100
@@ -2619,9 +2619,9 @@
@end defun
@defun
Richard Stallman [EMAIL PROTECTED] writes:
To make reliable judgement about the display state, line-move must
call sit-for which does redisplay.
That is a really bad problem.
IMO, it is not too bad -- line-move is primarily (solely?) for
interactive use, so redisplay will happen
Maybe a workaround is to give them generic string fence syntax (aka |)?
It seems to be a good idea. Are there any objection?
That isn't correct. There is a comment somewhere in the doc or code
about quotation marks intentionally _not_ having string syntax in text
modes or globally.
Which
To make reliable judgement about the display state, line-move must
call sit-for which does redisplay.
That is a really bad problem.
IMO, it is not too bad -- line-move is primarily (solely?) for
interactive use, so redisplay will happen after the command
anyway.
Agreed.
We need to
Stefan Monnier [EMAIL PROTECTED] writes:
To make scrolling (even of images or lines of widely different height)
reliable, compute-motion would need to pay attention to every display
element and parameter, including things like frame-local face properties.
So either it re-implements the
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug@gnu.org
But maybe it's important to be able to compute the matrix without *ever*
displaying it. E.g. in fit-window-to-buffer, count-screen-lines is used to
decide how to resize the window.
In the case where the matrix will be displayed sooner or later, I don't
think it makes much sense to delay the
It seems that it is bbdb that does some funny stuff with windows, VM
is strictly not needed to see this bug. I've made a change, can you
see if this helps your case?
If it does not, does a C-l fix the scroll bar? Or a small resize of
the window?
as far as I can tell the problem is gone. I
Johan Bockgård wrote:
The buffer's point and the window's point (cursor) aren't necessarily
the same thing. See
Of course not (slaps self). Thanks!
(info (elisp)Window Point)
___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
Frederik Fouvry wrote:
BUT: After applying the patch you sent around today (10 March - your
local patch), the calendar seems to be working again for me.
I installed those changes. If errors still occur, please send a
reproducible test case for a vanilla emacs. Thanks for the reports.
Stefan Monnier [EMAIL PROTECTED] writes:
I was thinking about the situation where the sit-for in line-move
results in a situation where we would adjust the vscroll, and thus
update the display once more. I haven't noticed this myself, but
I could envision that may cause flickering.
I see.
Stefan Monnier [EMAIL PROTECTED] writes:
I was thinking about the situation where the sit-for in line-move
results in a situation where we would adjust the vscroll, and thus
update the display once more. I haven't noticed this myself, but
I could envision that may cause flickering.
I see. If
On Fri, 11 Mar 2005 20:26:56 +0100, Reiner Steib
[EMAIL PROTECTED] wrote:
I've never seen guillemets used alone.
Occasionally people use `»' as a citation prefix in mail and news
instead of `'.
Sure, but I think that sort of thing is basically an obscure special
case, and really shouldn't
To make scrolling (even of images or lines of widely different height)
reliable, compute-motion would need to pay attention to every display
element and parameter, including things like frame-local face properties.
So either it re-implements the redisplay or it reuses the
On Fri, 11 Mar 2005 23:33:36 +0100, Kim F. Storm [EMAIL PROTECTED] wrote:
I don't know the internals of X, but if done properly, the Xserver
updates an internal bitmap and only transfers that to the screen when
flushed by Xflush.
The historical function of Xflush is to flush the queue of
$BEl5~8BDj$G%*!%W%s$7$F9%I[EMAIL
PROTECTED](HD%5%$%H!IEl5~%i%V%9%H!%j!!I$,A49q(B
$BHG$K$F%j%K%e!%%k%*!%W%s$7$^$7$?!#Ajj$N%%I%l%98+J|Bj$G40A4$JL5NA!#:#$^$G(B
$B3Z$7$a$J$+$C$?J}!2x$7$$%5%$%H$d$5$/$i$P$+$j$G$*C2$-$N$$J$?$K#7]G=?M(B
$B$d#A#V=wM%$J$I4XO$N6H3[EMAIL PROTECTED]$C$H(B
16 matches
Mail list logo