[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2017-12-04 Thread Ben Finney
On 04-Dec-2017, Nicolas Goaziou wrote: > Any 9.X version certainly contains the fix. Using this version of ‘org-mode’: Org mode version 9.1.2 (9.1.2-dist @ /usr/share/emacs/25.2/site-lisp/elpa/org-9.0.9/) I confirm that the display of the report is much better: | Headline

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2017-12-04 Thread Nicolas Goaziou
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 s

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2017-12-04 Thread Ben Finney
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

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2017-12-03 Thread Nicolas Goaziou
Hello, Ben Finney writes: > On 22-Aug-2016, Nicolas Goaziou wrote: >> The display for clock reports has been changed some months ago in >> development version. > > Which version contains this change? > >> I think this bug can be closed. > > How can we test the change, to know whether this bug is

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2017-12-03 Thread Ben Finney
On 22-Aug-2016, Nicolas Goaziou wrote: > The display for clock reports has been changed some months ago in > development version. Which version contains this change? > I think this bug can be closed. How can we test the change, to know whether this bug is resolved? -- \ “Instead of havi

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2017-12-01 Thread Nicolas Goaziou
Nicolas Goaziou writes: > Nicolas Goaziou writes: > >> The trick could be to use an Org entity which is as large as its >> overlay. Even better if that entity is readable without that overlay. >> I'll look into it soon. > > This should now be fixed. The markup used is more readable and doesn't >

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2017-12-01 Thread Glenn Morris
Nicolas Goaziou wrote: > Could this bug be marked as done? Thank you. Anyone can close any bug by sending mail to eg 18870-done at debbugs. (Thanks for looking at these reports.)

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2017-12-01 Thread Nicolas Goaziou
Hello, Glenn Morris writes: > Nicolas Goaziou wrote: > >> Could this bug be marked as done? Thank you. > > Anyone can close any bug by sending mail to eg 18870-done at debbugs. Indeed! Closing it right now. Thank you. > (Thanks for looking at these reports.) (You're welcome.) Regards, -- N

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2016-08-22 Thread Nicolas Goaziou
Hello, Sriram Karra 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

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2016-08-21 Thread Sriram Karra
On Wed, Mar 18, 2015 at 2:39 AM, Nicolas Goaziou wrote: > Hello, > > Ben Finney writes: > [...] > The "\emsp" should be space characters (of some kind; either U+0020 SPC > > or U+2003 EM SPACE) with correct alignment for the character width. > > Displaying literal "\emsp" is a regression and

Re: [O] bug#18870: bug#18870: \emsp and alignment in org clock report

2015-03-23 Thread J. David Boyd
Nicolas Goaziou writes: > Nicolas Goaziou writes: > >> The trick could be to use an Org entity which is as large as its >> overlay. Even better if that entity is readable without that overlay. >> I'll look into it soon. > > This should now be fixed. The markup used is more readable and doesn't >

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2015-03-22 Thread Nicolas Goaziou
Nicolas Goaziou writes: > The trick could be to use an Org entity which is as large as its > overlay. Even better if that entity is readable without that overlay. > I'll look into it soon. This should now be fixed. The markup used is more readable and doesn't alter table alignment.

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2015-03-21 Thread Nicolas Goaziou
Leo Ufimtsev writes: > Interesting, I didn't know that. Thank you for pointing it out. > > Maybe then just go along with the variable that would give people the choice, > (I wouldn't mind '\emsp' being the default, so long as it can be > changed to something else). Having a variable to choose i

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2015-03-19 Thread Leo Ufimtsev
t; -Original Message- > From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org > [mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On > Behalf Of Leo Ufimtsev > Sent: Wednesday, March 18, 2015 2:10 PM > To: Nicolas Goaziou > Cc: Ben Finney; 18...@

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

2015-03-18 Thread Leo Ufimtsev
I can't speak for the technical details, but I get the sense that \emsp isn't the right thing to be displayed on an *agenda clock report* because agenda clock reports don't get exported (afaik). Even \__ is more preffered than an \emsp, as \emsp is not 'easy to read' per se. Since there are