From: Daniel Hartwig <mandyke@gmail.com>
To: guile-devel@gnu.org
Subject: Re: [PATCH] Add inspection command "source (, src)" which shows Scheme code of loaded module
Date: Mon, 1 Apr 2013 12:22:43 +0800 [thread overview]
Message-ID: <CAN3veRe_2PRNrkU=57KCZpdqnDZPxpwi44TCgEjJ1H_SXV7P3g@mail.gmail.com> (raw)
In-Reply-To: <874nfq52jk.fsf@tines.lan>
On 1 April 2013 11:54, Mark H Weaver <mhw@netris.org> wrote:
> Daniel Hartwig <mandyke@gmail.com> writes:
>> these two points are enough information to obtain the unmodified
>> source from the file.
>
> This is enough to get the original characters, but then there's the
> other problem I mentioned: reader directives such as #!curly-infix
> earlier in the file.
>
> For this reason, I think we need to use 'read' from the beginning of the
> file, and look at the source properties of the returned datums to find
> the right top-level datum. In most cases, a top-level datum is what is
> desired, but in some cases not. In general, you will need to traverse
> the sublists of a top-level datum to find the right one.
Ah yes, right. Not such a trivial task after all. I had neglected
that such reader directives will sufficiently alter the meaning of the
file.
I think I will stick to ‘geiser-edit-symbol-at-point’ :-)
next prev parent reply other threads:[~2013-04-01 4:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 13:57 [PATCH] Add inspection command "source (,src)" which shows Scheme code of loaded module Nala Ginrut
2013-03-30 21:17 ` [PATCH] Add inspection command "source (, src)" " Mark H Weaver
2013-03-31 0:33 ` Daniel Hartwig
2013-03-31 12:47 ` [PATCH] Add inspection command "source (,src)" " Nala Ginrut
2013-04-01 0:42 ` [PATCH] Add inspection command "source (, src)" " Daniel Hartwig
2013-04-01 3:54 ` Mark H Weaver
2013-04-01 4:22 ` Daniel Hartwig [this message]
2013-04-01 19:12 ` Andy Wingo
2013-04-23 7:26 ` Show source code from .debug_info section (Was Re: [PATCH] Add inspection command "source (, src)" which shows Scheme code of loaded module) Nala Ginrut
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN3veRe_2PRNrkU=57KCZpdqnDZPxpwi44TCgEjJ1H_SXV7P3g@mail.gmail.com' \
--to=mandyke@gmail.com \
--cc=guile-devel@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.
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).