From: Jake Shilling <shilling.jake@gmail.com>
To: jgart <jgart@dismail.de>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: geiser-edit-symbol-at-point
Date: Mon, 14 Nov 2022 10:16:33 -0500 [thread overview]
Message-ID: <87h6z1sh0u.fsf@gmail.com> (raw)
In-Reply-To: <20221114090110.GB14300@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]
On 2022-11-14 09:01, jgart@dismail.de wrote:
> On Sat, 12 Nov 2022 10:48:54 -0500 Jake Shilling <shilling.jake@gmail.com> wrote:
>>
>> If I'm reading this right, I belive that this macro is looking for the
>> 'add-after symbol--as a symbol--and not looking for any value referenced
>> by it.
>
> Does geiser work on the macroexpanded forms in %modify-phases that are
> not macros?
It does for me. Here's a snippet from the file I tested on:
```
(arguments
`(#:bootstrap-scripts (list "autogen")
#:make-flags (list "-C" "utils")
#:configure-flags (list "--enable-start-stop-daemon"
"--disable-update-alternatives")
#:phases
(modify-phases %standard-phases
(add-before 'bootstrap 'patch-autogen-shebang
(lambda* (#:key bootstrap-scripts #:allow-other-keys)
(for-each patch-shebang (append bootstrap-scripts))
(let ((get-version "printf \"%s\" \"1.20.12\"")
(port (open-file "get-version" "w")))
(format port get-version)
(close-port port))))
(add-after 'configure 'build-lib
(lambda* (#:rest _)
(invoke "make" "-C" "lib"))))))
```
If I evaluate this file, then call `geiser-edit-symbol-at-point` on
`invoke` in the last line, I get taken to `guix/build/utils.scm` as
expected. None of the standard guile functions work for me though; if I
try to navigate to `close-port` or `for-each` nothing happens. I can run
C-c C-d C-d on any of those, however, and navigate from the
documentation to the manual.
I also want to clarify that this does work for me on the macro itself,
`modify-phases`, just not on the symbols used by the macro for pattern
matching (`add-before`, `add-after`, etc).
--
Best regards,
Jake Shilling
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-11-15 0:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 1:35 geiser-edit-symbol-at-point jgart
2022-11-11 1:39 ` geiser-edit-symbol-at-point jgart
2022-11-11 1:44 ` geiser-edit-symbol-at-point jgart
2022-11-11 14:31 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 16:17 ` geiser-edit-symbol-at-point Olivier Dion via
2022-11-11 16:47 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 17:10 ` geiser-edit-symbol-at-point Olivier Dion via
2022-11-11 18:40 ` geiser-edit-symbol-at-point jgart
2022-11-11 20:43 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 21:42 ` geiser-edit-symbol-at-point jgart
2022-11-11 21:45 ` geiser-edit-symbol-at-point jgart
2022-11-11 22:06 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-11 22:15 ` geiser-edit-symbol-at-point jgart
2022-11-12 0:07 ` geiser-edit-symbol-at-point jgart
2022-11-12 0:12 ` geiser-edit-symbol-at-point jgart
2022-11-12 15:48 ` geiser-edit-symbol-at-point Jake Shilling
2022-11-14 15:01 ` geiser-edit-symbol-at-point jgart
2022-11-14 15:16 ` Jake Shilling [this message]
2022-11-14 22:38 ` geiser-edit-symbol-at-point jgart
2022-11-15 1:31 ` geiser-edit-symbol-at-point Jake Shilling
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6z1sh0u.fsf@gmail.com \
--to=shilling.jake@gmail.com \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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).