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: Sat, 12 Nov 2022 10:48:54 -0500 [thread overview]
Message-ID: <87cz9sqil5.fsf@gmail.com> (raw)
In-Reply-To: <20221111181230.GD31484@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
On 2022-11-11 18:12, jgart wrote:
> But this doesn't work for geiser-edit-symbol-at-point because it is guix API code:
>
> (add-after 'build 'install-xsession
> ^^^^^^^^^
`add-after` might not be the best symbol to test on, because (with my
limited understanding of scheme) is not defined to be anything--it's
just used in the pattern matching for the `%modify-phases` macro:
```
(define-syntax %modify-phases
(syntax-rules (delete replace add-before add-after)
((_ phases (delete old-phase-name))
(alist-delete old-phase-name phases))
((_ phases (replace old-phase-name new-phase))
(alist-replace old-phase-name new-phase phases))
((_ phases (add-before old-phase-name new-phase-name new-phase))
(alist-cons-before old-phase-name new-phase-name new-phase phases))
((_ phases (add-after old-phase-name new-phase-name new-phase))
(alist-cons-after old-phase-name new-phase-name new-phase phases))))
```
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.
I am able to run `geiser-edit-symbol-at-point` on `modify-phases`, but
not `add-after` (or related). I should also point out that Geiser only
recognizes `modify-phases` after I've already evaluated the evaluated
the form that imports the (gnu build utils) module. If I simply open the
file, start guile, and try to edit `modify-phases` nothing
happens. Geiser needs me to evaluate the (use-module (gnu build utils))
bit first.
--
Best regards,
Jake Shilling
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-11-12 15:49 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 ` Jake Shilling [this message]
2022-11-14 15:01 ` geiser-edit-symbol-at-point jgart
2022-11-14 15:16 ` geiser-edit-symbol-at-point Jake Shilling
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=87cz9sqil5.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).