Re: [O] Organizing a collection of papers
> Frank writes: > I've used org-mode about a year and a half, and I don't think it's the best > application for what you describe. There are several packages available to > do this; the one I've used most often and successfully is Zotero > (zotero.org). This is a browswer plug-in which implements a very nice > database for your papers. At this point, I've indexed 1092 papers (PDFs, > web pages and other materials). In some cases, I have multiple files > attached to each of them. If you happen to have a Mac, the application DEVONthink Pro is simply wonderful for organizing collections like this. I have about 7k PDFs in a financial database, and it's always easy to find what I'm looking for. John
[O] License issue for a clone in a commercial editor
Hi. I just started a clone of some features of Org mode to the markdown mode of a commercial editor (Sublime Text 2); it's available at https://github.com/demon386/SmartMarkdown It's based on Python and until now I haven't referred to the implementation of Org. However, plan-text table is very challenging and I'm prepared to refer to the implementation of Org. I'm not very clear about the license issue in this case. Currently the plugin is licensed under MIT license. Is it necessary for me to release the plugin under GPL? Thanks.
Re: [O] Organizing a collection of papers
Victor Miller gmail.com> writes: > > I've just started using org-mode, and so far find it quite > useful. I have a very large collection of technical papers in a > directory tree, and I'd like to go through them and index them > through org-mode. What I'd like is to have a way of going through > them and look at the unannotated ones, and annotate them one by > one. I imagine doing this by first making up a file of links like > [[xxx.pdf][not done yet]], and then being presented with the not > done ones, glancing at them and deciding how what annotations to > put in. In addition I'd like to add tags. What I'd really like is > to be able to make up new tags on the fly. Has anyone done > anything like this in org-mode? I've used org-mode about a year and a half, and I don't think it's the best application for what you describe. There are several packages available to do this; the one I've used most often and successfully is Zotero (zotero.org). This is a browswer plug-in which implements a very nice database for your papers. At this point, I've indexed 1092 papers (PDFs, web pages and other materials). In some cases, I have multiple files attached to each of them. Zotero helps me manage the PDFs I have already, and makes it non unusual for me to add a few dozen to my collection, all nicely cross-referenced and ready for citations using Word or Latex. Once you realize how easy it is to get from a google scholar result to another PDF in your database, and the database entry is completely ready to support insertion as a citation, as a footnote or end-note,... this gets very addictive. I can't imagine any org-mode package accelerating the process of finding, displaying, indexing and citing sources as much as Zotero does for me.
Re: [O] git repo version clarificaiton
Daniel Hawthorne writes: > As stated by the variable "org-version," the git repo version is > 7.8.03. Each checkout you make from the repo has it's own version. Now, if you are shown version 7.8.03, it can mean several things: you really have that version checked out (forgot to pull? on a different branch?) or you may have a mixed install. > The stable release is 7.8.11. Is the version number for the > repo not meaningful? It is. The above tells us that something is amiss with your org-mode from Git. We just can't tell what exactly since you didn't give enough information. git remote update git fetch --tags git checkout master git describe Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html
Re: [O] git repo version clarificaiton
Tassilo Horn wrote: > Nick Dokos writes: > > Hi Nick, > > > Is this master or maint? > > master > > >> Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @ > >> /home/horn/Repos/el/org-mode/lisp/) > >> > >> instead of 7.8.11. > > > > Oh, and as Achim pointed out, you probably need to do > > > > git fetch --tags origin > > Oh, yes, that does the trick. So the org version is constructed from > the latest tag in git? > When you ``make autoloads'', it runs ``git describe --abbrev=6 HEAD'' and uses the resulting string to create a new org-version.el file. That file is then used from that point on. And yes, ``git describe'' calculates the name by counting how many commits past the latest available tag there are (on the appropriate branch). Nick
[O] R and babel on Windows problem
I typically use orgmode + babel on Linux and have no problems. Trying to run on Windows 7 and having issues... The pertinent bits from .emacs: -- ;; setup babel (add-to-list 'load-path "~/.emacs.d/ess-12.04/lisp") (require 'ess-site) (setq org-babel-R-command "C:/Program\ Files/R/R-2.15.0/bin/R") (org-babel-do-load-languages 'org-babel-load-languages '((latex . t) (R . t))) -- When I try to execute a simple R src block, I get: "The system cannot find the path specified." I get the same with or without setting the org-babel-R-command path and with or without using R.exe instead of just R. There's an *ESS* buffer that /appears/ to be finding the versions of R on my machine: -- [ess-site.el]: ess-customize-alist=nil [ess-site.el _2_]: ess-customize-alist=nil (R): ess-r-versions-create making M-x defuns for R-2.15.0-64bit R-2.14.1-64bit -- Any suggestions? Best regards, John
Re: [O] git repo version clarificaiton
Nick Dokos writes: Hi Nick, > Is this master or maint? master >> Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @ >> /home/horn/Repos/el/org-mode/lisp/) >> >> instead of 7.8.11. > > Oh, and as Achim pointed out, you probably need to do > > git fetch --tags origin Oh, yes, that does the trick. So the org version is constructed from the latest tag in git? Bye, Tassilo
Re: [O] git repo version clarificaiton
Tassilo Horn wrote: > Nick Dokos writes: > > Hi Nick, > > >>As stated by the variable "org-version," the git repo version is > >> 7.8.03. The stable release is 7.8.11. Is the version number for the > >> repo not meaningful? > > > > You probably have an out-of-date org-version.el[c]. You need to > > ``make autoloads'' after pulling. That will remake org-version.el and > > org-install.el to reflect reality. > > I think, it's still wrong. I can see that in commit > 60587ea91cb42ae8618666c7dae5b029f751b913 Basien bumped the defconst > org-version to 7.8.11, but that doesn't exist anymore. And making clean > and recompiling everything still says > > Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @ > /home/horn/Repos/el/org-mode/lisp/) > > instead of 7.8.11. > Oh, and as Achim pointed out, you probably need to do git fetch --tags origin Nick
Re: [O] git repo version clarificaiton
Tassilo Horn wrote: > Nick Dokos writes: > > Hi Nick, > > >>As stated by the variable "org-version," the git repo version is > >> 7.8.03. The stable release is 7.8.11. Is the version number for the > >> repo not meaningful? > > > > You probably have an out-of-date org-version.el[c]. You need to > > ``make autoloads'' after pulling. That will remake org-version.el and > > org-install.el to reflect reality. > > I think, it's still wrong. I can see that in commit > 60587ea91cb42ae8618666c7dae5b029f751b913 Basien bumped the defconst > org-version to 7.8.11, but that doesn't exist anymore. And making clean > and recompiling everything still says > > Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @ > /home/horn/Repos/el/org-mode/lisp/) > > instead of 7.8.11. > Is this master or maint? On maint, I get release_7.8.10-11-g5968047 On master, I get release_7.8.11-89-gcf8d979 Nick
Re: [O] git repo version clarificaiton
Confirmed. Jun 28 08:58 ./lisp/org-version.el Version 7.8.10. -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] git repo version clarificaiton
Nick Dokos writes: Hi Nick, >>As stated by the variable "org-version," the git repo version is >> 7.8.03. The stable release is 7.8.11. Is the version number for the >> repo not meaningful? > > You probably have an out-of-date org-version.el[c]. You need to > ``make autoloads'' after pulling. That will remake org-version.el and > org-install.el to reflect reality. I think, it's still wrong. I can see that in commit 60587ea91cb42ae8618666c7dae5b029f751b913 Basien bumped the defconst org-version to 7.8.11, but that doesn't exist anymore. And making clean and recompiling everything still says Org-mode version 7.8.10 (release_7.8.10-701-g054f99 @ /home/horn/Repos/el/org-mode/lisp/) instead of 7.8.11. Bye, Tassilo
Re: [O] git repo version clarificaiton
Daniel Hawthorne wrote: >As stated by the variable "org-version," the git repo version is 7.8.03. > The stable release is 7.8.11. Is the version number for the repo not > meaningful? > You probably have an out-of-date org-version.el[c]. You need to ``make autoloads'' after pulling. That will remake org-version.el and org-install.el to reflect reality. Nick
Re: [O] [LibreOffice] (void-variable org-line)
> Debugger entered--Lisp error: (error "Cannot determine style name for
> entity default of type character")
I have pushed a fix. The problem is:
There is a string that matches `org-emph-re'. (May be you are using
@...@ for marking things specially). But there is no entry for it in
`org-lparse-char-styles'. Since a style name was not found, org-odt.el
is complaining. For now, such text spans will be marked with "Default"
character style.
If you want them to be marked with emphasis (or any of the known styles)
then do,
(eval-after-load 'org-lparse
'(push (quote ("@" emphasis)) org-lparse-char-styles))
If want to roll out your own style (for example highlight the text
span), you need to add relevant entries to `org-lparse-char-styles',
`org-export-odt-default-org-styles-alist' and also the styles.xml.
i.e., changes are going to be a bit elaborate.
Jambunathan K.
--
[O] babel: is it possible to cache #+call executed blocks
Hello everyone,
i'm looking for a possibilty to call lengthy codeblocks a few times with
different parameters, but would like the results to be cached.
hopefully wiw becomes clear enough with a minimal example.
the code block speak, if directly evaluated, produces the correct result
hallo on the first run. all subsequent runs just return immediately,
until the code block is changed.
if one evaluates the #+call line, as expected the right result is
returned and the hash necessary for caching is added to #+RESULTS.
but subsequent evaluations always seem to evaluate the code block again,
i.e. one has to wait the 5 seconds.
is there a way to avoid this?
thanks,
jonas
#+begin_src org
* Test
#+name: speak
#+begin_src sh :var say="hallo" :results output :cache yes
echo $say
sleep 5
#+end_src
#+RESULTS[4370bde991d63488bcb6d297718919fcf2b4fa1f]: speak
: hallo
#+call: speak('welt') :cache yes
#+RESULTS[c393aea840734e972880a4a38512765d345e7125]: speak('welt'):cache yes
: welt
#+end_src
Re: [O] Showing or going to previous entry from agenda view
* Bernt Hansen wrote: > Karl Voit writes: > >> C-c C-p (outline-previous-visible-heading) jumps from «Meeting 3» >> directly to the previous *visible* heading «Person X» and not to >> «Meeting 2». > > C-c C-r should call org-reveal which will show the preceeding hidden > headline, then you can use C-c C-p normally. Hm, at my side, org-reveal does not show me the items above. In fact, org-reveal does not seem to have any effect at all :-O -- Karl Voit
[O] git repo version clarificaiton
Hi, As stated by the variable "org-version," the git repo version is 7.8.03. The stable release is 7.8.11. Is the version number for the repo not meaningful? Best, Daniel Hawthorne
Re: [O] [LibreOffice] (void-variable org-line)
Hi Sébastien, "Sebastien Vauban" writes: > When trying to export to LibreOffice, I get this error message: This should be fixed. Can you test and report? Thanks, -- Bastien
Re: [O] [LibreOffice] (void-variable org-line)
Hi Jambunathan,
Jambunathan K wrote:
> "Sebastien Vauban" writes:
>
>> When trying to export to LibreOffice, I get this error message:
>>
>> Debugger entered--Lisp error: (void-variable org-line)
>
> Fixed in both master and maint.
That does work. Thanks for your speedy answer and fix!
However, I'm now blocked by this:
--8<---cut here---start->8---
Debugger entered--Lisp error: (error "Cannot determine style name for entity
default of type character")
signal(error ("Cannot determine style name for entity default of type
character"))
error("Cannot determine style name for entity %s of type %s" default
character)
(or (cdr (assoc entity (cdr (assoc category
org-export-odt-org-styles-alist (cdr (assoc entity (cdr (assoc category
org-export-odt-default-org-styles-alist (error "Cannot determine style name
for entity %s of type %s" entity category))
(let ((entity (or entity (quote default (or (cdr (assoc entity (cdr
(assoc category org-export-odt-org-styles-alist (cdr (assoc entity (cdr
(assoc category org-export-odt-default-org-styles-alist (error "Cannot
determine style name for entity %s of type %s" entity category)))
org-odt-get-style-name-for-entity(character nil)
(cond ((stringp style) (org-odt-remap-stylenames style)) ((symbolp style)
(org-odt-get-style-name-for-entity (quote character) style)) ((listp style)
(assert (< 1 (length style))) (let ((parent-style (pop style))) (mapconcat
(lambda (s) (org-odt-remap-stylenames s)) style "") (org-odt-remap-stylenames
parent-style))) (t (error "Don't how to handle style %s" style)))
(let* ((style-name (cond ((stringp style) (org-odt-remap-stylenames style))
((symbolp style) (org-odt-get-style-name-for-entity (quote character) style))
((listp style) (assert (< 1 (length style))) (let ((parent-style ...))
(mapconcat (lambda ... ...) style "") (org-odt-remap-stylenames parent-style)))
(t (error "Don't how to handle style %s" style) (org-odt-format-tags (quote
("" . "")) text style-name))
org-odt-format-fontify(#("(XXX to be tested)" 0 18 (fontified nil list-item
3001 list-struct ((2845 0 "- " nil nil nil 2959) (2868 2 "+ " nil nil nil 2938)
(2938 2 "+ " nil nil nil 2959) (2959 0 "- " nil nil nil 3056) (2980 2 "+ " nil
nil nil 3001) (3001 2 "+ " nil nil nil 3056) (3056 0 "- " nil nil nil 3121)
(3096 2 "+ " nil nil nil 3121)) list-prevs ((2845) (2868) (2938 . 2868) (2959 .
2845) (2980) (3001 . 2980) (3056 . 2959) (3096)) list-context nil)) nil)
apply(org-odt-format-fontify (#("(XXX to be tested)" 0 18 (fontified nil
list-item 3001 list-struct ((2845 0 "- " nil nil nil 2959) (2868 2 "+ " nil nil
nil 2938) (2938 2 "+ " nil nil nil 2959) (2959 0 "- " nil nil nil 3056) (2980 2
"+ " nil nil nil 3001) (3001 2 "+ " nil nil nil 3056) (3056 0 "- " nil nil nil
3121) (3096 2 "+ " nil nil nil 3121)) list-prevs ((2845) (2868) (2938 . 2868)
(2959 . 2845) (2980) (3001 . 2980) (3056 . 2959) (3096)) list-context nil))
nil))
(let ((f (cdr (assoc entity org-lparse-entity-format-callbacks-alist
(unless f (error "Unknown entity: %s" entity)) (apply f args))
(cond ((consp entity) (let ((text (pop args))) (apply (quote
org-lparse-format) (quote TAGS) entity text args))) (t (let ((f (cdr (assoc
entity org-lparse-entity-format-callbacks-alist (unless f (error "Unknown
entity: %s" entity)) (apply f args
org-lparse-format(FONTIFY #("(XXX to be tested)" 0 18 (fontified nil
list-item 3001 list-struct ((2845 0 "- " nil nil nil 2959) (2868 2 "+ " nil nil
nil 2938) (2938 2 "+ " nil nil nil 2959) (2959 0 "- " nil nil nil 3056) (2980 2
"+ " nil nil nil 3001) (3001 2 "+ " nil nil nil 3056) (3056 0 "- " nil nil nil
3121) (3096 2 "+ " nil nil nil 3121)) list-prevs ((2845) (2868) (2938 . 2868)
(2959 . 2845) (2980) (3001 . 2980) (3056 . 2959) (3096)) list-context nil)) nil)
(concat (match-string 1 string) (org-lparse-format (quote FONTIFY)
(match-string 4 string) (nth 1 (assoc (match-string 3 string)
org-lparse-char-styles))) (match-string 5 string))
(setq s (match-beginning 0) rpl (concat (match-string 1 string)
(org-lparse-format (quote FONTIFY) (match-string 4 string) (nth 1 (assoc
(match-string 3 string) org-lparse-char-styles))) (match-string 5 string))
string (replace-match rpl t t string) s (+ s (- (length rpl) 2)))
(if (not (equal (substring string (match-beginning 3) (1+ (match-beginning
3))) (substring string (match-beginning 4) (1+ (match-beginning 4) (setq s
(match-beginning 0) rpl (concat (match-string 1 string) (org-lparse-format
(quote FONTIFY) (match-string 4 string) (nth 1 (assoc (match-string 3 string)
org-lparse-char-styles))) (match-string 5 string)) string (replace-match rpl t
t string) s (+ s (- (length rpl) 2))) (setq s (1+ s)))
(while (string-match org-emph-re string s) (if (not (equal (substring string
(match-beginning 3) (1+ (match-beginning 3))) (substring string
(match-beginning 4) (1+ (match-beginning 4) (setq s (mat
Re: [O] [LibreOffice] (void-variable org-line)
"Sebastien Vauban" writes: > When trying to export to LibreOffice, I get this error message: > > Debugger entered--Lisp error: (void-variable org-line) Fixed in both master and maint. --
Re: [O] Showing or going to previous entry from agenda view
Karl Voit writes: > Hi! > > Following scenario: I see my (daily) agenda, go to a meeting (which > is scheduled regularly) and press Enter. > > This jumps to the Org-mode file of this entry which has got > following (sub-)structure in the file: > > * Project > * Person X > * Meeting 1 > * Meeting 2 > * Meeting 3 > * Meeting 4 > > But what Org-mode shows me when I jump directly from agenda view to > lets say «Meeting 3» is following: > > * Project > * Person X... > * Meeting 3 > * Meeting 4 > > So Meeting 1 and 2 are «hidden» like being in a sparse tree. Please > do not misunderstand: This behavior is somewhat fine to me. > > BUT: I also want to be able to quickly jump to «Meeting 2» when I > «land» on «Meeting 3». (To check the open issues from last meeting.) > > C-c C-p (outline-previous-visible-heading) jumps from «Meeting 3» > directly to the previous *visible* heading «Person X» and not to > «Meeting 2». C-c C-r should call org-reveal which will show the preceeding hidden headline, then you can use C-c C-p normally. HTH, Bernt > > So I always end up going up, pressing TAB to expand the whole > subtree and then I start «searching» for the current Meeting once > again - which is obviously kina annoying to me :-( > > I am sure, that you have got a tipp that provides me either a > visible «Meeting 2» or a «working» jump-command for invisible > heading (outline-previous-heading does not exist) or something else > I did not think about :-) > > Thanks for that!
Re: [O] [dev] About a beamer back-end
Hi suvayu ali, > Hi Andreas, > > On Thu, Jun 28, 2012 at 12:40 PM, Andreas Leha > wrote: >> Will this new backend support presentations in subtrees? I think, what >> I want is not possible with the current one. >> >> As an example, consider files structured like this: >> >> #+begin_src org >> * Presentations >> ** Workshop 2013 >> ** Conference 2013 >> >> * Paper for journal X >> >> * Actual work on Project with all the code, etc >> >> #+end_src > > I do this all the time with the current exporter. You need to insert the > beamer options in subtree properties. You can use > `org-insert-beamer-options-template' to insert the options conveniently. > After this you can export the subtree to get your presentation. Wow great! I did not know about this. Thanks a lot! Cheers, Andreas
Re: [O] [dev] About a beamer back-end
Hi Andreas, On Thu, Jun 28, 2012 at 12:40 PM, Andreas Leha wrote: > Will this new backend support presentations in subtrees? I think, what > I want is not possible with the current one. > > As an example, consider files structured like this: > > #+begin_src org > * Presentations > ** Workshop 2013 > ** Conference 2013 > > * Paper for journal X > > * Actual work on Project with all the code, etc > > #+end_src I do this all the time with the current exporter. You need to insert the beamer options in subtree properties. You can use `org-insert-beamer-options-template' to insert the options conveniently. After this you can export the subtree to get your presentation. -- Suvayu Open source is the future. It sets us free.
Re: [O] Bug?: org-agenda-set-property sets property on wrong element
At Thu, 28 Jun 2012 06:16:06 -0400, Max Mikhanosha wrote: > > The problem seems to be that the code like this (with-current-buffer > buffer (goto-char pos (call-interactively 'some-command)) the point > inside of 'some-command will not be at `pos', but where the user last > moved it, _unless_ the buffer's window is selected window, then > (goto-char) sticks through (call-interactively) boundary. Above was wrong, it seems the culprit is anything that uses a completing read from minibuffer, while inside of (with-current-buffer) for a buffer that is not visible on any window; after reading from minibuffer the point is reset back to where user last moved it. I was able to fix parent message's test case by putting save-excursion around (org-icompleting-read), but I'm wondering if its my specific setup, or if anyone else can reproduce this.
Re: [O] [dev] About a beamer back-end
Hi Nicolas, > As I announced in another thread, I'm starting a Beamer back-end for the > new export engine. Though, before I start hacking, I have a question > about environments. Will this new backend support presentations in subtrees? I think, what I want is not possible with the current one. As an example, consider files structured like this: #+begin_src org * Presentations ** Workshop 2013 ** Conference 2013 * Paper for journal X * Actual work on Project with all the code, etc #+end_src Regards, Andreas
[O] Bug?: org-agenda-set-property sets property on wrong element
Can someone confirm this, before I try to fix this? 1. Generate agenda 2. Go to some entry A by pressing RET 3. Switch back to agenda, and make sure its the only window (or that A's buffer is not in any other window) 4. In Agenda navigate to entry B (in the same buffer as A), and C-c C-x p (org-agenda-set-property), use any property name or value Result: property is set in entry A not in entry B. This is with org-mode from git, and emacs 23. The problem seems to be that the code like this (with-current-buffer buffer (goto-char pos (call-interactively 'some-command)) the point inside of 'some-command will not be at `pos', but where the user last moved it, _unless_ the buffer's window is selected window, then (goto-char) sticks through (call-interactively) boundary. Could be that there are other pieces of code like this in lurking in there. Regards, Max
Re: [O] flet fixed in emacs trunk
Baptiste Fouques writes: > I do confirm that 'flet' is now working in emacs following emacs patch > http://lists.gnu.org/archive/html/emacs-devel/2012-06/msg00515.html > > Org mode is working like a charm with in emacs, trunk version. Great, thanks for confirming! -- Bastien
[O] flet fixed in emacs trunk (Was: Is Org mode gonna break on emacs 24.50.1x ?)
Hi all, thanks for your answers, I do confirm that 'flet' is now working in emacs following emacs patch http://lists.gnu.org/archive/html/emacs-devel/2012-06/msg00515.html Org mode is working like a charm with in emacs, trunk version. -- ~^v^~ Bat Baptiste Fouques writes: > Hi, > > thanks all for org. > > I wonder whether org-mode is going to break badly on next emacs > cleanup. > > --- > commit 1e211d886c96420904ad197cfee7fce7ae7b9d83 (HEAD, refs/heads/master) > Author: Stefan Monnier > Date: Fri Jun 22 09:42:38 2012 -0400 > > … > * lisp/emacs-lisp/cl.el (flet): Don't autoload. > … > --- > > Makes my org not working in several places (babel, coupling with > remenber, …). I think that the point in using 'flet' has appears > several times in this group. It seems to become more crucial here. > > Don't think that the problem of emacs, but org … > > Thanks.
[O] Showing or going to previous entry from agenda view
Hi! Following scenario: I see my (daily) agenda, go to a meeting (which is scheduled regularly) and press Enter. This jumps to the Org-mode file of this entry which has got following (sub-)structure in the file: * Project * Person X * Meeting 1 * Meeting 2 * Meeting 3 * Meeting 4 But what Org-mode shows me when I jump directly from agenda view to lets say «Meeting 3» is following: * Project * Person X... * Meeting 3 * Meeting 4 So Meeting 1 and 2 are «hidden» like being in a sparse tree. Please do not misunderstand: This behavior is somewhat fine to me. BUT: I also want to be able to quickly jump to «Meeting 2» when I «land» on «Meeting 3». (To check the open issues from last meeting.) C-c C-p (outline-previous-visible-heading) jumps from «Meeting 3» directly to the previous *visible* heading «Person X» and not to «Meeting 2». So I always end up going up, pressing TAB to expand the whole subtree and then I start «searching» for the current Meeting once again - which is obviously kina annoying to me :-( I am sure, that you have got a tipp that provides me either a visible «Meeting 2» or a «working» jump-command for invisible heading (outline-previous-heading does not exist) or something else I did not think about :-) Thanks for that! -- Karl Voit
[O] [LibreOffice] (void-variable org-line)
Hello, When trying to export to LibreOffice, I get this error message: --8<---cut here---start->8--- Debugger entered--Lisp error: (void-variable org-line) (string-match "^ORG-\\(.*\\)-\\(START\\|END\\)$" org-line) (if (string-match "^ORG-\\(.*\\)-\\(START\\|END\\)$" org-line) (progn (message "%s" (match-string 1)) (when (equal (match-string 2 org-line) "START") (org-close-par-maybe) (insert "\n") (org-open-par)) (when (equal (match-string 2 org-line) "END") (org-close-par-maybe) (insert "\n") (org-open-par)) (throw (quote nextline) nil))) (when (string-match "^ORG-\\(.*\\)-\\(START\\|END\\)$" org-line) (message "%s" (match-string 1)) (when (equal (match-string 2 org-line) "START") (org-close-par-maybe) (insert "\n") (org-open-par)) (when (equal (match-string 2 org-line) "END") (org-close-par-maybe) (insert "\n") (org-open-par)) (throw (quote nextline) nil)) org-special-blocks-convert-html-special-cookies() run-hooks(org-export-html-after-blockquotes-hook) (catch (quote nextline) (when (and (org-lparse-current-environment-p (quote quote)) (string-match org-outline-regexp-bol line)) (org-lparse-end-environment (quote quote))) (when (org-lparse-current-environment-p (quote quote)) (org-lparse-insert (quote LINE) line) (throw (quote nextline) nil)) (when (and org-export-with-fixed-width (string-match "^[ ]*:\\(\\([ ]\\|$\\)\\(.*\\)\\)" line)) (when (not (org-lparse-current-environment-p (quote fixedwidth))) (org-lparse-begin-environment (quote fixedwidth))) (org-lparse-insert (quote LINE) (match-string 3 line)) (when (or (not lines) (not (string-match "^[]*:\\(\\([ ]\\|$\\)\\(.*\\)\\)" (car lines (org-lparse-end-environment (quote fixedwidth))) (throw (quote nextline) nil)) (when (and (get-text-property 0 (quote org-native-text) line) (not (< (or (next-single-property-change 0 (quote org-native-text) line) 1) (length line (let ((ind (get-text-property 0 (quote original-indentation) line))) (org-lparse-begin-environment (quote native)) (org-lparse-insert (quote LINE) line) (while (and lines (or (= (length ...) 0) (not ind) (equal ind (get-text-property 0 ... ...))) (or (= (length ...) 0) (get-text-property 0 (quote org-native-text) (car lines (org-lparse-insert (quote LINE) (pop lines))) (org-lparse-end-environment (quote native))) (throw (quote nextline) nil)) (when (and (get-text-property 0 (quote org-protected) line) (not (< (or (next-single-property-change 0 (quote org-protected) line) 1) (length line (let ((ind (get-text-property 0 (quote original-indentation) line))) (org-lparse-insert (quote LINE) line) (while (and lines (or (= (length ...) 0) (not ind) (equal ind (get-text-property 0 ... ...))) (or (= (length ...) 0) (get-text-property 0 (quote org-protected) (car lines (org-lparse-insert (quote LINE) (pop lines (throw (quote nextline) nil)) (when (string-match "^ORG-\\(.+\\)-\\(START\\|END\\)\\([ ]+.*\\)?$" line) (let* ((style (intern (downcase (match-string 1 line (env-options-plist (org-lparse-get-block-params (match-string 3 line))) (f (cdr (assoc (match-string 2 line) (quote ...) (when (memq style (append (quote (blockquote verse center)) (mapcar (quote intern) org-lparse-special-blocks))) (funcall f style env-options-plist) (throw (quote nextline) nil (run-hooks (quote org-export-html-after-blockquotes-hook)) (when (org-lparse-current-environment-p (quote verse)) (let ((i (org-get-string-indentation line))) (if (> i 0) (setq line (concat (let (...) (org-lparse-format ... ...)) " " (org-trim line (unless (string-match "[]*$" line) (setq line (concat line "") (setq start 0) (while (string-match "<<]*\\)>>>?\\((INVISIBLE)\\)?[ ]*\n?" line start) (cond ((get-text-property (match-beginning 1) (quote org-protected) line) (setq start (match-end 1))) ((match-end 2) (setq line (replace-match (let (...) (org-lparse-format ... "" ...)) t t line))) ((and org-export-with-toc (equal (string-to-char line) 42)) (setq line (replace-match (let (...) (org-lparse-format ... ... "target")) t t line))) (t (setq line (replace-match (concat (let ... ...) " ") t t line) (let ((org-lparse-encode-pending t)) (setq line (org-lparse-handle-time-stamps line))) (or (string-match org-table-hline-regexp line) (string-match "^[ ]*\\([+]-\\||[ ]\\)[-+ |]*[+|][ ]*$" line) (setq line (org-xml-encode-org-text-skip-links line))) (setq line (org-lparse-format-org-link line opt-plist)) (if (and org-todo-line-regexp (string-match org-todo-line-regexp line) (match-beginning 2)) (setq line (concat (substring line 0 (match-beginning 2)) (org-lparse-format (quote TODO) (match-string 2 line)) (substring line (match-end 2) (when org-export-with-footnotes (setq start 0) (while (string-match "\\([^*].*?\\)[]*\\[\\([0-9]+\\)\\]" line start) (if (or (get-text-property (match-beginning 2) (quote org-prote
Re: [O] new exporter
Hello, Achim Gratz writes: > This code snippet has at last after revealed where the problem is: the > function call to (current-buffer) gets unquoted, when it clearly needs > to be in the expansion. The literal expansion of the buffer content > into the compiled bytecode is similarly explained by an unquoting of > (buffer-string). Here's a patch that seems to fix the compilation > (without changelog and everything because I think you may want to check > the rest of the new exporters for similar constructs). Nice catch. I think you can go ahead and commit it: your description of the problem will be more accurate than mine. Thank you for this investigation and, obviously, for the fix. Regards, -- Nicolas Goaziou
