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: find-function-source-directory
Date: Mon, 19 Feb 2018 16:43:41 +0100	[thread overview]
Message-ID: <20180219154341.GC16648@tuxteam.de> (raw)
In-Reply-To: <83a7w59ekg.fsf@gnu.org>

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

On Mon, Feb 19, 2018 at 05:36:31PM +0200, Eli Zaretskii wrote:
> > Date: Mon, 19 Feb 2018 12:44:20 +0100
> > From: <tomas@tuxteam.de>

> > Hm. Looking at the elisp sources, it seems to me that this variable
> > is used [...]

> Yes, I've seen that as well.  But it turns out the code pulls a few
> rabbits out of its hat before it even gets there [...]

Uh, oh. Rabbits in Emacs ;-/

I'll try to have a look this afternoon. No guarantees, though :-)

Cheers&thanks
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlqK8K0ACgkQBcgs9XrR2kZgGwCePpg7M8WZsap1SRVrmnkhQVzo
Y4EAmQH/GzJXTnTVdrhWVa9JlUkftiaC
=Wd2C
-----END PGP SIGNATURE-----



  reply	other threads:[~2018-02-19 15:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18 16:16 find-function-source-directory Richard Copley
2018-02-18 18:40 ` find-function-source-directory Eli Zaretskii
2018-02-18 19:35   ` find-function-source-directory Eli Zaretskii
2018-02-19 11:13     ` find-function-source-directory Richard Copley
2018-02-19 11:44       ` find-function-source-directory tomas
2018-02-19 15:36         ` find-function-source-directory Eli Zaretskii
2018-02-19 15:43           ` tomas [this message]
2018-02-18 19:53   ` find-function-source-directory Drew Adams
2018-02-18 20:18     ` find-function-source-directory Eli Zaretskii
     [not found]   ` <<a8455f40-e18a-44ac-8523-435e84f2d2e8@default>
     [not found]     ` <<83h8qe9hld.fsf@gnu.org>
2018-02-18 21:56       ` find-function-source-directory Drew Adams
2018-02-19  3:24         ` find-function-source-directory Richard Copley

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=20180219154341.GC16648@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.