From: email@example.com (J. David Boyd)
Subject: Re: /emsp in clock tables
Date: Fri, 12 Dec 2014 15:48:55 -0500 [thread overview]
Message-ID: <gjub8uicfvbc.fsf@W0144758.usac.mmm.com> (raw)
firstname.lastname@example.org (J. David Boyd) writes:
> I just looked through the git logs, and this is what I see:
> commit bacfe5b4f7244eaf151f4e26a1d94dd8f66c1d19
> Author: Nicolas Goaziou <email@example.com>
> 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...
So, I put the old code back into my org-clock.el, I'm running Org version
"8.3beta", and it now works fine in my clocktables.
Now I get lines like:
| Tasks | 1:18 | | | |
| \__ Infrastructure | | 0:31 | | |
| \____ WAITING Email | | | 0:07 | |
| \______ WAITING - respond to Bill | | | | 0:01 |
| \____ WAITING Research - Gnus | | | 0:14 | |
| \____ WAITING Research - Web | | | 0:04 | |
which is exactly what I wanted.
I read the linked message above from Buddy Butterfly. Was the problem only for
latext exporting? I personally look at the screen more than export...
next prev parent reply other threads:[~2014-12-12 20:49 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] ` <firstname.lastname@example.org>
2014-12-12 19:11 ` Daniel E. Doherty
2014-12-12 19:59 ` J. David Boyd
2014-12-12 20:48 ` J. David Boyd [this message]
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).