unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: guile-user@gnu.org
Subject: Re: Logo proposal
Date: Tue, 28 Jan 2020 21:40:44 +0100	[thread overview]
Message-ID: <36b77634-0f5e-52e5-89dc-3a86165c1488@posteo.de> (raw)
In-Reply-To: <87zhe8xvdr.fsf@gnus.jao.io>

Hmmm, I tried again and it worked in command line REPL and Geiser.
Weird, I was remembering something did not work. Perhaps it was only
when I needed lambda* or something. Great, I can use it more often again!

On 1/28/20 1:44 AM, Jose A. Ortega Ruiz wrote:
> On Tue, Jan 28 2020, Zelphir Kaltstahl wrote:
>
>> On 1/27/20 2:03 PM, Marc Chantreux wrote:
>>> hello,
>>>
>>> On Mon, Jan 27, 2020 at 12:30:51AM +0100, Arne Babenhauserheide wrote:
>>>> Did you try it?
>>> i never seen λ used in the documentation or code so what i actually
>>> wrote a macro:
>>>     (define-syntax λ
>>>       (syntax-rules ()
>>>         ((λ sign ...)
>>>          (lambda sign ...))))
>>>
>>> i just removed it and the code is still working. thanks a lot.
>>>
>>> marc
>>>
>> The thing is, it does not work in Geiser in Emacs.
> Hmm, it does work for me.  For instance, this simple example
>
>    (define-module (foo))
>
>    (define foo (λ () 3))
>
> in foo.scm does what i expect.  Also using λ directly in the REPL works
> for me.  What behaviour are you observing instead?  Could it be that
> you're not using UTF-8 as your encoding?
>
> Cheers,
> jao



  reply	other threads:[~2020-01-28 20:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-26 16:59 Logo proposal sirgazil
2020-01-26 19:14 ` Marc Chantreux
2020-01-26 19:27   ` sirgazil
2020-01-26 23:30   ` Arne Babenhauserheide
2020-01-27 13:03     ` Marc Chantreux
2020-01-27 23:33       ` Zelphir Kaltstahl
2020-01-28  0:44         ` Jose A. Ortega Ruiz
2020-01-28 20:40           ` Zelphir Kaltstahl [this message]
2020-01-28  1:06         ` Mikhail Kryshen
2020-01-28  3:06           ` Jose A. Ortega Ruiz
2020-01-26 22:47 ` John Cowan
2020-01-27 12:58   ` sirgazil
2020-01-30  3:57   ` Maxim Cournoyer
2020-01-31 16:05     ` sirgazil
2020-01-28  9:26 ` Ludovic Courtès
2020-01-28 10:26   ` Jérémy Korwin-Zmijowski
2020-01-28 14:20     ` sirgazil
2020-01-28 14:18   ` sirgazil
2020-02-05 19:38   ` Christopher Lemmer Webber

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=36b77634-0f5e-52e5-89dc-3a86165c1488@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=guile-user@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).