bug#18870: 25.0.50; \emsp and alignment in org clock report

bug#18870: 25.0.50; \emsp and alignment in org clock report

[Cédric Chépied]

It looks like the number of spaces after the headline element is calculated with
the size of the string "\emsp" instead of the real size of \emsp character.

emacs -Q
M-x org-mode
M-: (setq org-pretty-entities t)
* Test
M-x org-clock-report
M->
** Test2
C-c C-x C-i
... Wait for 1 min or manually change start time ...
C-c C-x C-o
... Go to BEGIN line of clock report ...
C-c C-c

Column alignment is wrong. If org-pretty-entities is nil, alignment is ok but
spaces are replaced with \emsp.



In GNU Emacs 25.0.50.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2014-10-27 on Zorglub
Windowing system distributor `The X.Org Foundation', version 11.0.11601000
System Description:	Arch Linux

Configured using:
 `configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib
 --localstatedir=/var --with-x-toolkit=lucid --with-xft 'CFLAGS=-march=x86-64
 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4'
 CPPFLAGS=-D_FORTIFY_SOURCE=2
 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro'

Configured features:
XAW3D XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GCONF GSETTINGS
NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB

Important settings:
  value of $LC_ALL: fr_FR.utf8
  value of $LC_CTYPE: fr_FR.UTF-8
  value of $LANG: fr_FR.UTF-8
  locale-coding-system: utf-8-unix

Major mode: LI

Minor modes in effect:
  global-git-gutter-mode: t
  global-srecode-minor-mode: t
  global-semantic-mru-bookmark-mode: t
  global-semanticdb-minor-mode: t
  global-semantic-idle-scheduler-mode: t
  global-semantic-highlight-func-mode: t
  semantic-mode: t
  yas-minor-mode: t
  global-auto-complete-mode: t
  auto-complete-mode: t
  magit-auto-revert-mode: t
  shell-dirtrack-mode: t
  diff-auto-refine-mode: t
  erc-track-mode: t
  erc-track-minor-mode: t
  erc-spelling-mode: t
  erc-ring-mode: t
  erc-match-mode: t
  erc-list-mode: t
  erc-pcomplete-mode: t
  erc-button-mode: t
  erc-fill-mode: t
  erc-stamp-mode: t
  erc-smiley-mode: t
  erc-irccontrols-mode: t
  erc-noncommands-mode: t
  erc-move-to-prompt-mode: t
  erc-readonly-mode: t
  show-paren-mode: t
  virtual-desktops-mode: t
  display-time-mode: t
  display-battery-mode: t
  tooltip-mode: t
  global-eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  hs-minor-mode: t

Recent input:
a u x x <backspace> <backspace> s s i <return> q u 
e l l e SPC n a <backspace> <backspace> b a n d e SPC 
d ' e s c r i c s <backspace> <backspace> <backspace> 
o c s <return> C-< C-< C-> C-> C-> C-< t o u t SPC 
ç a SPC p o u r SPC a l l e r SPC v o i r SPC t r a 
n s f o r m e r s <return> t r a n s <backspace> <backspace> 
<backspace> <backspace> <backspace> * t r a n s f o 
r m e r s SPC <kp-1> <kp-2> <backspace> <backspace> 
<kp-8> C-a <delete> <end> SPC <backspace> <return> 
C-> <help-echo> C-< <help-echo> <help-echo> <help-echo> 
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo> 
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo> 
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo> 
C-c r <down-mouse-1> <mouse-1> b o n SPC p a r SPC 
c o n r <backspace> t r e SPC v u SPC q u ' o n SPC 
n ' a SPC p a s SPC d e SPC n o u v e l l e s SPC d 
e SPC l a SPC p l u p a r t SPC d e s SPC g e n s SPC 
j e SPC n e SPC s a i s SPC p a s SPC q u i SPC p a 
r t i c i p e <return> <down-mouse-1> <mouse-1> C-> 
<help-echo> <down-mouse-1> <mouse-1> <down-mouse-1> 
<mouse-1> C-> M-x r e p o <tab> r <tab> b <tab> <return> 
C-g C-> C-c <right> <up> <up> <up> <up> <up> <up> <up> 
<up> <up> <up> <up> <up> <up> <up> <up> <up> <up> <C-left> 
<C-left> <right> <right> <right> <right> C-SPC <C-left> 
<left> M-w C-< M-x <up> <return>

