On 2/8/20 10:14 AM, Ricardo Wurmus wrote:
Matt Wette <matt.we...@gmail.com> writes:
On 2/7/20 9:50 AM, sirgazil wrote:
---- On Fri, 07 Feb 2020 11:30:43 -0500 Matt Wette <matt.we...@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.
