From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Jerram Subject: Re: org-babel-execute:go crashes on Mac Date: Thu, 25 Oct 2018 21:07:51 +0100 Message-ID: <878t2lbxig.fsf@ossau.homelinux.net> References: <99410E52-EB8E-4496-B494-21B26B131AC6@ossau.homelinux.net> <5D6C6CB3-EBE2-491D-B5BF-D82034BF505A@schnuddelhuddel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39626) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFm2M-0001Vp-MX for emacs-orgmode@gnu.org; Thu, 25 Oct 2018 16:15:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gFlv9-0002kD-FR for emacs-orgmode@gnu.org; Thu, 25 Oct 2018 16:08:00 -0400 Received: from ossau.homelinux.net ([18.217.239.99]:55380 helo=ip-172-31-40-63.us-east-2.compute.internal) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFlv9-0002jC-AS for emacs-orgmode@gnu.org; Thu, 25 Oct 2018 16:07:55 -0400 In-Reply-To: <5D6C6CB3-EBE2-491D-B5BF-D82034BF505A@schnuddelhuddel.de> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Mario Martelli Cc: emacs-orgmode@gnu.org Mario Martelli writes: > Thank you for your answer.=20 > >> If you haven't already, I suggest checking that there isn't a difference= in your Go setup, by working out the "go run ..." command that is being ru= n below, and running that manually yourself. > > My first assumption was - to be honest, still is - that the "go run =E2= =80=A6=E2=80=9D is not executed at all because the call to =E2=80=9Cgo run = =E2=80=A6=E2=80=9D is within an illegal elisp function. Am I wrong with my= assumption? > > Kind regards > Mario > > P.S. Would have no idea how to work out what the outcome of the function = is ;) Perhaps I misunderstood the error message, but I thought perhaps it was about code trying to represent the _result_ of the execution as an elisp function. But it is very difficult to tell! I guess if I had this on my system (which I can't because I don't run on a Mac), I'd use 'edebug-defun' on some of the functions involved in the error message, in order to start understanding whether they are actually being executed. Best wishes, Neil