Recent messages:
Updated (-0/+1) message(s).
Updated (-0/+1) message(s)
fnord
 
No more unsync folder
Flushing BBDB caches
Making completion list...
Quit
windmove-do-window-select: No window right from selected window
Mark set

Load-path shadows:
/usr/share/emacs/site-lisp/flim/hex-util hides /usr/share/emacs/25.0.50/lisp/hex-util
/usr/share/emacs/site-lisp/flim/md4 hides /usr/share/emacs/25.0.50/lisp/md4
/usr/share/emacs/site-lisp/flim/ntlm hides /usr/share/emacs/25.0.50/lisp/net/ntlm
/usr/share/emacs/site-lisp/flim/hmac-def hides /usr/share/emacs/25.0.50/lisp/net/hmac-def
/usr/share/emacs/site-lisp/flim/sasl hides /usr/share/emacs/25.0.50/lisp/net/sasl
/usr/share/emacs/site-lisp/flim/sasl-digest hides /usr/share/emacs/25.0.50/lisp/net/sasl-digest
/usr/share/emacs/site-lisp/flim/sasl-ntlm hides /usr/share/emacs/25.0.50/lisp/net/sasl-ntlm
/usr/share/emacs/site-lisp/flim/sasl-cram hides /usr/share/emacs/25.0.50/lisp/net/sasl-cram
/usr/share/emacs/site-lisp/flim/hmac-md5 hides /usr/share/emacs/25.0.50/lisp/net/hmac-md5
/usr/share/emacs/site-lisp/semi/smime hides /usr/share/emacs/25.0.50/lisp/gnus/smime
/usr/share/emacs/site-lisp/semi/pgg-pgp5 hides /usr/share/emacs/25.0.50/lisp/obsolete/pgg-pgp5
/usr/share/emacs/site-lisp/semi/pgg-gpg hides /usr/share/emacs/25.0.50/lisp/obsolete/pgg-gpg
/usr/share/emacs/site-lisp/semi/pgg hides /usr/share/emacs/25.0.50/lisp/obsolete/pgg
/usr/share/emacs/site-lisp/semi/pgg-pgp hides /usr/share/emacs/25.0.50/lisp/obsolete/pgg-pgp
/usr/share/emacs/site-lisp/semi/pgg-def hides /usr/share/emacs/25.0.50/lisp/obsolete/pgg-def
/usr/share/emacs/site-lisp/semi/pgg-parse hides /usr/share/emacs/25.0.50/lisp/obsolete/pgg-parse

