From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ben Finney <ben+emacs@benfinney.id.au>
Cc: 18870@debbugs.gnu.org
Subject: bug#18870: \emsp and alignment in org clock report
Date: Tue, 17 Mar 2015 23:07:03 +0100 [thread overview]
Message-ID: <87oanr1do8.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20150317214758.GE19234@benfinney.id.au> (Ben Finney's message of "Wed, 18 Mar 2015 08:47:58 +1100")
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,
next prev parent reply other threads:[~2015-03-17 22:06 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 [this message]
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
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=87oanr1do8.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=18870@debbugs.gnu.org \
--cc=ben+emacs@benfinney.id.au \
/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).