Re: [O] org-export-preprocess-hook and the new exporter (was Re: Using Org for a dissertation)
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Eric S Fraga e.fr...@ucl.ac.uk writes: This is probably more for Nicolas... and apologies for hijacking the thread slightly! I was intrigued by the comment above regarding the ignoreheading tag. Sounded just like what I needed. However, it doesn't do anything with org /out-of-the-box/. A little searching led to Suvayu's posting in stackoverflow [1] and that does the job nicely, but only for the standard (read: old) export engine. The question is: is there an equivalent hook for the new exporter? For heavy structure modifications (like headlines removal), there is `org-export-before-parsing-hook' and the dynamically bound variable `org-export-current-backend'. Another way to solve the problem could be to implement your own headline parser: #+BEGIN_SRC emacs-lisp (defun my-e-latex-headline (headline contents info) (if (member ignoreheading (org-element-property :tags headline)) contents (org-e-latex-headline headline contents info))) #+END_SRC Then you can either install it in the current `e-latex' back-end: #+BEGIN_SRC emacs-lisp (add-to-list 'org-e-latex-translate-table '(headline . my-e-latex-headline)) #+END_SRC Nicolas, I tried this but I get: , | Warning (initialization): An error occurred while loading `/home/ucecesf/.emacs': | | Symbol's value as variable is void: org-e-latex-translate-table | | To ensure normal operation, you should investigate and remove the | cause of the error in your initialization file. Start Emacs with | the `--debug-init' option to view a complete error backtrace. ` I think it should be #+BEGIN_SRC emacs-lisp (add-to-list 'org-e-latex-translate-alist '(headline . my-e-latex-headline)) #+END_SRC i.e. =alist= instead of =table=. In any case, with this change, it works like a charm! Many thanks. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1 : using Org release_7.8.09-527-gc2aac5
[O] make fails on Windows machine
I just downloaded the latest version (version 7.8.10 - release_7.8.10-573-g7b33d9) and typed make, only to obtain the following output: [C:\emacs\site-lisp\org-mode]make == = Invoke make help for a synopsis of make targets. = = Created a default local.mk template. = = Setting oldorg as the default target.= = Please adapt local.mk to your local setup! = == make -C doc clean; make -C lisp clean; make[1]: Entering directory `/c/emacs/site-lisp/org-mode/doc' rm -f org *.pdf *.html *_letter.tex org-version.inc \ *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys *.pg *.pgs \ *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps make[1]: Leaving directory `/c/emacs/site-lisp/org-mode/doc' make[1]: Entering directory `/c/emacs/site-lisp/org-mode/lisp' rm -f org-version.el org-install.el org-version.elc org-install.elc rm -f *.elc make[1]: Leaving directory `/c/emacs/site-lisp/org-mode/lisp' make -C lisp compile make[1]: Entering directory `/c/emacs/site-lisp/org-mode/lisp' rm -f org-version.el org-install.el org-version.elc org-install.elc org-version: 7.8.10 (release_7.8.10-573-g7b33d9) Loading c:/emacs/site-lisp/org-mode/lisp/org-compat.el (source)... Loading c:/emacs/site-lisp/org-mode/UTILITIES/org-fixup.el (source)... Saving file c:/emacs/site-lisp/org-mode/lisp/org-version.el... Loading vc-git... Wrote c:/emacs/site-lisp/org-mode/lisp/org-version.el org-install: 7.8.10 (release_7.8.10-573-g7b33d9) Loading c:/emacs/site-lisp/org-mode/lisp/org-compat.el (source)... Loading c:/emacs/site-lisp/org-mode/UTILITIES/org-fixup.el (source)... Saving file c:/c/emacs/site-lisp/org-mode/lisp/org-install.el... c:/c/emacs/site-lisp/org-mode/lisp/: no such directory Makefile:30: recipe for target `org-install.el' failed make[1]: *** [org-install.el] Error 127 make[1]: Leaving directory `/c/emacs/site-lisp/org-mode/lisp' targets.mk:54: recipe for target `compile' failed make: *** [compile] Error 2 [C:\emacs\site-lisp\org-mode] I'm running Emacs 24.0.96 under Windows, and from the output above it may well also be relevant that I'm using Cygwin's version of make (+ other tools).
Re: [O] make fails on Windows machine
Richard Stanton writes: I'm running Emacs 24.0.96 under Windows, and from the output above it may well also be relevant that I'm using Cygwin's version of make (+ other tools). Install the patch in my message to Sebastien: http://lists.gnu.org/archive/html/emacs-orgmode/2012-05/msg00528.html or pull from my Makefile branch (which already has it): git remote add -t Makefile remote-tableheadings git://repo.or.cz/org-mode/org-tableheadings.git git fetch remote-tableheadings Makefile:local-Makefile git checkout local-Makefile Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Macros [was: Re: ATTR_HTML for a clickable image, howto?]
Hello,
François Pinard pin...@iro.umontreal.ca writes:
The examples in the manual do not hint either about whether newlines
are allowed or not in macro arguments.
They are not.
In fact, the manual section Macro replacement says very little, so
when I initially read it, I guessed that macros are only usable in very
simple cases. However, the last statement says that macros can be used
to construct complex HTML code. Yet, the definition method at the
beginning suggests that macro definitions have to fit on one line, and
this seriously limits the complexity of what we can do with them. So,
on initial reading, I just decided I understood nothing about
them :-).
They can build complex code since you can eval a sexp in a macro:
--8---cut here---start-8---
#+TITLE: Macro test
#+MACRO: test2 recursive $1
#+MACRO: test A {{{test2(inner)}}} macro, $1.
#+MACRO: html-builder (eval (+ $1 $2))
{{{test(and an outer one)}}}
Some complex macro {{{html-builder(1,2)}}}.
--8---cut here---end---8---
If macros are there to stay in Org, it might be worth documenting a more
complete specification about how to define and use them.
They are useful. Though, for complex code, I think Babel should be the
way to go.
Regards,
--
Nicolas Goaziou
Re: [O] org-export-preprocess-hook and the new exporter (was Re: Using Org for a dissertation)
Hello, Eric Fraga e.fr...@ucl.ac.uk writes: I think it should be #+BEGIN_SRC emacs-lisp (add-to-list 'org-e-latex-translate-alist '(headline . my-e-latex-headline)) #+END_SRC i.e. =alist= instead of =table=. Indeed, that was a typo in my message (in fact I hesitated a long time between the two names before choosing one for the variable). Regards, -- Nicolas Goaziou
Re: [O] Macros [was: Re: ATTR_HTML for a clickable image, howto?]
Hello Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
#+TITLE: Macro test
#+MACRO: test2 recursive $1
#+MACRO: test A {{{test2(inner)}}} macro, $1.
#+MACRO: html-builder (eval (+ $1 $2))
{{{test(and an outer one)}}}
Some complex macro {{{html-builder(1,2)}}}.
out of curiosity I tried to export above snippet. it is working nice except for
new exporter latex option. (org-export-dispatch and d option)
here is the back trace:
--8---cut here---start-8---
Debugger entered--Lisp error: (void-variable \1)
(+ \1 \2)
(eval (+ \1 \2))
eval((eval (+ \1 \2)))
(setq value (eval (read value)))
(progn (setq value (eval (read value
(if (string-match \\`(eval\\ value) (progn (setq value (eval (read
value)
(when (string-match \\`(eval\\ value) (setq value (eval (read value
(let* ((key (org-element-property :key macro)) (args (org-element-property
:args macro)) (value (org-export-data (plist-get info (intern (format
:macro-%s key))) info))) (let ((s 0) n) (while (string-match
\\$\\([0-9]+\\) value s) (setq s (1+ (match-beginning 0)) n (string-to-number
(match-string 1 value))) (and (= (length args) n) (setq value (replace-match
(nth (1- n) args) t t value) (when (string-match \\`(eval\\ value) (setq
value (eval (read value (format %s (or value )))
org-export-expand-macro((macro (:key html-builder :value
{{{html-builder(1,2)}}} :args (1 2) :begin 185 :end 208 :post-blank 0))
(:author Yagnesh Raghava Yakkala :creator Generated by Org mode 7.8.10 in
Emacs 24.1.50.5. :date \\today :description nil :email
yagn...@okhotsk19.lowtem.hokudai.ac.jp :exclude-tags (noexport)
:headline-levels 3 :keywords nil :language en :preserve-breaks nil
:section-numbers t :select-tags (export) :time-stamp-file t :title (Macro
test) :with-archived-trees headline :with-author t :with-clocks nil
:with-creator comment :with-drawers t :with-email nil :with-emphasize t
:with-entities t :with-fixed-width t :with-footnotes t :with-plannings nil ...))
org-e-latex-macro((macro (:key html-builder :value
{{{html-builder(1,2)}}} :args (1 2) :begin 185 :end 208 :post-blank 0))
nil (:author Yagnesh Raghava Yakkala :creator Generated by Org mode 7.8.10
in Emacs 24.1.50.5. :date \\today :description nil :email
yagn...@okhotsk19.lowtem.hokudai.ac.jp :exclude-tags (noexport)
:headline-levels 3 :keywords nil :language en :preserve-breaks nil
:section-numbers t :select-tags (export) :time-stamp-file t :title (Macro
test) :with-archived-trees headline :with-author t :with-clocks nil
:with-creator comment :with-drawers t :with-email nil :with-emphasize t
:with-entities t :with-fixed-width t :with-footnotes t :with-plannings nil ...))
funcall(org-e-latex-macro (macro (:key html-builder :value
{{{html-builder(1,2)}}} :args (1 2) :begin 185 :end 208 :post-blank 0))
nil (:author Yagnesh Raghava Yakkala :creator Generated by Org mode 7.8.10
in Emacs 24.1.50.5. :date \\today :description nil :email
yagn...@okhotsk19.lowtem.hokudai.ac.jp :exclude-tags (noexport)
:headline-levels 3 :keywords nil :language en :preserve-breaks nil
:section-numbers t :select-tags (export) :time-stamp-file t :title (Macro
test) :with-archived-trees headline :with-author t :with-clocks nil
:with-creator comment :with-drawers t :with-email nil :with-emphasize t
:with-entities t :with-fixed-width t :with-footnotes t :with-plannings nil ...))
(and (fboundp transcoder) (funcall transcoder data nil info))
(let ((transcoder (org-export-transcoder data info))) (and (fboundp
transcoder) (funcall transcoder data nil info)))
(cond ((member data (plist-get info :ignore-list)) nil) ((eq type (quote
plain-text)) (org-export-filter-apply-functions (plist-get info
:filter-plain-text) (let ((transcoder (org-export-transcoder data info))) (if
transcoder (funcall transcoder data info) data)) info)) ((not
(org-export-interpret-p data info)) (org-export-data (org-export-expand data
(mapconcat (lambda (blob) (org-export-data blob info)) (org-element-contents
data) )) info)) ((not type) (mapconcat (lambda (obj) (org-export-data obj
info)) data )) ((or (not (org-element-contents data)) (and (eq type (quote
headline)) (eq (plist-get info :with-archived-trees) (quote headline))
(org-element-property :archivedp data))) (let ((transcoder
(org-export-transcoder data info))) (and (fboundp transcoder) (funcall
transcoder data nil info (t (let ((transcoder (org-export-transcoder data
info))) (when transcoder (let* ((greaterp (memq type
org-element-greater-elements)) (objectp (and ... ...)) (contents (mapconcat ...
... ))) (funcall transcoder data (if greaterp (org-element-normalize-string
contents) contents) info))
(let* ((type (org-element-type data)) (results (cond ((member data (plist-get
info :ignore-list)) nil) ((eq type (quote plain-text))
(org-export-filter-apply-functions (plist-get info :filter-plain-text) (let
(...) (if transcoder ... data)) info)) ((not
Re: [O] installation questions
Hello Achim, Thank you for the reply, Achim Gratz strom...@nexgo.de writes: Yagnesh Raghava Yakkala writes: 1. Is the above snippet is all that is needed to load org.? The public interfaces of org should all be autoloaded, IMHO. Bastien may be able to answer why some of the interactive functions are not autoloaded (my guess is that they may need some initialization, but it may purely be an oversight). ok. 3. why is contrib folder not byte compiled with make.? It seems there is no argument for make to do this. The build system is for org core. If you want to install something from contrib, please copy the file into the lisp directory (you can try them out without byte-compilation by simply loading the files in question). Understood. I will add require in my init files for needed modules. Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు YYR
[O] Refiling Issue
Hi, I have notes from mobile.org appearing in ~/org/from-mobile.org I try to refile them under a headline in my gtd.org, which is listed as an agenda file. However, when I do C-c C-w I don't see any options for refiling other than under other headlines in the from-mobile.org. The relevant sections of my .emacs file are: '(org-agenda-files (quote (~/Dropbox/GTD/gtd.org))) (setq org-refile-targets (quote ((nil :maxlevel . 9) (org-agenda-files :maxlevel . 9 (setq org-refile-use-outline-path t) (setq org-outline-path-complete-in-steps nil) (setq org-refile-allow-creating-parent-nodes (quote confirm)) (setq org-completion-use-ido t) (setq ido-everywhere t) (setq ido-max-directory-size 10) (ido-mode (quote both)) Any idea what I am doing wrong? S.
Re: [O] Opening an odt file - problem solved
So if want to be able to open odt files created with orgmode odt exporter you have to have nxml-auto-insert-xml-declaration-flag set to nil. Thanks for writing this down. It seems you aren't insisting on a fix. So I will keep things as they are now. --
[O] Outline structure and LaTeX
I'm preparing an academic document with several chapters. The text will eventually exist as a LaTeX document. However, I am doing my early planning and writing directly in an org file, making use of the structure elements (*, **, ***, etc) to provide structure and entering text for the relevant sections in the appropriate place. Org is a huge project and I have not explored every aspect and every contributed extension. Is there a best practice approach for what I am doing? Should I write directly in LaTeX rather? Is there an easy conversion process from an outlined document to LaTeX? I know there org can export to LaTeX. Would that be the best option? It has not worked well for me previously -- page breaks appeared in the wrong place and other pages has text that flowed over the end of the page.
Re: [O] Macros [was: Re: ATTR_HTML for a clickable image, howto?]
Hello,
Yagnesh Raghava Yakkala yagn...@live.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
#+TITLE: Macro test
#+MACRO: test2 recursive $1
#+MACRO: test A {{{test2(inner)}}} macro, $1.
#+MACRO: html-builder (eval (+ $1 $2))
{{{test(and an outer one)}}}
Some complex macro {{{html-builder(1,2)}}}.
out of curiosity I tried to export above snippet. it is working nice except
for
new exporter latex option. (org-export-dispatch and d option)
You're right. I was protecting dollar signs before replacing arguments.
This should be fixed in master.
Thank you for the report.
Regards,
--
Nicolas Goaziou
Re: [O] Refiling Issue
Aha, On Sun, May 20, 2012 at 10:56 AM, Stephen Nelson-Smith sanel...@gmail.com wrote: '(org-agenda-files (quote (~/Dropbox/GTD/gtd.org))) I think this should be (setq org-agenda-files ...) S.
[O] A custom agenda view for archivable non-project tasks?
Hi - I am trying to implement the following but I am not really getting anywhere. I want to have a block in a custom agenda that lists all archivable tasks, where archivable means in any of done states and not in a project. In my system projects are subtrees that have 'project' tag associated with them. This tag is non-inheritable and I'd rather keep it that way. So I would like to have a way to list all items in a done state where there is no 'project' tag on it nor in any of its (indirect) parents. Alternatively listing archivable projects too would work (these would be defined as all subitems in a done state - not necessarily the project itself in a done state), as long as its subitems are not listed, but that sounds more complex. TIA for any pointers to the right direction, -- Laurynas
[O] new latex exporter questions
Hello Nicolas, I am trying out new exporter, I have file local variables like this --8---cut here---start-8--- # Local Variables: # org-latex-to-pdf-process: (pdflatex -interaction nonstopmode %b /usr/bin/bibtex %b pdflatex -interaction nonstopmode %b pdflatex -interaction nonstopmode %b) # reftex-default-bibliography: (/home/yagnesh/git/bib/) # eval: (reftex-mode 1) # org-inlinetask-export: nil # org-e-latex-pdf-process: (pdflatex -interaction nonstopmode %b /usr/bin/bibtex %b pdflatex -interaction nonstopmode %b pdflatex -interaction nonstopmode %b) # org-e-latex-format-inlinetask-function: (lambda nil ) # End: --8---cut here---end---8--- - old exporter is running fine pdf processes fine, I get the citations and bibliography. but new exporter is failing to export bibliography. I was not sure how to debug this. - new exportor asking for confirmation every time I re export to latex. how can I stop that.? --8---cut here---start-8--- paper.tex changed on disk; really edit the buffer? (y, n, r or C-h) --8---cut here---end---8--- - I bound few variables using #+BIND:. exporter randomly asking for safety confirmation about binding. ( I don't know why it is random) - Inline tasks., how can i stop exporting inline tasks.? you can see above I tried to define `org-e-latex-format-inlinetask-function' and its not working. Thank you very much. -- ఎందరో మహానుభావులు అందరికి వందనములు YYR
Re: [O] Org-mode repeating tasks issue
On Sat, May 19, 2012 at 7:41 PM, c b 24x7x...@gmail.com wrote: Hi, I have been using org-mode with emacs(23) for about a year now and love it. However, sometime in the last couple of weeks, I did a git pull on the master branch (and I redid the same today) and noticed that my recurring tasks are broken. E.g. I have a task ** TODO Pay Creditcard bill DEADLINE: 2012-05-15 Tue +1m -7d and when I marked it done, it changed state to DONE ** DONE Pay Creditcard bill CLOSED: [2012-05-18 Fri 22:13] DEADLINE: 2012-05-15 Tue +1m -7d I have been trying to figure out what went wrong, but am clueless. Any pointers on what might be wrong, would be appreaciated. I don't use this much, but have been contemplating it and thus the various org-mode pages on repeating tasks are somewhat fresh in my head. Here was my initial thought: - The org-mode manual itself on repeated tasks does not mention that kind of repeating task syntax --- http://orgmode.org/manual/Repeated-tasks.html#Repeated-tasks --- Only +1, ++1, and .+1 are discussed - The /org-habit/ page, on the other hand, does mention such syntax (well, kind of) --- http://orgmode.org/manual/Tracking-your-habits.html --- Note that this page uses .+2d/4d syntax Anyway, I very likely missed something, but I can't find the specific syntax you're looking for in the manual sections above. If the functionality of org-habit /does/ do what you want, perhaps you could switch to that? If you use this syntax widely, that could be a pain. Let me know what you think? Also, please point to the documentation illustrating the +1m -7d usage. I'd like to see it as well as I'm curious about the various time stamp options. Thanks! John The org-todo-repeat-to-state variable in my setup is not set (i.e. it is the default) Thanks, c.b
[O] Language identifiers
Hello, Org people. Seeing again the (org) Languages node in the manual, I decided to check all my #+BEGIN_SRC for language tags, which I too often improvise, for normalizing them. I noticed a few things, and wonder if the manual should be amended, or if I should change my habits instead. - I was using lower case c and r, while the manual suggests upper case C and R instead. Both seem to work (in Emacs at least). Should the manual be amended to say that case does not matter? If then, should the manual stick uniformly to lower case? - The identifier in the left column did not work, but if I change it to the identifier in the right column, the content highlights (in Emacs). The manual does not list it. | config | conf | | email | mail | | make | makefile | | postscript | ps | - I was using elisp instead of emacs-lisp and javascript instead of js. Both seem to work (in Emacs at least). If there are many alternate languages identifiers for a language, should the manual list all acceptable identifiers? - Tag xml seems to work nicely (within Emacs). The manual does not list it. I wonder what are supported really means, in the first sentence. Maybe the fact that Emacs supports a language tag does not mean that Org supports it? Maybe exporters would fail to render them nicely? Maybe a few more words could be added to the page for explaining what users should expect, or not expect. Currently, I do not know whether if the list is missing a few identifiers, or if I'm not using them properly. Other tiny details about the table at the beginning of this Info page. It would be clearer if there was a separating line between the title line and the table contents. A vertical line separating both halves would be welcome too, one has to take a few seconds to understand that this is a two column table, each column itself holding two columns. Finally, the sorted entries are presented row wise in this two column table; the table would be easier to consult if the sorted entries were presented column wise instead. François
Re: [O] new latex exporter questions
Hello, Yagnesh Raghava Yakkala h...@yagnesh.org writes: I have file local variables like this # Local Variables: # org-latex-to-pdf-process: (pdflatex -interaction nonstopmode %b /usr/bin/bibtex %b pdflatex -interaction nonstopmode %b pdflatex -interaction nonstopmode %b) # reftex-default-bibliography: (/home/yagnesh/git/bib/) # eval: (reftex-mode 1) # org-inlinetask-export: nil # org-e-latex-pdf-process: (pdflatex -interaction nonstopmode %b /usr/bin/bibtex %b pdflatex -interaction nonstopmode %b pdflatex -interaction nonstopmode %b) # org-e-latex-format-inlinetask-function: (lambda nil ) # End: - old exporter is running fine pdf processes fine, I get the citations and bibliography. but new exporter is failing to export bibliography. I was not sure how to debug this. I'm not sure about it. Could you provide an ECM for that? Also, is the LaTeX code produced by the exporter (with 'L') correct? - new exportor asking for confirmation every time I re export to latex. how can I stop that.? --8---cut here---start-8--- paper.tex changed on disk; really edit the buffer? (y, n, r or C-h) --8---cut here---end---8--- I don't have that behaviour here. Maybe that's something in your config? - I bound few variables using #+BIND:. exporter randomly asking for safety confirmation about binding. ( I don't know why it is random) It should ask only once, the first time you export the buffer. Doesn't it? Anyway, you can customize `org-export-allow-BIND' to change this. - Inline tasks., how can i stop exporting inline tasks.? you can see above I tried to define `org-e-latex-format-inlinetask-function' and its not working. Your `org-e-latex-format-inlinetask-function' is ill-defined (wrong number of arguments). You can try: #+begin_src emacs-lisp # org-e-latex-format-inlinetask-function: (lambda (rest args) ) #+end_src or #+begin_src emacs-lisp # org-e-latex-format-inlinetask-function: ignore #+end_src or #+begin_src emacs-lisp #+BIND: org-e-latex-format-inlinetask-function ignore #+end_src You can also use filters to never export inlinetasks in e-latex bac-kend: #+begin_src emacs-lisp (defun my-ignore-inlinetask-filter (inlinetask backend info) (unless (eq back-end 'e-latex) inlinetask)) (add-to-list 'org-export-filter-inlinetask-functions 'my-ignore-inlinetask-filter) #+end_src Eventually, you can disable inlinetasks in _every_ back-end with: #+begin_src emacs-lisp (add-to-list 'org-export-filter-inlinetask-functions 'ignore) #+end_src Note that, in any case, `org-inlinetask-export' is ignored on purpose: there are already enough (and more consistent) ways to do it. Regards, -- Nicolas Goaziou
Re: [O] Language identifiers
Aloha François, François Pinard pin...@iro.umontreal.ca writes: Hello, Org people. Seeing again the (org) Languages node in the manual, I decided to check all my #+BEGIN_SRC for language tags, which I too often improvise, for normalizing them. I noticed a few things, and wonder if the manual should be amended, or if I should change my habits instead. - I was using lower case c and r, while the manual suggests upper case C and R instead. Both seem to work (in Emacs at least). Should the manual be amended to say that case does not matter? If then, should the manual stick uniformly to lower case? - The identifier in the left column did not work, but if I change it to the identifier in the right column, the content highlights (in Emacs). The manual does not list it. | config | conf | | email | mail | | make | makefile | | postscript | ps | The core Babel functions (viewing, export, tangling, etc…) are language agnostic and will work even for languages that are not explicitly supported. Explicit language-specific support is required only for evaluation of code blocks in a language. See http://orgmode.org/worg/org-contrib/babel/languages.html. - I was using elisp instead of emacs-lisp and javascript instead of js. Both seem to work (in Emacs at least). If there are many alternate languages identifiers for a language, should the manual list all acceptable identifiers? - Tag xml seems to work nicely (within Emacs). The manual does not list it. I wonder what are supported really means, in the first sentence. Maybe the fact that Emacs supports a language tag does not mean that Org supports it? Maybe exporters would fail to render them nicely? Maybe a few more words could be added to the page for explaining what users should expect, or not expect. Currently, I do not know whether if the list is missing a few identifiers, or if I'm not using them properly. See above. Suggested revisions to the sentence are welcome. I believe I wrote the sentence, but Eric S. will review and decide whether or not to make changes. Other tiny details about the table at the beginning of this Info page. It would be clearer if there was a separating line between the title line and the table contents. A vertical line separating both halves would be welcome too, one has to take a few seconds to understand that this is a two column table, each column itself holding two columns. Finally, the sorted entries are presented row wise in this two column table; the table would be easier to consult if the sorted entries were presented column wise instead. I totally agree. Do you know how to do this in texinfo? Can you propose a patch? All the best, Tom François -- Thomas S. Dye http://www.tsdye.com
Re: [O] Outline structure and LaTeX
Aloha SW, SW sabrewo...@gmail.com writes: I'm preparing an academic document with several chapters. The text will eventually exist as a LaTeX document. However, I am doing my early planning and writing directly in an org file, making use of the structure elements (*, **, ***, etc) to provide structure and entering text for the relevant sections in the appropriate place. Org is a huge project and I have not explored every aspect and every contributed extension. Is there a best practice approach for what I am doing? Should I write directly in LaTeX rather? Is there an easy conversion process from an outlined document to LaTeX? I know there org can export to LaTeX. Would that be the best option? It has not worked well for me previously -- page breaks appeared in the wrong place and other pages has text that flowed over the end of the page. Org mode can export to various formats. Export to LaTeX works well, but it helps to know LaTeX when something unwanted happens. One of the other export options might better suit your needs. There are some examples of academic documents prepared with Org mode that might help you follow the LaTeX export path, e.g. http://www.jstatsoft.org/v46/i03, http://orgmode.org/worg/org-contrib/babel/uses.html#sec-6. hth, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] new latex exporter questions
Hello,
Nicolas Goaziou n.goaz...@gmail.com writes:
- old exporter is running fine pdf processes fine, I get the citations and
bibliography. but new exporter is failing to export bibliography. I was not
sure how to debug this.
I'm not sure about it. Could you provide an ECM for that? Also, is the
LaTeX code produced by the exporter (with 'L') correct?
It turns out I have an ARCHIVE tag for the bibliography node which is stopping
bib snippet in the exported tex file.
--8---cut here---start-8---
* bibliography :ignoreheading:ARCHIVE:
\bibliographystyle{plain}
\bibliography{cld}
# blabla
--8---cut here---end---8---
I used your suggestion about ignoreheading from the other
discussion[1]. ARCHIVE tag is just to keep that node close while cycling.
now I set `org-export-with-archived-trees' to `t' and working fine. Thanks.
--8---cut here---start-8---
paper.tex changed on disk; really edit the buffer? (y, n, r or C-h)
--8---cut here---end---8---
I don't have that behaviour here. Maybe that's something in your config?
Could be. I will report to you I can create a ECM for this.
- Inline tasks., how can i stop exporting inline tasks.? you can see
above I tried to define `org-e-latex-format-inlinetask-function' and its
not
working.
Your `org-e-latex-format-inlinetask-function' is ill-defined (wrong
number of arguments).
True. your suggestions are working very well. Thanks again.
Footnotes:
[1] http://article.gmane.org/gmane.emacs.orgmode/55972
--
ఎందరో మహానుభావులు అందరికి వందనములు
YYR
[O] Simple git synchronization script
Dear org-moders, I have googled a lot for synchronization scripts but found nothing that fits my (perceived) requirements. So I cooked something up and today took the time polish it for a broader audience. It got some 6 months of testing, albeit not in its current form. As org-mode is my primary use case for it, I figured I'd share this here. https://github.com/simonthum/git-sync Unlike other scripts, it is lean but does not try to hide git from you. Let me know what you think! Cheers, Simon
Re: [O] Language identifiers
t...@tsdye.com (Thomas S. Dye) writes: Aloha François, :-) Do you know how to do this in texinfo? If I had to do this, I would search around to see if there is an Org to Texinfo exporter, and then blindly / fully rely on it to do various wonders automatically! ;-) I did not check, but presume that the current manual original is directly written in Texinfo? More seriously, I did not write Texinfo in a lot of years, and do not even remember how we do tables with it. Tables might have been added after my time, I'm not sure. What I would likely do, given the problem, is merely to format the table myself in fixed font, and use @example / @end example around it (if I remember well, @example generates pre). Would that be acceptable? I could offer that simple formatting if it could help, I presume it is likely a simple job for anybody. The problem for me is rather to know what contents should go in there. Write to me privately if you think I could be more of an help than a burden. :-) François
Re: [O] Language identifiers
François Pinard pin...@iro.umontreal.ca wrote: If I had to do this, I would search around to see if there is an Org to Texinfo exporter, and then blindly / fully rely on it to do various wonders automatically! ;-) I did not check, but presume that the current manual original is directly written in Texinfo? That's correct: that's a requirement for being an official emacs package I believe. More seriously, I did not write Texinfo in a lot of years, and do not even remember how we do tables with it. Tables might have been added after my time, I'm not sure. What I would likely do, given the problem, is merely to format the table myself in fixed font, and use @example / @end example around it (if I remember well, @example generates pre). Would that be acceptable? I could offer that simple formatting if it could help, I presume it is likely a simple job for anybody. The problem for me is rather to know what contents should go in there. Write to me privately if you think I could be more of an help than a burden. :-) You don't really need to know texinfo: just look at relevant place(s) in doc/org.texi, and munge it until it does what you want :-) Nick
[O] #+LABEL and CUSTOM_ID with reftex
Hello all., is it possible to make reftex to recongise CUSTOM_ID and #+LABEL.? I tried to modify `reftex-label-alist' with no success. did anybody try that.? other related question., do we have in buffer completion support for cross references.? I mean it would be good if C-c C-l can show link targets with in the buffer. Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు YYR
Re: [O] fast todo kw / - x
On Sat May 19 21:35:28 2012, Samuel Wales wrote: NEXTKA below is selected by x instead of /, which is surprising. Perhaps it's worth documenting the allowable keys? (setf org-todo-keywords '((type REF(e) NAKA(i) META(=) GOAL(G) QUESTION(Q) NOTE(O) TELL(+) ASK(?) EXPECT(E!) SUGU(g) CHUU(h!) ONGOING(o) WHENEVER(r) WHEN(W) STARTED(R) NEXT(n) NEXTKA(/) | MOSTKA(L) MOST(M) DONEKA(k) DONE(d) DUPLICATEKA(u) DUPLICATE(D) MOOTKA(K) MOOT(m) WAKARANAI(a) ASSERT(X Samuel, I definitely think that this is an omission in the doc. The doc for `org-todo-keywords' ascribes meaning to at (@), slash (/), bang (!), and at least close paren ()). I would think that the quick keywords should be limited to word characters as defined by [[info:elisp#Char%20Classes][info:elisp#Char Classes]]. I bet if you provide suggested rewording for variable and info that someone on this will push it into the doc. Neil Smithline http://www.neilsmithline.com Proud GNU Emacs user since 1986, v. 18.24.
Re: [O] Minimal overhead Org-mode blogging system
First, the only way to learn is to do. That said, I do understand that RL gets in the way of fun. Regarding the implementation, if you skip the index system, which is definitely an elegant solution, and modify my symbolic link solution for agendas to keep track of files with blog entries. The symlink solution is only a pseudo index and is not automated, but it is trivial to use. Just replace every use of the word agenda in my code to blog and then bind `org-add-blog-file' to some convenient key sequence. Then use selective exporting ([[info:elisp#Char%20Classes][info:elisp#Char Classes]]) when publishing your blog. You would assign `org-export-select-tags' to a tag like :blog:. Then you just need to define a custom export function to change the value of `org-export-select-tags'. I just cobbled it together (that's secret code for haven't tested) the custom export function at https://gist.github.com/2759661. I think that should get you most of the way. Neil Smithline http://www.neilsmithline.com Proud GNU Emacs user since 1986, v. 18.24. On Wed May 16 05:51:33 2012, Jude DaShiell wrote: I don't know enough lisp to implement this indexing system. On Tue, 15 May 2012, Neil Smithline wrote: I like your indexing idea. I use a less-complex system involving symbolic links for my agenda files. Yours sounds better. This is what I use for my agendas: (setq org-agenda-files (list (expand-file-name ~/Documents/+OrgAgendas))) (defun org-add-agenda-file () (interactive) (make-symbolic-link (buffer-file-name) ~/Documents/+OrgAgendas)) It is just a quick-and-dirty solution. If I remove or move a file, I get errors. Also, if I stop using a file for agenda items I must manually unlink the symlink. Have you implemented your indexing system Jude or just designed it? I'd love to see it if you have something working. I imagine it could be used for todos, cross-referencing tags, properties, etc... And to prevent Carsten from yelling at me :-D, I would insist that, by default, Emacs would not create the cross-referencing database. You'd have to explicitly enable it. Neil On Mon May 14 22:24:08 2012, Jude DaShiell wrote: Understand, I use update here in the sense of some file modification that subsequently gets saved. If files to be modified get archived into org-mode's revision control system, the blog tag and associated done tag could be searched for within the save process and an org database could build with file name and then tripplets of date stamp, line number for blog tag, line number for done tag and each tripplet would hold another blog entry in that unique file which is the first field in the data base. So you want to find a blog entry? Search the org-generated data base for a date stamp and you come up with the file and the range of line numbers holding that blog entry. Search one file and go to specific location in second file. That if it's done or gets done will keep file searching to a nice minimum permanently. On Sun, 13 May 2012, Neil Smithline wrote: Karl Voit devnull at Karl-Voit.at writes: Therefore I sat down and thought about a workflow that should be enough for writing simple weblog entries: - create an Org-mode heading (anywhere!) - make sure that there is an (uniq) :ID: property - add the tag :blog: to heading - write content, subheadings, ... - change state of top-heading to DONE - this enables blog entries ?in the queue? - (manually) invoke generation-script This enables me quick blogging with a list of advantages: - a blog entry can be located anywhere in all of my Orgmode files - no extra formatting steps - very small (almost non-existent) overhead to create a blog entry - no duplicate information - updates only in Orgmode, not HTML or any in-between format - static (fast) pages - self-hosting without any fancy services behind like RDBS Karl, I'm wondering if you've played around with this at all? I happen to really like the idea but I wonder about its performance. Unless I'm mistaken, and I very likely may be, won't you have to scan all of your .org files to look for the special tags/properties/todo states/whatever? If not, I'd love to have a pointer to how you can accomplish this without scanning every .org file. That would be cool. Jude jdashiel-at-shellworld-dot-net http://www.shellworld.net/~jdashiel/nj.html Jude jdashiel-at-shellworld-dot-net http://www.shellworld.net/~jdashiel/nj.html
[O] [FEATURE PROPOSAL]
Since falling in love with Org projects, I've run into one snag that I don't know how to handle with the current features. I want to be able to run org-export-project (\C-c\C-ep) from any file in a directory or sub-directory. Even if that file is not actually exported. In fact, I'd like to be able to export from a shell. For example, assume I have a directory myproject with sub-directories source, output, and tools. The files in source are exported to output. The files in tools and any other files in myproject don't get exported. Given the above example, I want to be able to run org-export-project from any file, shell buffer, dired buffer, or whatever, that is in myprojects directory subtree. New project type definition: '(myproject-root ;; While :publishing-directory is must be present to make ;; org-mode work: ;; `:base-directory' ;; `:recursive' ;; `:catch-all-project' ;; are the only ones used. :catch-all-project is a boolean. ;; When non-nil it will tell org-mode to use files in this ;; subtree to trigger exporting of a parent project :base-directory~/myproject :catch-all-project t :publishing-directory ~/myproject :recursive t ) Root project definition: '(myproject (:components myproject-source myproject-root)) The only thing that myproject-root does is enable org-mode to identify that a file is in the myproject meta-project. Thoughts? Neil -- Neil Smithline http://www.neilsmithline.com Proud GNU Emacs user since 1986, v. 18.24.
Re: [O] README.org on github
I've been looking at this too. I go with Bastien. Work with me to improve org-ruby gem or export to HTML before pushing to Git. Neil Smithline http://www.neilsmithline.com Proud GNU Emacs user since 1986, v. 18.24. On Sun May 20 00:03:12 2012, François Pinard wrote: Rainer M Krug r.m.k...@gmail.com writes: I would like to use a README.org file on github, and also include code blocks in the README.org - is this possible? Hi, Rainer. I'm not sure I'm really replying to your request, but nevertheless hope my comments might be useful. Having recently had a similar need, I gave into the following compromise: I push README.md (in Markdown format) on GitHub, but maintain my real sources as README.org (well, under a different name) at home. Directly quoting from the README.md file on GitHub: I currently much enjoy Org format for handling my own notes, and do not feel like switching to Markdown for original sources. So, README.md gets derived automatically from the Org source. Some of my Org notes are private, and even for the public ones, there are :noexport: sections. Because of these private parts, I do not make my Org sources directly available. Nodemacs.org becomes an HTML file through the Org publishing feature, and that HTML file is later turned into a Markdown file using the impressive Pandoc tool. Climbing from generated HTML back to the structural intent is not a trivial job in my opinion. Not only Pandoc did it well, it was blazing fast at it. Moreover, as it is written in Haskell, it scratches on my prejudice of Haskell being essentially an academical language! Pandoc is an installable package on the Ubuntu system I use, so very easy to install. To use, I added a Makefile containing: --8---cut here---start-8--- # Internal goals README.md: ~/fp/web/notes/Nodemacs.html pandoc -o $@ $^ --8---cut here---end---8--- to the project. The script which regularly synchronizes my projects from home to GitHub executes make in each project before pushing, this ensures for this one that README.md is up to date. I did not experiment with code blocks however, and cannot say how well or bad it works. François P.S. - Before Pandoc, I tried w3m -dump, which yielded something a little too flat for my taste. I also tried the generic exporter with Markdown parametrization, which did not produce a usable enough result.
[O] [bug?] new latex exporter failing to export
Hello,
I am getting following backtrace when exporting a file to latex (beamer
presentation). where as old exporter is working fine.
--8---cut here---start-8---
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match(^[ ]*\\[\\(NO-\\)?DEFAULT-PACKAGES\\][ ]*\n? nil)
org-splice-latex-header(nil ((AUTO inputenc t) (T1 fontenc t) (
fixltx2e nil) ( graphicx t) ( longtable nil) ( float nil) (
wrapfig nil) ( soul t) ( textcomp t) ( marvosym t) ( wasysym
t) ( latexsym t) ( amssymb t) ( hyperref nil) \\tolerance=1000)
nil nil nil)
(org-e-latex--guess-inputenc (org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra)))
(let* ((header (nth 1 (assoc class org-e-latex-classes)))
(document-class-string (and (stringp header) (if class-options
(replace-regexp-in-string ^[]*documentclass\\(\\[.*?\\]\\)
class-options header t nil 1) header (org-e-latex--guess-inputenc
(org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra
(org-element-normalize-string (let* ((header (nth 1 (assoc class
org-e-latex-classes))) (document-class-string (and (stringp header) (if
class-options (replace-regexp-in-string ^[
]*documentclass\\(\\[.*?\\]\\) class-options header t nil 1) header
(org-e-latex--guess-inputenc (org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra)
(let ((class (plist-get info :latex-class)) (class-options (plist-get info
:latex-class-options))) (org-element-normalize-string (let* ((header (nth 1
(assoc class org-e-latex-classes))) (document-class-string (and (stringp
header) (if class-options (replace-regexp-in-string ^[
]*documentclass\\(\\[.*?\\]\\) class-options header t nil 1) header
(org-e-latex--guess-inputenc (org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra))
(concat (and (plist-get info :time-stamp-file) (format-time-string %%
Created %Y-%m-%d %a %H:%M\n)) (let ((class (plist-get info :latex-class))
(class-options (plist-get info :latex-class-options)))
(org-element-normalize-string (let* ((header (nth 1 (assoc class
org-e-latex-classes))) (document-class-string (and (stringp header) (if
class-options ... header (org-e-latex--guess-inputenc
(org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra))
\\providecommand{\\alert}[1]{\\textbf{#1}}\n (let ((sec-num (plist-get info
:section-numbers))) (when (integerp sec-num) (format
\\setcounter{secnumdepth}{%d}\n sec-num))) (let ((author (and (plist-get info
:with-author) (let ((auth ...)) (and auth (org-export-data auth info)
(email (and (plist-get info :with-email) (org-export-data (plist-get info
:email) info (cond ((and author email (not (string= email))) (format
\\author{%s\\thanks{%s}}\n author email)) (author (format \\author{%s}\n
author)) (t \\author{}\n))) (let ((date (plist-get info :date))) (and date
(format \\date{%s}\n date))) (format \\title{%s}\n title) (format
\\hypersetup{\n pdfkeywords={%s},\n pdfsubject={%s},\n pdfcreator={%s}}\n
(or (plist-get info :keywords) ) (or (plist-get info :description) ) (if
(not (plist-get info :with-creator)) (plist-get info :creator)))
\\begin{document}\n\n (org-element-normalize-string (cond ((string= title)
nil) ((not (stringp org-e-latex-title-command)) nil) ((string-match
\\(?:[^%]\\|^\\)%s org-e-latex-title-command) (format
org-e-latex-title-command title)) (t org-e-latex-title-command))) (let ((depth
(plist-get info :with-toc))) (when depth (concat (when (wholenump depth)
(format \\setcounter{tocdepth}{%d}\n depth))
\\tableofcontents\n\\vspace*{1cm}\n\n))) contents (let ((creator-info
(plist-get info :with-creator))) (cond ((not creator-info) ) ((eq
creator-info (quote comment)) (format %% %s\n (plist-get info :creator))) (t
(concat (plist-get info :creator) \n \\end{document})
(let ((title (org-export-data (plist-get info :title) info))) (concat (and
(plist-get info :time-stamp-file) (format-time-string %% Created %Y-%m-%d %a
%H:%M\n)) (let ((class (plist-get info :latex-class)) (class-options
(plist-get info :latex-class-options))) (org-element-normalize-string (let*
((header (nth 1 ...)) (document-class-string (and ... ...)))
(org-e-latex--guess-inputenc (org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra))
\\providecommand{\\alert}[1]{\\textbf{#1}}\n (let ((sec-num
[O] New exporter [was: Re: Using Org for a dissertation]
Nicolas Goaziou n.goaz...@gmail.coma writes: Richard Lawrence richard.lawre...@berkeley.edu writes: I have seen mention of the new exporter on this list a bit [...] How can I try it [...]? Assuming contrib directory is in your load-path, just evaluate (require 'org-export) It would be that simple? This is surely worth a try then! Well, I'm quickly encountering a few problems. Are my tries premature, or should I push to get it going nevertheless? In the latter case, I would be reporting problems as a mere user, as I do not feel I have enough free time to dive and debug myself (it is common nowadays that maintainers, everywhere, are trying to pull users into maintenance). If this is acceptable, should I report to this list or privately to someone? François