Features:
(shadow emacsbug semantic/tag-write semantic/edit ediff-merg ediff-wind
ediff-diff ediff-mult ediff-help ediff-init ediff-util ediff vc-git
semantic/tag-file semantic/db-file data-debug cedet-files semantic/bovine/c
semantic/decorate/include semantic/decorate/mode semantic/bovine/c-by
semantic/lex-spp semantic/bovine semantic/analyze/refs hideif smtp sasl
sasl-anonymous sasl-login sasl-plain misearch multi-isearch modb-legacy smiley
gnus-art mm-uu mml2015 mm-view mml-smime smime gnus-sum gnus-group gnus-undo
gnus-start gnus-cloud nnimap nnmail mail-source utf7 nnoo parse-time gnus-spec
gnus-int gnus-range gnus-win gnus gnus-ems nnheader windmove wl-score
elmo-internal mel-q-ccl elmo-maildir modb-standard wl-mime mime-edit pgg-parse
pccl pccl-20 pgg-def signature mime-setup mail-mime-setup semi-setup mime-image
tabify org-table mule-util cal-china lunar solar cal-dst cal-bahai cal-islam
cal-hebrew holidays hol-loaddefs cal-iso org-agenda org-rmail org-mhe org-irc
org-info org-gnus org-docview org-bibtex bibtex org-bbdb org-w3m tramp-cache
tramp-sh epa-file gnutls url-cache org-clock org-caldav icalendar org-id
ox-latex ox-icalendar ox-html ox-ascii ox-publish ox org-element org org-macro
org-footnote org-pcomplete org-list org-faces org-entities noutline outline
org-version ob-emacs-lisp ob ob-tangle ob-ref ob-lob ob-table ob-exp org-src
ob-keys ob-comint ob-core ob-eval org-compat org-macs org-loaddefs find-func
url-dav url-http url url-proxy url-privacy url-expand url-methods url-history
mailcap url-auth url-cookie url-domsuf url-gw url-handlers url-util flymake
hideshow chep-lyrics chep-stickyfunc chep-tag-popup git-gutter
chep-auto-complete semantic/analyze/complete semantic/bovine/gcc semantic/dep
srecode/mode semantic/senator semantic/decorate pulse srecode/insert
srecode/filters srecode/args ede/speedbar ede/files ede ede/base ede/auto
ede/source eieio-speedbar eieio-custom srecode/find srecode/map srecode/srt-mode
semantic/analyze semantic/sort semantic/scope semantic/analyze/fcn
srecode/template srecode/srt-wy semantic/wisent semantic/wisent/wisent
srecode/ctxt srecode/compile srecode/dictionary srecode/table srecode inversion
semantic/db-global semantic/symref/global semantic/symref semantic/db-find
semantic/db-ref cedet-global semantic/mru-bookmark semantic/db-mode semantic/db
eieio-base semantic/idle semantic/format semantic/tag-ls semantic/find
semantic/ctxt semantic/util-modes semantic/util semantic semantic/tag
semantic/lex semantic/fw mode-local cedet yasnippet rtags-ac rtags dabbrev
bookmark auto-complete-config auto-complete popup smart-tabs-mode magit-blame
magit-key-mode magit view tramp tramp-compat tramp-loaddefs trampver shell
help-mode grep compile epa epg diff-mode autorevert filenotify git-rebase-mode
git-commit-mode server log-edit message rfc822 mml mml-sec mm-decode mm-bodies
mm-encode gmm-utils mailheader pcvs-util add-log newsticker newst-treeview
tree-widget newst-plainview newst-reader newst-ticker newst-backend url-parse
url-vars xml newsticker-notify znc erc-track erc-spelling flyspell ispell
erc-ring erc-match erc-list erc-pcomplete pcomplete comint ansi-color erc-button
erc-fill erc-stamp erc-goodies erc erc-backend erc-compat format-spec thingatpt
netrc appt diary-lib diary-loaddefs cal-menu calendar cal-loaddefs edmacro
kmacro bbdb-wl bbdb-hooks mail-parse rfc2231 bbdb-com warnings mailabbrev
bbdb-autoloads bbdb chep-notification mime-play filename mime-w3m advice w3m
browse-url doc-view jka-compr dired image-mode w3m-hist w3m-fb bookmark-w3m
w3m-ems wid-edit w3m-ccl ccl w3m-favicon w3m-image w3m-proc w3m-util wl-demo
wl-draft eword-encode wl-template sendmail rfc2047 rfc2045 ietf-drums mail-utils
elmo-net elmo-cache elmo-map elmo-dop wl-news derived wl-address wl-thread
wl-action wl-summary ps-print ps-def lpr wl-refile wl-message elmo-mime
mmelmo-buffer mmelmo-imap mime-view mime-conf calist semi-def mmimap mime-parse
mmbuffer mmgeneric wl-highlight elmo-multi wl-folder wl wl-e21 wl-util pp
elmo-flag elmo-localdir wl-vars wl-version elmo elmo-signal elmo-msgdb modb
modb-generic modb-entity mime elmo-util emu invisible inv-23 poem poem-e20
poem-e20_3 eword-decode mel mime-def alist std11 mcharset mcs-20 mcs-e20 pces
pces-e20 pces-20 broken pcustom elmo-date timezone elmo-vars path-util poe
elmo-version pym static apel-ver product luna concurrent-autoloads
smart-tabs-mode-autoloads info finder-inf package epg-config ibuf-macs
chep-mode-line php-mode etags ring cc-langs cl cc-mode cc-fonts cc-guess
cc-menus cc-cmds cc-styles cc-align cc-engine cc-vars cc-defs speedbar sb-image
ezimage dframe tag-stack paren chep-strike chep-couleur chep-retourne
chep-pastebin google_search ifndef_fichier_h fmanager chep-convert-audio
chep-video chep-mpd ampc easymenu avl-tree network-stream auth-source cl-macs gv
eieio byte-opt bytecomp byte-compile cconv eieio-core cl-loaddefs cl-lib
gnus-util mm-util help-fns mail-prsvr password-cache starttls tls chep-anchor
easy-mmode virtual-desktops ido time-date deeper-blue-theme time battery
cus-start cus-load tooltip eldoc electric uniquify ediff-hook vc-hooks
lisp-float-type mwheel x-win x-dnd tool-bar dnd fontset image regexp-opt fringe
tabulated-list newcomment elisp-mode lisp-mode prog-mode register page menu-bar
rfn-eshadow timer select scroll-bar mouse jit-lock font-lock syntax facemenu
font-core frame cham georgian utf-8-lang misc-lang vietnamese tibetan thai
tai-viet lao korean japanese hebrew greek romanian slovak czech european
ethiopic indian cyrillic chinese case-table epa-hook jka-cmpr-hook help simple
abbrev minibuffer nadvice loaddefs button faces cus-face macroexp files
text-properties overlay sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote make-network-process dbusbind gfilenotify
dynamic-setting system-font-setting font-render-setting x-toolkit x multi-tty
emacs)

