From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Ufimtsev Subject: bug#18870: bug#18870: \emsp and alignment in org clock report Date: Thu, 19 Mar 2015 17:33:54 -0400 (EDT) Message-ID: <621838154.36797.1426800834828.JavaMail.zimbra@redhat.com> References: <544f71eb.0aadc20a.595f.70e0@mx.google.com> <1426142440.1635596.239250013.1BC7F573@webmail.messagingengine.com> <87sid31gcs.fsf@nicolasgoaziou.fr> <20150317214758.GE19234@benfinney.id.au> <87oanr1do8.fsf@nicolasgoaziou.fr> <1296089020.23116290.1426713020569.JavaMail.zimbra@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55697) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYi5r-0003pI-9K for emacs-orgmode@gnu.org; Thu, 19 Mar 2015 17:35:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YYi5n-0004fe-C6 for emacs-orgmode@gnu.org; Thu, 19 Mar 2015 17:35:07 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:40578) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYi5n-0004ew-8U for emacs-orgmode@gnu.org; Thu, 19 Mar 2015 17:35:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YYi5m-0005oN-Qx for emacs-orgmode@gnu.org; Thu, 19 Mar 2015 17:35:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Subhan Michael Tindall Cc: Ben Finney , Nicolas Goaziou , 18870@debbugs.gnu.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 choic= e,=20 (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" To: "Leo Ufimtsev" , "Nicolas Goaziou" Cc: "Ben Finney" , 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 n= ame(s) and automatically export to one or more file types.=20 See: http://orgmode.org/manual/Exporting-Agenda-Views.html > -----Original Message----- > From: emacs-orgmode-bounces+subhant=3Dfamilycareinc.org@gnu.org > [mailto:emacs-orgmode-bounces+subhant=3Dfamilycareinc.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 repor= t >=20 > I can't speak for the technical details, >=20 > but I get the sense that \emsp isn't the right thing to be displayed on a= n > *agenda clock report* because agenda clock reports don't get exported > (afaik). >=20 > Even \__ is more preffered than an \emsp, as \emsp is not 'easy to read' = per > se. >=20 > Since there are clearly difference in opinions, maybe a solution is to ha= ve 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. >=20 > Thoughts? >=20 > Leo Ufimtsev | Intern Software Engineer @ Eclipse Team >=20 > ----- Original Message ----- > From: "Nicolas Goaziou" > To: "Ben Finney" > 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 >=20 > Ben Finney writes: >=20 > > The behaviour described =E2=80=93 displaying =E2=80=9C\emsp=E2=80=9D in= stead of space > > characters =E2=80=93 is a regression. That's what is being reported in = this > > bug. >=20 > There wasn't space characters in the first place, but "\___" constructs. > See commit bacfe5b4f7244eaf151f4e26a1d94dd8f66c1d19. >=20 > Also, the bug is about table alignment when `org-pretty-entities' is used= . >=20 > >> 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. >=20 > 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). >=20 > This is not a good idea, especially considering it is an invisible charac= ter. >=20 > > IS the above suggestion an acceptable solution? >=20 > No, it isn't. >=20 > An acceptable solution would be a character or a string that looks decent > both in the buffer and in an exported document, without further processin= g. >=20 > >> 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. >=20 > Actually, it works more or less correctly for display on GUI with a non-n= il `org- > pretty-entities', or calling `org-toggle-pretty-entities'. >=20 > Regards, >=20 >=20 >=20 >=20 >=20 This message is intended for the sole use of the individual and entity to w= hich it is addressed and may contain information that is privileged, confid= ential and exempt from disclosure under applicable law. If you are not the = intended addressee, nor authorized to receive for the intended addressee, y= ou are hereby notified that you may not use, copy, disclose or distribute t= o anyone the message or any information contained in the message. If you ha= ve received this message in error, please immediately advise the sender by = reply email and delete the message. Thank you.