From: ludo@gnu.org (Ludovic Courtès)
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>,
David Thompson <davet@gnu.org>
Subject: Re: [PATCH 01/10] gnu: Add emacs-smex.
Date: Sun, 05 Jun 2016 22:03:18 +0200 [thread overview]
Message-ID: <87vb1npfnd.fsf@gnu.org> (raw)
In-Reply-To: <5751739E.6030909@uq.edu.au> (Ben Woodcroft's message of "Fri, 3 Jun 2016 22:10:06 +1000")
Ben Woodcroft <b.woodcroft@uq.edu.au> skribis:
> On 06/03/2016 06:14 PM, Ludovic Courtès wrote:
[...]
>> I think the downside is that the GitHub updater won’t be able to
>> identify these, although I’m not 100% sure of that.
>
> I haven't actually tested but I would think that is right
> Ludo.
Indeed:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,use(guix upstream)
scheme@(guile-user)> ,use(guix import github)
scheme@(guile-user)> ,use(gnu packages emacs)
scheme@(guile-user)> (package-update-path emacs-smex (list %github-updater))
$2 = #f
scheme@(guile-user)> ((upstream-updater-latest %github-updater) emacs-smex)
$3 = #f
scheme@(guile-user)> ((upstream-updater-predicate %github-updater) emacs-smex)
$4 = #f
--8<---------------cut here---------------end--------------->8---
> However, I expect this issue is solvable with modifications to the
> GitHub updater.
Yeah, we should probably do it eventually.
Thanks for your feedback,
Ludo’.
next prev parent reply other threads:[~2016-06-05 20:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 14:05 [PATCH 01/10] gnu: Add emacs-smex David Thompson
2016-06-01 14:05 ` [PATCH 02/10] gnu: Add emacs-js2-mode David Thompson
2016-06-01 14:05 ` [PATCH 03/10] gnu: Add emacs-markdown-mode David Thompson
2016-06-01 14:05 ` [PATCH 04/10] gnu: Add emacs-projectile David Thompson
2016-06-01 14:05 ` [PATCH 05/10] gnu: Add emacs-elfeed David Thompson
2016-06-01 14:05 ` [PATCH 06/10] gnu: Add emacs-rainbow-delimiters David Thompson
2016-06-01 14:05 ` [PATCH 07/10] gnu: Add emacs-ido-completing-read+ David Thompson
2016-06-01 14:05 ` [PATCH 08/10] gnu: Add emacs-ido-ubiquitous David Thompson
2016-06-01 14:05 ` [PATCH 09/10] gnu: Add emacs-yaml-mode David Thompson
2016-06-03 15:37 ` Mark H Weaver
2016-06-03 15:44 ` Thompson, David
2016-06-01 14:05 ` [PATCH 10/10] gnu: Add emacs-web-mode David Thompson
2016-06-02 9:26 ` [PATCH 01/10] gnu: Add emacs-smex Alex Kost
2016-06-02 13:33 ` Thompson, David
2016-06-03 8:14 ` Ludovic Courtès
2016-06-03 12:10 ` Ben Woodcroft
2016-06-05 20:03 ` Ludovic Courtès [this message]
2016-06-03 8:16 ` Ludovic Courtès
2016-06-03 12:56 ` Thompson, David
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=87vb1npfnd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=b.woodcroft@uq.edu.au \
--cc=davet@gnu.org \
--cc=guix-devel@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).