Memory information:
((conses 16 961634 88725)
 (symbols 48 73610 217)
 (miscs 40 3602 3356)
 (strings 32 210174 34788)
 (string-bytes 1 6128095)
 (vectors 16 86025)
 (vector-slots 8 2170065 90956)
 (floats 8 1917 2086)
 (intervals 56 14380 255)
 (buffers 976 84)
 (heap 1024 85695 12182))

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

[Ben Finney]

I confirm this behaviour.

With a plain text terminal, a clock report shows like:

|-------------------+------------------------------+--------+------+------|
| willow-it.org     | *File time*                  | *5:25* |      |    
 |
|                   | Willow IT                    | 5:25   |      |    
 |
|                   | \emsp Administration         |        | 3:44 |    
 |
|                   | \emsp\emsp Induction         |        |      |
3:44 |
|                   | \emsp Training & development |        | 1:41 |    
 |
|                   | \emsp\emsp Odoo research     |        |      |
1:41 |
|-------------------+------------------------------+--------+------+------|

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 should not happen.

If having a U+2003 EM SPACE character is desirable, then instead of
LaTeX-specific markup (which is useless in the text buffer), that
character should appear directly in the data so it is useful for
display.

Thanks for working on Org Mode.

-- 
Ben Finney

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

[Nicolas Goaziou]

Hello,

Ben Finney <ben@benfinney.id.au> writes:

> I confirm this behaviour.
>
> With a plain text terminal, a clock report shows like:
>
> |-------------------+------------------------------+--------+------+------|
> | willow-it.org     | *File time*                  | *5:25* |      |    
>  |
> |                   | Willow IT                    | 5:25   |      |    
>  |
> |                   | \emsp Administration         |        | 3:44 |    
>  |
> |                   | \emsp\emsp Induction         |        |      |
> 3:44 |
> |                   | \emsp Training & development |        | 1:41 |    
>  |
> |                   | \emsp\emsp Odoo research     |        |      |
> 1:41 |
> |-------------------+------------------------------+--------+------+------|
>
> 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 should not happen.

This is not a regression. This change favors a correct export over
a correct display.

Having some space character is not desirable as it would just move the
problem the other way around (i.e., indentation would not appear during
export)

In a nutshell, the current situation is not perfect, but we have yet to
find a proper character to preserve both indentation during export and
readability.

> If having a U+2003 EM SPACE character is desirable, then instead of
> LaTeX-specific markup (which is useless in the text buffer), that
> character should appear directly in the data so it is useful for
> display.

Note that this is not LaTeX-specific markup. This is called an entity,
and is correctly exported in various back-ends.


Regards,

-- 
Nicolas Goaziou

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

[Ben Finney]

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

