* bug#7530: describe-function etc. should remember locations from $HOME too
@ 2010-12-02 4:05 jidanni
2010-12-20 11:00 ` Chong Yidong
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: jidanni @ 2010-12-02 4:05 UTC (permalink / raw)
To: 7530
We do
(describe-function (quote gnus-summary-w3m-safe-toggle-inline-images))
and see
gnus-summary-w3m-safe-toggle-inline-images is an interactive compiled
Lisp function.
(gnus-summary-w3m-safe-toggle-inline-images &optional ARG)
Toggle displaying of all images in the article buffer.
If the prefix arg is given, force displaying of images.
[back]
And wonder "why does it usually say what file it is in, but not today?"
Well that is because it was in
~/.emacs-w3m.elc
~/.emacs-w3m
Therefore, when these files are initially scanned, they should be
remembered, just like all the other .el's and .elc's are. Why make an
exception for those few that are in $HOME? Same with describe-variable,
and any file read at any time.
And if an item really was from just doing a ^X^E etc. and not from any
file, the describe-* commands should mention that too! Thanks.
emacs-version "24.0.50.1"
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7530: describe-function etc. should remember locations from $HOME too
2010-12-02 4:05 bug#7530: describe-function etc. should remember locations from $HOME too jidanni
@ 2010-12-20 11:00 ` Chong Yidong
2010-12-21 0:07 ` jidanni
2010-12-21 3:51 ` jidanni
2 siblings, 0 replies; 6+ messages in thread
From: Chong Yidong @ 2010-12-20 11:00 UTC (permalink / raw)
To: jidanni; +Cc: 7530
jidanni@jidanni.org writes:
> We do
> (describe-function (quote gnus-summary-w3m-safe-toggle-inline-images))
> and see
> gnus-summary-w3m-safe-toggle-inline-images is an interactive compiled
> Lisp function.
>
> And wonder "why does it usually say what file it is in, but not today?"
>
> Well that is because it was in
> ~/.emacs-w3m.elc
> ~/.emacs-w3m
Please provide a minimal recipe for reproducing this bug, including a
minimal .emacs file.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7530: describe-function etc. should remember locations from $HOME too
2010-12-02 4:05 bug#7530: describe-function etc. should remember locations from $HOME too jidanni
2010-12-20 11:00 ` Chong Yidong
@ 2010-12-21 0:07 ` jidanni
2010-12-21 2:47 ` Chong Yidong
2010-12-21 3:51 ` jidanni
2 siblings, 1 reply; 6+ messages in thread
From: jidanni @ 2010-12-21 0:07 UTC (permalink / raw)
To: cyd; +Cc: 7530
>>>>> "CY" == Chong Yidong <cyd@stupidchicken.com> writes:
CY> Please provide a minimal recipe for reproducing this bug, including a
CY> minimal .emacs file.
http://jidanni.org/comp/configuration/.emacs
(describe-function (quote jidanni-tidy-buffer))
Why doesn't it tell us that it came from ~/.emacs or ~/.emacs.elc?
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7530: describe-function etc. should remember locations from $HOME too
2010-12-21 0:07 ` jidanni
@ 2010-12-21 2:47 ` Chong Yidong
0 siblings, 0 replies; 6+ messages in thread
From: Chong Yidong @ 2010-12-21 2:47 UTC (permalink / raw)
To: jidanni; +Cc: 7530
jidanni@jidanni.org writes:
>>>>>> "CY" == Chong Yidong <cyd@stupidchicken.com> writes:
>
> CY> Please provide a minimal recipe for reproducing this bug, including a
> CY> minimal .emacs file.
>
> http://jidanni.org/comp/configuration/.emacs
> (describe-function (quote jidanni-tidy-buffer))
> Why doesn't it tell us that it came from ~/.emacs or ~/.emacs.elc?
Please provide a MINIMAL recipe for reproducing this bug. The
configuration file you specified contains links to various third-party
packages, any one of which could be causing the bug.
I tried with a .emacs file containing just the line
(defun foo () 1)
Then, in emacs,
C-h f foo RET
=> foo is a Lisp function in `.emacs'.
as expected; no bug here.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7530: describe-function etc. should remember locations from $HOME too
2010-12-02 4:05 bug#7530: describe-function etc. should remember locations from $HOME too jidanni
2010-12-20 11:00 ` Chong Yidong
2010-12-21 0:07 ` jidanni
@ 2010-12-21 3:51 ` jidanni
2010-12-21 6:45 ` Chong Yidong
2 siblings, 1 reply; 6+ messages in thread
From: jidanni @ 2010-12-21 3:51 UTC (permalink / raw)
To: cyd; +Cc: 7530
>>>>> "CY" == Chong Yidong <cyd@stupidchicken.com> writes:
CY> I tried with a .emacs file containing just the line
CY> (defun foo () 1)
CY> Then, in emacs,
CY> C-h f foo RET
CY> => foo is a Lisp function in `.emacs'.
CY> as expected; no bug here.
Ah ha! But not if you byte-compile your .emacs.
B runs the command dired-do-byte-compile ...
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#7530: describe-function etc. should remember locations from $HOME too
2010-12-21 3:51 ` jidanni
@ 2010-12-21 6:45 ` Chong Yidong
0 siblings, 0 replies; 6+ messages in thread
From: Chong Yidong @ 2010-12-21 6:45 UTC (permalink / raw)
To: jidanni; +Cc: 7530
jidanni@jidanni.org writes:
>>>>>> "CY" == Chong Yidong <cyd@stupidchicken.com> writes:
> CY> I tried with a .emacs file containing just the line
>
> CY> (defun foo () 1)
>
> CY> Then, in emacs,
>
> CY> C-h f foo RET
> CY> => foo is a Lisp function in `.emacs'.
>
> CY> as expected; no bug here.
>
> Ah ha! But not if you byte-compile your .emacs.
> B runs the command dired-do-byte-compile ...
Fixed, thanks.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-12-21 6:45 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-12-02 4:05 bug#7530: describe-function etc. should remember locations from $HOME too jidanni
2010-12-20 11:00 ` Chong Yidong
2010-12-21 0:07 ` jidanni
2010-12-21 2:47 ` Chong Yidong
2010-12-21 3:51 ` jidanni
2010-12-21 6:45 ` Chong Yidong
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).