all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "LaFreniere\, Joseph" <joseph@lafreniere.xyz>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 39384@debbugs.gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: [bug#39384] [PATCH] gnu: Add emacs-rg.
Date: Tue, 04 Feb 2020 21:08:11 -0600	[thread overview]
Message-ID: <87mu9xspd0.fsf@lafreniere.xyz> (raw)
In-Reply-To: <20200204095851.GA19864@E5400>


Efraim Flashner <efraim@flashner.co.il> writes:
> We want to have ripgrep as a regular input, so at the point in 
> the code
> where it searches through PATH for the rg binary we patch it to 
> refer to
> the specific binary. One example of this is in (gnu packages 
> emacs-xyz),
> with emacs-nov-el.

Ah, I see what you mean now.  But wouldn't hard-coding the path to 
ripgrep in that way prevent the package from being able to use 
remote systems' ripgrep binaries when running over TRAMP?

--
Joseph LaFreniere

  reply	other threads:[~2020-02-05  3:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 20:28 [bug#39384] [PATCH] gnu: Add emacs-rg LaFreniere, Joseph
2020-02-01 22:09 ` Nicolas Goaziou
2020-02-02 14:21   ` LaFreniere, Joseph
2020-02-02 18:47     ` Efraim Flashner
2020-02-03  3:41       ` LaFreniere, Joseph
2020-02-04  9:58         ` Efraim Flashner
2020-02-05  3:08           ` LaFreniere, Joseph [this message]
2020-02-05  7:13             ` Efraim Flashner
2020-02-05 21:33             ` Marius Bakke
2020-02-07  0:47               ` LaFreniere, Joseph
2020-02-07 10:54                 ` Efraim Flashner
2020-02-08 22:23                   ` LaFreniere, Joseph
2020-02-09 13:28                     ` Efraim Flashner
2020-02-22 23:08                       ` LaFreniere, Joseph
2020-02-23 11:17                         ` bug#39384: " Efraim Flashner

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=87mu9xspd0.fsf@lafreniere.xyz \
    --to=joseph@lafreniere.xyz \
    --cc=39384@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=mail@nicolasgoaziou.fr \
    /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.