On 17-Mar-2015, Nicolas Goaziou wrote:
> Hello,
> 
> Ben Finney <ben@benfinney.id.au> 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
> > should not happen.
> 
> This is not a regression. This change favors a correct export over
> a correct display.

The behaviour described – displaying “\emsp” instead of space
characters – is a regression. That's what is being reported in this bug.

> Having some space character is not desirable as it would just move
> the problem the other way around (i.e., indentation would not appear
> during export)

So the U+2003 EM SPACE character should be translated *during export*,
and not be literally in the displayed text.

> In a nutshell, the current situation is not perfect, but we have yet
> to find a proper character to preserve both indentation during
> export and readability.

IS the above suggestion an acceptable solution?

> Note that this is not LaTeX-specific markup. This is called an entity,
> and is correctly exported in various back-ends.

But not for display, which is the bug to be fixed here.

Thanks for working on Org mode.

-- 
 \       “The future always arrives too fast, and in the wrong order.” |
  `\                                                    —Alvin Toffler |
_o__)                                                                  |
Ben Finney <ben@benfinney.id.au>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

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

[Nicolas Goaziou]

Ben Finney <ben+emacs@benfinney.id.au> writes:

> The behaviour described – displaying “\emsp” instead of space
> characters – is a regression. That's what is being reported in this
> bug.

There wasn't space characters in the first place, but "\___" constructs.
See commit bacfe5b4f7244eaf151f4e26a1d94dd8f66c1d19. 

Also, the bug is about table alignment when `org-pretty-entities' is
used.

>> Having some space character is not desirable as it would just move
>> the problem the other way around (i.e., indentation would not appear
>> during export)
>
> So the U+2003 EM SPACE character should be translated *during export*,
> and not be literally in the displayed text.

No, because it means this character should be treated specially by Org
(e.g., LaTeX just ignores it so it needs to be turned into a space
there). 

This is not a good idea, especially considering it is an invisible
character.

> IS the above suggestion an acceptable solution?

No, it isn't. 

An acceptable solution would be a character or a string that looks
decent both in the buffer and in an exported document, without further
processing.

>> Note that this is not LaTeX-specific markup. This is called an entity,
>> and is correctly exported in various back-ends.
>
> But not for display, which is the bug to be fixed here.

Actually, it works more or less correctly for display on GUI with
a non-nil `org-pretty-entities', or calling
`org-toggle-pretty-entities'.

Regards,

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

