From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: bug#18870: bug#18870: \emsp and alignment in org clock report Date: Mon, 04 Dec 2017 14:43:12 +0100 Message-ID: <87k1y28v7z.fsf@nicolasgoaziou.fr> References: <544f71eb.0aadc20a.595f.70e0@mx.google.com> <1426142440.1635596.239250013.1BC7F573@webmail.messagingengine.com> <87sid31gcs.fsf@nicolasgoaziou.fr> <87y43pw801.fsf@saiph.selenimh> <20171204054932.GC21350@benfinney.id.au> <87374r9cus.fsf@nicolasgoaziou.fr> <20171204083232.GE21350@benfinney.id.au> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44948) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eLr2V-0000MV-2Y for emacs-orgmode@gnu.org; Mon, 04 Dec 2017 08:44:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eLr2Q-0006Gp-7Q for emacs-orgmode@gnu.org; Mon, 04 Dec 2017 08:44:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:35767) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eLr2Q-0006Gh-46 for emacs-orgmode@gnu.org; Mon, 04 Dec 2017 08:44:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eLr2P-0007I4-OU for emacs-orgmode@gnu.org; Mon, 04 Dec 2017 08:44:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20171204083232.GE21350@benfinney.id.au> (Ben Finney's message of "Mon, 4 Dec 2017 19:32:33 +1100") 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: Ben Finney Cc: 18870@debbugs.gnu.org Hello, Ben Finney writes: > On 04-Dec-2017, Nicolas Goaziou wrote: >> Ben Finney writes: >> > How can we test the change, to know whether this bug is resolved? >> >> You can test the latest ELPA release, scheduled for today > > Please state the exact version string, so that we can compare to see > whether we're using one that meets your description. We are talking about a 2 years old fix, so exact release doesn't really matter, really. Any 9.X version certainly contains the fix. Regards, -- Nicolas Goaziou