unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: kiasoc5 <kiasoc5@disroot.org>
Cc: 57927@debbugs.gnu.org
Subject: [bug#57927] [PATCH] gnu: source-highlight: Fix lesspipe file name and use gexps.
Date: Tue, 27 Sep 2022 15:22:19 +0200	[thread overview]
Message-ID: <87bkr1ey8x.fsf@nckx> (raw)
In-Reply-To: <29d55f693128126558e2e3e0a030194453312187.1663570649.git.kiasoc5@disroot.org>

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

Hi kiasoc5,

kiasoc5 via Guix-patches via 写道:
> This fixes src-hilite-lesspipe.sh so that lesspipe.sh is called 
> instead of lesspipe.

Thanks!  I reverted this change on master.  It caused over 4000 
rebuilds (per architecture), which means it's core-updates 
material.

You can test this yourself by running ‘guix refresh -l 
source-highlight’.  It's not perfect: it can fail to detect some 
paths, especially when inheritance is involved.  But it's a good 
sanity check.

When you notice a rebuild count higher than the thresholds given 
here[0], please add a ‘[PATCH core-updates]’ or ‘[PATCH staging]’ 
warning to your patch subject.  It reduces the chance of these 
slipping through.

> * gnu/packages/pretty-print.scm (source-highlight):
> [arguments]: Use gexps, remove trailing #ts.
> [phases]: Add phase to make src-highlight-lesspipe.sh work.

These unrelated changes should be separated into at least two 
patches next time: one to gexp and remove the #ts, the other to 
make the functional change.

‘At least’, because Gexpification often leaves the output hash 
unchanged, so a separate gexp patch might have been able to go 
straight to master.

> +    (arguments   

This introduced a whitespace error: there are extra trailing 
spaces.  Git should highlight these when showing the diff.  I 
removed them.

Kind regards,

T G-R

[0]: https://guix.gnu.org/manual/en/guix.html#Submitting-Patches

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2022-09-27 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19  6:57 [bug#57927] [PATCH] gnu: source-highlight: Fix lesspipe file name and use gexps kiasoc5 via Guix-patches via
2022-09-27  9:11 ` bug#57927: " Mathieu Othacehe
2022-09-27 13:22 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-09-28  4:34   ` [bug#57927] " kiasoc5 via Guix-patches via
2022-09-28 21:14     ` Maxime Devos
2022-09-28 21:16     ` Maxime Devos

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=87bkr1ey8x.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=57927@debbugs.gnu.org \
    --cc=kiasoc5@disroot.org \
    --cc=me@tobias.gr \
    /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).