From: firstname.lastname@example.org (J. David Boyd)
Subject: Re: /emsp in clock tables
Date: Fri, 12 Dec 2014 14:59:02 -0500 [thread overview]
Message-ID: <gjubfvckfxmh.fsf@W0144758.usac.mmm.com> (raw)
email@example.com (J. David Boyd) writes:
> I don't remember reading about this here, so hopefully I haven't just missed
> I've found some reference to it on the web, but no resolution.
> Sometime in the last few releases, clock tables have changed the display.
> I now see
> | *Total time* | *2:17* | | |
> | Tasks | 2:17 | | |
> | \emsp Infrastructure | | 0:27 | |
> | \emsp\emsp WAITING Email | | | 0:06 |
> How can I remove the \emsp artifact and get back the old behavior?
> Advance apologies if this is somewhere in a README that I didn't...
> Dave in Hudson, FL
I just looked through the git logs, and this is what I see:
Author: Nicolas Goaziou <firstname.lastname@example.org>
Date: Fri Jul 25 11:02:55 2014 +0200
org-clock: Update syntax for indentation in clock tables
* lisp/org-clock.el (org-clocktable-indent-string): Use "\emsp"
instead of "\__", which is not supported anymore since Org 8.0.
Thanks to Buddy Butterfly for reporting it.
Can't believe it was all the way back in July when this changed, guess I
haven't done any clocktables in a while.
So I guess the problem is 'how do I keep the \emsp from displaying on the
Is there anyway, or do I just live with it...
next prev parent reply other threads:[~2014-12-12 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 16:52 /emsp in clock tables J. David Boyd
2014-12-11 17:16 ` Joost Helberg
2014-12-12 15:18 ` J. David Boyd
2014-12-12 16:46 ` Daniel E. Doherty
[not found] ` <email@example.com>
2014-12-12 19:11 ` Daniel E. Doherty
2014-12-12 19:59 ` J. David Boyd [this message]
2014-12-12 20:48 ` J. David Boyd
2014-12-12 23:05 ` Nicolas Goaziou
2014-12-13 11:58 ` Joost Helberg
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).