all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 26795@debbugs.gnu.org
Subject: bug#26795: gnu: emacs-ag: Propagate the-silver-searcher.
Date: Sat, 06 May 2017 16:05:32 +0200	[thread overview]
Message-ID: <87fugiullf.fsf@gnu.org> (raw)
In-Reply-To: <87pofm5pbd.fsf@lassieur.org> ("Clément Lassieur"'s message of "Sat, 06 May 2017 11:04:22 +0200")

Hello Clément,

Clément Lassieur <clement@lassieur.org> skribis:

> emacs-ag is mostly unusable via Tramp (except if the
> 'the-silver-searcher' store element is also in the remote system, which
> will never happen if the remote system is not running Guix).
>
> I believe 'the-silver-searcher' should be propagated, and the executable
> should be 'ag' (which is the default value) instead of
> '/gnu/store/...-the-silver-searcher-1.0.2/bin/ag', so that it can be
> found on remote systems.

That makes sense to me.  Christopher Baines wrote it; WDYT Chris?

> This allows emacs-ag to be used on remote systems.
>
> * gnu/packages/emacs.scm (emacs-ag)[inputs]: Remove.  Move THE-SILVER-SEARCHER
> to...
> [propagated-inputs]: ... here.
> [arguments]: Remove 'patch-exec-paths' phase.

[...]

>      (propagated-inputs
>       `(("dash" ,emacs-dash)
> -       ("s" ,emacs-s)))
> +       ("s" ,emacs-s)
> +       ("the-silver-searcher" ,the-silver-searcher)))

I’d suggest writing the rationale for propagation in a comment above.

Thanks,
Ludo’.

  parent reply	other threads:[~2017-05-06 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06  9:04 bug#26795: gnu: emacs-ag: Propagate the-silver-searcher Clément Lassieur
2017-05-06  9:07 ` bug#26795: [PATCH] " Clément Lassieur
2017-05-06 14:05 ` Ludovic Courtès [this message]
2017-05-11 16:44   ` bug#26795: " Mathieu Othacehe
2017-05-12  8:42     ` Clément Lassieur

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=87fugiullf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=26795@debbugs.gnu.org \
    --cc=clement@lassieur.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 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.