[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: confusing info in C-u C-x =

From: Kenichi Handa
Subject: Re: confusing info in C-u C-x =
Date: Thu, 08 Dec 2005 10:49:04 +0900

In article <address@hidden>, Andreas Schwab <address@hidden> writes:
>>    There is an overlay here:
>>     From 14 to 15
>>  What does the `From 14 to 15' mean?

> It is supposed to be the overlay start and end, but uses the overlay that
> has been put at the character in the help buffer instead of the original
> overlay.  This was apparently a deliberate choice so that you can do C-u
> C-x = on a character in the *Help* buffer and still get information on the
> text properties and overlays:

> 2004-05-05  Kenichi Handa  <address@hidden>

>       * descr-text.el (describe-char): Copy the character with text
>       properties and overlays into the first line, and call
>       describe-text-properties on it.

> Unfortunately that has the side effect of losing the original overlay
> position.

I've just installed two changes to fix it.

(1) Use *Help-2* buffer if the current buffer is *Help*.
The function describe-text-properties already does it.

(2) Don't change the value of arg POS in describe-char, and
call describe-text-properties while temporarily setting the
original buffer.

martin rudalics <address@hidden> writes:

> You could try the following patch:
>    ;;;###autoload
> ! (defun describe-text-properties (pos &optional output-buffer overlay-bounds)

I think that adding the arg OVERLAY-BOUNDS is too adhoc.  To
make this function more convenient, isn't it better to add
arg OBJECT (buffer of string POS is pointing to) just like
the other text property related functions ... after the

Kenichi Handa

reply via email to

[Prev in Thread] Current Thread [Next in Thread]