[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 clearly difference in opinions, maybe a solution is to have a variable like 'org-clockreport-indentation-character' which defaults to \emsp 
for correct export, but could be changed to spaces or '\__' by the user. This would give people the choice between better export or better text-buffer display.

Thoughts?

Leo Ufimtsev | Intern Software Engineer @ Eclipse Team

----- Original Message -----
From: "Nicolas Goaziou" <mail@nicolasgoaziou.fr>
To: "Ben Finney" <ben+emacs@benfinney.id.au>
Cc: 18870@debbugs.gnu.org
Sent: Tuesday, March 17, 2015 6:07:03 PM
Subject: [O] bug#18870: \emsp and alignment in org clock report

Ben Finney <ben+emacs@benfinney.id.au> writes:

> The behaviour described – displaying “\emsp” instead of space
> characters – is a regression. That's what is being reported in this
> bug.

There wasn't space characters in the first place, but "\___" constructs.
See commit bacfe5b4f7244eaf151f4e26a1d94dd8f66c1d19. 

Also, the bug is about table alignment when `org-pretty-entities' is
used.

>> Having some space character is not desirable as it would just move
>> the problem the other way around (i.e., indentation would not appear
>> during export)
>
> So the U+2003 EM SPACE character should be translated *during export*,
> and not be literally in the displayed text.

No, because it means this character should be treated specially by Org
(e.g., LaTeX just ignores it so it needs to be turned into a space
there). 

This is not a good idea, especially considering it is an invisible
character.

> IS the above suggestion an acceptable solution?

No, it isn't. 

An acceptable solution would be a character or a string that looks
decent both in the buffer and in an exported document, without further
processing.

>> Note that this is not LaTeX-specific markup. This is called an entity,
>> and is correctly exported in various back-ends.
>
> But not for display, which is the bug to be fixed here.

Actually, it works more or less correctly for display on GUI with
a non-nil `org-pretty-entities', or calling
`org-toggle-pretty-entities'.

Regards,

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

[Subhan Michael Tindall]

Agendas can & do get exported.  Current agenda buffer can be exported using org-agenda-write to several formats. Custom agendas can be assigned file name(s) and automatically export to one or more file types. 

See: http://orgmode.org/manual/Exporting-Agenda-Views.html


> -----Original Message-----
> From: emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org
> [mailto:emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org] On
> Behalf Of Leo Ufimtsev
> Sent: Wednesday, March 18, 2015 2:10 PM
> To: Nicolas Goaziou
> Cc: Ben Finney; 18870@debbugs.gnu.org
> Subject: [O] bug#18870: bug#18870: \emsp and alignment in org clock report
> 
> 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 clearly difference in opinions, maybe a solution is to have a
> variable like 'org-clockreport-indentation-character' which defaults to \emsp
> for correct export, but could be changed to spaces or '\__' by the user. This
> would give people the choice between better export or better text-buffer
> display.
> 
> Thoughts?
> 
> Leo Ufimtsev | Intern Software Engineer @ Eclipse Team
> 
> ----- Original Message -----
> From: "Nicolas Goaziou" <mail@nicolasgoaziou.fr>
> To: "Ben Finney" <ben+emacs@benfinney.id.au>
> Cc: 18870@debbugs.gnu.org
> Sent: Tuesday, March 17, 2015 6:07:03 PM
> Subject: [O] bug#18870: \emsp and alignment in org clock report
> 
> Ben Finney <ben+emacs@benfinney.id.au> writes:
> 
> > The behaviour described – displaying “\emsp” instead of space
> > characters – is a regression. That's what is being reported in this
> > bug.
> 
> There wasn't space characters in the first place, but "\___" constructs.
> See commit bacfe5b4f7244eaf151f4e26a1d94dd8f66c1d19.
> 
> Also, the bug is about table alignment when `org-pretty-entities' is used.
> 
> >> Having some space character is not desirable as it would just move
> >> the problem the other way around (i.e., indentation would not appear
> >> during export)
> >
> > So the U+2003 EM SPACE character should be translated *during export*,
> > and not be literally in the displayed text.
> 
> No, because it means this character should be treated specially by Org (e.g.,
> LaTeX just ignores it so it needs to be turned into a space there).
> 
> This is not a good idea, especially considering it is an invisible character.
> 
> > IS the above suggestion an acceptable solution?
> 
> No, it isn't.
> 
> An acceptable solution would be a character or a string that looks decent
> both in the buffer and in an exported document, without further processing.
> 
> >> Note that this is not LaTeX-specific markup. This is called an
> >> entity, and is correctly exported in various back-ends.
> >
> > But not for display, which is the bug to be fixed here.
> 
> Actually, it works more or less correctly for display on GUI with a non-nil `org-
> pretty-entities', or calling `org-toggle-pretty-entities'.
> 
> Regards,
> 
> 
> 
> 
> 


This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message.  Thank you.

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

[Leo Ufimtsev]

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

Thoughts?

Leo Ufimtsev | Intern Software Engineer @ Eclipse Team

----- Original Message -----
From: "Subhan Michael Tindall" <SubhanT@familycareinc.org>
To: "Leo Ufimtsev" <lufimtse@redhat.com>, "Nicolas Goaziou" <mail@nicolasgoaziou.fr>
Cc: "Ben Finney" <ben+emacs@benfinney.id.au>, 18870@debbugs.gnu.org
Sent: Thursday, March 19, 2015 12:48:40 PM
Subject: [O] bug#18870: \emsp and alignment in org clock report

Agendas can & do get exported.  Current agenda buffer can be exported using org-agenda-write to several formats. Custom agendas can be assigned file name(s) and automatically export to one or more file types. 

See: http://orgmode.org/manual/Exporting-Agenda-Views.html


> -----Original Message-----
> From: emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org
> [mailto:emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org] On
> Behalf Of Leo Ufimtsev
> Sent: Wednesday, March 18, 2015 2:10 PM
> To: Nicolas Goaziou
> Cc: Ben Finney; 18870@debbugs.gnu.org
> Subject: [O] bug#18870: bug#18870: \emsp and alignment in org clock report
> 
> 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 clearly difference in opinions, maybe a solution is to have a
> variable like 'org-clockreport-indentation-character' which defaults to \emsp
> for correct export, but could be changed to spaces or '\__' by the user. This
> would give people the choice between better export or better text-buffer
> display.
> 
> Thoughts?
> 
> Leo Ufimtsev | Intern Software Engineer @ Eclipse Team
> 
> ----- Original Message -----
> From: "Nicolas Goaziou" <mail@nicolasgoaziou.fr>
> To: "Ben Finney" <ben+emacs@benfinney.id.au>
> Cc: 18870@debbugs.gnu.org
> Sent: Tuesday, March 17, 2015 6:07:03 PM
> Subject: [O] bug#18870: \emsp and alignment in org clock report
> 
> Ben Finney <ben+emacs@benfinney.id.au> writes:
> 
> > The behaviour described – displaying “\emsp” instead of space
> > characters – is a regression. That's what is being reported in this
> > bug.
> 
> There wasn't space characters in the first place, but "\___" constructs.
> See commit bacfe5b4f7244eaf151f4e26a1d94dd8f66c1d19.
> 
> Also, the bug is about table alignment when `org-pretty-entities' is used.
> 
> >> Having some space character is not desirable as it would just move
> >> the problem the other way around (i.e., indentation would not appear
> >> during export)
> >
> > So the U+2003 EM SPACE character should be translated *during export*,
> > and not be literally in the displayed text.
> 
> No, because it means this character should be treated specially by Org (e.g.,
> LaTeX just ignores it so it needs to be turned into a space there).
> 
> This is not a good idea, especially considering it is an invisible character.
> 
> > IS the above suggestion an acceptable solution?
> 
> No, it isn't.
> 
> An acceptable solution would be a character or a string that looks decent
> both in the buffer and in an exported document, without further processing.
> 
> >> Note that this is not LaTeX-specific markup. This is called an
> >> entity, and is correctly exported in various back-ends.
> >
> > But not for display, which is the bug to be fixed here.
> 
> Actually, it works more or less correctly for display on GUI with a non-nil `org-
> pretty-entities', or calling `org-toggle-pretty-entities'.
> 
> Regards,
> 
> 
> 
> 
> 


This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message.  Thank you.

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

[Nicolas Goaziou]

Leo Ufimtsev <lufimtse@redhat.com> 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 in which way Org should be broken doesn't
sound great to me.

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.


Regards,

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

[Nicolas Goaziou]

Nicolas Goaziou <mail@nicolasgoaziou.fr> 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.

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

[Ben Finney]

[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]

On 17-Mar-2015, Nicolas Goaziou wrote:

> Also, the bug is about table alignment when `org-pretty-entities' is
> used.

Okay. So if I'm reporting a regression in the text (non-GUI) Emacs
behaviour of Org mode, I should make a separate report?

> > So the U+2003 EM SPACE character should be translated *during
> > export*, and not be literally in the displayed text.
> 
> No, because it means this character should be treated specially by
> Org (e.g., LaTeX just ignores it so it needs to be turned into a
> space there).

That conflicts with what you're saying later:

> > But not for display, which is the bug to be fixed here.
> 
> Actually, it works more or less correctly for display on GUI with a
> non-nil `org-pretty-entities', or calling
> `org-toggle-pretty-entities'.

So the behaviour is masked by special behaviour of “entities”. Why is
that special behaviour acceptable, but allowing export of U+2003 is not?

On 22-Mar-2015, Nicolas Goaziou wrote:

> This should now be fixed. The markup used is more readable and
> doesn't alter table alignment.

Is that true for text-only terminals too?

-- 
 \       “See, in my line of work you gotta keep repeating things over |
  `\       and over and over again, for the truth to sink in; to kinda |
_o__)               catapult the propaganda.” —George W. Bush, 2005-05 |
Ben Finney <ben@benfinney.id.au>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

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

