Max Nikulin <maniku...@gmail.com> writes: >>> I still believe that >>> >>> something\\[0pt]%__ORG_EXPORT__ >>> >>> is quite safe to remove (depending on the following character) and >>> unlikely harmful if remained for some reason. >> >> What about the side effect you mentioned in a previous email? >> >>> TeX reads >>> >>> "a% comment >>> b" >>> >>> as "ab", dropping newline and starting spaces. > > Unlike in Org, in TeX "a\\b" still contains a line break. Besides exotic > packages and user setups it should just work. After all, during normal > operation all "%__ORG_EXPORT__" should be stripped by a filter. They are > just marks where a decision is necessary whether to retain "[0pt]" or to > remove it.
Thanks for the clarification. So, we can 1. Change org-latex-line-break-safe to "\\\\[0pt]%__ORG_EXPORT__", making it unique to distinguish Org-generated line breaks. 2. Establish a regexp criterion when it is safe to strip "[0pt]%__ORG_EXPORT__" from the page break (I am still unsure what will be the most reliable criteria here). If not safe, we just strip the "%__ORG_EXPORT__" part. 3. Write a filter that replaces the above from final output. Note: If we go __ORG_EXPORT__ way, it might be safe to leave the filter on by default as long as we can find a really robust criteria on when it is safe to drop [0pt] part. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
