unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
	Taylan Kammer <taylan.kammer@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Indentation with inline comments in Emacs
Date: Sun, 17 Apr 2022 16:58:13 +0200	[thread overview]
Message-ID: <dbaa7e1def5de4412533062a3f0d62bc0e296b43.camel@telenet.be> (raw)
In-Reply-To: <15968029-3c0c-9ced-ea8f-3bbc8446d96d@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 622 bytes --]

Zelphir Kaltstahl schreef op zo 17-04-2022 om 11:06 [+0000]:
> I never understood, why Emacs indented that way, but now I understand. First 
> argument is seen as special, as the function/procedure that is being called – 
> aha! I do not know, whether the syntax for vector creation #(...) is the same in 
> all Scheme dialects, which have vectors, in general. Perhaps it would require a 
> specific GNU Guile mode for Emacs, if it is not the same in all Scheme dialects.

#(vector things ...) is standard R6RS scheme:

http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-7.html#node_sec_4.3.3

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-04-17 14:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 12:12 Indentation with inline comments in Emacs Zelphir Kaltstahl
2022-04-16 14:57 ` Jérémy Korwin-Zmijowski
2022-04-17 10:49   ` Zelphir Kaltstahl
2022-04-17 13:44     ` Luis Felipe
2022-04-18 10:48       ` Zelphir Kaltstahl
2022-04-18 13:33         ` Ricardo G. Herdt
2022-04-18 14:09           ` Luis Felipe
2022-04-18 14:05         ` Luis Felipe
2022-04-17  3:03 ` Taylan Kammer
2022-04-17 11:06   ` Zelphir Kaltstahl
2022-04-17 14:58     ` Maxime Devos [this message]
2022-04-18 10:49       ` Zelphir Kaltstahl

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=dbaa7e1def5de4412533062a3f0d62bc0e296b43.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guile-user@gnu.org \
    --cc=taylan.kammer@gmail.com \
    --cc=zelphirkaltstahl@posteo.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).