Re: [O] Converting a Dissertation Template from docx to .org to use for LaTeX
Paul Harper harper.pau...@gmail.com writes: he other thing is in the end I have to convert from the .tex file to a .docx file using pandoc Org exports to odt via ox-odt. You can presumably export directly to docx using org-odt-convert-processes. —Rasmus -- Together we will make the possible totay impossible!
Re: [O] Inline LaTeX formulae
Hi Titus, Titus von der Malsburg malsb...@posteo.de writes: Parentheses are punctuation, so the $ in my example should be interpreted as math delimiters. I think whoever wrote the code, simply overlooked parentheses when implementing the punctuation part. I believe the problem is complicated. In principal you could change the regexp in org-element-latex-fragment-parser to something like \\(\\s.\\|\\s-\\|\\s)\\|\\s\\\|\\s_\\) You'd only be relying on syntax tables, which I believe is what you are suggesting. But this is also dangerous, see e.g. the recent change of org-string-nw-p which previously relied on \\S cf.: http://article.gmane.org/gmane.emacs.orgmode/95473 This should be fixed. Patches welcome. You could try to submit a patch where you add closing parenthesis characters. It could even be patches to org.texi! Thanks, Rasmus -- Got mashed potatoes. Ain't got no T-Bone. No T-Bone
[O] Bug: Export to html fails when link to header in non existing file in document present WAS: Error export to html - Org-publish-cache-get: `org-publish-cache-get' called, but no cache present [8.
Hi more info and a reproducible example: when exporting the following org file --8---cut here---start-8--- * A link to a non existent file [[file:~/NONEXISTENT.org::*SOMETHING][Link to header in non existing org file]] --8---cut here---end---8--- I get the error , | Org-publish-cache-get: `org-publish-cache-get' called, but no cache present ` which goes away when I remove the header as follow: --8---cut here---start-8--- * A link to a non existent file [[file:~/NONEXISTENT.org][Link to non existing org file]] --8---cut here---end---8--- Hope this helps, Rainer Rainer M Krug rai...@krugs.de writes: Hi I don't know how long I have this error (just back at the office after two weeks away and haven't fone any html export for some time before), but even when using , | emacs -Q ` and loading the current org, I get the error when exporting to html - but not to latex. When using the build in org (8.2.10), the export works. The error is: , | Org-publish-cache-get: `org-publish-cache-get' called, but no cache present ` org and emacs version: , | GNU Emacs 24.5.1 (x86_64-apple-darwin14.3.0, Carbon Version 157 AppKit 1347.57) of 2015-04-13 on Rainers-MacBook-Pro.local | Org-mode version 8.3beta (release_8.3beta-1115-g8f3946 @ /Users/rainerkrug/.emacs.d/org-mode/lisp/) ` Any suggestions? Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug PGP: 0x0F52F982 signature.asc Description: PGP signature
[O] Bug: org-babel-ref-parse needs to set current buffer to the buffer of the marker [8.2.2 (release_8.2.2-188-gc57372 @ /home/wvxvw/Projects/org-mode/lisp/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Hello,
I've been having this problem for a while, and now I think I found its
culprit: The org-babel-ref-parse function will try to move the point in
a wrong buffer (a temporary buffer with the contents of the buffer being
exported), while doing so, it will not switch to this temporary buffer.
Below is what I did to deal with it:
(defun org-babel-ref-parse (assignment)
Parse a variable ASSIGNMENT in a header argument.
If the right hand side of the assignment has a literal value
return that value, otherwise interpret as a reference to an
external resource and find its value using
`org-babel-ref-resolve'. Return a list with two elements. The
first element of the list will be the name of the variable, and
the second will be an emacs-lisp representation of the value of
the variable.
(when (string-match org-babel-ref-split-regexp assignment)
(let ((var (match-string 1 assignment))
(ref (match-string 2 assignment)))
(cons (intern var)
(let ((out (save-excursion
(when org-babel-current-src-block-location
;; Added this line, to avoid
;; Marker points into wrong buffer error
(set-buffer (marker-buffer
org-babel-current-src-block-location))
(goto-char org-babel-current-src-block-location))
(org-babel-read ref
(if (equal out ref)
(if (string-match ^\.*\$ ref)
(read ref)
(org-babel-ref-resolve ref))
out))
Best,
Oleg
Emacs : GNU Emacs 25.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.12)
of 2015-05-03 on wvxvvw-laptop
Package: Org-mode version 8.2.2 (release_8.2.2-188-gc57372 @
/home/wvxvw/Projects/org-mode/lisp/)
current state:
==
(setq
org-export-backends '(ascii html icalendar latex man texinfo)
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-latex-classes '((djcb-org-article
\\documentclass[11pt,a4paper]{article}\n\\usepackage[T1]{fontenc}\n\\usepackage{fontspec}\n\\usepackage{graphicx}\n\\usepackage{hyperref}\n\\usepackage[normalem]{ulem}\n\\defaultfontfeatures{Mapping=tex-text}\n\\setromanfont{Gentium}\n\\setromanfont
[BoldFont={Gentium Basic Bold},\nItalicFont={Gentium Basic
Italic}]{Gentium Basic}\n\\setsansfont{Charis SIL
Compact}\n\\setmonofont[Scale=0.8]{DejaVuSansMono}\n\\usepackage{geometry}\n\\geometry{a4paper,
textwidth=6.5in, textheight=10in,\nmarginparsep=7pt,
marginparwidth=.6in}\n\\pagestyle{empty}\n\\title{}\n
[NO-DEFAULT-PACKAGES]\n [NO-PACKAGES]
(\\section{%s} . \\section*{%s}) (\\subsection{%s}
. \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})
(\\paragraph{%s} . \\paragraph*{%s})
(\\subparagraph{%s} . \\subparagraph*{%s}))
(koma-article \\documentclass{scrartcl}
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})
(\\paragraph{%s} . \\paragraph*{%s})
(\\subparagraph{%s} . \\subparagraph*{%s}))
(org-article
\\documentclass{org-article}\n
[NO-DEFAULT-PACKAGES]\n [PACKAGES]\n [EXTRA]
(\\section{%s} . \\section*{%s}) (\\subsection{%s}
. \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})
(\\paragraph{%s} . \\paragraph*{%s})
(\\subparagraph{%s} . \\subparagraph*{%s}))
(memoir
\\documentclass[oneside]{memoir}\n
[DEFAULT-PACKAGES]\n [PACKAGES]\n [EXTRA]
(\\chapter{%s} . \\chapter*{%s}) (\\section{%s} .
\\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})
(\\paragraph{%s} . \\paragraph*{%s})
(\\subparagraph{%s} . \\subparagraph*{%s}))
(article \\documentclass[11pt]{article}
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})
(\\paragraph{%s} . \\paragraph*{%s})
(\\subparagraph{%s} . \\subparagraph*{%s}))
(report \\documentclass[11pt]{report} (\\part{%s} .
\\part*{%s})
Re: [O] Bug: Export to html fails when link to header in non existing file in document present
Hi, Rainer M Krug rai...@krugs.de writes: more info and a reproducible example: when exporting the following org file * A link to a non existent file [[file:~/NONEXISTENT.org::*SOMETHING][Link to header in non existing org file]] What do you expect? Should the ::*SOMETHING-part be discarded without warning? The internal link cannot be known without the file, as it is of the form orgheadlineN where N=n+1 and n is the number of headlines prior to *Something... Though perhaps the #-construct should work, as we know the custom-id. * A link to a non existent file [[file:~/NONEXISTENT.org::#SOMETHING][Link to header in non existing org file]] —Rasmus -- Vote for proprietary math!
[O] Bug: Table alignment [8.2.10 (release_8.2.10 @ /usr/local/src/emacs/lisp/org/)]
I was trying to get table elements to align left when exported to html,
and I was having a bit of trouble doing it. I had a table entry
at the top
| l |
in the appropriate column, but that wasn't working.
When I looked at the resulting html, it looked fine:
th scope=col class=leftMath Department/th
But then I checked the css code, which is given by the value of
`org-html-style-default' in ox-html.el:
th.right { text-align: center; }
th.left { text-align: center; }
th.center { text-align: center; }
td.right { text-align: right; }
td.left { text-align: left; }
td.center { text-align: center; }
(It's this way in emacs 24.5 and the latest development version of emacs.)
Easy to change locally, but am I missing something, or should
`org-html-style-default' have
th.right { text-align: right; }
th.left { text-align: left; }
th.center { text-align: center; }
td.right { text-align: right; }
td.left { text-align: left; }
td.center { text-align: center; }
Thanks,
Jay
Emacs : GNU Emacs 25.0.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.4.2)
of 2015-05-02 on belanger-home
Package: Org-mode version 8.2.10 (release_8.2.10 @
/usr/local/src/emacs/lisp/org/)
[O] correlating positions between org-mode and export
Is there any way to correlate between the position in an org-mode buffer and an export from that buffer. So, if I have * Header With some text Exported to h1Header/h1 pWith some text/p I want do be able to match between the position of the W in with between the two buffers? Phil
Re: [O] Bug: Table alignment [8.2.10 (release_8.2.10 @ /usr/local/src/emacs/lisp/org/)]
Jay Belanger jay.p.belan...@gmail.com writes:
When I looked at the resulting html, it looked fine:
th scope=col class=leftMath Department/th
But then I checked the css code, which is given by the value of
`org-html-style-default' in ox-html.el:
th.right { text-align: center; }
th.left { text-align: center; }
th.center { text-align: center; }
td.right { text-align: right; }
td.left { text-align: left; }
td.center { text-align: center; }
Indeed that looks weird. It seems to be a stylistic hack to have
*headers* always centered. I have no clue why.
(It's this way in emacs 24.5 and the latest development version of emacs.)
Easy to change locally, but am I missing something, or should
`org-html-style-default' have
th.right { text-align: right; }
th.left { text-align: left; }
th.center { text-align: center; }
td.right { text-align: right; }
td.left { text-align: left; }
td.center { text-align: center; }
I guess it should, but I don't know the rational for the always-centering
of headers. . . If we imposed that change headlines of tables with no
instructions would no longer be centered as they default to the left
class. This could be an issue if this is a good default style...
—Rasmus
--
With monopolies the cake is a lie!
[O] Bug: org-toggle-heading breaks with double colon '::' list items.
Hello, If I have a list with colons like: - List a :: Cheese Bannana - List b :: Pineapples Tomatoes If I then select the entire list and call org-toggle-headings, then I would *expect* this: * List a Cheese Bannana * List b Pineapples Tomatoes But instead the first item is placed on the same line as the heading: * List a Cheese Bannana * List b Pineapples Tomatoes This is happens only with items that have colons. A workaround is not to use colons or add a dot after the colons, e.g - List a :: . Cheese The use case is that I often start making lists, but as things grow turn them into headings. I'm on Emacs 25.0.50.4 (~3 weeks old) and my org-mode is from this morning (8.3beta). Please advise. Thank you Leo
Re: [O] Converting a Dissertation Template from docx to .org to use for LaTeX
On 2015-05-06 at 06:28, Rasmus ras...@gmx.us wrote: Paul Harper harper.pau...@gmail.com writes: he other thing is in the end I have to convert from the .tex file to a .docx file using pandoc Org exports to odt via ox-odt. You can presumably export directly to docx using org-odt-convert-processes. Although I recommend exporting to TeX and then using Pandoc to generate the DOCX file. It seems (to me) to work better and have better support for bibliography: pandoc -f latex -t docx -o foo.docx --bibliography foo.bib foo.tex -k.
Re: [O] Bug: Export to html fails when link to header in non existing file in document present
Rainer M Krug rai...@krugs.de writes: What do you expect? Should the ::*SOMETHING-part be discarded without warning? Well - the ideal solution would be a warning (or error message) with a reference to the link. At the moment, a link to a non existing file is exported, a link to a section in a non existing produces a cryptic error message. At the moment, I have no clue how I can find the link. So I would hope for 1) consistent behavior for the two cases 2) a meaningful warning which helps to find the culprit 3) an html file, where the links do not work, but the export is fine. or, if 3) is not possible, meaningful error messages which actually help me to track down the error (I only found out what was causing this error accidentally) The issue with warnings is that I don't see them Though an error seems a bit drastic here. The attached patch inserts a link without the anchor and issues a warning if exporting such links without ox-publish. The internal link cannot be known without the file, as it is of the form orgheadlineN where N=n+1 and n is the number of headlines prior to *Something... Sure - this is obvious. Actually, the error you found is more interesting than what I first though, as any link with anchors will trigger the error, it seems. org-publish-cache must be non-nil, which seems to linger on publishing a project. —Rasmus -- Don't panic!!! From 8e1dd6c43e8a358a85a8034825c475199bd2ffb7 Mon Sep 17 00:00:00 2001 From: Rasmus ras...@gmx.us Date: Wed, 6 May 2015 15:44:26 +0200 Subject: [PATCH] ox-html: Improve links with search * ox-html.el (org-html-link): Handle links with search when not using Publish. Reported-by: Rainer M Krug rai...@krugs.de http://permalink.gmane.org/gmane.emacs.orgmode/97420 --- lisp/ox-html.el | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/lisp/ox-html.el b/lisp/ox-html.el index 6c712f6..0e69e6a 100644 --- a/lisp/ox-html.el +++ b/lisp/ox-html.el @@ -2849,12 +2849,18 @@ INFO is a plist holding contextual information. See ;; relative to a custom-id, a headline title a name, ;; a target or a radio-target. (let ((option (org-element-property :search-option link))) - (if (not option) raw-path - (concat raw-path - # - (org-publish-resolve-external-link - option - (org-element-property :path link)) + (cond ((and option org-publish-cache) + (concat raw-path + # + (org-publish-resolve-external-link + option + (org-element-property :path link + ((and option (not org-publish-cache)) + (org-display-warning + (format Link to file %s cannot be resolved. Please use Org Publish. + (org-element-property :path link))) + raw-path) + (t raw-path (t raw-path))) ;; Extract attributes from parent's paragraph. HACK: Only do ;; this for the first link in parent (inner image link for -- 2.4.0
Re: [O] Bug: Table alignment [8.2.10 (release_8.2.10 @ /usr/local/src/emacs/lisp/org/)]
Matt Price mopto...@gmail.com writes:
I guess it should, but I don't know the rational for the always-centering
of headers. . . If we imposed that change headlines of tables with no
instructions would no longer be centered as they default to the left
class. This could be an issue if this is a good default style...
Not use if this belongs in the same thread, but another potential issue
with the left and right classes is a namespace clash with external css
frameworks which use those classes to assign float values. I export to
WordPress using a zurb foundation based css framework, and my tables were
all messed up until I figured that out.
I don't know what e.g. zurb foundation means, but perhaps something like
the attached fixes your problem. It's probably a good idea not to use
generic names like left as class names anyway.
—Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
From fee51384c0384c2a4ead9b9eead109b941408db7 Mon Sep 17 00:00:00 2001
From: Rasmus ras...@gmx.us
Date: Wed, 6 May 2015 16:08:44 +0200
Subject: [PATCH 2/2] ox-html: Less generic names for table aligns.
* ox-html.el (org-html-style-default):
(org-html-table-cell, org-html-table): Prefix left, right, center classes.
Reported-by: Matt Price mopto...@gmail.com
http://permalink.gmane.org/gmane.emacs.orgmode/97431
---
lisp/ox-html.el | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/lisp/ox-html.el b/lisp/ox-html.el
index 0e69e6a..96e9f92 100644
--- a/lisp/ox-html.el
+++ b/lisp/ox-html.el
@@ -286,9 +286,9 @@ for the JavaScript code in this tag.
padding: 2px; font-size: 80%; font-weight: normal; }
.timestamp { color: #bebebe; }
.timestamp-kwd { color: #5f9ea0; }
- .right { margin-left: auto; margin-right: 0px; text-align: right; }
- .left { margin-left: 0px; margin-right: auto; text-align: left; }
- .center { margin-left: auto; margin-right: auto; text-align: center; }
+ .org-right { margin-left: auto; margin-right: 0px; text-align: right; }
+ .org-left { margin-left: 0px; margin-right: auto; text-align: left; }
+ .org-center { margin-left: auto; margin-right: auto; text-align: center; }
.underline { text-decoration: underline; }
#postamble p, #preamble p { font-size: 90%; margin: .2em; }
p.verse { margin-left: 3%; }
@@ -327,12 +327,12 @@ for the JavaScript code in this tag.
caption.t-above { caption-side: top; }
caption.t-bottom { caption-side: bottom; }
td, th { vertical-align:top; }
- th.right { text-align: center; }
- th.left { text-align: center; }
- th.center { text-align: center; }
- td.right { text-align: right; }
- td.left { text-align: left; }
- td.center { text-align: center; }
+ th.org-right { text-align: center; }
+ th.org-left { text-align: center; }
+ th.org-center { text-align: center; }
+ td.org-right { text-align: right; }
+ td.org-left { text-align: left; }
+ td.org-center { text-align: center; }
dt { font-weight: bold; }
.footpara:nth-child(2) { display: inline; }
.footpara { display: block; }
@@ -3279,7 +3279,7 @@ channel.
(if (not (plist-get info :html-table-align-individual-fields))
(format (if (and (boundp 'org-html-format-table-no-css)
org-html-format-table-no-css)
- align=\%s\ class=\%s\)
+ align=\%s\ class=\org-%s\)
(org-export-table-cell-alignment table-cell info)
(when (or (not contents) (string= (org-trim contents)))
(setq contents #xa0;))
@@ -3399,7 +3399,7 @@ contextual information.
(alignspec
(if (and (boundp 'org-html-format-table-no-css)
org-html-format-table-no-css)
- align=\%s\ class=\%s\))
+ align=\%s\ class=\org-%s\))
(table-column-specs
(function
(lambda (table info)
--
2.4.0
Re: [O] Bug: Export to html fails when link to header in non existing file in document present
Rasmus ras...@gmx.us writes: Hi, Rainer M Krug rai...@krugs.de writes: more info and a reproducible example: when exporting the following org file * A link to a non existent file [[file:~/NONEXISTENT.org::*SOMETHING][Link to header in non existing org file]] What do you expect? Should the ::*SOMETHING-part be discarded without warning? Well - the ideal solution would be a warning (or error message) with a reference to the link. At the moment, a link to a non existing file is exported, a link to a section in a non existing produces a cryptic error message. At the moment, I have no clue how I can find the link. So I would hope for 1) consistent behavior for the two cases 2) a meaningful warning which helps to find the culprit 3) an html file, where the links do not work, but the export is fine. or, if 3) is not possible, meaningful error messages which actually help me to track down the error (I only found out what was causing this error accidentally) The internal link cannot be known without the file, as it is of the form orgheadlineN where N=n+1 and n is the number of headlines prior to *Something... Sure - this is obvious. Though perhaps the #-construct should work, as we know the custom-id. * A link to a non existent file [[file:~/NONEXISTENT.org::#SOMETHING][Link to header in non existing org file]] To fix this, I have to find the link fierst... Cheers, Rainer —Rasmus -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug PGP: 0x0F52F982 signature.asc Description: PGP signature
Re: [O] Bug: Table alignment [8.2.10 (release_8.2.10 @ /usr/local/src/emacs/lisp/org/)]
On May 6, 2015 06:57, Rasmus ras...@gmx.us wrote:
Jay Belanger jay.p.belan...@gmail.com writes:
When I looked at the resulting html, it looked fine:
th scope=col class=leftMath Department/th
But then I checked the css code, which is given by the value of
`org-html-style-default' in ox-html.el:
th.right { text-align: center; }
th.left { text-align: center; }
th.center { text-align: center; }
td.right { text-align: right; }
td.left { text-align: left; }
td.center { text-align: center; }
Indeed that looks weird. It seems to be a stylistic hack to have
*headers* always centered. I have no clue why.
(It's this way in emacs 24.5 and the latest development version of
emacs.)
Easy to change locally, but am I missing something, or should
`org-html-style-default' have
th.right { text-align: right; }
th.left { text-align: left; }
th.center { text-align: center; }
td.right { text-align: right; }
td.left { text-align: left; }
td.center { text-align: center; }
I guess it should, but I don't know the rational for the always-centering
of headers. . . If we imposed that change headlines of tables with no
instructions would no longer be centered as they default to the left
class. This could be an issue if this is a good default style...
Not use if this belongs in the same thread, but another potential issue
with the left and right classes is a namespace clash with external css
frameworks which use those classes to assign float values. I export to
WordPress using a zurb foundation based css framework, and my tables were
all messed up until I figured that out.
Matt
—Rasmus
--
With monopolies the cake is a lie!
Re: [O] Bug: org-toggle-heading breaks with double colon '::' list items.
Hello, Leo Ufimtsev lufim...@redhat.com writes: If I have a list with colons like: - List a :: Cheese Bannana - List b :: Pineapples Tomatoes If I then select the entire list and call org-toggle-headings, then I would *expect* this: * List a Cheese Bannana * List b Pineapples Tomatoes But instead the first item is placed on the same line as the heading: * List a Cheese Bannana * List b Pineapples Tomatoes This should be fixed in 9aa69058bc4cbe3be088df9e96b18caf5359a3a8. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Bug: Export to html fails when link to header in non existing file in document present
Hello, Rasmus ras...@gmx.us writes: Actually, the error you found is more interesting than what I first though, as any link with anchors will trigger the error, it seems. org-publish-cache must be non-nil, which seems to linger on publishing a project. Correct. External references can only be solved using publishing. From 8e1dd6c43e8a358a85a8034825c475199bd2ffb7 Mon Sep 17 00:00:00 2001 From: Rasmus ras...@gmx.us Date: Wed, 6 May 2015 15:44:26 +0200 Subject: [PATCH] ox-html: Improve links with search * ox-html.el (org-html-link): Handle links with search when not using Publish. Thank you. However, I fixed it at ox-publish.el's level in e42c1611094a689f77f09cc66c5a50fb1e3ac7bb instead, and throw an error instead of a warning. Regards, -- Nicolas Goaziou
Re: [O] \\ in headlines
Hello, Rasmus ras...@gmx.us writes: Vikas Rawal vikasli...@agrarianresearch.org writes: Isn’t \\ in headlines expected to cause a line break? (member 'line-break (org-element-restriction 'headline)) = nil I don't know the rational. Because, in Org, line breaks can only happen at the end of line, and headlines are only 1 line long. Regards, -- Nicolas Goaziou
Re: [O] [bug, org] footnote-action broken with narrowed buffer
Rasmus ras...@gmx.us writes: I guess that's fine. Still, someone who never uses narrows may find jump better, especially for short documents. If the org-src window can be configured to show less than a fullscreen I guess I would have no concerns with this proposal. I pushed a different approach. C-c C-c still jumps to definition or throw an error if outside narrowed part of buffer. However, creating a new footnote now doesn't break narrowing and automatically switches to remote editing when not accessible. Regards,
Re: [O] \\ in headlines
On 06-May-2015, at 9:44 pm, Ken Mankoff mank...@gmail.com wrote:
Recent update means you have to put it in a macro...
#+TITLE: Foo @@latex:\\@@ Bar
Or:
#+MACRO: NEWLINE @@latex:\\@@ @@html:br@@
#+TITLE: Foo {{{NEWLINE}}} Bar
https://emacs.stackexchange.com/questions/255/new-line-in-title-of-an-org-mode-exported-html-document
This solution works for headlines as well.
Thanks.
Vikas
Re: [O] \\ in headlines
Recent update means you have to put it in a macro...
#+TITLE: Foo @@latex:\\@@ Bar
Or:
#+MACRO: NEWLINE @@latex:\\@@ @@html:br@@
#+TITLE: Foo {{{NEWLINE}}} Bar
https://emacs.stackexchange.com/questions/255/new-line-in-title-of-an-org-mode-exported-html-document
-k.
On 2015-05-06 at 07:58, Vikas Rawal vikasli...@agrarianresearch.org wrote:
Isn’t \\ in headlines expected to cause a line break?
It gets exported in LaTeX to $\backslash$
Is this intended behaviour?
Thanks,
Vikas
Re: [O] Inline LaTeX formulae
On 2015-05-06 Wed 03:24, Rasmus wrote: Hi Titus, Titus von der Malsburg malsb...@posteo.de writes: Parentheses are punctuation, so the $ in my example should be interpreted as math delimiters. I think whoever wrote the code, simply overlooked parentheses when implementing the punctuation part. I believe the problem is complicated. I had a look at the code in org-element.el (thanks for the pointer). There is clearly a bigger problem here: There is a regexp listing all characters that must follow the final $ to make it qualify as a math delimiter (whitespace, punctuation). As I suspected, the parentheses are missing from that list (and adding them solves my problem). However, a metric ton of other punctuation marks are missing as well, Spanish question marks, curly/smart quotes, real dashes (a minus is not a dash!), …, even the exclamation mark is missing. If syntax tables allow a proper solution, great. I understand that syntax tables have a different meaning in different modes but does that matter? We’re only concerned about org-mode, right? Are there scenarios where the org parser is used in a non-org-mode buffer? I also saw that the commit that introduced the problem had the following description: Avoid using slow regexp. So if the problem is only due to mistaken optimization, it would perhaps be best to just revert to the previous code. Titus In principal you could change the regexp in org-element-latex-fragment-parser to something like \\(\\s.\\|\\s-\\|\\s)\\|\\s\\\|\\s_\\) You'd only be relying on syntax tables, which I believe is what you are suggesting. But this is also dangerous, see e.g. the recent change of org-string-nw-p which previously relied on \\S cf.: http://article.gmane.org/gmane.emacs.orgmode/95473 This should be fixed. Patches welcome. You could try to submit a patch where you add closing parenthesis characters. It could even be patches to org.texi! Thanks, Rasmus signature.asc Description: PGP signature
[O] \\ in headlines
Isn’t \\ in headlines expected to cause a line break? It gets exported in LaTeX to $\backslash$ Is this intended behaviour? Thanks, Vikas
Re: [O] \\ in headlines
Vikas Rawal vikasli...@agrarianresearch.org writes: Isn’t \\ in headlines expected to cause a line break? (member 'line-break (org-element-restriction 'headline)) = nil I don't know the rational. —Rasmus -- May the Force be with you
Re: [O] Bug: HTML export ignoring CUSTOM_ID properties
Hello Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: [... 77 lines omitted ...] I hope this clarifies the purpose of the change. It does. Thank you very much for taking the time. [... 41 lines omitted ...] Are you still planning on throwing warnings or errors in the event of duplicate or invalid CUSTOM_ID's? I have implemented something related recently, but I'll comment about this in another thread. I look forward to reading it. Best, Terry -- T.F. Torrey
Re: [O] \\ in headlines
Ken Mankoff mank...@gmail.com writes:
Or:
#+MACRO: NEWLINE @@latex:\\@@ @@html:br@@
#+TITLE: Foo {{{NEWLINE}}} Bar
For some instances of foo and bar, this may be a nicer solution:
#+title: foo
#+subtitle: bar
--
. . . The proofs are technical in nature and provides no real understanding
Re: [O] Bug: Pressing TAB in table cell with CJK characters sometimes destroys proper column alignment [8.2.10 (8.2.10-dist @ /usr/share/emacs24/site-lisp/org-mode/)]
Is there a task defined for this work? I am interested in this too. Grant Rettke -- g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Mon, Apr 6, 2015 at 9:18 PM, Eric Abrahamsen e...@ericabrahamsen.net wrote: Eugen Dueck eu...@tworks.co.jp writes: In a simple org-table like the following: | | | | 漢 | | when pressing the TAB key in the bottom left cell, one space character is removed from that cell and the table thus looks like | | | | 漢 | | Pressing TAB again in that cell removes another space character | | | | 漢 | | I can repeat this until only one space remains between the Japanese character and the column separator to its right. When working on a table, navigating via TAB, over time all the CJK cells that I TABbed out of - or Shift-TABbed out of - get affected, messing up the overall table layout. Once I press C-c C-c, the formatting of the whole table gets restored, until my next TAB, but it would of course be nice if TABs didn't destroy it in the first place. Btw, org-table rocks and I use it all the time - and I hope to be able to use it with Japanese characters as well. A while ago I spent some time making this work as well as possible for double-width glyphs, but I also noticed that sometime recently it's gone back to the old behavior. I can look into it again, but work is encroaching and it might take me a little time...
