Re: [O] How to programmatically use/edit data provided on capture
Hi Marcin,
Marcin Antczak marcin.antc...@neutrico-themes.pl writes:
I got capture template with prompts to collect some properties:
#+BEGIN_SRC
* TODO %\1 / Some task description
:PROPERTIES:
:NAME: %^{NAME}
:END:
#+END_SRC
My question is: How to get information on user input data to transform
this data before capture finalize.
I too have wanted to do something like this, but I am not sure that it
is possible without hacking org-capture, because I don't think you can
hook into the template processing at an arbitrary point.
Is it really important that you transform the data *before* capture
finalize? If not, I think you could do this *during* capture finalize
by replacing, say, a pre-determined string PUT-NAME-HERE with the value of
(custom-dashify-function (org-entry-get (point) NAME))
You could do that from org-capture-prepare-finalize-hook, maybe. Would
that work for you? It has some limitations:
- it's only easy to recover data that was entered as properties or tags, not
arbitrary strings
- you can't continue to edit the capture buffer after doing this
processing, since the hook will only be called after you start
finalization
If you come up with a better solution, I'd like to hear about it! I
have scratched my head about this several times before, but I've never
come up with a satisfactory solution.
Good luck!
Best,
Richard
Re: [O] Export org-mode buffer to dynamic html document (collapse/expand details)
Von: Eric Abrahamsen e...@ericabrahamsen.net Datum: Fri, 01 Aug 2014 09:04:07 +0800 An: emacs-orgmode@gnu.org Betreff: Re: [O] Export org-mode buffer to dynamic html document (collapse/expand details) Martin Beck elwood...@web.de writes: it would be great if the text below headings could be collapsed somehow or if there was an overview page listing all projects and some important sub-headings or remarks and a hyperlink pointing to the detailed notes concerning this project. This just sounds like a table of contents -- if you export to a format that supports hyperlinks, wouldn't a plain old TOC do? Eric, thanks for your comment! Indeed a TOC is a good start as it would give an overview of the projects. I just discovered that if I export a todo tree in visible only C-c / t C-c C-e C-v C-h C-o (with Rober Eckl's HTML export settings suggested in the same thread here) the generated TOC only contains those headings from the TODO tree.. :-) Kind regards Martin
Re: [O] Bug: Export to Latex - Incorrect output for list items starting with left bracket [8.2.3c (8.2.3c-elpa @ /Users/jdegenhardt/.emacs.d/elpa/org-20131115/)]
Hello, Eric S Fraga e.fr...@ucl.ac.uk writes: Sebastien Vauban sva-n...@mygooglest.com writes: Nicolas Goaziou wrote: [...] The question is still open, though: should it be the default? I'd vote for it, for both LaTeX and HTML. Best regards, Seb As would I. Check boxes with bullet points look quite ugly. Removing the bullet point leaves a very clean format. I have no idea how to achieve this in HTML with filters, mind you... I looked into implementing it in ox-latex.el (about time), but mixing checkboxed ordered and unordered lists is not pretty then - [-] A 1. [X] B 2. [-] C - [ ] D Regards, -- Nicolas Goaziou
[O] [BUG] Re: error in only text exporter
Xebar Saram zelt...@gmail.com writes: Hi again i really would appreciate any help here (i know im a neewb :) ). all but the text exporter works. can someone guide me on how to start debugging this? This bug was introduced in dd6b4ff -- in `org-ascii-filter-paragraph-spacing', the function body was originally protected by a: (when (wholenump org-ascii-paragraph-spacing) ...) which was taken out, meaning that the default value of 'auto falls through to `org-export-data' and causes an explosion. I've cc'd Nicolas, who will know what to do! E On Mon, Jul 28, 2014 at 9:35 PM, Xebar Saram zelt...@gmail.com wrote: Hi list for some reason exporting to txt dosent work here. all other options (html,pdf etc) work. in the message window i get: concat: Wrong type argument: wholenump, auto anyway i can get more info on this and try to figure out whats going on? thx! Z
[O] [BUG] Re: error in only text exporter
Xebar Saram zelt...@gmail.com writes: Hi again i really would appreciate any help here (i know im a neewb :) ). all but the text exporter works. can someone guide me on how to start debugging this? This bug was introduced in dd6b4ff -- in `org-ascii-filter-paragraph-spacing', the function body was originally protected by a: (when (wholenump org-ascii-paragraph-spacing) ...) which was taken out, meaning that the default value of 'auto falls through to `org-export-data' and causes an explosion. I've cc'd Nicolas, who will know what to do! E On Mon, Jul 28, 2014 at 9:35 PM, Xebar Saram zelt...@gmail.com wrote: Hi list for some reason exporting to txt dosent work here. all other options (html,pdf etc) work. in the message window i get: concat: Wrong type argument: wholenump, auto anyway i can get more info on this and try to figure out whats going on? thx! Z
Re: [O] [PATCH] ox-bibtex.el: Extend to use bibtex files not in current, working directory
Hello, thanks. I am quite new to this. What is about this FSF copyright assignment Bastien mentioned? I filled it and send it to ass...@gnu.org but since then nothing happened. How long does this usually take? Best, Konrad Am 08/02/2014 09:27 PM, schrieb Nicolas Goaziou: Hello, Konrad Herbst k.her...@stud.uni-heidelberg.de writes: From: Konrad Herbst k.her...@stud.uni-heidelberg.de Date: Wed, 9 Jul 2014 15:26:10 +0200 Subject: [PATCH] ox-bibtex.el: Extend to use bibtex files not in current working directory * contrib/lisp/ox-bibtex.el (org-bibtex-process-bib-files): Process bibtexfilename so that it does not have to be in the same directory. Applied. Thank you. Regards,
[O] mathjax vs. imagemagick
Hello, In order to convert a tikzpicture into html webpage, one needs #+OPTIONS: tex:imagemagick and it means that the other equations are no more converted via Mathjax. Is there a mean to combine the use of imagemagick only for tikzpicture, and keeping the use of Mathjax to read the other equations in the html file? Best wishes Jo.
Re: [O] Bug: can not export pdf file [8.2.7c (8.2.7c-elpa @ /Users/mac/.emacs.d/elpa/org-20140730/)]
Am 02.08.2014 um 15:32 schrieb 童俊翔 tongjunxi...@gmail.com: Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. When I press C-c C-e l o, *Messages* shows: /bin/bash: xelatex: command not found /bin/bash: bibtex: command not found /bin/bash: xelatex: command not found [2 times] org-latex-compile: PDF file ./LapRPHepatectomy.pdf wasn't produced my mactex has updated to the latest version. How to deal with this problem? First try if these programs work: Open Terminal and enter xelatex --version if that works, start emacs from the terminal: /Applications/Emacs.app/Contents/MacOS/Emacs this should start the GUI emacs. (Your path may vary.) From this emacs you can now export the pdf. You may want to define an alias to call emacs. An alternative would be to hardcode the path in custom.el '(org-latex-pdf-process (quote (/usr/texbin/xelatex -interaction nonstopmode -output-directory %o %f /usr/texbin/xelatex -interaction nonstopmode -output-directory %o %f))) Of course you can do this using the customize interface. Axel
Re: [O] [POLL] Syntax change: make \[...\] non-inline (+1)
5. Existing documents are very easy to fix. Backwards compatibility is important. It has been broken before, for very good reasons, and even though it was done very carefully, it still caused many problems (still does). So I don't buy the very easy to fix part: it will bite somebody two minutes before he/she has to make a presentation (or even during the presentation - DAMHIKT). Don't get me wrong, I value backward compatibility. However, here for the end user the change would amount to something like if \[ is not at the beginning of a line, then insert \n before \[ if \] does not end a line, then insert \n after \] for the whole document (or something similar). This should obviously be documented in the release notes where an exact procedure to fix the document can be detailed (possibly two query-replace expressions). And if somebody updates just before a presentation and without reading the release notes, then it's his own fault. Regards, Federico
Re: [O] [PATCH] ox-bibtex.el: Extend to use bibtex files not in current, working directory
Aloha Konrad, IIRC, it took my assignment about a month to be completed. All the best, Tom Konrad Herbst k.her...@stud.uni-heidelberg.de writes: Hello, thanks. I am quite new to this. What is about this FSF copyright assignment Bastien mentioned? I filled it and send it to ass...@gnu.org but since then nothing happened. How long does this usually take? Best, Konrad Am 08/02/2014 09:27 PM, schrieb Nicolas Goaziou: Hello, Konrad Herbst k.her...@stud.uni-heidelberg.de writes: From: Konrad Herbst k.her...@stud.uni-heidelberg.de Date: Wed, 9 Jul 2014 15:26:10 +0200 Subject: [PATCH] ox-bibtex.el: Extend to use bibtex files not in current working directory * contrib/lisp/ox-bibtex.el (org-bibtex-process-bib-files): Process bibtexfilename so that it does not have to be in the same directory. Applied. Thank you. Regards, -- Thomas S. Dye http://www.tsdye.com
Re: [O] [POLL] Syntax change: make \[...\] non-inline (+1)
Federico Beffa be...@ieee.org writes: 5. Existing documents are very easy to fix. Backwards compatibility is important. It has been broken before, for very good reasons, and even though it was done very carefully, it still caused many problems (still does). So I don't buy the very easy to fix part: it will bite somebody two minutes before he/she has to make a presentation (or even during the presentation - DAMHIKT). Don't get me wrong, I value backward compatibility. However, here for the end user the change would amount to something like if \[ is not at the beginning of a line, then insert \n before \[ if \] does not end a line, then insert \n after \] for the whole document (or something similar). This should obviously be documented in the release notes where an exact procedure to fix the document can be detailed (possibly two query-replace expressions). And if somebody updates just before a presentation and without reading the release notes, then it's his own fault. It's a bit more complicated than that: one upgrades org at some opportune moment, then three months/years/centuries later, tries to use that presentation that worked perfectly before - boom. If you go back and check all your old presentations each time you upgrade org, you are, I would guess, the exception, not the rule. I certainly don't do that Just to be clear: on the whole issue you bring up, I'm more or less neutral (slightly negative to be sure, mostly because I'm not convinced that it's a serious problem, but I could live with it either way). I generally put displays in separate paragraphs, I rarely use autofill[fn:1] and I'm happy to do M-q on individual paragraphs instead, but if I happen to do it on the wrong paragraph (backtraces, code fragments, displayed equations), undo is easy enough. Footnotes: [fn:1] I use it in gnus message composition modes by default, and I often swear at it and turn it off because it does things that I don't want it to do - mostly mangles backtraces and code fragments; I probably should turn it off completely. -- Nick
Re: [O] [PATCH] ox-bibtex.el: Extend to use bibtex files not in current, working directory
t...@tsdye.com (Thomas S. Dye) writes: Aloha Konrad, IIRC, it took my assignment about a month to be completed. Mine too - I don't remember the details, so don't hold me to it, but I think I found out that it had gone through from Bastien first, rather than the FSF. Eventually, I think I got a signed copy of the assignment from the FSF (I don't remember whether it was a scanned PDF in email, or a paper copy in snail mail), but it took a few more days/weeks. So don't give up hope yet. Nick All the best, Tom Konrad Herbst k.her...@stud.uni-heidelberg.de writes: Hello, thanks. I am quite new to this. What is about this FSF copyright assignment Bastien mentioned? I filled it and send it to ass...@gnu.org but since then nothing happened. How long does this usually take? Best, Konrad Am 08/02/2014 09:27 PM, schrieb Nicolas Goaziou: Hello, Konrad Herbst k.her...@stud.uni-heidelberg.de writes: From: Konrad Herbst k.her...@stud.uni-heidelberg.de Date: Wed, 9 Jul 2014 15:26:10 +0200 Subject: [PATCH] ox-bibtex.el: Extend to use bibtex files not in current working directory * contrib/lisp/ox-bibtex.el (org-bibtex-process-bib-files): Process bibtexfilename so that it does not have to be in the same directory. Applied. Thank you. Regards, -- Nick
Re: [O] [RFC] Rewrite `org-entry-properties' using parser
I have used the following approaches in the past: Lisp lists, and use read later to get them. * Some heading :PROPERTIES: :SUBJECT: '(subject1 subject2 subject3) :END: #+BEGIN_SRC emacs-lisp (read (org-entry-get (point) SUBJECT)) #+END_SRC #+RESULTS: | quote | (subject1 subject2 subject3) | * Second heading :PROPERTIES: :SUBJECT: subject1 subject2 subject3 :END: delimited strings. You have to split them them yourself later if you are using the properties in code. You can delimit on spaces, commas, etc... depending on your subjects. #+BEGIN_SRC emacs-lisp (split-string (org-entry-get (point) SUBJECT)) #+END_SRC #+RESULTS: | subject1 | subject2 | subject3 | They are both pretty flexible. Erik Hetzner e...@e6h.org writes: At Fri, 01 Aug 2014 01:21:47 +0200, Thorsten Jolitz wrote: Hi List, here is my first take of rewriting `org-entry-properties'. The existing function predates the new parser and some Org variables, and thus does the parsing and the property classification itself. The new version leaves parsing to the parser and property classification (mostly) to existing Org variables, resulting in much simpler code. […] Hi Thorsten, This doesn’t directly related to this work, but I have been trying to come up with a workflow for using org-mode for research and have had trouble with the fact that user properties cannot be multi-valued. So if a user wants to assign subjects to an entry, they need to figure some way to assign multiple subjects. There are workarounds, but it would be helpful if user properties could be multivalued. I don’t know if this is feasible given the current codebase; when I looked into it, it seemed pretty difficult. best, Erik -- --- John Kitchin Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu
[O] How to disable block evaluation results being wrapped with a single character like =?
Hi, Sometimes block evaluation results are wrapped with a single character like =. When exporting to latex, the results block is lost. How may one force block evaluation always to be wrapped properly for export to latex? org 8.2.7a Kind regards, Grant Rettke | ACM, ASA, FSF, IEEE, SIAM g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson
Re: [O] [BUG] Re: error in only text exporter
Hello, Eric Abrahamsen e...@ericabrahamsen.net writes: This bug was introduced in dd6b4ff -- in `org-ascii-filter-paragraph-spacing', the function body was originally protected by a: (when (wholenump org-ascii-paragraph-spacing) ...) which was taken out, meaning that the default value of 'auto falls through to `org-export-data' and causes an explosion. I've cc'd Nicolas, who will know what to do! Fixed. Thanks to you and Xebar Saram. Regards, -- Nicolas Goaziou
Re: [O] [POLL] Syntax change: make \[...\] non-inline (+1)
It's a bit more complicated than that: one upgrades org at some opportune moment, then three months/years/centuries later, tries to use that presentation that worked perfectly before - boom. If you go back and check all your old presentations each time you upgrade org, you are, I would guess, the exception, not the rule. I certainly don't do that Well, if I reuse an old presentation I usually use the old pdf. I generally put displays in separate paragraphs, I rarely use autofill[fn:1] and I'm happy to do M-q on individual paragraphs instead, but if I happen to do it on the wrong paragraph (backtraces, code fragments, displayed equations), undo is easy enough. The problem with that is that a displayed equation should NOT start a new paragraph (in the generated LaTeX file). This is because if it does then LaTeX puts more (vertical) space than desirable. Regards, Federico
Re: [O] [POLL] Syntax change: make \[...\] non-inline (+1)
Federico Beffa be...@ieee.org writes: It's a bit more complicated than that: one upgrades org at some opportune moment, then three months/years/centuries later, tries to use that presentation that worked perfectly before - boom. If you go back and check all your old presentations each time you upgrade org, you are, I would guess, the exception, not the rule. I certainly don't do that Well, if I reuse an old presentation I usually use the old pdf. Well, if you are lucky enough to have a static presentation that will cover the past and present as well as the future, fine. But most of mine are templates that incorporate the latest set of numbers: the old pdf will not cut it. I suspect that most people do something similar at least some of the time. It is then that that (mostly forgotten) update from a couple of weeks ago that broke backwards compatibility will bite. I generally put displays in separate paragraphs, I rarely use autofill[fn:1] and I'm happy to do M-q on individual paragraphs instead, but if I happen to do it on the wrong paragraph (backtraces, code fragments, displayed equations), undo is easy enough. The problem with that is that a displayed equation should NOT start a new paragraph (in the generated LaTeX file). This is because if it does then LaTeX puts more (vertical) space than desirable. It's a matter of perspective: I don't expect org to replace latex (but I realize that some people do). -- Nick
[O] [PATCH] problem with size of inline images
Hello: I've noticed a problem around line 19171 of org.el. The size of images is supposed to be controlled by attributes and by `org-image-actual-width'. But it seems like the use of `when', `save-match-data' and `string-to-number' are in the wrong order in this region, so that `(match-string 1)' is not defined properly when it's evaluated. The following instructions should allow you to reproduce the issue: Run this: #+BEGIN_SRC shell wget http://www.lisperati.com/lisplogo_warning_256.png -O lisp_warning.png #+END_SRC Then: [[elisp:(setq org-image-actual-width '(1200))]] [[elisp:(org-toggle-inline-images)]] #+ATTR_ORG: :width 256 [[file:./lisp_warning.png]] ... and the attached patch fixed the problem for me. save-match-data.patch Description: Binary data
Re: [O] ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.
Alexis flexibe...@gmail.com writes: Hi all, i'm pleased to announce the initial release of org-vcard, a package for Org-based export and import of vCards: * Backwards-compatible with org-contacts.el. org-vcard comes with a built-in contacts style called 'flat', which adheres to org-contacts' method of structuring contacts and contact information. It not only supports the properties specified in org-contacts.el, but many other properties as well. * Basic support for vCard 4.0, 3.0 and 2.1. org-vcard is working towards full compliance with the vCard 4.0 (RFC 6350), 3.0 (RFC 2426 and RFC 4770) and 2.1 specifications. * New contacts style: 'tree'. Is it possible support this style? #+begin_comment * People ** Joan Smith :PROPERTIES: :KIND: individual :FIELDTYPE: name :END: *** Cell :PROPERTIES: :FIELDTYPE: cell-folder :END: 999 991 999 992 999 993 999 994 999 995 *** Email :PROPERTIES: :FIELDTYPE: emails-folder :END: address1@hidden address2@hidden address3@hidden address4@hidden address5@hidden #+end_comment
Re: [O] ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.
Alexis flexibe...@gmail.com writes: * New contacts style: 'tree'. Is this tree style possible? #+begin-comment * People ** Joan Smith :PROPERTIES: :KIND: individual :FIELDTYPE: name :END: *** Cell :PROPERTIES: :FIELDTYPE: cells-folder :END: 999 991 999 992 999 993 999 994 999 995 *** Email :PROPERTIES: :FIELDTYPE: emails-folder :END: address1@hidden address2@hidden address3@hidden address4@hidden address5@hidden #+end-comment
Re: [O] ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.
Feng Shu writes: Is it possible support this style? In general, i'd prefer not to implement support /myself/ for everyone's preferred style; the idea is that people implement their own style, including: * the relevant mapping structure which maps Org properties to vCard properties/types; * the org-vcard-export-from-[new style] function; and * the org-vcard-import-to-[new style] function. And, preferably, new tests to accompany the new style. :-) Then, if a new style turns out to be particularly popular, i'll consider including it in org-vcard by default. Having said all that, as a proof-of-concept, i'll try to create a mapping and export function for the style you describe, for vCard 4.0, and will post the relevant code here. :-) Alexis.
Re: [O] How to disable block evaluation results being wrapped with a single character like =?
I'm somewhat confused by the wrapped in = part, but I think you are looking for 'C-h v org-babel-min-lines-for-block-output'. Best, Ista On Sun, Aug 3, 2014 at 3:03 PM, Grant Rettke g...@wisdomandwonder.com wrote: Hi, Sometimes block evaluation results are wrapped with a single character like =. When exporting to latex, the results block is lost. How may one force block evaluation always to be wrapped properly for export to latex? org 8.2.7a Kind regards, Grant Rettke | ACM, ASA, FSF, IEEE, SIAM g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson
[O] cant get org-protocol right
I tried to setup here org-protocol with firefox, first the docu is very old does refer to gnome 2: http://orgmode.org/worg/org-contrib/org-protocol.html#sec-3-1 So after searching around I found a howto to make the protocol known by apps with a desktop file and the command update-desktop-database like descripted here: http://stackoverflow.com/questions/7464951/how-to-make-org-protocol-work I have following in my init.el: (require 'org-protocol) (setq org-protocol-default-template-key l) (setq org-capture-templates '((t Todo entry (file+headline ~/notes/notes.org BLA) * TODO %?\n %i\n %a) (l Link entry (file+olp ~/notes/notes.org Web Links) * %a\n %?\n %i) its running in servermode. If I call it manually at least with org-capture links it works like excepted: emacsclient org-protocol://capture://http://slash.org/ I get a capture buffer and can add that url and it gets added. Now the strange behaviour, with that desktop file I got firefox to ask at least for a programm if I enter there such a url, and I choose org-protocol, what I get as choice from the desktop file. But then nothing happens in emacs. So again pasting this url into epiphany, emacs opens a new file buffer with the name: ~org-protocol:/capture/http:/slash.org/ (its a fundamental buffer) So I dont know why but I tried the same link in epiphany a bit different: org-protocol:/capture://slash.org so removing one of the slashes after org-protocol helps also he doesnt like the http:// in the string. So do u think thats a gnome bug (I am using fedora 20 with the gnome COPR). here is my org-protocol.desktop file: [Desktop Entry] Name=org-protocol Exec=emacsclient '%u' Type=Application Terminal=false Categories=System; MimeType=x-scheme-handler/org-protocol; thanx for any advise!
Re: [O] What is the best in-Emacs presentation mode for org-files today?
Bastien b...@gnu.org writes: Hi Grant, Grant Rettke g...@wisdomandwonder.com writes: What are you opinions on the best mode for doing: 1. Presentations inside of Emacs 2. Using all the options available for org mode while in the presentation ... org-mode. I've found out that tweaking the font size and navigating through an Emacs buffer is often good enough for presentations. I agree, full screen and large font is often sufficient. However... When I want more I use the following. https://github.com/eschulte/epresent Best, Eric -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D (see https://u.fsf.org/yw)
Re: [O] [BABEL] Can all languages deal with multi-line headers?
Thorsten Jolitz tjol...@gmail.com writes: Hi List, I wonder if I can assume that all ob-xxx.el languages, even those written before the new parser/exporter framework existed, know how to deal with multi-line headers like: , | #+name: foo | #+header_args: :var x=bar | #+begin_src lang | ... | #+end_src ` (I would think that argument parsing is done by the framework-core and was thus updated once and for all languages with Org 8+, but want to be sure). Yes, this is true of all languages however you have the syntax wrong in your example. See the manual. (info (org)Code block specific header arguments) -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D (see https://u.fsf.org/yw)
Re: [O] [BUG] src_blocks - :results raw and replace don't work together
Nick Dokos ndo...@gmail.com writes: Thorsten Jolitz tjol...@gmail.com writes: Hi List, evaluating this 3 times does not work as expected: , | * A | | #+header: :results raw replace | #+begin_src emacs-lisp | (+ 2 2) | #+end_src | | #+results: | 4 | 4 | 4 ` Independent from argument order, 'replace' (which should be default anyway) is ignored. Right - `raw' inserts results without delimiters so org has no idea where they end and cannot delete them (try org-babel-remove-result) or replace them. Well said Nick, this is a natural limitation. See the drawer portion of the following page of the manual. (info (org)Results) In general checking the manual before posting to the ML is a good idea. -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D (see https://u.fsf.org/yw)
Re: [O] How does org-babel-post-tangle-hook work?
This says that when the hook is executed, the current buffer (as identified by the `current-buffer' function) will be a buffer visiting the file of the tangled code. Grant Rettke g...@wisdomandwonder.com writes: Hi, In this document http://orgmode.org/manual/Extracting-source-code.html#Extracting-source-code the hook 'org-babel-post-tangle-hook is explained as , | This hook is run from within code files tangled by org-babel-tangle. Example applications could include post-processing, compilation or evaluation of tangled code files. ` I know what a hook is and how to use them and where they run. My trouble is that I don't understand what this documentation is saying. Is it saying that if this hook exists in a file that was tangled by org that it will be executed? If so does it only work for elisp files or any kind of file? Kind regards, Grant Rettke | ACM, ASA, FSF, IEEE, SIAM g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D (see https://u.fsf.org/yw)
Re: [O] bug in lisp code blocks
Hi Mark,
Thanks for the example, I've just pushed up a fix.
Best,
Eric
Mark Scala marksc...@gmail.com writes:
Thanks, Bastien, for helping me report this bug more effectively.
This email summarizes all the information I have about this bug and
how to reproduce it. The problem is that a comment which appears as
the _last_ line of a (common) lisp code block causes an error when
that block is evaluated with C-c C-c. Here's how to reproduce it:
1. You will need to have SBCL and Slime
installed. Your distribution of linux probably has a good enough
SBCL (I'm using 1.2.0 in Arch linux). The easiest way to get the
latest version of Slime is with Quicklisp, which you can find here
(together with instructions to install):
http://www.quicklisp.org/beta/.
Once you have Quicklisp installed and loaded, installing Slime is a
matter of calling (ql:quickload swank) at the sbcl repl.
Note: I am also able to reproduce the bug using clisp:
- GNU CLISP 2.49 (2010-07-07) (built on
var-lib-archbuild-extra-x86_64-barthalion)
2. Start emacs with the following as the entire init.el (of course,
you'll probably have to modify the paths).
#+BEGIN_SRC emacs-lisp
(add-to-list 'load-path (expand-file-name ~/opt/org-mode/lisp))
(require
'org)
(org-babel-do-load-languages
'org-babel-load-languages
'((lisp . t)))
(setq inferior-lisp-program /usr/bin/sbcl)
(add-to-list 'load-path
~/quicklisp/dists/quicklisp/software/slime-2.8)
(require 'slime)
#+END_SRC
Note: I've also just reproduced the bug using the version of org-mode
that ships with Emacs 24:
- Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @
/usr/share/emacs/24.3/lisp/org/)
3. Finally, create a new org file and insert this block:
#+BEGIN_SRC lisp :results output
(format t Hello world.)
;; comment after, causes crash when block is evaluated with C-c C-c
#+END_SRC
If you now evaluate the block with C-c C-c, you should get an EOF
error. Here is a piece of the debugger report:
#+BEGIN_QUOTE
end of file on #SB-IMPL::STRING-INPUT-STREAM {1003F862D3}
[Condition of type END-OF-FILE]
#+END_QUOTE
It appears that the bug is caused by a comment string that is the last
element of the block. Comments elsewhere do not cause this error.
Here are the versions strings of the software I'm running:
- GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.12.2)
of 2014-06-11 on var-lib-archbuild-staging-x86_64-jgc
- Org-mode version 8.3beta (release_8.3beta-51-g02f2d5 @
/home/mark/opt/org-mode/lisp/)
- SBCL 1.2.0
On Tue, Jul 29, 2014 at 9:13 AM, Bastien b...@gnu.org wrote:
Hi Mark,
you forgot to CC the list -- please do so, so that anyone can help
fixing the problem.
All this new information is important. A complete recipe would take
the user from a bare emacs -Q to an emacs with a sbcl connection and
slime, and explain the steps for launching sbcl, connecting via slime,
etc.
Assume the ones who may fix the problem (like me and other maintainers)
are not 100% familiar with Emacs/slime/sbcl, even though they can follow
good recipes easily.
Thanks for your efforts!
PS: The hint about the last commented line triggered the bug is
important and will certainly lead to a quick fix.
--
Bastien
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)
Re: [O] [RFC] Rewrite `org-entry-properties' using parser
Hi John,
Thanks for the tips! I have been using this:
* Foo
:PROPERTIES:
:subject: Bar; Baz
:END:
This allows me to search with subject={Bar}, which is very helpful.
But it would be nice if org supported multi-valued properties. Again,
though, I don’t know how hard this would be.
best, Erik
At Sun, 03 Aug 2014 14:59:02 -0400,
John Kitchin wrote:
I have used the following approaches in the past:
Lisp lists, and use read later to get them.
* Some heading
:PROPERTIES:
:SUBJECT: '(subject1 subject2 subject3)
:END:
#+BEGIN_SRC emacs-lisp
(read (org-entry-get (point) SUBJECT))
#+END_SRC
#+RESULTS:
| quote | (subject1 subject2 subject3) |
* Second heading
:PROPERTIES:
:SUBJECT: subject1 subject2 subject3
:END:
delimited strings. You have to split them them yourself later if you
are using the properties in code. You can delimit on spaces, commas, etc...
depending on your subjects.
#+BEGIN_SRC emacs-lisp
(split-string (org-entry-get (point) SUBJECT))
#+END_SRC
#+RESULTS:
| subject1 | subject2 | subject3 |
They are both pretty flexible.
Erik Hetzner e...@e6h.org writes:
At Fri, 01 Aug 2014 01:21:47 +0200,
Thorsten Jolitz wrote:
Hi List,
here is my first take of rewriting `org-entry-properties'.
The existing function predates the new parser and some Org variables,
and thus does the parsing and the property classification itself. The
new version leaves parsing to the parser and property classification
(mostly) to existing Org variables, resulting in much simpler code.
[…]
Hi Thorsten,
This doesn’t directly related to this work, but I have been trying to
come up with a workflow for using org-mode for research and have had
trouble with the fact that user properties cannot be multi-valued. So
if a user wants to assign subjects to an entry, they need to figure
some way to assign multiple subjects.
There are workarounds, but it would be helpful if user properties
could be multivalued. I don’t know if this is feasible given the
current codebase; when I looked into it, it seemed pretty difficult.
best, Erik
--
---
John Kitchin
Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
--
Sent from my free software system http://fsf.org/.
Re: [O] [RFC] Rewrite `org-entry-properties' using parser
Hi Erik,
2014ko abuztuak 3an, Erik Hetzner-ek idatzi zuen:
Hi John,
Thanks for the tips! I have been using this:
* Foo
:PROPERTIES:
:subject: Bar; Baz
:END:
This allows me to search with subject={Bar}, which is very helpful.
But it would be nice if org supported multi-valued properties.
It does, at least to a first approximation. Look at the functions
described in:
(info (org) Using the property API)
I’m not sure how well this feature is integrated with agenda
search/filtering, though – maybe you should give it a try.
--
Aaron Ecay
[O] HTML lists are including paragraphs (lip…/p/li)
Hi. With latest org I'm getting lip…/p/li, which makes no sense; it should be li…/li Aren't there tests to find this type of breakages in export? Example: - hola - uno - dos - tres Is exported to: ul class=org-ul lip hola /p /li lip uno /p ul class=org-ul lidos /li /ul /li lip tres /p /li /ul
