unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 6716@debbugs.gnu.org
Subject: bug#6716: 23.2; Setting `find-function-source-path' has no effect.
Date: Mon, 26 Jul 2010 13:20:39 +0200	[thread overview]
Message-ID: <87mxteebg8.fsf@gmail.com> (raw)
In-Reply-To: <jwv6302czvq.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 26 Jul 2010 12:23:06 +0200")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>> I don't care if the source I jump to is really "equivalent" to the
>> version I have loaded
>
> There lies the problem.  Other people do.  So the fix to your problem
> will need to satisfy both cases.

But if you care about that, you don't need `find-function-source-path'
at all, no? (And actually, I don't see a reliable way to jump to the
"right" source of a byte-compiled function in general (as I already
pointed out in the previous mail).)

Also, you replied to none of my other questions, notably -- do you
really (_really_) plan to reimplement `load-history', or was that just a
"would be nice to have"? If the latter, could you propose a better
solution that would improve the current situation? (I'm sorry, but as I
also already wrote, I didn't really understand the point(s) you were
making.)

Štěpán





  reply	other threads:[~2010-07-26 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24 11:56 bug#6716: 23.2; Setting `find-function-source-path' has no effect Štěpán Němec
2010-07-25 23:45 ` Stefan Monnier
2010-07-26  4:17   ` Štěpán Němec
2010-07-26  4:51     ` Štěpán Němec
2010-07-26 10:23     ` Stefan Monnier
2010-07-26 11:20       ` Štěpán Němec [this message]
2010-07-26 21:44         ` Stefan Monnier
2010-07-27 10:07           ` Štěpán Němec
2010-07-27 11:57             ` Stefan Monnier
2010-07-26 21:40 ` MON KEY
2010-07-27  9:39   ` Štěpán Němec
2010-07-28  1:38     ` MON KEY
2022-02-13 10:02 ` Lars Ingebrigtsen
2022-02-15 14:50   ` Štěpán Němec
2022-02-17 11:33     ` Lars Ingebrigtsen

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=87mxteebg8.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=6716@debbugs.gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).