unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: OFFICE ZERO <hi-oh230@air.ocn.ne.jp>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>,
	<672@emacsbugs.donarmstrong.com>
Subject: bug#672: 23.0.60; To source or not to source (from help)
Date: Sat, 9 Aug 2008 10:03:20 +0900	[thread overview]
Message-ID: <008f01c8f9bb$b73762c0$0100a8c0@yourhigxg9gyo4> (raw)
In-Reply-To: 489C2956.1030202@gmail.com

配信不要
----- Original Message ----- 
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: "martin rudalics" <rudalics@gmx.at>
Cc: "Bug-Gnu-Emacs" <bug-gnu-emacs@gnu.org>; 
<587@emacsbugs.donarmstrong.com>
Sent: Friday, August 08, 2008 8:09 PM
Subject: bug#672: 23.0.60; To source or not to source (from help)


> martin rudalics wrote:
>>  > If you do C-h v and look at a variable and click on the library link 
>> in
>>  > the help buffer you will go to the file in your current Emacs tree. If
>>  > you do C-h f to look at a function and do the same you will be taken 
>> to
>>  > the cvs checkout file instead.
>>
>> I suspect you compiled Emacs in the checkout directory and then copied
>> the Emacs tree to another directory.
>
> I use the normal
>
>   make install INSTALL_DIR=...
>
>> In this case the following might
>> happen: As for C-h f `describe-function-1' will execute
>>
>>       ;; See if lisp files are present where they where installed from.
>>       (if (not (eq file-name 'C-source))
>>       (setq file-name (find-source-lisp-file file-name)))
>>
>> which sets `file-name' to the ".el" file from the checkout directory
>> (because you did compile it there) and installs the corresponding
>> reference in the hyperlink.
>>
>> As for C-h v `describe-variable' does _not_ care whether you compiled in
>> another directory and simply goes to the file supplied by `symbol-file'.
>> You could try inserting the snipped above in `describe-variable'
>> immediately before the line
>>
>>           (if file-name
>>
>> and see whether it now jumps to the checkout directory instead.
>
> Yes, I guess that is correct.
>
>> Personally, I'd prefer something like the following in both cases:
>>
>>       (unless (or (eq file-name 'C-source)
>>           (file-exists-p file-name))
>>     (setq file-name (find-source-lisp-file file-name)))
>
>
> Thanks martin. I think a variable (or an option) for which elisp to go to 
> would be the best. Is there any reason not to have that?
>
>
>
>
> 







  parent reply	other threads:[~2008-08-09  1:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08  9:52 bug#671: 23.0.60; To source or not to source (from help) martin rudalics
2008-08-08 11:09 ` bug#587: " Lennart Borgman (gmail)
2008-08-08 12:03   ` martin rudalics
2008-08-08 12:20     ` Lennart Borgman (gmail)
2008-08-09  1:02       ` bug#674: " OFFICE ZERO
     [not found]         ` <handler.674.B674.121824629829764.ackinfo@emacsbugs.donarmstrong.com>
2008-08-09  3:04           ` bug#674: Info received (bug#674: 23.0.60; To source or not to source (from help)) OFFICE ZERO
2008-08-09  1:02       ` bug#587: 23.0.60; To source or not to source (from help) OFFICE ZERO
2008-08-09 12:37       ` martin rudalics
2008-08-09 12:44         ` Lennart Borgman (gmail)
2008-08-09 12:58           ` martin rudalics
2008-08-09 13:02             ` Lennart Borgman (gmail)
2008-08-09 13:52               ` OFFICE ZERO
     [not found]                 ` <handler.587.B587.121828992525830.ackinfo@emacsbugs.donarmstrong.com>
2008-08-09 14:28                   ` bug#587: Info received (bug#587: 23.0.60; To source or not to source (from help)) OFFICE ZERO
2008-08-09 13:16             ` bug#587: 23.0.60; To source or not to source (from help) OFFICE ZERO
     [not found]               ` <handler.587.B587.121828781715147.ackinfo@emacsbugs.donarmstrong.com>
2008-08-09 13:51                 ` bug#587: Info received (bug#587: 23.0.60; To source or not to source (from help)) OFFICE ZERO
     [not found]                   ` <handler.587.B587.121828987325755.ackinfo@emacsbugs.donarmstrong.com>
2008-08-09 14:27                     ` bug#587: Info received (bug#587: Info received (bug#587: 23.0.60; To source or not to source (from help))) OFFICE ZERO
2008-08-09 14:14             ` bug#587: 23.0.60; To source or not to source (from help) OFFICE ZERO
2008-08-09 13:17           ` OFFICE ZERO
     [not found]             ` <handler.587.B587.121828782615157.ackinfo@emacsbugs.donarmstrong.com>
2008-08-09 13:51               ` bug#587: Info received (bug#587: 23.0.60; To source or not to source (from help)) OFFICE ZERO
     [not found]                 ` <handler.587.B587.121828986725748.ackinfo@emacsbugs.donarmstrong.com>
2008-08-09 14:27                   ` bug#587: Info received (bug#587: Info received (bug#587: 23.0.60; To source or not to source (from help))) OFFICE ZERO
2008-08-09 13:17         ` bug#587: 23.0.60; To source or not to source (from help) OFFICE ZERO
2008-08-09  1:02     ` bug#673: " OFFICE ZERO
2008-08-09 14:12     ` bug#587: " OFFICE ZERO
2008-08-09 14:12     ` bug#673: " OFFICE ZERO
2008-08-09  1:03   ` OFFICE ZERO [this message]
2008-08-09 14:12   ` bug#672: " OFFICE ZERO
2008-08-08 18:43 ` bug#671: " 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

  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='008f01c8f9bb$b73762c0$0100a8c0@yourhigxg9gyo4' \
    --to=hi-oh230@air.ocn.ne.jp \
    --cc=672@emacsbugs.donarmstrong.com \
    --cc=lennart.borgman@gmail.com \
    /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).