unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: confusing info in C-u C-x =
Date: Thu, 08 Dec 2005 10:49:04 +0900	[thread overview]
Message-ID: <E1EkAu8-0004QI-00@etlken> (raw)
In-Reply-To: <je1x1b4aex.fsf@sykes.suse.de> (message from Andreas Schwab on Sun, 20 Nov 2005 16:16:22 +0100)

In article <je1x1b4aex.fsf@sykes.suse.de>, Andreas Schwab <schwab@suse.de> 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  <handa@m17n.org>

> 	* 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 <rudalics@gmx.at> 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
release?

---
Kenichi Handa
handa@m17n.org

  parent reply	other threads:[~2005-12-08  1:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20  9:55 confusing info in C-u C-x = Werner LEMBERG
2005-11-20 15:16 ` Andreas Schwab
2005-11-20 22:07   ` [SPAM?]: " Werner LEMBERG
2005-11-21  7:35   ` Juri Linkov
2005-12-08  1:49   ` Kenichi Handa [this message]
2005-12-09  9:57     ` Juri Linkov
2005-12-09 15:07       ` Kim F. Storm
2005-12-09 21:15       ` Richard M. Stallman
2005-12-09 23:52         ` Juri Linkov
2005-12-10 16:18           ` Richard M. Stallman
2005-12-11  0:46             ` Juri Linkov
2005-12-10 22:50           ` Kim F. Storm
2005-12-11  0:55       ` Juri Linkov
2005-12-11 16:49         ` Richard M. Stallman
2005-11-20 23:21 ` Richard M. Stallman
  -- strict thread matches above, loose matches on Subject: below --
2005-11-20 19:35 martin rudalics
2005-11-21  8:56 martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1EkAu8-0004QI-00@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).