From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Sriram Karra <karra.etc@gmail.com>
Cc: 18870@debbugs.gnu.org, Ben Finney <ben@benfinney.id.au>
Subject: bug#18870: bug#18870: \emsp and alignment in org clock report
Date: Mon, 22 Aug 2016 09:57:50 +0200 [thread overview]
Message-ID: <87y43pw801.fsf@saiph.selenimh> (raw)
In-Reply-To: <CAFkt3UOO9OHOTRcnFSZWQ=sLvWjJHTbu8yzSvj34xA0QhjAmbg@mail.gmail.com> (Sriram Karra's message of "Mon, 22 Aug 2016 11:48:43 +0530")
Hello,
Sriram Karra <karra.etc@gmail.com> writes:
> I find the above reasoning completely broken. Why is the above choice
> considered the right tradeoff when there is no easy way to get something
> sensible (with or without configuration) for display? Do more people export
> rather than view?
The display for clock reports has been changed some months ago in
development version. I think this bug can be closed.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-08-22 7:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <544f71eb.0aadc20a.595f.70e0@mx.google.com>
2015-03-12 6:40 ` bug#18870: \emsp and alignment in org clock report Ben Finney
2015-03-17 21:09 ` Nicolas Goaziou
2015-03-17 21:47 ` Ben Finney
2015-03-17 22:07 ` Nicolas Goaziou
2015-03-18 21:10 ` bug#18870: " Leo Ufimtsev
2015-03-19 16:48 ` Subhan Michael Tindall
2015-03-19 21:33 ` bug#18870: " Leo Ufimtsev
2015-03-21 8:55 ` Nicolas Goaziou
2015-03-22 21:44 ` Nicolas Goaziou
2015-03-23 16:09 ` J. David Boyd
2017-12-01 18:48 ` Nicolas Goaziou
2017-12-01 18:53 ` Glenn Morris
2017-12-01 19:11 ` Nicolas Goaziou
2015-03-22 22:49 ` Ben Finney
2015-03-23 0:02 ` Nicolas Goaziou
2016-08-22 6:18 ` bug#18870: " Sriram Karra
2016-08-22 7:57 ` Nicolas Goaziou [this message]
2017-12-04 5:49 ` Ben Finney
2017-12-04 7:22 ` Nicolas Goaziou
2017-12-04 8:32 ` Ben Finney
2017-12-04 13:43 ` Nicolas Goaziou
2017-12-04 19:42 ` Ben Finney
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=87y43pw801.fsf@saiph.selenimh \
--to=mail@nicolasgoaziou.fr \
--cc=18870@debbugs.gnu.org \
--cc=ben@benfinney.id.au \
--cc=karra.etc@gmail.com \
/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).