all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: getting the source finding button in c-h f help buffers to work
Date: Fri, 12 Feb 2016 20:15:30 +0100	[thread overview]
Message-ID: <20160212191530.GA21592@tuxteam.de> (raw)
In-Reply-To: <CAJcAo8v+gSq0pemaSwUyro7aUEkyMQwKe=MdrPXxhqoz2qmUfg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Feb 12, 2016 at 10:24:44AM -0700, Samuel Wales wrote:
> when you do c-h f, emacs provides a link to the source.  i have always
> relied on this feature.
> 
> in my own code, i have always kept byte-compiled files in a separate
> directory from the source.  this has never been a problem.
> 
> in a recent version of emacs, perhaps a recent emacs 24 minor version,
> it seems that c-h f source links no longer work if you keep your
> byte-compiled files in a separate directory from the source files.
> more specifically, they no longer exist.

This is a dejà vu...

there was a thread about that here a while ago:

  <http://lists.gnu.org/archive/html/help-gnu-emacs/2016-02/threads.html#00004>

The gist is you can set a variable `find-function-C-source-directory'
to tip Emacs in the right direction.

Regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAla+L1IACgkQBcgs9XrR2kbMSACdGG9t5PXcoPJSDp568FrzGiDB
sSAAnjqLreoh5tkQxHlEbfNtsYA4XRTV
=6Fv/
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2016-02-12 19:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 17:24 getting the source finding button in c-h f help buffers to work Samuel Wales
2016-02-12 17:43 ` Drew Adams
2016-02-12 19:15 ` tomas [this message]
2016-02-12 21:18   ` Drew Adams
2016-02-13 15:17     ` tomas
2016-02-13 20:23       ` Samuel Wales
2016-02-12 19:16 ` Emanuel Berg

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=20160212191530.GA21592@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@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.