Re: [O] Bug: org-columns adds spaces [8.3beta (release_8.3beta-1286-g20795f @ /home/youngfrog/sources/org-mode/lisp/)]

2015-07-18 Thread Nicolas Goaziou
Hello, Nicolas Richard writes: > Nicolas Richard writes: >> The buffer is still marked "unmodified" but there are five space >> characters at the end of the headline. (and this will later confuse org >> element cache which thus give errors, but I guess that's to be >> expected.) > > Meanwhile I

Re: [O] [ox bug] batch export seems to be broken or have changed

2015-07-18 Thread Nicolas Goaziou
Hello, Rasmus writes: > I used to be able to something like > > emacs -Q --file foo.org --batch --no-init-file -f org-latex-export-to-pdf > # tex output > > And everything would work. > > Now I get something like > > emacs -Q --file foo.org --batch --no-init-file -f > org-latex-

[O] getting todo-keywords from org-element-property

2015-07-18 Thread Matt Price
I don't understand how to extract todo-keyword values from a headline using org-element-property. I am trying something like this: (org-element-map (org-element-parse-buffer) 'headline (lambda (item) (print (nth 0 (org-element-property :todo-keyword item))) (when

[O] how the $@%& do you add a property to a plist?

2015-07-18 Thread Matt Price
Hi, I am continuing to work on my marking stuff; it's working really well, actually. I am currently importing a list of student names and emails from a csv file -- this is normally how I get the list of enrolled students. I have modified the defauly settings from our Universities CSV export so I

Re: [O] getting todo-keywords from org-element-property

2015-07-18 Thread Nicolas Goaziou
Hello, Matt Price writes: > I don't understand how to extract todo-keyword values from a headline using > org-element-property. > > I am trying something like this: > > (org-element-map (org-element-parse-buffer) 'headline > (lambda (item) >(print (nth 0 (org-element-proper

Re: [O] how the $@%& do you add a property to a plist?

2015-07-18 Thread Thomas S . Dye
Matt Price writes: > Hi, > > I am continuing to work on my marking stuff; it's working really well, > actually. > > I am currently importing a list of student names and emails from a csv file > -- this is normally how I get the list of enrolled students. I have > modified the defauly settings f

Re: [O] getting todo-keywords from org-element-property

2015-07-18 Thread Matt Price
On Sat, Jul 18, 2015 at 3:59 PM, Nicolas Goaziou wrote: > Hello, > > Matt Price writes: > > > I don't understand how to extract todo-keyword values from a headline > using > > org-element-property. > > > > I am trying something like this: > > > > (org-element-map (org-element-parse-buffer) 'hea

[O] PATCH: make org-mime-htmlize argument optional

2015-07-18 Thread Matt Price
At present, it's difficult to call org-mime-htmlize noninteractively. This trivial patch fixes that. From ebe5dc40bafb55d019d43efe89957c3b50379553 Mon Sep 17 00:00:00 2001 From: Matt Price Date: Sat, 18 Jul 2015 16:14:33 -0400 Subject: [PATCH 3/3] org-mime.el: fix org-mime-htmlize * org-mime.el:

Re: [O] [ox bug] batch export seems to be broken or have changed

2015-07-18 Thread Rasmus
Hi, I hope you had a pleasant break from the PC. Nicolas Goaziou writes: > Rasmus writes: > >> I used to be able to something like >> >> emacs -Q --file foo.org --batch --no-init-file -f >> org-latex-export-to-pdf >> # tex output >> >> And everything would work. >> >> Now I get some

[O] [PATCH] Make html export honor html-viewport option

2015-07-18 Thread Richard Hoskins
* ox-html.el (options-alist) Change html-viewport to honor html-viewport: option in org file. Value of `html-viewport' is being checked by `org-html--build-meta-info', but it could not be changed due to its `options-alist' entry. TINYCHANGE --- lisp/ox-html.el | 2 +- 1 file changed, 1 inserti