From: jgart via Guix-patches via <guix-patches@gnu.org>
To: 59217@debbugs.gnu.org
Cc: jgart <jgart@dismail.de>
Subject: [bug#59217] [PATCH] guix: lint: Improve message in linter warning.
Date: Sat, 12 Nov 2022 09:09:07 -0600 [thread overview]
Message-ID: <20221112150907.29793-1-jgart@dismail.de> (raw)
* guix/lint.scm (check-end-of-sentence-space): Improve message.
---
guix/lint.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/guix/lint.scm b/guix/lint.scm
index 8e3976171f..37a9539e2c 100644
--- a/guix/lint.scm
+++ b/guix/lint.scm
@@ -14,6 +14,7 @@
;;; Copyright © 2021 Xinglu Chen <public@yoctocell.xyz>
;;; Copyright © 2021, 2022 Maxime Devos <maximedevos@telenet.be>
;;; Copyright © 2021 Brice Waegeneire <brice@waegenei.re>
+;;; Copyright © 2022 jgart <jgart@dismail.de>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -409,7 +410,7 @@ (define (check-end-of-sentence-space description)
(list
(make-warning package
(G_ "sentences in description should be followed ~
-by two spaces; possible infraction~p at ~{~a~^, ~}")
+by two spaces due to issues wth Emacs; possible infraction~p at ~{~a~^, ~}")
(list (length infractions)
infractions)
#:field 'description)))))
--
2.38.1
next reply other threads:[~2022-11-12 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 15:09 jgart via Guix-patches via [this message]
[not found] ` <handler.59217.B.166826577117982.ack@debbugs.gnu.org>
2022-11-12 15:15 ` [bug#59217] Acknowledgement ([PATCH] guix: lint: Improve message in linter warning.) jgart via Guix-patches via
2022-11-22 20:58 ` Arun Isaac
2022-11-23 10:13 ` zimoun
2022-11-23 12:52 ` Arun Isaac
2023-03-21 19:50 ` [bug#59217] [PATCH] guix: lint: Improve message in linter warning Maxim Cournoyer
2023-03-22 21:22 ` Arun Isaac
2023-03-23 2:52 ` Maxim Cournoyer
2023-03-22 21:37 ` jgart via Guix-patches via
2022-11-19 18:37 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221112150907.29793-1-jgart@dismail.de \
--to=guix-patches@gnu.org \
--cc=59217@debbugs.gnu.org \
--cc=jgart@dismail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.