From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: batch failure of first org-num test Date: Tue, 8 Jan 2019 06:37:49 -0500 Message-ID: References: <87y37ws2cy.fsf@kyleam.com> <87va30s0ls.fsf@kyleam.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000003073a3057ef0c771" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:34319) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ggphy-0001OB-6W for emacs-orgmode@gnu.org; Tue, 08 Jan 2019 06:38:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ggphw-0006y1-CB for emacs-orgmode@gnu.org; Tue, 08 Jan 2019 06:38:10 -0500 Received: from mail-lf1-x135.google.com ([2a00:1450:4864:20::135]:34560) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ggphu-0006oE-8a for emacs-orgmode@gnu.org; Tue, 08 Jan 2019 06:38:08 -0500 Received: by mail-lf1-x135.google.com with SMTP id p6so2687727lfc.1 for ; Tue, 08 Jan 2019 03:38:04 -0800 (PST) In-Reply-To: <87va30s0ls.fsf@kyleam.com> 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: Kyle Meyer Cc: emacs-org list --0000000000003073a3057ef0c771 Content-Type: text/plain; charset="UTF-8" On Mon, Jan 7, 2019, 2:56 PM Kyle Meyer Sorry, I just now spotted an earlier message from Kaushal that reports > the same test failure: > https://lists.gnu.org/archive/html/emacs-orgmode/2019-01/msg00112.html No need to be sorry. You did the debugging and even found a fix for this. :) --0000000000003073a3057ef0c771 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jan = 7, 2019, 2:56 PM Kyle Meyer <kyle@kyl= eam.com wrote:
Sorry, I just now spotted an earlier message from Kaushal that repor= ts
the same test failure:
https://lists.gnu.o= rg/archive/html/emacs-orgmode/2019-01/msg00112.html
<= /div>

No need to be sorry. You= did the debugging and even found a fix for this. :)
--0000000000003073a3057ef0c771--