Re: [O] How to match TODO items not SCHEDULED or DEADLINE'd
Nicolas Goaziou writes: jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes: Nikolaus Rath writes: Actually, it seems it does not work for some cases. If I have a file with * TODO Item 1 * TODO Item 2 SCHEDULED: 2015-04-24 Fri * Heading ** TODO Subitem 1 ** TODO Subitem 1 SCHEDULED: 2015-04-24 Fri end do the above procedure, I'm getting * TODO Item 1 * TODO Item 2... * Heading ** TODO Subitem 1... Why is Item 2 not being hidden? That is a good question, I don't know. It fails for me as well in the org-sparse-tree, but not in the agenda. In the agenda it only shows Item 1 and Subitem 1, as it should. I had never used the sparse tree, it might by what it is supposed to do, perhaps it shows by default all entries up to a certain level. Hopefully someone can answer, if not perhaps a new thread with just that issue could serve as a bug report. If you're using development version, see `org-show-context-detail'. Thank you that answers the question, that list has (default . ancestors) in the default. Nikolaus, for the sparse trees to look like you want, probably you want to add: #+BEGIN_SRC emacs-lisp (add-to-list 'org-show-context-detail '(tags-tree . minimal)) (add-to-list 'org-show-context-detail '(occur-tree . minimal)) #+END_SRC Best, -- Jorge.
Re: [O] How to match TODO items not SCHEDULED or DEADLINE'd
Nikolaus Rath writes:
On Apr 21 2015, Nikolaus Rath nikol...@rath.org wrote:
On Apr 21 2015, jorge.alfaro-muri...@yale.edu (Jorge A.
Alfaro-Murillo) wrote:
Now, if you want to narrow the agenda (C-c a) or
org-sparse-tree (C-c /) to show TODO items not SCHEDULED or
DEADLINE'd use the key 'm' and the following match:
-SCHEDULED={.+}-DEADLINE={.+}+TODO=TODO
This, however, works perfectly, thanks a lot!
Actually, it seems it does not work for some cases. If I have a
file with
* TODO Item 1 * TODO Item 2
SCHEDULED: 2015-04-24 Fri
* Heading ** TODO Subitem 1 ** TODO Subitem 1
SCHEDULED: 2015-04-24 Fri
end do the above procedure, I'm getting
* TODO Item 1 * TODO Item 2... * Heading ** TODO Subitem 1...
Why is Item 2 not being hidden?
That is a good question, I don't know. It fails for me as well in
the org-sparse-tree, but not in the agenda. In the agenda it only
shows Item 1 and Subitem 1, as it should. I had never used the
sparse tree, it might by what it is supposed to do, perhaps it
shows by default all entries up to a certain level. Hopefully
someone can answer, if not perhaps a new thread with just that
issue could serve as a bug report.
--
Jorge.
Re: [O] New Org-HTML-theme!!
Fabrice Niessen writes: I've just published a new theme, called ReadTheOrg, on https://github.com/fniessen/org-html-themes. Thank you very much! I just tried it and it is very nice. -- Jorge.
Re: [O] Sparse tree for undated TODOs, or hierachical agenda?
Nikolaus Rath writes: Jorge A. Alfaro-Murillo writes: #+BEGIN_SRC emacs-lisp (setq org-agenda-prefix-format '((agenda . %i %-12:c%?-12t% s) (timeline . % s) (todo . %i %-12:c%-24:b) (tags . %i %-12:c) (search . %i %-12:c))) (setq org-agenda-sorting-strategy ((agenda habit-down time-up priority-down category-keep) (todo category-keep) (tags priority-down category-keep) (search category-keep))) #+END_SRC For me the second assignment fails with: Sorry, I am missing a quote for the list, the second part should be #+BEGIN_SRC emacs-lisp (setq org-agenda-sorting-strategy '((agenda habit-down time-up priority-down category-keep) (todo category-keep) (tags priority-down category-keep) (search category-keep))) #+END_SRC Best, -- Jorge.
Re: [O] How to match TODO items not SCHEDULED or DEADLINE'd
Hello,
jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:
Nikolaus Rath writes:
On Apr 21 2015, Nikolaus Rath nikol...@rath.org wrote:
On Apr 21 2015, jorge.alfaro-muri...@yale.edu (Jorge A.
Alfaro-Murillo) wrote:
Now, if you want to narrow the agenda (C-c a) or org-sparse-tree
(C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key
'm' and the following match:
-SCHEDULED={.+}-DEADLINE={.+}+TODO=TODO
This, however, works perfectly, thanks a lot!
Actually, it seems it does not work for some cases. If I have a file
with
* TODO Item 1 * TODO Item 2 SCHEDULED: 2015-04-24 Fri * Heading
** TODO Subitem 1 ** TODO Subitem 1 SCHEDULED: 2015-04-24 Fri
end do the above procedure, I'm getting
* TODO Item 1 * TODO Item 2... * Heading ** TODO Subitem 1...
Why is Item 2 not being hidden?
That is a good question, I don't know. It fails for me as well in the
org-sparse-tree, but not in the agenda. In the agenda it only shows
Item 1 and Subitem 1, as it should. I had never used the sparse tree,
it might by what it is supposed to do, perhaps it shows by default all
entries up to a certain level. Hopefully someone can answer, if not
perhaps a new thread with just that issue could serve as a bug report.
If you're using development version, see `org-show-context-detail'.
Regards,
--
Nicolas Goaziou
Re: [O] How to export an Org file to LaTeX's book class, but without parts?
On Wednesday, 22 Apr 2015 at 00:33, Marcin Borkowski wrote:
[...]
I want to export my Org file to the book class (actually, a class
similar to it, but never mind), but I want my first-level headings to
be chapters, not parts. OTOH, I don't want to modify
org-latex-classes. Is that possible, and if yes, how to achieve that?
The easiest way is, unfortunately, to modify org-latex-classes but the
modification is simply adding an element to the list:
#+begin_src emacs-lisp
(add-to-list 'org-latex-classes
'(bookwithnoparts \\documentclass{book}
(\\chapter{%s} . \\chapter*{%s})
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})))
#+end_src
or similar...
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1030-g65bbb1
[O] Publishing on Worg succeeds or fails? -- I can't say!
Hello, I tried to add a section on Worg (about the ReadTheOrg HTML theme). The Git commit was successfull, the Git push (for which I do have access on Worg) ended with an error code of 0 (hence, successfully?), but it's not visible on Worg! Any idea why? --8---cut here---start-8--- $ git push Enter passphrase for key '/cygdrive/d/Users/fni/.ssh/id_repo.or.cz_rsa': remote: From /home/worg/worg remote: * branchmaster - FETCH_HEAD remote: Merge made by recursive. remote: org-hacks.org | 21 - remote: 1 files changed, 16 insertions(+), 5 deletions(-) remote: worg publish process 24723 started at 04/22/15@11:35:23 remote: Loading 00debian-vars... remote: Loading /etc/emacs-snapshot/site-start.d/00emacs-snapshot-common.el (source)... remote: Loading /etc/emacs/site-start.d/50git-core.el (source)... remote: Loading /home/emacs/.emacs.el (source)... remote: Loading /home/emacs/.emacs-custom.el (source)... remote: Source file `/home/emacs/git/org-mode/lisp/org.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-macs.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-compat.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-emacs-lisp.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-eval.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-core.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-comint.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-exp.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-src.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-keys.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-table.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-lob.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-ref.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ob-tangle.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-entities.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-faces.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-list.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-pcomplete.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-footnote.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-macro.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ox-org.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ox.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/org-element.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ox-ascii.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ox-publish.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ox-html.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ox-icalendar.el' newer than byte-compiled file remote: Source file `/home/emacs/git/org-mode/lisp/ox-latex.el' newer than byte-compiled file remote: Emacs 24.2.50.1 remote: Loading /home/emacs/.org-timestamps/worg-org-faq.cache... remote: Source file `/home/emacs/git/org-mode/lisp/org-agenda.el' newer than byte-compiled file remote: Skipping unmodified file /home/emacs/git/worg/org-faq.org remote: Resetting org-publish-cache remote: Loading /home/emacs/.org-timestamps/worg-pages.cache... remote: Skipping unmodified file /home/emacs/git/worg/worgmap.org [...] remote: Skipping unmodified file /home/emacs/git/worg/org-info-js.org remote: Publishing file /home/emacs/git/worg/org-hacks.org using `org-html-publish-to-html' remote: Source file `/home/emacs/git/org-mode/lisp/org-table.el' newer than byte-compiled file remote: Unknown cross-reference #field-coordinates-in-formulas-transpose-table in file org-hacks.org remote: Unknown cross-reference #transpose-table in file org-hacks.org remote: Unable to resolve link org-capture remote: worg publish process 24723 exited at 04/22/15@11:35:28 To w...@orgmode.org:worg.git 4103052..2015bcd master - master $ --8---cut here---end---8--- It seems there are warnings or errors, but the status is not clear (to me). Note that all the above messages are outputted on stderr, which does not feel right, but that's how Emacs outputs messages in batch mode.
Re: [O] [RFC] Org linting library
Here's another update. I added a few more tests. If there's no more bug report or feedback, I'll simply put it in a wip-lint branch until Org 8.4 starts its development cycle. Regards, org-lint.el Description: application/emacs-lisp
Re: [O] [RFC] Org linting library
Hello Nicolas, Nicolas Goaziou wrote: Here's another update. I added a few more tests. If there's no more bug report or feedback, I'll simply put it in a wip-lint branch until Org 8.4 starts its development cycle. I'd like to enforce org-lint on all my Org docs, either in a find-file hook or before export, for example. Can't you put it in master as well? Best regards, Seb -- Sebastien Vauban
Re: [O] Publishing on Worg succeeds or fails? -- I can't say!
Hello, Fabrice Niessen fni-news-TA4HMoP+1wHrZ44/dzw...@public.gmane.org writes: I tried to add a section on Worg (about the ReadTheOrg HTML theme). The Git commit was successfull, the Git push (for which I do have access on Worg) ended with an error code of 0 (hence, successfully?), but it's not visible on Worg! The push succeeded, i.e., the .org file is probably up to date on the server. However the publishing process failed. remote: Unknown cross-reference #field-coordinates-in-formulas-transpose-table in file org-hacks.org remote: Unknown cross-reference #transpose-table in file org-hacks.org remote: Unable to resolve link org-capture remote: worg publish process 24723 exited at 04/22/15@11:35:28 To worg-ngzghnk++c5afugrpc6...@public.gmane.org:worg.git 4103052..2015bcd master - master $ It seems there are warnings or errors, but the status is not clear (to me). org-hacks.org has some invalid links, which result in an export error. You may want to fix them and republish (try to export locally first). I implemented a tool that may help you in the process. See http://permalink.gmane.org/gmane.emacs.orgmode/97082 Regards, -- Nicolas Goaziou
Re: [O] [RFC] Org linting library
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: I'd like to enforce org-lint on all my Org docs, either in a find-file hook or before export, for example. Can't you put it in master as well? No, I can't. As explained in the original post, org-lint.el requires at least Emacs 24.3 (lexical binding, pcase, tabulated-list-mode...) whereas Org 8.3 is expected to be Emacs 23 compatible. Regards,
Re: [O] Publishing on Worg succeeds or fails? -- I can't say!
Hello, Nicolas Goaziou wrote: Fabrice Niessen writes: I tried to add a section on Worg (about the ReadTheOrg HTML theme). The Git commit was successfull, the Git push (for which I do have access on Worg) ended with an error code of 0 (hence, successfully?), but it's not visible on Worg! The push succeeded, i.e., the .org file is probably up to date on the server. However the publishing process failed. Could that be stated clearly in the output? remote: Unknown cross-reference #field-coordinates-in-formulas-transpose-table in file org-hacks.org remote: Unknown cross-reference #transpose-table in file org-hacks.org remote: Unable to resolve link org-capture remote: worg publish process 24723 exited at 04/22/15@11:35:28 To w...@orgmode.org:worg.git 4103052..2015bcd master - master $ It seems there are warnings or errors, but the status is not clear (to me). org-hacks.org has some invalid links, which result in an export error. You may want to fix them and republish (try to export locally first). The thing is that I did not touch those links, as you can see in my commit. So, somehow, Org became more strict. And the fact that that file wasn't modified for some time means it wasn't re-exported for the same period; hence, the problem was never found -- until someone modifies whatever in the file... IOW, shouldn't all files be published each time, to spot such problems as soon as they become problems (because of syntax changes, for example), instead of being much later, whenever the file is changed (if it ever is)? I implemented a tool that may help you in the process. See http://permalink.gmane.org/gmane.emacs.orgmode/97082 OK, I'll see whether it can help. Thanks, Fabrice -- Fabrice Niessen Leuven, Belgium http://www.pirilampo.org/
Re: [O] Publishing on Worg succeeds or fails? -- I can't say!
Fabrice Niessen fni-news-TA4HMoP+1wHrZ44/dzw...@public.gmane.org writes: Could that be stated clearly in the output? You should ask to whom implemented Worg. The thing is that I did not touch those links, as you can see in my commit. So, somehow, Org became more strict. And the fact that that file wasn't modified for some time means it wasn't re-exported for the same period; hence, the problem was never found -- until someone modifies whatever in the file... Correct. IOW, shouldn't all files be published each time, to spot such problems as soon as they become problems (because of syntax changes, for example), instead of being much later, whenever the file is changed (if it ever is)? So you get 50-100 files to fix instead of the one you modified? IMO, it would be a waste to re-publish unmodified files. You only have to consider syntax changes when updating a file. OK, I'll see whether it can help. Note that you need to have a very recent Org (less than 7 hours) to use it. Regards,
[O] [release_8.3beta-1062-gce4e64] Error when exporting to ODT
Hello list. Just tried to export an Org file to ODT but this error appeared (taken from the Messages buffer): ... LaTeX to MathML converter not available. Formatting LaTeX using verbatim OpenDocument export failed: Assertion failed: (funcall predicate element info) Tried with a MWE and with a minimal init.el (because of org-export-backends and the odt symbol) but the error persists. Org and Emacs version: Org-mode version 8.3beta (release_8.3beta-1062-gce4e64 @ /usr/local/share/emacs/site-lisp/org/) GNU Emacs 24.5.50.1 (i686-pc-linux-gnu, GTK+ Version 3.4.2)
Re: [O] ob-R, problem with try/catch
On Wed, 22 Apr 2015, Thomas S. Dye wrote:
Aloha all,
Prior to eaa3a761dae, when working in a session, I was able to run this
R source code block without problems:
,-
| #+header: :file r/adze_wt_log.pdf
| #+header: :results output graphics
| #+header: :width 4 :height 3
| #+begin_src R
| g - ggplot(x, aes(x = weight))
| g + geom_histogram(aes(y=..density..))
## Try this:
print( g + geom_histogram(aes(y=..density..)) ) # before rm(g).
| rm(g)
| #+end_src
`-
After eaa3a761dae, I get an error and an empty output file.
That commit introduced a tryCatch() wrapper for graphics results.
You probably know that ggplot (or ggplot2) relies on printing of objects
to produce graphics (see R-FAQ 7.22).
tryCatch(expr,...) evaluates expr and returns its value, which is `rm(g)'
in your case. But `rm(g)' is not autoprinted, and you get an empty file.
I can work around this error by removing the line rm(g),
Right. Then, the expression returned by tryCatch is
g + geom_histogram(aes(y=..density..))
which is autoprinted giving the graph.
When in doubt, there is no harm in explicitly print()ing objects that
would have been autoprinted otherwise.
For reference, here is what org-babel-execute:R produces for your src
block (lightly formatted for readability):
#+BEGIN_SRC R
pdf(file=\r/adze_wt_log.pdf\,width=4,height=3)
tryCatch({
g - ggplot(x, aes(x = weight))
g + geom_histogram(aes(y=..density..))
rm(g)
},
error=function(e){
plot(x=-1:1, y=-1:1, type='n', xlab='', ylab='',
axes=FALSE)
text(x=0, y=0, labels=e$message, col='red')
paste('ERROR', e$message, sep=' : ')})
dev.off()
#+END_SRC
HTH,
Chuck
[O] ob-R, problem with try/catch
Aloha all, Prior to eaa3a761dae, when working in a session, I was able to run this R source code block without problems: ,- | #+header: :file r/adze_wt_log.pdf | #+header: :results output graphics | #+header: :width 4 :height 3 | #+begin_src R | g - ggplot(x, aes(x = weight)) | g + geom_histogram(aes(y=..density..)) | rm(g) | #+end_src `- After eaa3a761dae, I get an error and an empty output file. I can work around this error by removing the line rm(g), however, I'd like to keep the session clean and not have a bunch of variables hanging around. Is there a way to do this with ob-R.el in its current state? Or, should I adopt a different set of habits? All the best, Tom -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] ob-R, problem with try/catch
Envoyé de mon iPhone
Le 23 avr. 2015 à 04:23, Charles C. Berry ccbe...@ucsd.edu a écrit :
On Wed, 22 Apr 2015, Thomas S. Dye wrote:
Aloha all,
Prior to eaa3a761dae, when working in a session, I was able to run this
R source code block without problems:
,-
| #+header: :file r/adze_wt_log.pdf
| #+header: :results output graphics
| #+header: :width 4 :height 3
| #+begin_src R
| g - ggplot(x, aes(x = weight))
| g + geom_histogram(aes(y=..density..))
## Try this:
print( g + geom_histogram(aes(y=..density..)) ) # before rm(g).
| rm(g)
| #+end_src
`-
After eaa3a761dae, I get an error and an empty output file.
That commit introduced a tryCatch() wrapper for graphics results.
You probably know that ggplot (or ggplot2) relies on printing of objects to
produce graphics (see R-FAQ 7.22).
tryCatch(expr,...) evaluates expr and returns its value, which is `rm(g)' in
your case. But `rm(g)' is not autoprinted, and you get an empty file.
I am not in front of my computer but there must be more, as even before the
commit there should have been empty file for exactly the same reason. Also, the
error is strange. Could you send a small reproducable example, so that we can
see which error you get? Because if you get an error and an empty file, an
error must be in the tryCatcb block.
Thanks,
Rainer
I can work around this error by removing the line rm(g),
Right. Then, the expression returned by tryCatch is
g + geom_histogram(aes(y=..density..))
which is autoprinted giving the graph.
When in doubt, there is no harm in explicitly print()ing objects that would
have been autoprinted otherwise.
For reference, here is what org-babel-execute:R produces for your src block
(lightly formatted for readability):
#+BEGIN_SRC R
pdf(file=\r/adze_wt_log.pdf\,width=4,height=3)
tryCatch({
g - ggplot(x, aes(x = weight))
g + geom_histogram(aes(y=..density..))
rm(g)
},
error=function(e){
plot(x=-1:1, y=-1:1, type='n', xlab='', ylab='',
axes=FALSE)
text(x=0, y=0, labels=e$message, col='red')
paste('ERROR', e$message, sep=' : ')})
dev.off()
#+END_SRC
HTH,
Chuck
Re: [O] Publishing on Worg succeeds or fails? -- I can't say!
Nicolas Goaziou wrote: Fabrice Niessen writes: Could that be stated clearly in the output? You should ask to whom implemented Worg. And that is? Bastien? The thing is that I did not touch those links, as you can see in my commit. So, somehow, Org became more strict. And the fact that that file wasn't modified for some time means it wasn't re-exported for the same period; hence, the problem was never found -- until someone modifies whatever in the file... Correct. IOW, shouldn't all files be published each time, to spot such problems as soon as they become problems (because of syntax changes, for example), instead of being much later, whenever the file is changed (if it ever is)? So you get 50-100 files to fix instead of the one you modified? No much fun, that's right. IMO, it would be a waste to re-publish unmodified files. You only have to consider syntax changes when updating a file. OTOH, I find it uncomfortable to have a project (in the publishing sense) which is, in fact, not publishable anymore, because many files won't export anymore -- some could even still rely on Org 7... But I understand your point. The question comes down to what we want: a uniform, coherent set of Org files (all up-to-date, and exportable) or a set of HTML pages which we don't touch anymore if their Org counterpart is not touched either. Note that you need to have a very recent Org (less than 7 hours) to use it. Fixed the problems. Now that page is up-to-date on Worg again. Thanks. Best regards, Fabrice -- Fabrice Niessen Leuven, Belgium http://www.pirilampo.org/
Re: [O] How to export an Org file to LaTeX's book class, but without parts?
If you don't mind to live with part-chapter-section instead chapter-section-subsection: ---8-orgmode src8--- #+LaTeX_CLASS: book #+LaTeX_HEADER: \let\part\chapter #+LaTeX_HEADER: \let\chapter\section #+LaTeX_HEADER: \let\section\subsection ---8---end of orgmode src8--- Regards. -Original Message- From: mb...@mbork.pl Sent: Wed, 22 Apr 2015 00:33:24 +0200 To: emacs-orgmode@gnu.org Subject: [O] How to export an Org file to LaTeX's book class, but without parts? Hi all, this is an actual question, but it can be viewed as a continuation of the why use LaTeX directly and not Org thread (disclaimer: from the POV of an experienced LaTeX user and much less experienced Org-exporter user). So, I tried to do the opposite, just to learn something/unlock the Org Exporter skill;-). I want to export my Org file to the book class (actually, a class similar to it, but never mind), but I want my first-level headings to be chapters, not parts. OTOH, I don't want to modify org-latex-classes. Is that possible, and if yes, how to achieve that? TIA, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium
Re: [O] New Org-HTML-theme!!
Hello, Fabrice Niessen wrote: I've just published a new theme, called ReadTheOrg, on https://github.com/fniessen/org-html-themes. It is a clone of the great Sphinx theme used in the http://docs.readthedocs.org/en/latest/ site. It gives a beautiful and professional style to all your Org docs... Wanna test it right away? Just add the following to your Org files: #+HTML_HEAD: script src=https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js;/script #+HTML_HEAD: script src=https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js;/script #+HTML_HEAD: script type=text/javascript src=http://www.pirilampo.org/styles/readtheorg/js/readtheorg.js;/script and export... Ooops! *You need the CSS* as well, hence: --8---cut here---start-8--- #+HTML_HEAD: link rel=stylesheet type=text/css href=http://www.pirilampo.org/styles/readtheorg/css/readtheorg.css/ #+HTML_HEAD: script src=https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js;/script #+HTML_HEAD: script src=https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js;/script #+HTML_HEAD: script type=text/javascript src=http://www.pirilampo.org/styles/readtheorg/js/readtheorg.js;/script --8---cut here---end---8--- Please see the https://github.com/fniessen/org-html-themes/blob/master/demo/org-mode-syntax.org page for full examples of headings, code, admonitions, footnotes, tables and other details. Best regards, Fabrice -- Fabrice Niessen Leuven, Belgium http://www.pirilampo.org/
Re: [O] ox-latex and small caps links
Hi,
David Dynerman da...@block-party.net writes:
I've been using links to render text in small caps when exporting to
LaTeX and HTML, e.g.
[[latex:textsc][this is in small caps]]
This worked fine in 8.2.10, but causes an error in latest. When I try to
export the file to LaTeX, the export fails with:
Unable to resolve link latex:textsc
Perhaps you did not add the latex link type. You could also use a macro.
I use the following hack, which (tries to) captures words like ThIs, THIS,
or thIS and export is as \textsc{t}h\textsc{i}s, \textsc{this}, or
th\textsc{is}. It won't manage e.g. (i).
For html you need to add support for a small-caps class.
(defun rasmus/org-guess-textsc (content backend info)
Automatically downcase and wrap all-caps words in textsc.
The function is a bit slow...
TODO: Make the function work with headlines, but without doing it
on subsequent text.
TODO: Add ODT support.
(if (org-export-derived-backend-p backend 'latex 'html)
(let* (case-fold-search
(latexp (org-export-derived-backend-p backend 'latex))
(wrap (if latexp \\textsc{%s}
span class=\small-caps\%s/span)))
(replace-regexp-in-string
\\w+
(lambda (str)
(if (or (string-equal str (downcase str))
(string-equal str (capitalize str)))
str
(replace-regexp-in-string
[[:upper:]]+
(lambda (x) (format wrap (downcase x)))
str t t)))
content t t))
content))
(add-to-list 'org-export-filter-plain-text-functions
'rasmus/org-guess-textsc)
I have also found the slantsc latex package useful for emphases with small
caps.
Here's what I have used for small caps in css.
body {
font-family: Linux Libertine;
-moz-font-feature-settings:onum 1, kern 1, liga 1;
-moz-font-feature-settings:onum=1, kern=1, liga=1;
-ms-font-feature-settings:onum 1, kern 1, liga 1;
-o-font-feature-settings:onum 1, kern 1, liga 1;
-webkit-font-feature-settings:onum 1, kern 1, liga 1;
font-feature-settings:onum 1, kern 1, liga 1;}
.small-caps {
-ms-font-feature-settings: smcp;
-moz-font-feature-settings: smcp;
-webkit-font-feature-settings: smcp;
font-feature-settings: smcp;
letter-spacing:.02em;
font-variant-caps: small-caps;
text-transform: lowercase;}
Hope it helps,
Rasmus
--
I hear there's rumors on the, uh, Internets. . .
