From: David Pirotte <david@altosw.be>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Blake Shaw <blake@reproduciblemedia.com>, guile-devel@gnu.org
Subject: Re: [PATCH v3] docs/match: pattern matcher example makeover
Date: Thu, 2 Feb 2023 14:47:20 -0300 [thread overview]
Message-ID: <20230202144720.306d1bb3@aicha> (raw)
In-Reply-To: <9725d8d9-faf2-3306-94ae-209086aa5a82@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
> > -
> > style: switch to "Indiana style", bracketing lets and clauses
> > --
> > After spending much time looking at the examples in black & white
> > to edit the texinfo document, it occurred to me just how much the
> > brackets improve legibility.
Not at all - and quite annoying. imo.
So i'd 'vote' not to use them anywhere in the guile reference manual
David.
It makes the code appear as if it was another language, and requires
you train yourself to ignore them - as they actually do _not_ have any
specific meaning, but nonetheless 'pretend they do', by their mere
presence, and this causes a reading nuisance.
They are also often used inconsistently by those who use them, as
where/how you'd use them is a matter of taste, which further adds to
the reading nuisance, imo.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-02 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 13:09 [PATCH v3] docs/match: pattern matcher example makeover Blake Shaw
2023-02-01 16:40 ` Maxime Devos
2023-02-02 17:47 ` David Pirotte [this message]
2023-02-03 10:05 ` Blake Shaw
2023-02-03 12:05 ` Arun Isaac
2023-02-03 13:10 ` Blake Shaw
2023-02-03 13:43 ` Josselin Poiret
2023-02-03 14:14 ` Blake Shaw
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=20230202144720.306d1bb3@aicha \
--to=david@altosw.be \
--cc=blake@reproduciblemedia.com \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).