unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: chris <chris@bumblehead.com>
To: 68948@debbugs.gnu.org
Cc: chris@bumblehead.com
Subject: bug#68948: temp fix
Date: Wed, 27 Mar 2024 13:58:03 -0700	[thread overview]
Message-ID: <ZgSIW9fJH9ODsKum@guix-xps> (raw)
In-Reply-To: <ZcIRii9JpxqWrGSk@guix-xps>

The following workaround can be used,
```
HLDIRS=$(guix build highlight); # returns two directories
HLDIR="${HLDIRS##*[[:space:]]}"; # returns the second dir, after whitespace
DATADIR="$HLDIR/etc/highlight/";
echo "(highlight (package bug))" | highlight --data-dir=$DATADIR -O xterm256 --syntax lisp
```

Based on my understanding, the current package definition is correct. Possibly a patch like this could resolve the issue the current package definition seems correct.
```
diff --git a/gnu/packages/pretty-print.scm b/gnu/packages/pretty-print.scm
index b95f56729a..2a7cf74009 100644
--- a/gnu/packages/pretty-print.scm
+++ b/gnu/packages/pretty-print.scm
@@ -389,7 +389,7 @@ (define-public highlight
                           (lambda* (#:key inputs outputs #:allow-other-keys)
                             (let* ((out (assoc-ref outputs "out"))
                                    (data (string-append out
-                                                        "/share/highlight/"))
+                                                        "/etc/highlight/"))
                                    (conf (string-append out "/etc/highlight/"))
                                    (doc (string-append out
                                          "/share/doc/highlight/"))
```




  reply	other threads:[~2024-03-27 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 11:01 bug#68948: highlight error, cannot open filetypes.conf: No such file or directory chris
2024-03-27 20:58 ` chris [this message]
2024-03-28 11:51 ` chris

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=ZgSIW9fJH9ODsKum@guix-xps \
    --to=chris@bumblehead.com \
    --cc=68948@debbugs.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).