[Nicolas Goaziou]

Hello,

Ben Finney <ben+emacs@benfinney.id.au> writes:

> Okay. So if I'm reporting a regression in the text (non-GUI) Emacs
> behaviour of Org mode, I should make a separate report?

First, please update Org and test the new behaviour if you can.

> So the behaviour is masked by special behaviour of “entities”. Why is
> that special behaviour acceptable, but allowing export of U+2003 is
> not?

Because entities syntax is well defined, and uses easy-to-reach
characters. Asking users to insert EM SPACE as special markup doesn't
seem right for Org.

> On 22-Mar-2015, Nicolas Goaziou wrote:
>
>> This should now be fixed. The markup used is more readable and
>> doesn't alter table alignment.
>
> Is that true for text-only terminals too?

Yes, it is.


Regards,

-- 
Nicolas Goaziou

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

[J. David Boyd]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> 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.

Thanks very much, I feel this is much better.  I can read the columns ok, and
they export fine too.

Thanks for all your efforts in Org-mode!

Dave in Hudson, FL

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

[Sriram Karra]

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

On Wed, Mar 18, 2015 at 2:39 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Ben Finney <ben@benfinney.id.au> 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 should not happen.
>
> This is not a regression. This change favors a correct export over
> a correct display.
>

I recently upgraded to a new machine and got the updated org-mode (8.2.10)
with Aquamacs 3.2 and ran into this problem

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?

