From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: ABI and emacs-guix Date: Fri, 26 Apr 2019 10:37:10 +0200 Message-ID: <871s1pnow9.fsf@gnu.org> References: <87d0l9rdh0.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:48627) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJwZp-0005us-2e for guix-devel@gnu.org; Fri, 26 Apr 2019 04:51:26 -0400 In-Reply-To: <87d0l9rdh0.fsf@posteo.net> (Brett Gilio's message of "Thu, 25 Apr 2019 16:18:03 -0500") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Brett Gilio Cc: Guix-devel Hi Brett, Brett Gilio skribis: > Was there another ABI change to Guix? The last time this happened > emacs-guix began behaving improperly and spitting out unresolvable error > messages in the *Messages* buffer. This is happening again, and Ludo > fixed it by rebuilding it I think? Can you share those terrible error messages? As I write this, Emacs-Guix works awesomely fine for me. :-) > If this is the case, is there a consistent way to have emacs-guix be > rebuilt after these changes? I haven=E2=80=99t checked how Emacs-Guix spawns its REPL server, but I think that to be safe, it should spawn it via =E2=80=98guix repl=E2=80=99, which = is guaranteed to be using the right APIs and all. Thanks, Ludo=E2=80=99.