all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kelly Dean <kellydeanch@yahoo.com>
To: 14238@debbugs.gnu.org
Subject: bug#14238: [PATCH] Help page for character description forgets the character
Date: Fri, 26 Apr 2013 14:01:42 -0700 (PDT)	[thread overview]
Message-ID: <1367010102.16966.YahooMailClassic@web141101.mail.bf1.yahoo.com> (raw)
In-Reply-To: <jwvr4i27ikm.fsf-monnier+emacs@gnu.org>

--- On Mon, 4/22/13, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> Not sure if it is really a bug: while the name is
> "describe-char" what
> it does is more like "describe-pos" (and indeed it receives
> a position
> rather than a char as argument).
> 
> So when you "back" you ask to redisplay the info about the
> pos where
> A used to be (and where C is now instead).
> 
> The data stored with `help-setup-xref' is also used for
> `revert-buffer'
> which lets you refresh the description after the buffer was
> modified.

Put point on a function name, and do C-h f RET, then again on another function name. Then delete the first function name and type a new one, and do back in the help buffer. The documentation for the original first function name is displayed, not for the new one. Surely Emacs's behavior in this case is correct. Why then is it correct for describe-char to follow changes in the source buffer, if describe-function doesn't? I don't see how it's a useful feature. All it does it cause problems: one, after browsing a series of help pages, you go back to review the character description you looked at, and it's gone; two, there's an unexpected character description in your history, and you're left futilely trying to remember why you looked up the description for that character.






  reply	other threads:[~2013-04-26 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 11:38 bug#14238: [PATCH] Help page for character description forgets the character Kelly Dean
2013-04-22 14:26 ` Stefan Monnier
2013-04-26 21:01   ` Kelly Dean [this message]
2013-04-27  4:19     ` Stefan Monnier

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

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

  git send-email \
    --in-reply-to=1367010102.16966.YahooMailClassic@web141101.mail.bf1.yahoo.com \
    --to=kellydeanch@yahoo.com \
    --cc=14238@debbugs.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.