From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Fredrik Salomonsson <plattfot@gmail.com>,
Ricardo Wurmus <rekado@elephly.net>,
Kyle Andrews <kyle.c.andrews@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Guix completion in Emacs
Date: Mon, 15 Jun 2020 08:46:09 +0200 [thread overview]
Message-ID: <87ftawesi6.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87wo49qn9m.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 173 bytes --]
It works on and off for me, sometimes with the same error.
I haven't figured out yet how to reproduce this issue reliably.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-06-15 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 21:36 Guix completion in Emacs Kyle Andrews
2020-06-14 22:00 ` Ricardo Wurmus
2020-06-14 22:46 ` Fredrik Salomonsson
2020-06-15 6:46 ` Pierre Neidhardt [this message]
2020-07-05 19:48 ` Kyle Andrews
2020-07-06 7:40 ` Pierre Neidhardt
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=87ftawesi6.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=kyle.c.andrews@gmail.com \
--cc=plattfot@gmail.com \
--cc=rekado@elephly.net \
/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.
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).