From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: guile-user@gnu.org,Matt Wette <matt.wette@gmail.com>
Subject: Re: Geiser vs. guile-mode?
Date: Thu, 13 Feb 2020 10:38:24 +0100 [thread overview]
Message-ID: <508C2F30-A33C-4699-8F5D-F470B2457E41@korwin-zmijowski.fr> (raw)
In-Reply-To: <F5513F8F-F6A8-4AAC-8AF3-C91991CE8E40@korwin-zmijowski.fr>
Mistake, here is the full text haha
Here is the repo I am using for my emacs conf dedicated to Guile !
https://framagit.org/Jeko/emacs-guile
If anyone can benefit/want to contribute/submit ideas/share ... Anyway you get it.
Thank you!
Jérémy
Le 13 février 2020 10:34:45 GMT+01:00, "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr> a écrit :
>Here is the repo I am using for my emacs conf dedicated to Guile
>
>Le 8 février 2020 19:59:14 GMT+01:00, Matt Wette <matt.wette@gmail.com>
>a écrit :
>>On 2/8/20 10:14 AM, Ricardo Wurmus wrote:
>>> Matt Wette <matt.wette@gmail.com> writes:
>>>
>>>> On 2/7/20 9:50 AM, sirgazil wrote:
>>>>> ---- On Fri, 07 Feb 2020 11:30:43 -0500 Matt Wette
>><matt.wette@gmail.com> wrote ----
>>>>> > Thanks for doing this. I'd like to have #! ... !# handled
>>robustly as
>>>>> > comment.
>>>>> > It's not working for me and I believe I saw a comment in the
>>code that
>>>>> > it was
>>>>> > intentionally left out (for some reason I don't remember).
>>>>>
>>>>> I don't remember those block comments working for me either, so I
>>use #| ... |# instead for top-level and nested block comments.
>>>>>
>>>> And for scripts I use the following which seems like a kludge to
>me.
>>>>
>>>> #!/bin/sh
>>>> #|
>>>> xxx
>>>> xxx
>>>> xxx
>>>> exec guile $0 "$@
>>>> |#
>>>> !#
>>> Why is this necessary? Why not use guile in the shebang?
>>>
>>
>>Finding the right installed guile, setting environment variables
>>(like GUILE_LOAD_PATH), etc. And it's not always about avoiding
>>something because it's not necessary, sometime easier to use sh.
--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
next prev parent reply other threads:[~2020-02-13 9:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:18 Geiser vs. guile-mode? Pierre Neidhardt
2020-02-04 16:16 ` Jérémy Korwin-Zmijowski
2020-02-04 16:40 ` Pierre Neidhardt
2020-02-07 13:50 ` Pierre Neidhardt
2020-02-07 16:19 ` Jérémy Korwin-Zmijowski
2020-02-07 16:30 ` Matt Wette
2020-02-07 17:50 ` sirgazil
2020-02-07 22:24 ` Matt Wette
2020-02-08 18:14 ` Ricardo Wurmus
2020-02-08 18:59 ` Matt Wette
[not found] ` <F5513F8F-F6A8-4AAC-8AF3-C91991CE8E40@korwin-zmijowski.fr>
2020-02-13 9:38 ` Jérémy Korwin-Zmijowski [this message]
2020-02-18 23:53 ` sirgazil
2020-02-19 14:16 ` Ricardo Wurmus
2020-02-20 14:24 ` sirgazil
2020-02-20 22:50 ` Jose A. Ortega Ruiz
2020-02-21 0:01 ` sirgazil
2020-02-21 1:44 ` Jose A. Ortega Ruiz
2020-02-21 8:41 ` Arne Babenhauserheide
2020-02-21 22:57 ` Jose A. Ortega Ruiz
2020-02-08 16:30 ` Pierre Neidhardt
2020-02-07 23:44 ` Jose A. Ortega Ruiz
2020-02-14 8:38 ` Pierre Neidhardt
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=508C2F30-A33C-4699-8F5D-F470B2457E41@korwin-zmijowski.fr \
--to=jeremy@korwin-zmijowski.fr \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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).