emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "J. David Boyd" <dboyd2@mmm.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: /emsp in clock tables
Date: Sat, 13 Dec 2014 00:05:06 +0100	[thread overview]
Message-ID: <87mw6sa2ql.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <gjub8uicfvbc.fsf@W0144758.usac.mmm.com> (J. David Boyd's message of "Fri, 12 Dec 2014 15:48:55 -0500")

dboyd2@mmm.com (J. David Boyd) writes:

> 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...

The problem is that "\___" appears in any export output, not only LaTeX.

Another option could be to use dots. At least, they wouldn't be as ugly
as "\___" in output, and keep clocktable readable in the buffer.

Regards,

  reply	other threads:[~2014-12-12 23:04 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]   ` <87iohgbwz4.fsf@nicolasgoaziou.fr>
2014-12-12 19:11     ` Daniel E. Doherty
2014-12-12 19:59 ` J. David Boyd
2014-12-12 20:48   ` J. David Boyd
2014-12-12 23:05     ` Nicolas Goaziou [this message]
2014-12-13 11:58       ` Joost Helberg

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mw6sa2ql.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=dboyd2@mmm.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).