unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: d.love@dl.ac.uk, emacs-devel@gnu.org
Subject: Re: [nickrob@snap.net.nz: Links in Help buffer]
Date: Thu, 22 Dec 2005 10:27:28 +1300	[thread overview]
Message-ID: <17321.51392.834071.858335@kahikatea.snap.net.nz> (raw)
In-Reply-To: <E1EouB6-0003dj-Oh@fencepost.gnu.org>

 >      > 2000-05-09  Dave Love  <fx@gnu.org>
 >      > 
 >      > 	Changes mostly following Richard Sharman
 >      > 	<rsharman@wave.home.com>.
 >      > 
 >      > 	* help.el (describe-variable): Have customize button pop the
 >      > 	help-xref stack when invoked.
 > 
 >     I've reverted this change (now in help-mode.el) since I can see now
 >     that in 21.3 help-follow pushed an item onto the stack but that's not
 >     the case now.
 > 
 > I have a feeling that Dave Love made that change to fix some bug.
 > Maybe that other bug has come back now.  Perhaps we need to fix it
 > some other way, but we shoud fix it.
 > 
 > Dave, can you tell us what bug that fixed?

Maybe Dave does have something to add, but I can see the bug that this change
fixed in 21.3 and why its not needed now (causes a bug now, in fact).  If I
couldn't, I wouldn't have reverted the change.

I have a patch for Help links which I guess will have to wait after the
release.  I also want to convert descr-text.el from widgets to help links so
solve some of its problems, but this isn't a trivial task.  Perhaps I should
mention this in TODO so there isn't duplication of effort.

Nick

  reply	other threads:[~2005-12-21 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20  5:33 [nickrob@snap.net.nz: Links in Help buffer] Richard M. Stallman
2005-12-20  9:02 ` Nick Roberts
2005-12-21  2:58   ` Richard M. Stallman
2005-12-21 21:27     ` Nick Roberts [this message]
2005-12-22  5:46       ` Richard M. Stallman
2005-12-23 12:14     ` Dave Love
2005-12-23 18:11       ` Richard M. Stallman

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=17321.51392.834071.858335@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=d.love@dl.ac.uk \
    --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).