[O] bug#18870: \emsp and alignment in org clock report
Hello, Ben Finney ben+em...@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
[O] bug#18870: \emsp and alignment in org clock report
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 b...@benfinney.id.au signature.asc Description: Digital signature
[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@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...@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 m...@nicolasgoaziou.fr To: Ben Finney ben+em...@benfinney.id.au Cc: 18...@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+em...@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.
[O] bug#18870: \emsp and alignment in org clock report
Ben Finney ben+em...@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,
[O] bug#18870: \emsp and alignment in org clock report
Hello, Ben Finney b...@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
[O] bug#18870: \emsp and alignment in org clock report
On 17-Mar-2015, Nicolas Goaziou wrote: Hello, Ben Finney b...@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 b...@benfinney.id.au signature.asc Description: Digital signature
[O] bug#18870: \emsp and alignment in org clock report
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
