[O] Cannot use unknown latex back-end
Aloha all, I pulled from master this morning, refreshed Org mode, and got this error message in *Messages*: Loading /Users/dk/.emacs.d/src/org-mode/contrib/lisp/ox-koma-letter.el (source)... org-export-register-backend: Cannot use unknown latex back-end as a parent All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] [PATCH, take 2] Processing language support in Babel
Nicolas Goaziou m...@nicolasgoaziou.fr writes: 1. A patch implementing Processing programming language support in Babel. The commit message of the patch is the following: Thank you. Applied, with minor stylistic tweaks. I also removed the binding C-c C-v C-k but suggested it in the the comments. Thanks, great news! 2. File test.org, illustrating the use of Processing in Org. The HTML export of this file can be viewed at http://www.syk.fi/~jhurri/org-processing/test.html The sketches (figures) on the page will be re-initialised on page reload. Could you turn this file into an appropriate language documentation for Worg? See http://orgmode.org/worg/org-contrib/babel/languages.html. I will. All the best, Jarmo
Re: [O] Display Agenda in Reverse Order
smt Take a look at smt smtorg-agenda-sorting-strategy Will do! smt It should help you out. Once I figure out how to configure it! ;-) smt Note though that the timestamp sorting does not work on all smt agenda types, it's a known bug. OK. Thanks for your useful and prompt reply! -Kenneth
Re: [O] [bug, org] footnote-action broken with narrowed buffer
Rasmus ras...@gmx.us writes: The problem is that narrow can be time-consuming to recreate. This is why we shouldn't mess with it in the first place. Wouldn't it only find definition in the same file? If you use a popup indirect buffer narrowed to the footnote-definition in question I don't think these problems can exist. In any case, this would seem similar to the way ob handles code blocks. Good idea. I didn't thought about using org-src.el, but, albeit not perfect, it goes a long way towards avoiding these problems. I toyed a bit with that. Now C-' on a (non inline) footnote reference should edit it in a dedicated buffer. Feedback welcome. Regards,
Re: [O] [RFC] Org linting library
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Could `org-lint' return a success/fail indication, so that we could write something along in an export hook: (if (org-lint) ... continue with export ... ... stop with message or display the lint buffer ...) As well, could the buffer be hidden (or killed) if it's empty? When called non-interactively `org-lint' returns the reports, as an alist or nil, so it can be used as a predicate. Regards,
Re: [O] ob-R, problem with try/catch
Hello, Rainer M Krug r.m.k...@gmail.com writes: Possible a candidate for the new linting library for org, to mark it as an invalid argument combination Done. Do you know any other such combinations? Regards, -- Nicolas Goaziou
[O] capture contacts org-vcard
Hello, I've managed to import my contacts stored in ownCloud server (synced with my Android phone) with the help of org-vcard. Now I wonder about entering new ones? Documentation for org-contacts mentions usage of org-capture-templates which then utilises e.g. org-contacts-template-name/email etc. Now I wonder if I should still use org-contacts or it's assumed to use something else for capturing contacts along with org-vcard? Sincerely, Gour -- A person is said to be established in self-realization and is called a yogī [or mystic] when he is fully satisfied by virtue of acquired knowledge and realization.
[O] Conditional .gitignore for org-mode files
Hi all, Sorry in advance, this might be more of a git question than an org-mode question, but I thought someone on this list might know the answer. Is it possible to conditionally gitignore certain files based on files that are being tracked? What I'd like is something like the following gitignore logic: if filename.org is tracked by git: ignore filename.tex, filename.html If this isn't possible, does anyone have any nice setups for ignoring exported versions of org-mode files? Thanks, David signature.asc Description: PGP signature
[O] Tangled Latex code gives error
I'm following the Latex howto of org-mode babel. Here's the snippet from
the howto I've got in a separate .org file (see bottom of howto page):
#+LATEX_HEADER: \usepackage{tikz}
First execute the second code block, to define the convenience macro
and to set the required new variables in ob-latex.el. Then export to
HTML and to pdf to see the tree exported as an SVG image and as
embedded tikz respectively.
* Tikz test
Here's a tree, exported to both html and pdf.
#+header: :file (by-backend (html tree.svg) (t 'nil))
#+header: :imagemagick
#+header: :results (by-backend (pdf latex) (t raw))
#+header: :tangle yes
#+begin_src latex
\usetikzlibrary{trees}
\begin{tikzpicture}
\node [circle, draw, fill=red!20] at (0,0) {1}
child { node [circle, draw, fill=blue!30] {2}
child { node [circle, draw, fill=green!30] {3} }
child { node [circle, draw, fill=yellow!30] {4} }};
\end{tikzpicture}
#+end_src
* COMMENT setup
#+header: :tangle yes
#+begin_src emacs-lisp :results silent
(setq org-babel-latex-htlatex htlatex)
(defmacro by-backend (rest body)
`(case (if (boundp 'backend) (org-export-backend-name backend) nil)
,@body))
#+end_src
This doesn't really produce a .svg of the tree as advertised, but exporting
to Latex does produce it just fine.
My real confusion starts when I try to tangle the babel code blocks. The
C-c C-v t command produces two separate files just fine, a .tex and .el,
but then if I try to Run Latex on the .tex file just by itself it gives an
error. Here's what the org-mode tangle produces:
\usetikzlibrary{trees}
\begin{tikzpicture}
\node [circle, draw, fill=red!20] at (0,0) {1}
child { node [circle, draw, fill=blue!30] {2}
child { node [circle, draw, fill=green!30] {3} }
child { node [circle, draw, fill=yellow!30] {4} }};
\end{tikzpicture}
And here's the error log after I try to run it by itself in Emacs:
. . .entering extended mode
restricted \write18 enabled.
file:line:error style messages enabled.
%-line parsing enabled.
**\input prac2.tex
(./prac2.tex
./prac2.tex:2: Undefined control sequence.
l.2 \usetikzlibrary
{trees}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
Another version (from C-c `) produces this error message:
ERROR: Undefined control sequence.
--- TeX said ---
l.2 \usetikzlibrary
{trees}
--- HELP ---
TeX encountered an unknown command name. You probably misspelled the
name. If this message occurs when a LaTeX command is being processed,
the command is probably in the wrong place---for example, the error
can be produced by an \item command that's not inside a list-making
environment. The error can also be caused by a missing \documentclass
command.
What am I missing here? I'd like to be able to keep my org stuff separate
from the Latex source, which org-mode seems to do nicely. But then it has
to run properly too. . . .
LB
[O] Org-lint and #+call lines
Aloha all, Org-lint is a big help picking up an old project. Thanks Nicolas. The original patch sent to the ML ran through my old org mode file and found lots of potential problems. So, I decided to track wip-lint. Now, the linting stops with this error: , | Org linting process starting... | let: Wrong type argument: listp, :results replace org ` The *Org Lint* buffer is empty, except for the header line. Here is the offending line in the Org mode file: ,-- | #+call: r-duplicate-ids() :results replace org `-- All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] export fails with byte-code: Before first headline at position ...
Hi Joon, Joon Ro joon...@outlook.com writes: When I try to export my org files I'm getting this error. For example: byte-code: Before first headline at position 1 in buffer Blog.org2 I could not find any way to fix this - any help will be very appreciated. Could you please send us a minimal example and clear instructions on how to produce this error? I was unable to reproduce it. Thanks, Rasmus -- El Rey ha muerto. ¡Larga vida al Rey!
Re: [O] Cannot use unknown latex back-end
Hi Tom, t...@tsdye.com (Thomas S. Dye) writes: I pulled from master this morning, refreshed Org mode, and got this error message in *Messages*: Loading /Users/dk/.emacs.d/src/org-mode/contrib/lisp/ox-koma-letter.el (source)... org-export-register-backend: Cannot use unknown latex back-end as a parent Weird. I can't reproduce this here. Does it happen with emacs -q and, say, (require 'ox-koma-letter)? —Rasmus -- It was you, Jezebel, it was you
Re: [O] ob-R, problem with try/catch
Charles C. Berry ccbe...@ucsd.edu writes: Except for langs emacs-lisp, clojure, ruby, picolisp, and python `:results pp' does nothing. mathematica refers to pp but I don't get what it does - it looks like raw would be a more suitable :results format. Of course, somebody could add a pretty print routine for another language, so maybe avoid hard coding the langs. Done. I guess this would be 'low' trust? The whole check already has `low' trust anyway. For inline src block and inline babel call, `:results list' and `:results table' are invalid and throw an error in `org-babel-insert-result'. Done. Regards,
Re: [O] Error when using org-ctrl-c-ctrl-c to add tags
Hi, I'm still experiencing this bug, although with a slightly different error message. When C-c C-c on a headline, I see: org-set-tags: Wrong type argument: listp, org-tags-completion-function Compared to the original report of: apply: Wrong type argument: listp, org-tags-completion-function I'm running latest git head: Org-mode version 8.3beta (release_8.3beta-1078-gd13a2b @ /Users/mankoff/local/src/org-mode/lisp/) -k. On Mon, Apr 20, 2015 at 4:02 PM, Marc Ihm m...@ihm.name wrote: Works for me too, and probably better than my suggestion :-) best regards Marc
Re: [O] [bug, org] footnote-action broken with narrowed buffer
Nicolas Goaziou m...@nicolasgoaziou.fr writes: Good idea. I didn't thought about using org-src.el, but, albeit not perfect, it goes a long way towards avoiding these problems. I toyed a bit with that. Now C-' on a (non inline) footnote reference should edit it in a dedicated buffer. I tried it. It works nicely. I like it better than the default move to footnote. It's less of an interruption (to me) and it works consistently across narrows. Would it make sense to allow this to hook into org-footnote-action? For this, the popup buffer would also have to work with *new* footnotes. Note that new footnotes currently break the narrow, which is pretty annoying. Thanks, Rasmus -- . . . It begins of course with The Internet. A Net of Peers
Re: [O] export fails with byte-code: Before first headline at position ...
Apparently it was caused by the following custom function for org-export-before-parsing-hook that I had to remove the subtree with beameronly tag: (defun as/delete-ignored-heading (backend) (unless (equal backend 'beamer) ; remove subtree with beameronly tag (org-map-entries (lambda () (progn (org-narrow-to-subtree) (org-cut-subtree) ) ) +beameronly 'tree) ) ) (setq org-export-before-parsing-hook '(as/delete-ignored-heading)) What I did wrong to cause this error? It worked for sum subtrees but not for others. From: joon...@outlook.com To: emacs-orgmode@gnu.org Date: Sun, 26 Apr 2015 14:35:53 -0500 Subject: [O] export fails with byte-code: Before first headline at position ... Hi, When I try to export my org files I'm getting this error. For example: byte-code: Before first headline at position 1 in buffer Blog.org2 I could not find any way to fix this - any help will be very appreciated. Thank you,Joon
Re: [O] Cannot use unknown latex back-end
Rasmus ras...@gmx.us writes: Hi Tom, t...@tsdye.com (Thomas S. Dye) writes: I pulled from master this morning, refreshed Org mode, and got this error message in *Messages*: Loading /Users/dk/.emacs.d/src/org-mode/contrib/lisp/ox-koma-letter.el (source)... org-export-register-backend: Cannot use unknown latex back-end as a parent Weird. I can't reproduce this here. Does it happen with emacs -q and, say, (require 'ox-koma-letter)? I agree. Fortunately, it is weird and gone once I started emacs again. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] export fails with byte-code: Before first headline at position ...
Hi, When I try to export my org files I'm getting this error. For example: byte-code: Before first headline at position 1 in buffer Blog.org2 I could not find any way to fix this - any help will be very appreciated. Thank you,Joon
Re: [O] ob-R, problem with try/catch
On Sun, 26 Apr 2015, Nicolas Goaziou wrote: Hello, Rainer M Krug r.m.k...@gmail.com writes: Possible a candidate for the new linting library for org, to mark it as an invalid argument combination Done. Do you know any other such combinations? Except for langs emacs-lisp, clojure, ruby, picolisp, and python `:results pp' does nothing. mathematica refers to pp but I don't get what it does - it looks like raw would be a more suitable :results format. Of course, somebody could add a pretty print routine for another language, so maybe avoid hard coding the langs. I guess this would be 'low' trust? == For inline src block and inline babel call, `:results list' and `:results table' are invalid and throw an error in `org-babel-insert-result'. HTH, Chuck
Re: [O] Marking/highlighting text temporarily
Very nice start! - make comment links a different color/face (e.g. https://github.com/jkitchin/org-ref/blob/master/org-ref.el#L360) otherwise, I think item 4 is the most important one on the todo list. We are writing lots of papers this year, so this will be a really helpful tool! Eric Abrahamsen writes: Eric Abrahamsen e...@ericabrahamsen.net writes: Vikas Rawal vikasli...@agrarianresearch.org writes: On 25-Apr-2015, at 6:22 am, John Kitchin jkitc...@andrew.cmu.edu wrote: Inspired by this conversation, I hacked up this functional comment link: http://kitchingroup.cheme.cmu.edu/blog/2015/04/24/Commenting-in-org-files/ It has a custom link type that exports in html and latex, and when you click on it, it asks if you want to delete the comment. Nice. One small issue is that when I highlight a text and add comment to it, and then delete the comment, one space following the last word is removed. Also, it would be good to make the comment stand out in LaTeX (and other) exports, preferably by pushing it to the margin (so it does not move everything else). Hang on a bit, I'm wasting my afternoon expanding this... Okay, this is as far as I got today. I changed some behavior from John's implementation: when following the links, it seemed like displaying the comment text would be more useful than deleting it -- I think many of us have delete-org-link functions lying around. I also couldn't get the add-comment thing to work, as it complained when there was no region, so I changed how that works. Lastly, I spent most of my time learning how tabular list mode works, and haven't actually tested the export. Will save that for tomorrow. Otherwise, here's the introduction from the Commentary. Comments and suggestions very welcome! Provides a new link type for Org that allows you to create comments on arbitrary chunks of text. The link prefix is comment:. Add comments with `org-comment-add-comment'. Following the link will display the text of the comment in a pop-up buffer. The buffer is in special-mode, hit q to dismiss it. Call `org-comment-display-comments' to see all comments in a buffer. See the `org-comment-[backend]-export-style' options for ways to format comments in export. TODO: 1. Better export customization options. 2. What does the ODT comment XML look like? 3. More functions in the display comment buffer: copy as kill... what else? 4. More functions in the comments list buffer, to display, pop to, delete, and edit comment text. 5. Is it possible to have multi-line filled tabular list items? Long comments are not very useful if you can't see the whole thing. 5. Allow multiple comment list buffers attached to different Org buffers. 6. Maybe a minor mode for ease of manipulating comments? -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] Tangled Latex code gives error
. . . okay, I realize that a viable Latex document has many preliminary
commands. Here's a working version of my tangled code
\documentclass{article}
\usepackage{tikz}
\usetikzlibrary{trees}
\begin{document}
\begin{tikzpicture}
\node [circle, draw, fill=red!20] at (0,0) {1}
child { node [circle, draw, fill=blue!30] {2}
child { node [circle, draw, fill=green!30] {3} }
child { node [circle, draw, fill=yellow!30] {4} }};
\end{tikzpicture}
\end{document}
I guess I need to know where to begin to get the default org-mode Latex
export functionality for Latex babel tangling.
But then maybe I'm barking up the wrong tree. One of the hardest things
about learning org-mode is finding out what the best practice of
something really is.
On Sun, Apr 26, 2015 at 7:20 PM, Lawrence Bottorff borg...@gmail.com
wrote:
I'm following the Latex howto of org-mode babel. Here's the snippet from
the howto I've got in a separate .org file (see bottom of howto page):
#+LATEX_HEADER: \usepackage{tikz}
First execute the second code block, to define the convenience macro
and to set the required new variables in ob-latex.el. Then export to
HTML and to pdf to see the tree exported as an SVG image and as
embedded tikz respectively.
* Tikz test
Here's a tree, exported to both html and pdf.
#+header: :file (by-backend (html tree.svg) (t 'nil))
#+header: :imagemagick
#+header: :results (by-backend (pdf latex) (t raw))
#+header: :tangle yes
#+begin_src latex
\usetikzlibrary{trees}
\begin{tikzpicture}
\node [circle, draw, fill=red!20] at (0,0) {1}
child { node [circle, draw, fill=blue!30] {2}
child { node [circle, draw, fill=green!30] {3} }
child { node [circle, draw, fill=yellow!30] {4} }};
\end{tikzpicture}
#+end_src
* COMMENT setup
#+header: :tangle yes
#+begin_src emacs-lisp :results silent
(setq org-babel-latex-htlatex htlatex)
(defmacro by-backend (rest body)
`(case (if (boundp 'backend) (org-export-backend-name backend) nil)
,@body))
#+end_src
This doesn't really produce a .svg of the tree as advertised, but
exporting to Latex does produce it just fine.
My real confusion starts when I try to tangle the babel code blocks. The
C-c C-v t command produces two separate files just fine, a .tex and .el,
but then if I try to Run Latex on the .tex file just by itself it gives an
error. Here's what the org-mode tangle produces:
\usetikzlibrary{trees}
\begin{tikzpicture}
\node [circle, draw, fill=red!20] at (0,0) {1}
child { node [circle, draw, fill=blue!30] {2}
child { node [circle, draw, fill=green!30] {3} }
child { node [circle, draw, fill=yellow!30] {4} }};
\end{tikzpicture}
And here's the error log after I try to run it by itself in Emacs:
. . .entering extended mode
restricted \write18 enabled.
file:line:error style messages enabled.
%-line parsing enabled.
**\input prac2.tex
(./prac2.tex
./prac2.tex:2: Undefined control sequence.
l.2 \usetikzlibrary
{trees}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
Another version (from C-c `) produces this error message:
ERROR: Undefined control sequence.
--- TeX said ---
l.2 \usetikzlibrary
{trees}
--- HELP ---
TeX encountered an unknown command name. You probably misspelled the
name. If this message occurs when a LaTeX command is being processed,
the command is probably in the wrong place---for example, the error
can be produced by an \item command that's not inside a list-making
environment. The error can also be caused by a missing \documentclass
command.
What am I missing here? I'd like to be able to keep my org stuff separate
from the Latex source, which org-mode seems to do nicely. But then it has
to run properly too. . . .
LB
Re: [O] TAB cycling doesn't work from end of line
i think maybe somebody patched this? one more similar thing. if the headline is folded, and point is somewhere not in the headline, m-right etc. don't work. this is common when you yank folded, i think.
[O] custom agenda view not possible?
I'm transitioning from a web-based to-do list, and one thing I rely on is viewing recently CREATED or CLOSED tasks, e.g. within the last 2 days. My hope is to recreate this with a custom agenda view, but I haven't been able to find the correct commands/filters. Keeping in mind I'm new to Emacs/Lisp/OrgMode, here's what I've tried so far (for just the CLOSED example): This doesn't work because tags-todo excludes 'DONE' status tasks: (add-to-list 'org-agenda-custom-commands '(J Completed Recently tags-todo CLOSED=\-2d\)) This doesn't work because the org-agenda-tag-filter-preset only works for tags: (add-to-list 'org-agenda-custom-commands '(J Completed Recently todo DONE ((org-agenda-tag-filter-preset '(+CLOSED=\-2d\) Regarding the desired CREATED agenda view, I use a script to add a CREATED timestamp as property to each task (see: http://stackoverflow.com/questions/12262220/add-created-date-property-to-todos-in-org-mode ), so a task will look something like this: TODO New task for today :PROPERTIES: :CREATED: [2015-04-13 Mon 17:57] :END: There is no agenda filtering preset options for Properties (only tags/category/regexp), which is the only way I could think of to do the necessary date comparisons (e.g. -2d). The task seems simple, so I'm hopeful I'm overlooking some way of accomplishing it.
Re: [O] org-latex question
True. This is because org-latex-headline is written this way:
,
| (if (and numberedp opt-title
| ;; ^^^ ^ why this? Maybe there's a good reason...
| (not (equal opt-title full-text))
| (string-match \\`\\(.*?[^*]\\){ section-fmt))
| (...)
|;; Impossible to add an alternative heading. Fallback to
|;; regular sectioning format string.
|(format section-fmt full-text
|(concat headline-label pre-blanks contents)))
`
However, it need not be this way: LaTeX itself (or more precisely: the
default classes) seem to support the alt-title even for starred
sectioning commands.
I removed NUMBEREDP, since I cannot remember the reason for its
presence.
Sorry, it took me some time before I could get back to figure this out.
In the document (manuscript of a book) that I am working, ALT_TITLE now works
in most cases. However, ALT_TITLE does not work for headlines in Appendices,
which come after
\begin{appendices}
Just as a reminder (since these emails are several days old), we are trying to
enable ALT_TITLE in all headlines irrespective of whether they appear in TOC or
not.
So there is perhaps still a problem somewhere.
Vikas
