GNU bug report logs - #16792
24.3.50; wish: following a variable name should show the value from initial buffer

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 16792 in the body.
You can then email your comments to 16792 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Richard <theonewiththeevillook <at> yahoo.fr>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3.50;
 wish: following a variable name should show the value from initial
 buffer
Date: Tue, 18 Feb 2014 16:03:04 +0100

Hello,

Consider the following~:

(with-current-buffer (get-buffer-create "foo")
  ;; change a variable locally
  (setq-local beginning-of-defun-function #'beginning-of-line)
  ;; describe a function that references the above variable
  (describe-function 'beginning-of-defun)
  (switch-to-buffer "*Help*")
  ;; go to the reference and follow it
  (search-forward "beginning-of-defun-functio")
  (execute-kbd-macro (kbd "RET")))

The second line is:
: Its value is nil

I somewhat expected to see:
: Its value is beginning-of-line
: Local in buffer foo; global value is nil

If the old buffer is killed before following the reference, I guess I'd
like to be warned about it and see the global value instead.

What do you think ?

-- 
Nico.

Message #8 received at 16792 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Nicolas Richard <theonewiththeevillook <at> yahoo.fr>
Cc: 16792 <at> debbugs.gnu.org
Subject: Re: bug#16792: 24.3.50;
 wish: following a variable name should show the value from initial
 buffer
Date: Tue, 18 Feb 2014 11:45:41 -0500

So you're saying that describe-function should remember in which buffer
it was invoked, in case we use describe-variable from the resulting
*Help* buffer.

It's not a terribly bad idea, but to the extent that functions can't be
buffer-local, it'd be an ad-hoc hack.  It wouldn't be the first ad-hoc
hack by the long shot, but I'm not sure I'd like to add this one.


        Stefan

Message #11 received at 16792 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Nicolas Richard <theonewiththeevillook <at> yahoo.fr>, 16792 <at> debbugs.gnu.org
Subject: Re: bug#16792: 24.3.50; wish: following a variable name should show
 the value from initial buffer
Date: Sun, 30 May 2021 06:48:42 +0200

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

> It's not a terribly bad idea, but to the extent that functions can't be
> buffer-local, it'd be an ad-hoc hack.  It wouldn't be the first ad-hoc
> hack by the long shot, but I'm not sure I'd like to add this one.

No, it sounds somewhat confusing, so I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.