From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 73216@debbugs.gnu.org,
"Katherine Cox-Buday" <cox.katherine.e+guix@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>,
"Andrew Tropin" <andrew@trop.in>
Subject: [bug#73216] [PATCH 1/2] gnu: Add emacs-org-texlive-collection.
Date: Fri, 13 Sep 2024 23:28:17 +0900 [thread overview]
Message-ID: <875xqzy6f2.fsf@gmail.com> (raw)
In-Reply-To: <01c3222d5f9e4207bc8af806c3778c89089b4d66.camel@gmail.com> (Liliana Marie Prikler's message of "Fri, 13 Sep 2024 08:26:29 +0200")
Hi again,
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
[...]
> Nitpick: these comments are not aligned.
> As a personal thing, I also suggest using a space between ; and for,
> but I see both styles used in Guix.
Actually, re-reading our referenced style [0], it opines for no spaces
between ';' and the comment, at least it says it's acceptable and uses
that in its example:
The only comments in which omission of a space between the semicolon
and the text is acceptable are margin comments.
Examples:
;;;; Frob Grovel
;;; This section of code has some important implications:
;;; 1. Foo.
;;; 2. Bar.
;;; 3. Baz.
(define (fnord zarquon)
;; If zob, then veeblefitz.
(quux zot
mumble ;Zibblefrotz.
frotz))
Phew. I can continue writing my inline comments the way I got accustomed
to :-).
[0] https://mumble.net/~campbell/scheme/style.txt
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-09-13 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 2:23 [bug#73216] [PATCH 1/2] gnu: Add emacs-org-texlive-collection Maxim Cournoyer
2024-09-13 2:29 ` [bug#73216] [PATCH 2/2] gnu: emacs-org: Mention the emacs-org-texlive-collection in description Maxim Cournoyer
2024-09-13 6:26 ` Liliana Marie Prikler
2024-09-13 16:08 ` bug#73216: " Maxim Cournoyer
2024-09-13 17:02 ` [bug#73216] " Nicolas Goaziou via Guix-patches via
2024-09-13 6:26 ` [bug#73216] [PATCH 1/2] gnu: Add emacs-org-texlive-collection Liliana Marie Prikler
2024-09-13 14:16 ` Maxim Cournoyer
2024-09-13 14:30 ` Liliana Marie Prikler
2024-09-13 14:28 ` Maxim Cournoyer [this message]
2024-09-13 14:42 ` Liliana Marie Prikler
2024-09-13 17:00 ` Nicolas Goaziou via Guix-patches via
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xqzy6f2.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=73216@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=liliana.prikler@gmail.com \
--cc=ludo@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).