On Tue, 29 Mar 2005 09:36:52 +0200, Kim F. Storm [EMAIL PROTECTED] wrote:
IIRC, the redisplay code tries to optimize overlay handling by
only looking for one arrow in each buffer...
Try removing this line in xdisp.c to see if it has the desired
effect:
overlay_arrow_seen = 1;
Seems
Miles Bader [EMAIL PROTECTED] writes:
On Tue, 29 Mar 2005 09:36:52 +0200, Kim F. Storm [EMAIL PROTECTED] wrote:
IIRC, the redisplay code tries to optimize overlay handling by
only looking for one arrow in each buffer...
Try removing this line in xdisp.c to see if it has the desired
effect:
Stefan Monnier [EMAIL PROTECTED] writes:
I recently suggested patches to report menu bindings using the real
menu item texts rather than the internal names, like this:
File=Print=Print With Faces
I agree it would be an improvement. But IIRC you did it by modifying
key-description,
Kim Storm created a variable overlay-arrow-variable-list to allow
multiple overlay arrows (see info). I have used this for buffers
displaying assembler in gdb-ui.el (gdb-overlay-arrow-position).
I tried to use overlay-arrow-variable-list, but can't display more
than one fringe
David Kastrup [EMAIL PROTECTED] writes:
how feasible would it be to
make kbd accept File=Print=Print With Faces strings? Then there
would be no necessity to report a different form.
Does kbd really generate proper menu bindings in its current form?
Does it make sense at all to use kbd for
With my patch, (key-description KEY t) will do just that.
Making C-h c using that is trivial (I already did so).
Great, then I strongly support it.
C-h k File New File... reports:
,--
| File=New File... runs the command find-file
|which is an interactive
Try removing this line in xdisp.c to see if it has the desired
effect:
overlay_arrow_seen = 1;
I tried removing this line and without this line
overlay-arrow-variable-list can display more than one arrow.
--
Juri Linkov
http://www.jurta.org/emacs/
I don't have the crashed session any more, but I'll try recompiling without
optimization and see if I can get a more informative report for you.
This may take a couple of weeks, though -- I'm leaving shortly for a trip.
- Benjamin
___
Keyboard macros now get confused if C-s is terminated by C-x ). To
reproduce, in the default *scratch* do:
C-s is C-x ( C-s C-s C-x ) C-x e
and get an obscure `Not defining keyboard macro' error, though the
macro actually runs.
This is error-free in 21.3 and is probably the way I most often
A few weeks ago (mark-sexp -1) changed behavior in CUA mode.
I've got this key mapped.
(global-set-key [?\C-\M- ] '(lambda ()(interactive)(mark-sexp -1)))
In older versions of CVS Emacs, repeated pressing of C-M-SPC
would select successive prior statements. For example:
(foo)
(bar)
Miles Bader [EMAIL PROTECTED] writes:
I've no idea why non-breaking characters should be displayed like
this, but U+00AD isn't one -- it's SOFT HYPHEN. If you're going to
change its display, the issue (see Unicode) is whether or not it
should be displayed at all -- not that I think it
Kenichi Handa [EMAIL PROTECTED] writes:
I think it's possible to detect utf-16 by using heuristics
with high accuracy. I'll try it in emacs-unicode.
Yes. Perhaps someone knows exactly what Windows does (assuming the
only significant use of it is in Windows)?
If they have common name or
Juri Linkov [EMAIL PROTECTED] writes:
I agree. ^L fontified as a keyword looks horrible. That's why I suggested
to change its color to dark red to look more like comments.
The point isn't the specific colour, but the fact that there is
mysterious highlighting at all.
I've no idea why
Stefan Monnier [EMAIL PROTECTED] writes:
in either case, standard-display-table is not nil, so this let's make sure
the standard-display-table default is nil argument doesn't hold much water.
It would be better if it _was_ nil rather than having the misleading
display of eight-bit characters
Nick Roberts [EMAIL PROTECTED] writes:
I don't use more than one arrow per buffer. However, I do think compile
should use overlay-arrow-variable-list instead of making
overlay-arrow-position a local variable.
And so should GUD, although overlay-arrow-position was probably
I recently suggested patches to report menu bindings using the real
menu item texts rather than the internal names, like this:
File=Print=Print With Faces
I don't think it is much of an improvement. In any case,
it would have to be a very important improvement to be
Kim Storm wrote:
Dave Love [EMAIL PROTECTED] writes:
Keyboard macros now get confused if C-s is terminated by C-x ). To
reproduce, in the default *scratch* do:
C-s is C-x ( C-s C-s C-x ) C-x e
and get an obscure `Not defining keyboard macro' error, though the
Dave Love [EMAIL PROTECTED] writes:
Yes. Perhaps someone knows exactly what Windows does (assuming the
only significant use of it is in Windows)?
I would guess that the presence of a BOM is sufficient
heuristics. Detecting 0 or other low byte values every second
byte would work for Latin
18 matches
Mail list logo
