Re: [O] Problems with capture and lisp code

Hello, Thomas Holst writes: > for my work flow I would like to set up a capture template based on the > ideas described in: > > http://www.jboecker.de/2010/04/14/general-reference-filing-with-org-mode.html#sec-5 > > The original is based on remember but I want to use

Re: [O] Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/)

Hello, Derek Feichtinger writes: > The thing which made it hard for me to identify the initial problem was > that the test CLOCK lines I had in the testing file where placed there > without a heading. When later in the day I wanted to clock in to my tasks, > I then just ended

Re: [O] [RFC] Change \[..\] and $$...$$ into elements

Hello, Rasmus writes: > What's wrong with equation (potentially coupled with mathtools for > handling numbering automatically)? Is it worth breaking old documents > (irrespective of org-lint) for this inconvenience? Actually, the idea behind this patch is to mimic the expected

[O] Problems with capture and lisp code

Hi, for my work flow I would like to set up a capture template based on the ideas described in: http://www.jboecker.de/2010/04/14/general-reference-filing-with-org-mode.html#sec-5 The original is based on remember but I want to use capture. The principle is as follows: In the capture template

Re: [O] Renaming of +NAME for code blocks to in HTML export, no longer user defined

Hello, Adam Aviv writes: > Interesting. I don't know if it is a bug, though, as this seems intentional > and matches my experience. The idea being that if you want to label > something, you use the :name tag, but this will make it so the second item > is evaluated, producing a

Re: [O] Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/)

Hi Nicolas Ok, that makes sense, then. Probably there are other users who indeed will rely on clocking in non-agenda files. The thing which made it hard for me to identify the initial problem was that the test CLOCK lines I had in the testing file where placed there without a heading. When later

Re: [O] quote block interrupts text?

Hello, Lawrence Bottorff writes: > I've got this > > ** The quick red fox > >#+BEGIN_QUOTE >red foxes are great >#+END_QUOTE > >jumped over the lazy brown dog. > > But when I export to HTML I see the > > > > 1.5 >The quick red fox >

Re: [O] [PATCH] org-latex-compile timestamp checks

Hello, Rasmus writes: > Since this is a bugfix I guess you should use org-sublist (*shiver*) in > maint and cl-subseq in master. We can’t use cl-lib in maint, right > Nicolas? Absolutely. >> Eventually, I think at least ox-texinfo.el, ox-man.el and ox-groff.el >> need a

Re: [O] [RFC] Change \[..\] and $$...$$ into elements

Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >> What's wrong with equation (potentially coupled with mathtools for >> handling numbering automatically)? Is it worth breaking old documents >> (irrespective of org-lint) for this inconvenience? > >

Re: [O] [PATCH] org-latex-compile timestamp checks

Nicolas Goaziou writes: >>> Eventually, I think at least ox-texinfo.el, ox-man.el and ox-groff.el >>> need a similar trick. >> >> Perhaps there should be an error check in ox-odt as well? I guess the >> only thing that could happen is that the zip/odt can’t be written,

Re: [O] Renaming of +NAME for code blocks to in HTML export, no longer user defined

On Thu, Jan 21, 2016 at 4:20 AM, Nicolas Goaziou wrote: > That and the fact that one might introduce forbidden characters in the > name (e.g., ask the user to know about forbidden characters in the > target format). The generic names are pretty safe. > > Anyway, what

Re: [O] Problems with capture and lisp code

Hi Nicolas, · Nicolas Goaziou wrote: > Hello, > > Thomas Holst writes: > >> for my work flow I would like to set up a capture template based on the >> ideas described in: >> >>

Re: [O] ob-julia, src block execution undefined function org-babel-get-header

Hi Andreas, Andreas writes: > Hi list, > I was hoping to get some help with this issue > > I use: > Org-mode version 8.3.3 (release_8.3.3-468-gf3f4b2) > GNU Emacs 25.1.50.2 (x86_64-pc-linux-gnu, GTK+ Version 3.16.7) of 2016-01-17 > ess-version: 15.09-2 patched [git:

[O] ob-julia, src block execution undefined function org-babel-get-header

Hi list, I was hoping to get some help with this issue I use: Org-mode version 8.3.3 (release_8.3.3-468-gf3f4b2) GNU Emacs 25.1.50.2 (x86_64-pc-linux-gnu, GTK+ Version 3.16.7) of 2016-01-17 ess-version: 15.09-2 patched [git: 6d05ba7c89371764c43e30a436d7166417cabd4d] julia version 0.4.2 I'm

[O] Bug: [PATCH] Tiny timezone bug in ox-icalendar [8.3.3 (release_8.3.3-2-g6bc48c @ /home/rwl/src/org-mode/lisp/)]

Hi all, I finally got annoyed enough to debug a problem with the timezone field in the .ics export of my agenda. Turns out the problem was simple: org-icalendar--vcalendar was being called with the wrong argument order in org-icalendar-export-current-agenda, so the timezone was going into the