Re: [O] Change in ox export for #+DATE keywords
Peter Salazar writes:
> As I mentioned, I'm getting that same error, not just with #+DATE but also
> with #+TITLE, #+AUTHOR, etc. Any one of these is sufficient to break export
> for me.
Yeah further poking has shown they have all broken. I can't quite follow
the logic of the patch as to what the new parse is expecting.
>
> On Fri, Aug 7, 2015 at 3:59 PM, Alex Bennée wrote:
>
>> Hi,
>>
>> I've been using org-mode as a source for my presentations but exporting
>> broke today following an ELPA update. It seems the line:
>>
>> #+DATE: KVM Forum 2015
>>
>> Is no longer acceptable. I think this changed as of:
>>
>> ae9db17482a183e5613428c3abf1c691f86b4ac0
>>
>> I'm not quite sure what the new "parse" is expecting. If I change it to
>> a datestamp I see breakage on other lines like the title:
>>
>> apply: Wrong type argument: listp, #("My presentation title" 0 26 (:parent
>> (#0)))
>>
>> So what form am I meant to be using for these options and why the change?
>>
>> --
>> Alex Bennée
>>
>>
--
Alex Bennée
Re: [O] Change in ox export for #+DATE keywords
Hello, Alex Bennée writes: > I've been using org-mode as a source for my presentations but exporting > broke today following an ELPA update. It seems the line: > > #+DATE: KVM Forum 2015 > > Is no longer acceptable. FWIW, I export it without an error. Do you use a custom export back-end? Regards, -- Nicolas Goaziou
Re: [O] wrong type argument listp... org-element-set-contents
Hello,
Peter Salazar writes:
> I'm getting a strange error whenever I try to export an org file,
> and I'm not sure how to track down the cause. It seemed to start when I
> upgraded to org 8.3.1, but it's hard to tell because this is the first
> time I've exported anything in a week or so.
>
> The error says:
> (wrong-type-argument listp #("Test document" 0 13 (:parent (#1
> org-element-set-contents(#("Test document" 0 13 (:parent (#0
>
> I was able to figure out that the error only occurs when I have an org file
> with document data, e.g. a line like:
>
> #+TITLE: Test document
>
> When I remove that line as well as #+AUTHOR etc, then it exports fine. With
> that line it, it won't export to HTML, LaTeX, or text.
>
> Any suggestions on how to figure out what part of my configuration is
> causing the problem? Here's the complete Backtrace:
> https://gist.github.com/fe45c4d42d52f0ce0e42
I cannot reproduce the problem. Could you provide a backtrace using an
uncompiled Org? (i.e., using `org-reload' with an argument).
Regards,
--
Nicolas Goaziou
Re: [O] wrong type argument listp... org-element-set-contents
Hello,
Peter Salazar wrote:
[...]
> The error says:
> (wrong-type-argument listp #("Test document" 0 13 (:parent (#1
> org-element-set-contents(#("Test document" 0 13 (:parent (#0
Is this the same issue as here?
http://permalink.gmane.org/gmane.emacs.orgmode/99535?
Things may have gone wrong when compiling during the update, so it is
worth trying to uninstall and reinstall.
--
Kyle
Re: [O] latest org from Elpa error: Invalid function: org-babel-header-args-safe-fn
Hello, Xebar Saram wrote: > Hi > > just updated org today and now i get this error on startup: > > > Invalid function: org-babel-header-args-safe-fn > > is this related to the new release? It may be related to an issue with compiling during the package update[1]. Magit has also had problems with this lately (e.g., this issue[2]). Please try to uninstall and reinstall. [1] http://emacs.stackexchange.com/questions/13574/technical-considerations-for-package-maintainers-to-not-use-the-emacs-package-ma [2] https://github.com/magit/magit/issues/2154 -- Kyle
Re: [O] elpa upgrade to 8.3.1 on emacs 24.5
Kaushal wrote: > That's odd. `setq-local` macro was added in emacs 24.3; it is in subr.el. > > (defmacro setq-local (var val) > "Set variable VAR to value VAL in current buffer." > ;; Can't use backquote here, it's too early in the bootstrap. > (list 'set (list 'make-local-variable (list 'quote var)) val)) Perhaps this is an issue with compiling during the update: http://permalink.gmane.org/gmane.emacs.orgmode/99689 -- Kyle
Re: [O] latest org from Elpa error: Invalid function: org-babel-header-args-safe-fn
Hi Kyle i tried uninstall and install with no success best Z On Sat, Aug 8, 2015 at 10:28 AM, Kyle Meyer wrote: > Hello, > > Xebar Saram wrote: > > Hi > > > > just updated org today and now i get this error on startup: > > > > > > Invalid function: org-babel-header-args-safe-fn > > > > is this related to the new release? > > It may be related to an issue with compiling during the package > update[1]. Magit has also had problems with this lately (e.g., this > issue[2]). Please try to uninstall and reinstall. > > [1] > http://emacs.stackexchange.com/questions/13574/technical-considerations-for-package-maintainers-to-not-use-the-emacs-package-ma > [2] https://github.com/magit/magit/issues/2154 > > -- > Kyle >
Re: [O] [bug] canonical context not work in 8.3
Samuel Wales writes: > i compiled it and tried it. it seems improved, to maybe 2.5s. I think it is as good as it can get. You probably have an awful lot of children to display. Anyway, could you provide the same report using an un-compiled Org? A report using ELP (elp-instrument-package and elp-report) would be nice too, as it gives the number of times a function is called. Regards,
Re: [O] 8.3 hangs
Samuel Wales writes: > thanks, suvayu, how do i use this org element minor mode? > > i get hangs quite frequently, for example when sorting in the outline > buffer. The freeze is the consequence of a cache corruption, but it doesn't give information about what caused that corruption (almost certainly without any visible consequence at that time). This minor mode solves this by sending a message in the minibuffer whenever an action corrupts the cache. However, it slows down editing a lot, so it is only reasonable to use it on short documents. If you run it and notice a cache corruption, please report it. Regards,
Re: [O] Change in ox export for #+DATE keywords
Nicolas Goaziou writes: > Hello, > > Alex Bennée writes: > >> I've been using org-mode as a source for my presentations but exporting >> broke today following an ELPA update. It seems the line: >> >> #+DATE: KVM Forum 2015 >> >> Is no longer acceptable. > > FWIW, I export it without an error. Do you use a custom export > back-end? I'm using ox-reveal (for Reveal.js). I'm finding it hard to trigger an actual backtrace so maybe the problem is there. > > > Regards, -- Alex Bennée
Re: [O] fontenc makes pdf non-searchable
Martin Leduc writes: > Hi Bastien, thanks a lot for your response but I finally solved the > issue by installing the package cm-super. Thanks for confirming! -- Bastien
[O] agenda item formatting
In the past I've been pretty happy with the default Agenda formats for display todo items and such. It used to bug me that you couldn't see the lineage of the items in the todo list, but then I discovered org-agenda-prefix-format, and the %b escape for breadcrumbs, and that was good enough. Now I've got a couple of custom blocks where I *really* want to control the formatting exactly, and I'm having difficulty doing that. The docstring says you can use this in org-agenda-prefix-format: %(expression) Eval EXPRESSION and replace the control string by the result I don't know how I'm supposed to use this. I can put a custom function in there, but the function is passed no arguments, and is `eval'ed in a nil environment, so I can't access any dynamic variables. Apparently all it can do is return a string that is unrelated to the item being formatted, which isn't very useful! Probably I'm wrong about that, but I've tried for a while, and can't get it to do anything else. Is there any other way to access the final formatted string for an Agenda item, and doctor it? Thanks! Eric
Re: [O] [bug] canonical context not work in 8.3
Correcting myself,
> I think it is as good as it can get. You probably have an awful lot of
> children to display.
This one may improve the situation:
(defun show-children (&optional level)
(save-excursion
(org-back-to-heading t)
(let* ((current-level (funcall outline-level))
(level (if level (+ (prefix-numeric-value level) current-level)
(save-excursion
(outline-next-heading)
(if (eobp) current-level (funcall outline-level)
(re (format "^\\*\\{%d,%d\\} +" current-level level))
(end (save-excursion (org-end-of-subtree t t
(while (re-search-forward re end t)
(outline-flag-region (line-end-position 0) (line-end-position)
nil)
Would you mind testing it?
Regards,
Re: [O] comment trees in 8.3
Samuel Wales writes: > ok, then i don't understand the code. (i thought that was how it > determined whether it was a commented headline to skip.) (it's nil > but commented headers show.) My bad. I misread your question. It should be non-nil, indeed. What is the return value of (org-in-commented-heading-p) on your pseudo-commented headlines? Regards,
Re: [O] Change in ox export for #+DATE keywords
Alex Bennée writes: > Nicolas Goaziou writes: > >> Hello, >> >> Alex Bennée writes: >> >>> I've been using org-mode as a source for my presentations but exporting >>> broke today following an ELPA update. It seems the line: >>> >>> #+DATE: KVM Forum 2015 >>> >>> Is no longer acceptable. >> >> FWIW, I export it without an error. Do you use a custom export >> back-end? > > I'm using ox-reveal (for Reveal.js). I'm finding it hard to trigger an > actual backtrace so maybe the problem is there. I've had a cursory look at ox-reveal.el[fn:1]. There is a strange thing, indeed. In `org-reveal-template', line 888, (plist-get info :author) should be wrapped within (org-export-data ...). However, it is not related to your error. Therefore, I suspect an installation problem on your side. Regards, [fn:1] https://github.com/yjwen/org-reveal/blob/master/ox-reveal.el
Re: [O] Change in ox export for #+DATE keywords
Nicolas Goaziou writes:
> Alex Bennée writes:
>
>> Nicolas Goaziou writes:
>>
>>> Hello,
>>>
>>> Alex Bennée writes:
>>>
I've been using org-mode as a source for my presentations but exporting
broke today following an ELPA update. It seems the line:
#+DATE: KVM Forum 2015
Is no longer acceptable.
>>>
>>> FWIW, I export it without an error. Do you use a custom export
>>> back-end?
>>
>> I'm using ox-reveal (for Reveal.js). I'm finding it hard to trigger an
>> actual backtrace so maybe the problem is there.
>
> I've had a cursory look at ox-reveal.el[fn:1]. There is a strange thing,
> indeed. In `org-reveal-template', line 888, (plist-get info :author)
> should be wrapped within (org-export-data ...).
>
> However, it is not related to your error. Therefore, I suspect an
> installation problem on your side.
I've tried re-building all my elpa packages as well as doing a plaing
HTML export and I can now get a backtrace:
Debugger entered--Lisp error: (wrong-type-argument listp #("Towards
multi-threaded TCG" 0 26 (:parent (#1
org-element-set-contents(#("Towards multi-threaded TCG" 0 26 (:parent (#0
apply(org-element-set-contents #("Towards multi-threaded TCG" 0 26 (:parent
(#0))) nil)
#[(s) "\306\307\310#\311\312
\211:\204 \313\202\" @9\203! AA\202\" )\"\210\314\315\n
\211:\2043\313\202@ @9\203? AA\202@ )#\210
\316\211\n ;\203V\317\320\f #\202\\\321 A@\f\"* \211;\203n\322 \313\f$\202z A\323 A@\f#\240\210 +\210\nA
A@\240\210\n@\240*\207" [s new old element property value
replace-regexp-in-string "\n" " " mapc #[(blob) "\305
\211;\203 \306\f\307 \n$\202 \fA\310\fA@ \n#\240\210\f+\207" [blob old value
property element :parent org-add-props nil plist-put] 6] nil apply
org-element-set-contents :parent get-text-property 0 plist-get org-add-props
plist-put] 6](#("Towards multi-threaded TCG" 0 26 (:parent (#0
#[(--data) "\211:\204 ;\205 \306\202 @9\205
@)?\206\337 \203,\307 \310\">\206\337\n\2047\311\f\"\202\337\n\312=\203\\\311\f\211:\204J\313\202W
@9\203V AA\202W
)\"\202\337\n>\203\202!\211\203\201\203z\314\315\"\210\202\201B)\316=\203\312;\204\312\n\236A\313\211\203\311@\f
;\203\266\317\320 #\202\275\307
A@ \"*!\210A\211\204\234* \203\202\316=\203\202\n >\203\202 \313
\211\203\201@\211 @ A ;\203\317\320 #\202 \307
A@ \"*!\"!\203w\"#\235\203_\"$\235\203P\321!!\313%\211\203L@%\f%A!\210\f%@!\210A\211\2042*\202w\f!A!\210\f!@!\210\202w\"$\235\203r\311\f\321!!\"\210\202w\f!!\210*A\211\204\350*\n&>\206\337\211:\204\224\313\202\241
@9\203\240 AA\202\241
)?\206\337\322=\203\265\n'>?\206\337\323=\203\303\n(>\206\337\311\f\211:\204\320\313\202\335
@9\203\334 AA\202\335 )\")\207" [--data element --type info
--walk-tree types plain-text plist-get :ignore-list mapc org-data nil throw
--map-first-match objects get-text-property 0 reverse greater-elements elements
fun result first-match --acc --category org-element-secondary-value-alist p
--dolist-tail-- property with-affiliated org-element-all-elements
org-element--parsed-properties-alist kwd-pair value kwd
org-element-dual-keywords org-element-multiple-keywords line no-recursion
org-element-greater-elements org-element-all-objects] 6](#("Towards
multi-threaded TCG" 0 26 (:parent (#0
mapc(#[(--data) "\211:\204 ;\205 \306\202 @9\205
@)?\206\337 \203,\307 \310\">\206\337\n\2047\311\f\"\202\337\n\312=\203\\\311\f\211:\204J\313\202W
@9\203V AA\202W
)\"\202\337\n>\203\202!\211\203\201\203z\314\315\"\210\202\201B)\316=\203\312;\204\312\n\236A\313\211\203\311@\f
;\203\266\317\320 #\202\275\307
A@ \"*!\210A\211\204\234* \203\202\316=\203\202\n >\203\202 \313
\211\203\201@\211 @ A ;\203\317\320 #\202 \307
A@ \"*!\"!\203w\"#\235\203_\"$\235\203P\321!!\313%\211\203L@%\f%A!\210\f%@!\210A\211\2042*\202w\f!A!\210\f!@!\210\202w\"$\235\203r\311\f\321!!\"\210\202w\f!!\210*A\211\204\350*\n&>\206\337\211:\204\224\313\202\241
@9\203\240 AA\202\241
)?\206\337\322=\203\265\n'>?\206\337\323=\203\303\n(>\206\337\311\f\211:\204\320\313\202\335
@9\203\334 AA\202\335 )\")\207" [--data element --type info
--walk-tree types plain-text plist-get :ignore-list mapc org-data nil throw
--map-first-match objects get-text-property 0 reverse greater-elements elements
fun result first-match --acc --category org-element-secondary-value-alist p
--dolist-tail-- property with-affiliated org-element-all-elements
org-element--parsed-properties-alist kwd-pair value kwd
org-element-dual-keywords org-element-multiple-keywords line no-recursion
org-element-greater-elements org-element-all-objects] 6] (#("Towards
multi-threaded TCG" 0 26 (:parent #0
#[(--data) "\211:\204 ;\205 \306\202 @9\205
@)?\206\337 \203,\307 \310\">\206\337\n\2047\311\f\"\202\337\n\312=\203\\\311\f\211:\204J\313\202W
Re: [O] Emacs-Orgmode Archive search fails
On 08/04/2015 08:00 PM, Bastien Guerry wrote: Hi Charles, Charles Millar writes: It has been a while since I searched the mailing list archives. Did I miss an announcement or is the search engine broken? Did you get any answer by Lars on this? Thanks, No. I just tried the mail list archive search again with simply "latex" and "LaTeX" and still the one and only result is to a February 2015 message. Other similar simple searches yield nothing. Charlie
Re: [O] Change in ox export for #+DATE keywords
Alex Bennée writes: > Nicolas Goaziou writes: > >> Alex Bennée writes: >> >>> Nicolas Goaziou writes: FWIW, I export it without an error. Do you use a custom export back-end? >>> >>> I'm using ox-reveal (for Reveal.js). I'm finding it hard to trigger an >>> actual backtrace so maybe the problem is there. >> >> I've had a cursory look at ox-reveal.el[fn:1]. There is a strange thing, >> indeed. In `org-reveal-template', line 888, (plist-get info :author) >> should be wrapped within (org-export-data ...). >> >> However, it is not related to your error. Therefore, I suspect an >> installation problem on your side. > > I've tried re-building all my elpa packages as well as doing a plaing > HTML export and I can now get a backtrace: > OK ignore that. If I do a -q -l mininit.el I get a more useful backtrace that reveals problems with ox-reveal.el which I can address. -- Alex Bennée
Re: [O] wrong type argument listp... org-element-set-contents
Sure, I'll try that. I'm not quite sure how to figure out what
argument org-export-dispatch takes. Something like this? (org-reload
(org-export-dispatch 'html))
On Sat, Aug 8, 2015 at 3:29 AM, Nicolas Goaziou
wrote:
> Hello,
>
> Peter Salazar writes:
>
> > I'm getting a strange error whenever I try to export an org file,
> > and I'm not sure how to track down the cause. It seemed to start when I
> > upgraded to org 8.3.1, but it's hard to tell because this is the first
> > time I've exported anything in a week or so.
> >
> > The error says:
> > (wrong-type-argument listp #("Test document" 0 13 (:parent (#1
> > org-element-set-contents(#("Test document" 0 13 (:parent (#0
> >
> > I was able to figure out that the error only occurs when I have an org
> file
> > with document data, e.g. a line like:
> >
> > #+TITLE: Test document
> >
> > When I remove that line as well as #+AUTHOR etc, then it exports fine.
> With
> > that line it, it won't export to HTML, LaTeX, or text.
> >
> > Any suggestions on how to figure out what part of my configuration is
> > causing the problem? Here's the complete Backtrace:
> > https://gist.github.com/fe45c4d42d52f0ce0e42
>
> I cannot reproduce the problem. Could you provide a backtrace using an
> uncompiled Org? (i.e., using `org-reload' with an argument).
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
Re: [O] FYI: habits in agenda view with 8.3.1, order of drawers
Hello, Michael Welle writes: > after the latest update from the package repository, tasks, that have the > property style set to habit, did not show up as habits in the agenda > anymore, i.e. the bar graph isn't shown. It turned out that the task > description looks like follows: > > * TODO foo > SCHEDULED: <2015-08-01 Sat ++1d> >:LOGBOOK: >:END: >:PROPERTIES: >:STYLE:habit >:LAST_REPEAT: [2015-08-01 Sat 17:33] >:END: > >[2015-04-29 Wed] > > If I put the properties drawer above the logbook drawer it works again > as expected. In other words, the order of the drawers seem to matter now. > Is that wanted/documented behaviour? Yes it is. See release notes, first entry (i.e., section "Incompatible changes"). Regards, -- Nicolas Goaziou
Re: [O] wrong type argument listp... org-element-set-contents
Peter Salazar writes: > Sure, I'll try that. I'm not quite sure how to figure out what > argument org-export-dispatch takes. Something like this? (org-reload > (org-export-dispatch 'html)) I meant C-u M-x org-reload. Then regular export (e.g., C-c C-e l L). Regards,
Re: [O] latest org from Elpa error: Invalid function: org-babel-header-args-safe-fn
Unfortunately I now can't reproduce the problem, so I can't check if
my suggestion to byte compile ob-R.el works or not. When I did observe
the issue you describe that seemed to fix it, and at least one other
person confirmed that it worked for them as well.
Since it doesn't work for you I suggest removing org-plus-contrib (or
org), starting emacs with 'emacs -Q' and running something like
(require 'package)
(add-to-list 'package-archives
'("org" . "http://orgmode.org/elpa/";) t)
(package-initialize)
(package-install 'org-plus-contrib)
;; or (package-install 'org)
Best,
Ista
On Sat, Aug 8, 2015 at 12:07 AM, Xebar Saram wrote:
> Hi Ista
>
> i did do a byte compiling but that didnt help. i got this message when i did
> byte compile
>
> Compiling no file at Sat Aug 8 07:06:30 2015
> Leaving directory `/home/zeltak/.emacs.d/elpa/ace-isearch-20150807.1803'
> Compiling file /home/zeltak/.emacs.d/elpa/org-20150805/ob-R.el at Sat Aug 8
> 07:06:55 2015
> Entering directory `/home/zeltak/.emacs.d/elpa/org-20150805/'
> ob-R.el:72:11:Warning: reference to free variable
> `org-babel-safe-header-args'
>
> In end of data:
> ob-R.el:470:1:Warning: the following functions are not known to be defined:
> org-babel-header-args-safe-fn, org-babel-graphical-output-file
>
> best
>
> Z
>
>
> On Fri, Aug 7, 2015 at 10:01 PM, Ista Zahn wrote:
>>
>> We discussed this already in another thread[0]. The upshot was run
>> "M-x byte-compile-file" on ob-R.el.
>>
>> Best,
>> Ista
>> [0] https://www.mail-archive.com/emacs-orgmode@gnu.org/msg98762.html
>>
>> On Fri, Aug 7, 2015 at 12:47 PM, Xebar Saram wrote:
>> >
>> > Thx for the response Bastien
>> >
>> > i removed (require 'org-install) from my init.el file (correct?) and
>> > restarted emacs but get the same error
>> >
>> > Invalid function: org-babel-header-args-safe-fn
>> >
>> > i also tried now to downgrade to previous version from 3/8/15 and the
>> > error
>> > is gone so its 100% reproducible with the 5/8/15 elpa version
>> >
>> > thx again
>> >
>> > Z
>> >
>> >
>> >
>> > On Fri, Aug 7, 2015 at 6:33 PM, Bastien wrote:
>> >>
>> >> Hi Xebar,
>> >>
>> >> try removing (require 'org-install), it is not needed since long.
>> >>
>> >> --
>> >> Bastien
>> >
>> >
>
>
Re: [O] wrong type argument listp... org-element-set-contents
Yes! That worked. What does this mean? I tried going to package-list-packages and uninstalling and reinstalling org, but that didn't help. What's my next step? On Sat, Aug 8, 2015 at 9:27 AM, Nicolas Goaziou wrote: > Peter Salazar writes: > > > Sure, I'll try that. I'm not quite sure how to figure out what > > argument org-export-dispatch takes. Something like this? (org-reload > > (org-export-dispatch 'html)) > > I meant C-u M-x org-reload. Then regular export (e.g., C-c C-e l L). > > Regards, >
Re: [O] wrong type argument listp... org-element-set-contents
Peter Salazar wrote:
> Yes! That worked. What does this mean?
>
> I tried going to package-list-packages and uninstalling and reinstalling
> org, but that didn't help. What's my next step?
>
> On Sat, Aug 8, 2015 at 9:27 AM, Nicolas Goaziou
> wrote:
>
>> Peter Salazar writes:
>>
>> > Sure, I'll try that. I'm not quite sure how to figure out what
>> > argument org-export-dispatch takes. Something like this? (org-reload
>> > (org-export-dispatch 'html))
>>
>> I meant C-u M-x org-reload. Then regular export (e.g., C-c C-e l L).
Nicolas might have a better suggestion of what to do next, but I think
it means the state of your Emacs session was interfering with the
correct compilation. Since 'C-u M-x org-reload' forced an uncompiled
reload, you could try uninstalling/installing the package again. Or you
try Ista's snippet[1] for installing in a fresh session:
Since it doesn't work for you I suggest removing org-plus-contrib
(or org), starting emacs with 'emacs -Q' and running something like
(require 'package)
(add-to-list 'package-archives
'("org" . "http://orgmode.org/elpa/";) t)
(package-initialize)
(package-install 'org-plus-contrib)
;; or (package-install 'org)
[1] http://permalink.gmane.org/gmane.emacs.orgmode/99708
--
Kyle
[O] Pass options to \columns{} environment in beamer export
I have an org beamer file with the following header since I generally
prefer top-alignment for frames:
#+latex_class_options: [aspectratio=169,t,presentation,bigger,fleqn]
I have some columns where I want vertically centered text, and am not
sure how to pass the option to \columns{} instead of an individual
\column{}.
Worg says this(http://orgmode.org/worg/exporters/beamer/ox-beamer.html):
"All contiguous environments are automatically wrapped in a columns
environment, although it can be forced at any point by setting the
BEAMER_env property to columns. This might be handy if you want to
pass special options."
But where does that go? I have this:
* Test
** Col1 :BMCOL:
:PROPERTIES:
:BEAMER_col: 0.5
:END:
- blah
- blah
- blah
** Col2 :BMCOL:
:PROPERTIES:
:BEAMER_col: 0.5
:END:
- blah
- blah
- blah
I want this (note the [c] to override my document-wide [t] option):
\begin{frame}[label={sec:orgheadline1}]{Test}
\begin{columns}[c]
\begin{column}{0.5\columnwidth}
\begin{itemize}
\item blah
\item blah
\item blah
\end{itemize}
\end{column}
\begin{column}{0.5\columnwidth}
\begin{itemize}
\item blah
\item blah
\item blah
\end{itemize}
\end{column}
\end{columns}
\end{frame}
\end{document}
But if I add =:beamer_env: columns= to both subheadlines, I get each
in it's own \begin/end{columns} environment, which is not what I want.
I just need a single columns env, with the [c] option passed, that
encompasses both individual column environments.
John
Re: [O] wrong type argument listp... org-element-set-contents
Yes, that worked! Thank you so much!
On Sat, Aug 8, 2015 at 11:59 AM, Kyle Meyer wrote:
> Peter Salazar wrote:
> > Yes! That worked. What does this mean?
> >
> > I tried going to package-list-packages and uninstalling and reinstalling
> > org, but that didn't help. What's my next step?
> >
> > On Sat, Aug 8, 2015 at 9:27 AM, Nicolas Goaziou
> > wrote:
> >
> >> Peter Salazar writes:
> >>
> >> > Sure, I'll try that. I'm not quite sure how to figure out what
> >> > argument org-export-dispatch takes. Something like this? (org-reload
> >> > (org-export-dispatch 'html))
> >>
> >> I meant C-u M-x org-reload. Then regular export (e.g., C-c C-e l L).
>
> Nicolas might have a better suggestion of what to do next, but I think
> it means the state of your Emacs session was interfering with the
> correct compilation. Since 'C-u M-x org-reload' forced an uncompiled
> reload, you could try uninstalling/installing the package again. Or you
> try Ista's snippet[1] for installing in a fresh session:
>
> Since it doesn't work for you I suggest removing org-plus-contrib
> (or org), starting emacs with 'emacs -Q' and running something like
>
> (require 'package)
> (add-to-list 'package-archives
> '("org" . "http://orgmode.org/elpa/";) t)
> (package-initialize)
> (package-install 'org-plus-contrib)
> ;; or (package-install 'org)
>
>
> [1] http://permalink.gmane.org/gmane.emacs.orgmode/99708
>
> --
> Kyle
>
Re: [O] wrong type argument listp... org-element-set-contents
Peter Salazar wrote: > Yes, that worked! Thank you so much! Great. Just for future reference, these were the steps that worked? - C-u M-x org-reload - Uninstall and then reinstall from package-list-packages menu. -- Kyle
Re: [O] latest org from Elpa error: Invalid function: org-babel-header-args-safe-fn
Xebar Saram wrote: > Hi Kyle > > i tried uninstall and install with no success What if you do 'C-u M-x org-reload' before this uninstall/reinstall? -- Kyle
[O] Update tables 8.3.1
I'm beginning to wonder if upgrading to 8.3.1 is a mistake. I had no trouble at all with 8.2.10, but many problems with 8.3.1. My latest issue follows. When I update a table (using C-u C-c *, or C-u C-c C-c, or M-x org-table-recalculate), the table doesn't update and I get the following error message: Wrong type argument: number-or-marker-p, (4) The number in parentheses varies depending on the table. Here are two examples of table formulas I have, formulas which worked perfectly until I upgraded to 8.3.1: #+TBLFM: $tot=vsum(@<<..@>>>);%.2f #+TBLFM: $13=vsum($3..$12);%.1f::$qs=$q1+$q2;%.1f I can provide example tables if necessary. I tried the example table given in section 3.5.10 of the documentation and I get the same error. |---+-++++---+--| | | Student | Prob 1 | Prob 2 | Prob 3 | Total | Note | |---+-++++---+--| | ! | | P1 | P2 | P3 | Tot | | | # | Maximum | 10 | 15 | 25 |50 | 10.0 | | ^ | | m1 | m2 | m3 |mt | | |---+-++++---+--| | # | Peter | 10 | 8 | 23 |41 | 8.2 | | # | Sam | 2 | 4 | 3 | 9 | 1.8 | |---+-++++---+--| | | Average |||| 25.0 | | | ^ | ||||at | | | $ | max=50 |||| | | |---+-++++---+--| #+TBLFM: $6=vsum($P1..$P3)::$7=10*$Tot/$max;%.1f::$at=vmean(@-II..@-I);%.1f Error message: Wrong type argument: number-or-marker-p, (6) I will appreciate any help with this issue. If it can't be fixed, I will have to downgrade to 8.2.10. Scott Randby
Re: [O] templating with Org?
I don't have the impression you would need to hijack the export process. It seems like you would need to call a function that gets data from some source (e.g the org document) and then populates a template with that data, and once that is done, call a regular export function. There are a number of template solutions: http://www.emacswiki.org/emacs/CategoryTemplates. I am not sure these are too easy to adapt to what you describe. I played around with some ideas for this here: http://kitchingroup.cheme.cmu.edu/blog/2014/01/20/Alternatives-to-long-complex-format-statements-in-emacs-lisp/ http://kitchingroup.cheme.cmu.edu/blog/2014/01/26/Another-alternative-to-string-templates/ Something like these could be used to populate a template I think. John --- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu On Sat, Aug 8, 2015 at 12:48 AM, Eric Abrahamsen wrote: > Exporting org files and subtrees is awfully flexible, given all the > possible customizations, but for a long while I've occasionally felt the > need to come at the "export" process from the other direction: instead > of customizing the export appearance of a series of headings, instead > starting with a common block of export text, and interpolating values > from the headings into that text -- ie, templating. > > I've felt this need off and on for a couple of years, most recently when > organizing a small literary festival. I really need to keep all the > information about the events in a single place, otherwise I know that > information will go stale right away. But I need the information in a > series of such wildly-varying formats that I can't imagine setting up > (and switching between) export filters in a way that wouldn't make me > cry. Not to mention that the different "export" use-cases all have their > own per-heading boilerplate text, and there's no way I'm going to repeat > all that different boilerplate under each heading. > > Obviously there's many ways this could be done. I could somehow hijack > the export process -- in many cases it would be nice too make use of the > skeleton document structures that export provides. > > Or maybe dynamic blocks? I've never used them before. Or maybe just a > plain old `org-map-entries', which reads the template text from an > external file and then steals some of the macro expansion functions to > fill out the values. > > Has anyone wanted to do this before? Has anyone actually done it? Any > thoughts or suggestions would be much appreciated! > > Yours, > Eric > > >
Re: [O] comment trees in 8.3
0 in outline nil in agenda On 8/8/15, Nicolas Goaziou wrote: > What is the return value of (org-in-commented-heading-p) on your > pseudo-commented headlines?
[O] LaTeX special characters 8.3.1
Until 8.3.1, I needed to use \% in an org document in order to get the % symbol displayed when exporting to LaTeX. I just discovered that \% messes up the exported document, and that using % only works. I've also experimented with \$ and $ and found the same behavior. I've looked through the 8.3.1 changes document, but I can't find reference to this change. Since I use special characters frequently, I need more information about this change. Where can I find it? Scott Randby
Re: [O] LaTeX special characters 8.3.1
On 2015-08-08 at 14:19, Scott Randby wrote: > Until 8.3.1, I needed to use \% in an org document in order to get the % > symbol displayed when exporting to LaTeX. I just discovered that \% > messes up the exported document, and that using % only works. I've also > experimented with \$ and $ and found the same behavior. > > I've looked through the 8.3.1 changes document, but I can't find > reference to this change. Since I use special characters frequently, I > need more information about this change. Where can I find it? I export to LaTeX with pre-8.3 and now 8.3 and do not escape % and $. -k.
Re: [O] bug: isearch puts ellipses at top of window
On 7/3/14, Samuel Wales wrote: > in maint, isearch very often puts ... at the top of the window. is 8.3 seems to do this a little more. however, i have found that running scroll-lock-next-line after the isearch repairs the buggy ellipsis. is there a hook i can use to do so as a silly but effective workaround?
[O] 8.3.1 and org-latex-with-hyperref
What happened to the variable org-latex-with-hyperref? It is missing in
8.3.1 and I need it. I have this set to nil so that I can can use the
following in my documents
#+LATEX_HEADER: \hypersetup{...}
How do I now prevent org from automatically inserting \hypersetup{...}
when exporting to LaTeX?
Scott Randby
Re: [O] 8.3.1 and org-latex-with-hyperref
Sorry for the noise, I figured out how to prevent the automatic
insertion of \hypersetup{...} by deleting the settings for
org-latex-hyperref-template
Scott Randby
Re: [O] 8.3.1 and org-latex-with-hyperref
Scott Randby writes:
> Sorry for the noise, I figured out how to prevent the automatic
> insertion of \hypersetup{...} by deleting the settings for
> org-latex-hyperref-template
I'm curious to know what you are missing in org-latex-hyperref-template?
What do you need in order to use the provided method?
Thanks,
Rasmus
--
Got mashed potatoes. Ain't got no T-Bone. No T-Bone
Re: [O] LaTeX special characters 8.3.1
Scott Randby writes: > Until 8.3.1, I needed to use \% in an org document in order to get the > % symbol displayed when exporting to LaTeX. I just discovered that \% > messes up the exported document, and that using % only works. I've > also experimented with \$ and $ and found the same behavior. > > I've looked through the 8.3.1 changes document, but I can't find > reference to this change. Since I use special characters frequently, I > need more information about this change. Where can I find it? % Is exported as "\%" in latex. $ is a mess. It's uses some heuristic to determine if it's a math snippet or a currency symbol. You can always use a snippet, @@latex:%@@ which is exported literally in the backend before the colon. Hope it helps, Rasmus -- Er du tosset for noge' lårt!
Re: [O] LaTeX special characters 8.3.1
On 08/08/2015 02:52 PM, Rasmus wrote: Scott Randby writes: Until 8.3.1, I needed to use \% in an org document in order to get the % symbol displayed when exporting to LaTeX. I just discovered that \% messes up the exported document, and that using % only works. I've also experimented with \$ and $ and found the same behavior. I've looked through the 8.3.1 changes document, but I can't find reference to this change. Since I use special characters frequently, I need more information about this change. Where can I find it? % Is exported as "\%" in latex. $ is a mess. It's uses some heuristic to determine if it's a math snippet or a currency symbol. You can always use a snippet, @@latex:%@@ which is exported literally in the backend before the colon. Hope it helps, Yes, that helps. Thank you. Rasmus
Re: [O] 8.3.1 and org-latex-with-hyperref
On 08/08/2015 02:50 PM, Rasmus wrote:
Scott Randby writes:
Sorry for the noise, I figured out how to prevent the automatic
insertion of \hypersetup{...} by deleting the settings for
org-latex-hyperref-template
I'm curious to know what you are missing in org-latex-hyperref-template?
What do you need in order to use the provided method?
Nothing is missing. I had difficulties with the default \hypersetup{...}
with an old version of org, and my habit became to use my own
\hypersetup{...} instead. Since I now have a huge number of documents
with my own setup, it isn't worth it to go and change all of them.
Scott
Thanks,
Rasmus
Re: [O] latest org from Elpa error: Invalid function: org-babel-header-args-safe-fn
Hi guys It turns out i didnt have the org-plus-contrib packages installed (never really used contrib stuff :)) and after installing that the problem seems to be gone! :) thx so much again and sorry for the trouble best Z On Sat, Aug 8, 2015 at 8:15 PM, Kyle Meyer wrote: > Xebar Saram wrote: > > Hi Kyle > > > > i tried uninstall and install with no success > > What if you do 'C-u M-x org-reload' before this uninstall/reinstall? > > -- > Kyle >
Re: [O] Exporting multiple images in a float (LaTeX)
Eric S Fraga writes:
> On Friday, 7 Aug 2015 at 16:23, Rasmus wrote:
>
> [...]
>
>> I guess there would also be no loss from actually inserting a "%" after
>> \includegraphics[·]{·} in ox-latex.
>
> Except that then the suggestion I just made would not work and would in
> fact be quite confusing as the second figure would be lost in the
> export?
But we can insert "%\n" and in the latex end there's no difference between
\includegraphics[]{}%
\includegraphics[]{}%
And
\includegraphics[]{}\includegraphics[]{}%
To the best of my knowledge.
Rasmus
--
Slowly unravels in a ball of yarn and the devil collects it
Re: [O] org-html-use-unicode-chars breaks source code blocks
Hi, [ deleted: discussion on beatification ] > > My initial reaction was to kill it as well. But I might feel like this a > bit to often (I feel the same way about headline keywords like COMMENT). There has been repeated 'bashing' of the COMMENT keyword lately on this list. Let me just raise a voice in defence. I do not mind the syntax too much, but the functionality of commenting a whole subtree without loosing the outline functionality is really handy. Especially also in distinction to the equally handy :noexport: tag. So, even if there is probably not a high risk for the COMMENT keyword to be dropped I just wanted to express my support for it. Regards, Andreas
Re: [O] Update tables 8.3.1
Hi Scott, Scott Randby writes: > I'm beginning to wonder if upgrading to 8.3.1 is a mistake. I had no > trouble at all with 8.2.10, but many problems with 8.3.1. My latest > issue follows. We appreciate your bug reports. If you have got the time, please keep testing Org 8.3 and let us know about errors you find. > When I update a table (using C-u C-c *, or C-u C-c C-c, or M-x > org-table-recalculate), the table doesn't update and I get the following > error message: > >Wrong type argument: number-or-marker-p, (4) I see this as well. > I can provide example tables if necessary. The example below is sufficient. > I tried the example table given in section 3.5.10 of the documentation > and I get the same error. > > |---+-++++---+--| > | | Student | Prob 1 | Prob 2 | Prob 3 | Total | Note | > |---+-++++---+--| > | ! | | P1 | P2 | P3 | Tot | | > | # | Maximum | 10 | 15 | 25 |50 | 10.0 | > | ^ | | m1 | m2 | m3 |mt | | > |---+-++++---+--| > | # | Peter | 10 | 8 | 23 |41 | 8.2 | > | # | Sam | 2 | 4 | 3 | 9 | 1.8 | > |---+-++++---+--| > | | Average |||| 25.0 | | > | ^ | ||||at | | > | $ | max=50 |||| | | > |---+-++++---+--| > > #+TBLFM: $6=vsum($P1..$P3)::$7=10*$Tot/$max;%.1f::$at=vmean(@-II..@-I);%.1f > > Error message: Wrong type argument: number-or-marker-p, (6) > > I will appreciate any help with this issue. If it can't be fixed, I will > have to downgrade to 8.2.10. Can you try the attached patch? It seems to work on the example from the manual, but you likely have more straining examples at hand. Thanks, Rasmus -- Enough with the bla bla! >From 5fbcbffea86757e068a866643f3e7470dae1e10f Mon Sep 17 00:00:00 2001 From: Rasmus Date: Sat, 8 Aug 2015 23:11:39 +0200 Subject: [PATCH 1/5] org-table: Fix typo * org-table.el (org-table-goto-field): Fix typo. --- lisp/org-table.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/org-table.el b/lisp/org-table.el index 62de402..ef6427c 100644 --- a/lisp/org-table.el +++ b/lisp/org-table.el @@ -2567,7 +2567,7 @@ This function assumes the table is already analyzed (i.e., using (string-to-number (match-string 2 ref (t (user-error "Unknown field: %s" ref (line (car coordinates)) - (column (cdr coordinates)) + (column (cadr coordinates)) (create-new-column (if (functionp create-column-p) (funcall create-column-p column) create-column-p))) -- 2.5.0
Re: [O] Pass options to \columns{} environment in beamer export
This should do it :
* Hello
** columns
:B_columns:
:PROPERTIES:
:BEAMER_env: columns
:BEAMER_opt: [c]
:END:
*** Column 1
:BMCOL:
:PROPERTIES:
:BEAMER_col: 0.3
:END:
Colonne 1
*** Column 2
:BMCOL:
:PROPERTIES:
:BEAMER_col: 0.7
:END:
Colonne 2
Fabrice
2015-08-08 18:30 GMT+02:00 John Hendy :
> I have an org beamer file with the following header since I generally
> prefer top-alignment for frames:
>
> #+latex_class_options: [aspectratio=169,t,presentation,bigger,fleqn]
>
> I have some columns where I want vertically centered text, and am not
> sure how to pass the option to \columns{} instead of an individual
> \column{}.
>
> Worg says this(http://orgmode.org/worg/exporters/beamer/ox-beamer.html):
>
> "All contiguous environments are automatically wrapped in a columns
> environment, although it can be forced at any point by setting the
> BEAMER_env property to columns. This might be handy if you want to
> pass special options."
>
> But where does that go? I have this:
>
> * Test
>
> ** Col1 :BMCOL:
>:PROPERTIES:
>:BEAMER_col: 0.5
>:END:
>
> - blah
> - blah
> - blah
>
> ** Col2 :BMCOL:
>:PROPERTIES:
>:BEAMER_col: 0.5
>:END:
>
> - blah
> - blah
> - blah
>
> I want this (note the [c] to override my document-wide [t] option):
>
> \begin{frame}[label={sec:orgheadline1}]{Test}
> \begin{columns}[c]
> \begin{column}{0.5\columnwidth}
> \begin{itemize}
> \item blah
> \item blah
> \item blah
> \end{itemize}
> \end{column}
>
> \begin{column}{0.5\columnwidth}
> \begin{itemize}
> \item blah
> \item blah
> \item blah
> \end{itemize}
> \end{column}
> \end{columns}
> \end{frame}
> \end{document}
>
> But if I add =:beamer_env: columns= to both subheadlines, I get each
> in it's own \begin/end{columns} environment, which is not what I want.
> I just need a single columns env, with the [c] option passed, that
> encompasses both individual column environments.
>
>
> John
>
>
--
Fabrice Popineau
-
SUPELEC
Département Informatique
3, rue Joliot Curie
91192 Gif/Yvette Cedex
Tel direct : +33 (0) 169851950
Standard : +33 (0) 169851212
--
Re: [O] Update tables 8.3.1
On 08/08/2015 05:18 PM, Rasmus wrote: Hi Scott, Scott Randby writes: I'm beginning to wonder if upgrading to 8.3.1 is a mistake. I had no trouble at all with 8.2.10, but many problems with 8.3.1. My latest issue follows. We appreciate your bug reports. If you have got the time, please keep testing Org 8.3 and let us know about errors you find. When I update a table (using C-u C-c *, or C-u C-c C-c, or M-x org-table-recalculate), the table doesn't update and I get the following error message: Wrong type argument: number-or-marker-p, (4) I see this as well. I can provide example tables if necessary. The example below is sufficient. I tried the example table given in section 3.5.10 of the documentation and I get the same error. |---+-++++---+--| | | Student | Prob 1 | Prob 2 | Prob 3 | Total | Note | |---+-++++---+--| | ! | | P1 | P2 | P3 | Tot | | | # | Maximum | 10 | 15 | 25 |50 | 10.0 | | ^ | | m1 | m2 | m3 |mt | | |---+-++++---+--| | # | Peter | 10 | 8 | 23 |41 | 8.2 | | # | Sam | 2 | 4 | 3 | 9 | 1.8 | |---+-++++---+--| | | Average |||| 25.0 | | | ^ | ||||at | | | $ | max=50 |||| | | |---+-++++---+--| #+TBLFM: $6=vsum($P1..$P3)::$7=10*$Tot/$max;%.1f::$at=vmean(@-II..@-I);%.1f Error message: Wrong type argument: number-or-marker-p, (6) I will appreciate any help with this issue. If it can't be fixed, I will have to downgrade to 8.2.10. Can you try the attached patch? It seems to work on the example from the manual, but you likely have more straining examples at hand. I applied the patch, and tried it on several tables which have simple and complex formulas. It works on those tables. Thanks for your help. Scott Thanks, Rasmus
Re: [O] Exporting multiple images in a float (LaTeX)
On Sat, Aug 08, 2015 at 09:23:57PM +0200, Rasmus wrote:
> Eric S Fraga writes:
>
> > On Friday, 7 Aug 2015 at 16:23, Rasmus wrote:
> >
> > [...]
> >
> >> I guess there would also be no loss from actually inserting a "%" after
> >> \includegraphics[·]{·} in ox-latex.
> >
> > Except that then the suggestion I just made would not work and would in
> > fact be quite confusing as the second figure would be lost in the
> > export?
>
> But we can insert "%\n" and in the latex end there's no difference between
>
> \includegraphics[]{}%
> \includegraphics[]{}%
>
> And
>
> \includegraphics[]{}\includegraphics[]{}%
>
> To the best of my knowledge.
I think you are correct!
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Update tables 8.3.1
Hello, Rasmus writes: > Can you try the attached patch? It seems to work on the example from the > manual, but you likely have more straining examples at hand. Thank you. I pushed a similar patch in maint (46f3f4c626d6dfe48c0101e3c994a929b542ba77). Regards, -- Nicolas Goaziou
[O] org-element approach to modify or add ID to every headline
Good evening, Emacs 24.4 and Org from Git. Goal: 1) Visit every headline 2) If there is an ID property 1) Then replace it's value with a UUID 3) If there is not an ID property 1) Add an ID property and give it a UUID. `org-uuid' [provides] the functionality to add the ID with a UUID. [This post] explains how to do it: ┌ │ (require 'org-id) │(save-excursion │ (goto-char (point-max)) │ (while (outline-previous-heading) │ (org-id-get-create))) └ What is the best way to do it with `org-element'? [provides] http://orgmode.org/w/?p=org-mode.git;a=blob_plain;f=lisp/org-id.el;hb=HEAD [This post] https://stackoverflow.com/questions/13340616/assign-ids-to-every-entry-in-org-mode
[O] How to visit every source block and modify it's NAME property with org-element?
Good evening, Emacs 24.4 and Org from Git. Goal: 1) Visit every source block 2) If there is a NAME property 1) Then replace it's value with a UUID 3) If there is not an NAME property 1) Add an NAME property and give it a UUID. `org-uuid' [provides] the functionality to create a UUID. It seems like this could be re-used for this NAME property. Would that be a good idea? The code would be nearly the same (choose a UUID program, get a value, insert it). What is the best way to do it with `org-element'? This is very similar to a post I just made about headlines and the ID property but they are different enough to post separately. [provides] http://orgmode.org/w/?p=org-mode.git;a=blob_plain;f=lisp/org-id.el;hb=HEAD
Re: [O] wrong type argument listp... org-element-set-contents
Yes. In my case, I installed org-plus-contrib. On Sat, Aug 8, 2015 at 1:09 PM, Kyle Meyer wrote: > Peter Salazar wrote: > > Yes, that worked! Thank you so much! > > Great. Just for future reference, these were the steps that worked? > > - C-u M-x org-reload > - Uninstall and then reinstall from package-list-packages menu. > > -- > Kyle >
