From: Leo Ufimtsev <lufimtse@redhat.com>
To: Subhan Michael Tindall <SubhanT@familycareinc.org>
Cc: Ben Finney <ben+emacs@benfinney.id.au>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>,
18870@debbugs.gnu.org
Subject: bug#18870: bug#18870: \emsp and alignment in org clock report
Date: Thu, 19 Mar 2015 17:33:54 -0400 (EDT) [thread overview]
Message-ID: <621838154.36797.1426800834828.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <d455133d669f4449a20dbcf272ba3d7b@fcmailsvr2.familycareinc.org>
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.
next prev parent reply other threads:[~2015-03-19 21:35 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 ` Leo Ufimtsev [this message]
2015-03-21 8:55 ` bug#18870: " 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=621838154.36797.1426800834828.JavaMail.zimbra@redhat.com \
--to=lufimtse@redhat.com \
--cc=18870@debbugs.gnu.org \
--cc=SubhanT@familycareinc.org \
--cc=ben+emacs@benfinney.id.au \
--cc=mail@nicolasgoaziou.fr \
/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).