[-- Attachment #2: Type: text/html, Size: 1457 bytes --]

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

[Nicolas Goaziou]

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

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

[Nicolas Goaziou]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> 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.

Could this bug be marked as done? Thank you.

Regards,

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

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

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

[Nicolas Goaziou]

Hello,

Glenn Morris <rgm@gnu.org> 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,

-- 
Nicolas Goaziou                                                0x80A93738

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

[Ben Finney]

[-- Attachment #1: Type: text/plain, Size: 559 bytes --]

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 having ‘answers’ on a math test, they should just |
  `\               call them ‘impressions’, and if you got a different |
_o__)   ‘impression’, so what, can't we all be brothers?” —Jack Handey |
Ben Finney <ben@benfinney.id.au>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Nicolas Goaziou]

Hello,

Ben Finney <ben+emacs@benfinney.id.au> 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 resolved?

You can test the latest ELPA release, scheduled for today (the current
ELPA release also contains the bug but has a nasty fontification bug
too).

You can also test Org bundled with Emacs 26.0.50.

Regards,

-- 
Nicolas Goaziou

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

[Ben Finney]

[-- Attachment #1: Type: text/plain, Size: 621 bytes --]

On 04-Dec-2017, Nicolas Goaziou wrote:
> Ben Finney <ben+emacs@benfinney.id.au> 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 your description.

-- 
 \       “We must find our way to a time when faith, without evidence, |
  `\    disgraces anyone who would claim it.” —Sam Harris, _The End of |
_o__)                                                     Faith_, 2004 |
Ben Finney <ben@benfinney.id.au>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Nicolas Goaziou]

Hello,

Ben Finney <ben+emacs@benfinney.id.au> writes:

> On 04-Dec-2017, Nicolas Goaziou wrote:
>> Ben Finney <ben+emacs@benfinney.id.au> 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 your description.

We are talking about a 2 years old fix, so exact release doesn't really
matter, really. Any 9.X version certainly contains the fix.

Regards,

-- 
Nicolas Goaziou

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

[Ben Finney]

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

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                    | Time   |      |      |
    |-----------------------------+--------+------+------|
    | *Total time*                | *0:20* |      |      |
    |-----------------------------+--------+------+------|
    | Lorem ipsum, dolor sit amet | 0:20   |      |      |
    | \_  Suscipit sint quod      |        | 0:13 |      |
    | \_  Ab facilis nulla        |        | 0:07 |      |
    | \_    Dolore laborum        |        |      | 0:07 |

Thank you to the Org developers for resolving this bug.

-- 
 \          “A thing moderately good is not so good as it ought to be. |
  `\        Moderation in temper is always a virtue; but moderation in |
_o__)                       principle is always a vice.” —Thomas Paine |
Ben Finney <ben@benfinney.id.au>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]