Re: [O] Recursive formulaes in org-mode tables
On Tuesday, 13 Oct 2015 at 17:35, michael.zom...@googlemail.com wrote: [...] > After reading a related SO question I tried the formula > > #+TBLFM: @<<<..>$2=@<<..>>$2+2*$3 This worked for me: #+TBLFM: @<<<$2..@>$2=@-1+2*@-1$+1 HTH, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.2-161-gd2ac25
Re: [O] org-mobile-push and MobileOrg compatibility issue
On Tuesday, 13 Oct 2015 at 15:28, Chris Patti wrote: > I must confess I am not wild about the whole way MobileOrg purports to > function. > > I don't really want to have to push or pull my OrgFiles to/from > mobile. With mechanisms like Dropbox what I *really* want is to be > able to access and manipulate Org content on my device directly. Yes, we'd all like that but that requires Emacs basically... you *can* run Emacs on an Android device, just not very well in my opinion. You could try and see if it works for you: http://play.google.com/store/apps/details?id=com.zielm.emacs My solution was to buy and OpenPandora palmtop computer that runs full Debian Linux (and hence any version of Emacs I want!). -- : Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.2-161-gd2ac25
Re: [O] 'org-switch-to-buffer-other-window' prevents customisation ofpop-up buffers by binding key variables [8.2.10 (release_8.2.10 @ c:/ProgramFiles/emacs/share/emacs/24.5/lisp/org/)]
I worked around it by using an elisp ‘advice’ snippet another user suggested (http://emacs.stackexchange.com/questions/17112/prevent-org-todo-pop-up-window-from-displaying-in-new-frame-dedicated-window) Before that I wasted several hours trying to ‘fix’ the problem in various ways. I imagine org is overriding default handling for a good reason, but it is frustrating to have to override said functionality with a code-snippet, which will undoubtedly break at some point while I scratch my head to understand how I can fix it! From: Nicolas Goaziou Sent: 13 October 2015 9:52 PM To: Hassan Dar Cc: emacs-orgmode@gnu.org Subject: Re: 'org-switch-to-buffer-other-window' prevents customisation ofpop-up buffers by binding key variables [8.2.10 (release_8.2.10 @ c:/ProgramFiles/emacs/share/emacs/24.5/lisp/org/)] Hello, Hassan Dar writes: > As seen in the following StackExchange questions: > > http://emacs.stackexchange.com/questions/14817/how-to-control-where-the-org-todo-keywords-buffer-displays > > http://emacs.stackexchange.com/questions/17112/prevent-org-todo-pop-up-window-from-displaying-in-new-frame-dedicated-window > > The org-no-popups macro (which is leveraged by ' > org-switch-to-buffer-other-window' let-binds key variables such as > "display-buffer-alist" to 'nil'. > > This ultimately prevents a user from > customising pop-ups generated by org in the same way they would with > other pop-up windows. I'm not a big fan of Org's opinionated way to handle windows either. However, couldn't you use `display-buffer-overriding-action' in this case? It is checked before `display-buffer-alist'. Regards, -- Nicolas Goaziou
Re: [O] ox-beamer and CUSTOM_ID
Fabrice Popineau writes: > This is a pity. Things would be more straightforward. Straightforward for what? Use againframes? Or force label? Regards,
[O] org-agenda-scheduled-leaders and repeating tasks
hello everyone, i think what i am trying to say is best shown with an example. so let's say that today is oct 13th. the task ** TODO check smoke alarm SCHEDULED: <2015-10-04 Sun .+10d> shows up in the agenda as: Sched.10x: TODO check smoke alarm however, had the task been scheduled a day before (or if today was oct 14th): ** TODO check smoke alarm SCHEDULED: <2015-10-03 Sat .+10d> it would show up in the agenda as: Scheduled: TODO check smoke alarm that is to say, the marker that indicates it is overdue is gone. for some cases, like checking the smoke alarm, i don't want the "Sched.?x" to reset. ie, Sched.11x: TODO check smoke alarm i tracked this down to the function org-time-string-to-absolute. when rendering the agenda it gets called with today as its DAYNR argument, which causes "org-closest-date" to return "today" for the case of repeating timestamps. i can understand why it is done this way, and i find it useful. however for some tasks, i'd rather the counter not reset lest i miss something for longer than i should have (the smoke alarm case for example). i patched my version of org to do this (release_8.2.10); but i did it by not calling org-closest-date in the case of repeating timestamps with the effect they all act this way. to do this properly i'd imagine we would need another identifier in the timestamp(?) i am willing to do the work to contribute the proper patches and update the doc if people are interested. ... or is there another way of doing this? :) thank you kindly for reading! - cesar
Re: [O] ox-beamer and CUSTOM_ID
2015-10-13 22:52 GMT+02:00 Nicolas Goaziou : > Fabrice Popineau writes: > > > This time , I'm the one who is puzzled: > > what is the point in naming the link "foo" and getting sec:orgheadline1 > > instead? :-) > > > > If you add :BEAMER_OPT: label=foo > > to the properties of the first frame, then you get the foo label. > > But that doesn't seem very obvious to me. Why not taking directly the > > CUSTOM_ID label ? > > Because CUSTOM_ID's value may contain forbidden characters in LaTeX, > e.g., "%". Oh ... thanks for this explanation. Speaking for myself, I would have prefered to take the risk to use forbidden characters in CUSTOM_ID. > See also `org-latex-prefer-user-labels', which is not > implemented in Beamer, since BEAMER_OPT can already force a value for > label. > This is a pity. Things would be more straightforward. Regards, Fabrice
Re: [O] 'org-switch-to-buffer-other-window' prevents customisation of pop-up buffers by binding key variables [8.2.10 (release_8.2.10 @ c:/Program Files/emacs/share/emacs/24.5/lisp/org/)]
Hello, Hassan Dar writes: > As seen in the following StackExchange questions: > > http://emacs.stackexchange.com/questions/14817/how-to-control-where-the-org-todo-keywords-buffer-displays > > http://emacs.stackexchange.com/questions/17112/prevent-org-todo-pop-up-window-from-displaying-in-new-frame-dedicated-window > > The org-no-popups macro (which is leveraged by ' > org-switch-to-buffer-other-window' let-binds key variables such as > "display-buffer-alist" to 'nil'. > > This ultimately prevents a user from > customising pop-ups generated by org in the same way they would with > other pop-up windows. I'm not a big fan of Org's opinionated way to handle windows either. However, couldn't you use `display-buffer-overriding-action' in this case? It is checked before `display-buffer-alist'. Regards, -- Nicolas Goaziou
Re: [O] ox-beamer and CUSTOM_ID
Fabrice Popineau writes: > This time , I'm the one who is puzzled: > what is the point in naming the link "foo" and getting sec:orgheadline1 > instead? :-) > > If you add :BEAMER_OPT: label=foo > to the properties of the first frame, then you get the foo label. > But that doesn't seem very obvious to me. Why not taking directly the > CUSTOM_ID label ? Because CUSTOM_ID's value may contain forbidden characters in LaTeX, e.g., "%". See also `org-latex-prefer-user-labels', which is not implemented in Beamer, since BEAMER_OPT can already force a value for label. Regards,
Re: [O] ox-beamer and CUSTOM_ID
2015-10-13 21:50 GMT+02:00 Nicolas Goaziou :
> Fabrice Popineau writes:
>
> > 2015-10-13 21:26 GMT+02:00 Nicolas Goaziou :
> >
> >> Hello,
> >>
> >> I don't understand the issue. BEAMER_REF: #foo generates the same
> >> internal reference as :CUSTOM_ID: foo, doesn't it?
> >>
> >>
> > My point is that you need to set :
> >
> > * Frame 1
> > :PROPERTIES:
> > :BEAMER_OPT: label=foo
> > :END:
> >
> > * Frame 2
> > :PROPERTIES:
> > :BEAMER_env: againframe
> > :BEAMER_ref: #foo
> > :END:
>
> If I try to export this file, I get an error:
>
> user-error: Unable to resolve link: "foo"
>
> which is to be expected since :CUSTOM_ID: foo doesn't exist.
>
> > because if you use CUSTOM_ID in the first frame, the link is not
> > resolved.
>
> It should be. With the following document
>
> * Frame 1
> :PROPERTIES:
> :CUSTOM_ID: foo
> :END:
>
> * Frame 2
> :PROPERTIES:
> :BEAMER_env: againframe
> :BEAMER_ref: #foo
> :END:
>
> I get
>
> \begin{document}
>
> \begin{frame}[label={sec:orgheadline1}]{Frame 1}
> \end{frame}
>
> \againframe{{sec:orgheadline1}}
> \end{document}
>
> So, I'm still puzzled.
This time , I'm the one who is puzzled:
what is the point in naming the link "foo" and getting sec:orgheadline1
instead? :-)
If you add :BEAMER_OPT: label=foo
to the properties of the first frame, then you get the foo label.
But that doesn't seem very obvious to me. Why not taking directly the
CUSTOM_ID label ?
Fabrice
Re: [O] org-mobile-push and MobileOrg compatibility issue
Hello, Vamsi Vytla writes: > I can guarantee you that your suggestion did NOT work for me. I haven't > heard anything from Sergey here. Looks like people at MobileOrg-Android > maybe running into the same issue: > > https://github.com/matburt/mobileorg-android/issues/472#issuecomment-147403622 > > Any thoughts? Not really. I hesitate to revert the change since it looks correct. It may be a problem on the MobileOrg side. Could you show the difference between an index file generated with the current org-mobile.el and one with your patched org-mobile.el? Regards, -- Nicolas Goaziou
Re: [O] [PATCH] Reverse capture finalize and refile, hack buffer killing.
Hello, Jan Seeger writes: > Attached is the full output of git-format patch (should have done it > like that earlier^^). Applied, finally! Thank you. Regards, -- Nicolas Goaziou
Re: [O] ox-beamer and CUSTOM_ID
Fabrice Popineau writes:
> 2015-10-13 21:26 GMT+02:00 Nicolas Goaziou :
>
>> Hello,
>>
>> I don't understand the issue. BEAMER_REF: #foo generates the same
>> internal reference as :CUSTOM_ID: foo, doesn't it?
>>
>>
> My point is that you need to set :
>
> * Frame 1
> :PROPERTIES:
> :BEAMER_OPT: label=foo
> :END:
>
> * Frame 2
> :PROPERTIES:
> :BEAMER_env: againframe
> :BEAMER_ref: #foo
> :END:
If I try to export this file, I get an error:
user-error: Unable to resolve link: "foo"
which is to be expected since :CUSTOM_ID: foo doesn't exist.
> because if you use CUSTOM_ID in the first frame, the link is not
> resolved.
It should be. With the following document
* Frame 1
:PROPERTIES:
:CUSTOM_ID: foo
:END:
* Frame 2
:PROPERTIES:
:BEAMER_env: againframe
:BEAMER_ref: #foo
:END:
I get
\begin{document}
\begin{frame}[label={sec:orgheadline1}]{Frame 1}
\end{frame}
\againframe{{sec:orgheadline1}}
\end{document}
So, I'm still puzzled.
> The code at stake is :
> ox-beamer:org-beamer-headline which calls ox-beamer:org-beamer--get-label
> at line 624
>
> Clearly, org-beamer--get-label doesn't make use of CUSTOM_ID.
It doesn't need to, since CUSTOM_ID will not be used anyway in the final
output.
Regards,
Re: [O] [wish] Execute preparation-function before getting base files
Hello,
Arun Isaac writes:
> org-export-before-{processing,parsing} hooks are only useful when I have
> existing source files and I want to modify them in some way before I
> {process,parse} them. In my case, the source files don't exist at all,
> before my preparation-function is run.
>
> Regarding the preparation-function, the use case described in the manual
> is for running make to update files before publishing.
>
> http://orgmode.org/manual/Sources-and-destinations.html
>
> Therefore, I think it makes sense only if the source filenames are collected
> using org-publish-get-base-files after the preparation-function is run.
>
> With the above logic, maybe the order of execution can actually be
> considered a bug?
I made the change in master. Thank you.
Regards,
--
Nicolas Goaziou
Re: [O] ox-beamer and CUSTOM_ID
2015-10-13 21:26 GMT+02:00 Nicolas Goaziou : > Hello, > > I don't understand the issue. BEAMER_REF: #foo generates the same > internal reference as :CUSTOM_ID: foo, doesn't it? > > My point is that you need to set : * Frame 1 :PROPERTIES: :BEAMER_OPT: label=foo :END: * Frame 2 :PROPERTIES: :BEAMER_env: againframe :BEAMER_ref: #foo :END: because if you use CUSTOM_ID in the first frame, the link is not resolved. The code at stake is : ox-beamer:org-beamer-headline which calls ox-beamer:org-beamer--get-label at line 624 Clearly, org-beamer--get-label doesn't make use of CUSTOM_ID. It is a bit strange to have to use another way to set custom labels than a CUSTOM_ID property. Regards, Fabrice
Re: [O] org-mobile-push and MobileOrg compatibility issue
I must confess I am not wild about the whole way MobileOrg purports to function. I don't really want to have to push or pull my OrgFiles to/from mobile. With mechanisms like Dropbox what I *really* want is to be able to access and manipulate Org content on my device directly. -Chris On Mon, Oct 12, 2015 at 1:42 PM, Vamsi Vytla wrote: > Hi Nicolas, > > I can guarantee you that your suggestion did NOT work for me. I haven't > heard anything from Sergey here. Looks like people at MobileOrg-Android > maybe running into the same issue: > > https://github.com/matburt/mobileorg-android/issues/472#issuecomment-147403622 > > Any thoughts? > > Vamsi > > On Sat, Sep 5, 2015 at 1:44 AM Nicolas Goaziou > wrote: >> >> Hello, >> >> Vamsi Vytla writes: >> >> > M-x 'org-mobile-push', with the latest org-mode leaves the files >> > incompatible with MobileOrg Android application. There have been no >> > changes >> > in MobileOrg for over a year. >> > >> > I bisected the latest org-mobile related changes and noticed that >> > reverting >> > this one line below "fixes" the issue (at least for me). Since there >> > aren't >> > any tests, it's hard to validate changes and understand things easily. >> > >> > If anybody can point me in the right direction, I would love to look >> > into >> > it further. >> > >> > Cheers! >> > >> > diff --git a/lisp/org-mobile.el b/lisp/org-mobile.el >> > index 6c7c8d0..7e1127c 100644 >> > --- a/lisp/org-mobile.el >> > +++ b/lisp/org-mobile.el >> > @@ -446,7 +446,7 @@ agenda view showing the flagged items." >> > x)) >> >(cdr entry))) >> > (insert "#+TODO: " (mapconcat 'identity kwds " ") "\n") >> > - (setq dwds (or (member "|" kwds) (last kwds)) >> > + (setq dwds (member "|" kwds) >> > twds (org-delete-all dwds kwds) >> > todo-kwds (org-delete-all twds todo-kwds) >> > done-kwds (org-delete-all dwds done-kwds))) >> >> IIRC this change was introduced to fix another bug. It might be useful >> to discuss with the author of this change. Another option is to use >> >> (or (member "|" kwds) (cons "|" (last kwds))) >> >> >> Regards, >> >> -- >> Nicolas Goaziou -- Christopher Patti - Geek At Large | GTalk: cpa...@gmail.com | AIM: chrisfeohpatti | P: (260) 54PATTI "Technology challenges art, art inspires technology." - John Lasseter, Pixar
Re: [O] ox-beamer and CUSTOM_ID
Hello, Fabrice Popineau writes: > Something I don't understand in ox-beamer. > I wanted to use the againframe feature. > > I setup a CUSTOM_ID to foo on the first frame. > > I use #foo as a BEAMER_REF in the againframe. > > But ox-beamer insists in using its own generated label to refer to the > frame. > I trace it to org-beamer--get-label which looks only for label=%s in the > BEAMER_OPT property of the initial frame. > IMHO, it should look for a CUSTOM_ID too. > That would make it more consistent. > > Am I missing something ? I don't understand the issue. BEAMER_REF: #foo generates the same internal reference as :CUSTOM_ID: foo, doesn't it? Regards, -- Nicolas Goaziou
Re: [O] Recursive formulaes in org-mode tables
I posted the following on Stack Overflow: I recommend using the following range formula: | Year (Beginn) |Price | Increase | |---+--+--| | 2016 | 2.00 | 1000.00 | | 2017 | | 1000.00 | | 2018 | | 1000.00 | | 2019 | | 1000.00 | | 2020 | | 1000.00 | | 2021 | | 1000.00 | | 2022 | | 1000.00 | | 2023 | | 1000.00 | | 2024 | | 1000.00 | | 2025 | | 1000.00 | | 2026 | | 1000.00 | | 2027 | | 1000.00 | | 2028 | | 1000.00 | | 2029 | | 1000.00 | | 2030 | | 1000.00 | |---+--+--| #+TBLFM: @<<<$2..@>$2=@<<$0+2*vsum(@<<$3..@-1$3);%.2f You could write a recursive formula, but that would propagate one row at a time. Even org-table-iterate (C-u C-u C-c * on any table cell) would have to be called more than once, since it stops after 10 iterations. Shankar Rao On Tue, Oct 13, 2015 at 8:35 AM, wrote: > Hi, > > I have the following table: > > | Year (Beginn) |Price | Increase | > |---+--+--| > | 2016 | 2.00 | 1000.00 | > | 2017 | | 1000.00 | > | 2018 | | 1000.00 | > | 2019 | | 1000.00 | > | 2020 | | 1000.00 | > | 2021 | | 1000.00 | > | 2022 | | 1000.00 | > | 2023 | | 1000.00 | > | 2024 | | 1000.00 | > | 2025 | | 1000.00 | > | 2026 | | 1000.00 | > | 2027 | | 1000.00 | > | 2028 | | 1000.00 | > | 2029 | | 1000.00 | > | 2030 | | 1000.00 | > |---+--+--| > > I want to compute the price recursively such that the final table looks > like this: > > | Year (Beginn) |Price | Increase | > |---+--+--| > | 2016 | 2.00 | 1000.00 | > | 2017 | 22000.00 | 1000.00 | > | 2018 | 24000.00 | 1000.00 | > | 2019 | 26000.00 | 1000.00 | > | 2020 | 28000.00 | 1000.00 | > | 2021 | 3.00 | 1000.00 | > | 2022 | 32000.00 | 1000.00 | > | 2023 | 34000.00 | 1000.00 | > | 2024 | 36000.00 | 1000.00 | > | 2025 | 38000.00 | 1000.00 | > | 2026 | 4.00 | 1000.00 | > | 2027 | 42000.00 | 1000.00 | > | 2028 | 44000.00 | 1000.00 | > | 2029 | 46000.00 | 1000.00 | > | 2030 | 48000.00 | 1000.00 | > |---+--+--| > After reading a related SO question I tried the formula > > #+TBLFM: @<<<..>$2=@<<..>>$2+2*$3 > > but it doesn't work. It gives an error and also seems to operate on > column one instead of the specified column two. Any idea how to > correctly compute column two? I am using org-mode version 8.2.5c with > Emacs version 24.5.1. > > Disclaimer: I posted this question also on Stack Overflow: > > > http://stackoverflow.com/questions/33063425/recursive-formulaes-in-org-mode-tables > > Feel free to answer here or there. > > Thanks! > > Best, > Michael > > >
[O] Recursive formulaes in org-mode tables
Hi, I have the following table: | Year (Beginn) |Price | Increase | |---+--+--| | 2016 | 2.00 | 1000.00 | | 2017 | | 1000.00 | | 2018 | | 1000.00 | | 2019 | | 1000.00 | | 2020 | | 1000.00 | | 2021 | | 1000.00 | | 2022 | | 1000.00 | | 2023 | | 1000.00 | | 2024 | | 1000.00 | | 2025 | | 1000.00 | | 2026 | | 1000.00 | | 2027 | | 1000.00 | | 2028 | | 1000.00 | | 2029 | | 1000.00 | | 2030 | | 1000.00 | |---+--+--| I want to compute the price recursively such that the final table looks like this: | Year (Beginn) |Price | Increase | |---+--+--| | 2016 | 2.00 | 1000.00 | | 2017 | 22000.00 | 1000.00 | | 2018 | 24000.00 | 1000.00 | | 2019 | 26000.00 | 1000.00 | | 2020 | 28000.00 | 1000.00 | | 2021 | 3.00 | 1000.00 | | 2022 | 32000.00 | 1000.00 | | 2023 | 34000.00 | 1000.00 | | 2024 | 36000.00 | 1000.00 | | 2025 | 38000.00 | 1000.00 | | 2026 | 4.00 | 1000.00 | | 2027 | 42000.00 | 1000.00 | | 2028 | 44000.00 | 1000.00 | | 2029 | 46000.00 | 1000.00 | | 2030 | 48000.00 | 1000.00 | |---+--+--| After reading a related SO question I tried the formula #+TBLFM: @<<<..>$2=@<<..>>$2+2*$3 but it doesn't work. It gives an error and also seems to operate on column one instead of the specified column two. Any idea how to correctly compute column two? I am using org-mode version 8.2.5c with Emacs version 24.5.1. Disclaimer: I posted this question also on Stack Overflow: http://stackoverflow.com/questions/33063425/recursive-formulaes-in-org-mode-tables Feel free to answer here or there. Thanks! Best, Michael
[O] Return Top-Level Heading
Hello, Is there a way to reference the top-level heading that a lower-level heading belongs to? For instance: * One ** Two *** Three If I have "Three", how can I get it to tell me that the top-level is "One"? For reference, this is for an org-agenda-prefix. Thanks!
[O] :point-entered and :point-left on text in org-mode?
Has anyone tried using :point-entered and :point-left properties in text in org-mode? I have been looking into them as replacements for some things I currently do with timers on functional links. The idea is to use them to run some code when a point enters a link, e.g. toggle a latex equation, or display a message about the link. I think it would be better than using post-command-hook, and simpler than the idle-timer approach I have been using. Is there some other canonical way to execute code on entering a region? Thanks! -- 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
Re: [O] line numbers in org src blocks?
I meant in the org-file buffer. The numbers in export are pretty straightforward. I made a partial solution here: http://kitchingroup.cheme.cmu.edu/blog/2015/10/13/Line-numbers-in-org-mode-code-blocks/ It works pretty well I think. Nick Dokos writes: > John Kitchin andrew.cmu.edu> writes: > >> >> Does anyone know if it is possible to get line numbering only in code >> blocks in an org-file? >> > > When exporting? Or in the buffer? If the latter, I don't know. If the > former, -n does that but it is position-sensitive I think: > > --8<---cut here---start->8--- > > * A code block for exporting with line number > > #+BEGIN_SRC python -n :exports code > import sys > > sys.exit(0) > > #+END_SRC > > #+BEGIN_EXAMPLE -n > import sys > > sys.exit(0) > #+END_EXAMPLE > --8<---cut here---end--->8--- > > works, but putting it at the end of the BEGIN_SRC line does not. > > See > > (info "(org) Literal examples") > > for more. -- 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
[O] Clock table quarterly block doesn't work anymore
Dear list, I tried to generate a report on my activities of this year using org clock tables, and found out that the 'quarterly block option' doesn't seem to work any more. This is what I do: #+begin_src org #+BEGIN: clocktable :maxlevel 2 :scope agenda-with-archives :block 2015-Q1 :tags "ProjectA" :fileskip0 #+END: #+end_src Until some time ago this worked. However, when I run it now I get: #+begin_src org #+BEGIN: clocktable :maxlevel 2 :scope agenda-with-archives :block 2015-Q3 :tags "ProjectA" :fileskip0 #+CAPTION: Clock summary at [2015-10-13 di 10:51], for 4th quarter of 2015. | File | Headline | Time | | |+--++--| || ALL *Total time* | *2:08* | | |+--++--| | todo.org | *File time* | *1:34* | | || Programming | 0:36 | | || \_ support forum|| 0:36 | || Courses | 0:58 | | || \_ school 2016 || 0:58 | |+--++--| | todo_ProjectA.org | *File time* | *0:34* | | || Financial| 0:21 | | || \_ Progress reports || 0:21 | || WP4 | 0:13 | | || \_ User support || 0:13 | #+END: #+end_src Notice how the caption mentions Q4 instead of Q3 like I asked. The same happens when I use Q1 or Q2. Could this be related to the fact that I upgraded to org 8.3 earlier this year? I just upgraded to org 20151005 but that didn't fix it. Any input is appreciated. Best regards, Lennart Karssen. -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* L.C. Karssen Utrecht The Netherlands lenn...@karssen.org http://blog.karssen.org GPG key ID: A88F554A -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- signature.asc Description: OpenPGP digital signature
[O] ox-beamer and CUSTOM_ID
Hi, Something I don't understand in ox-beamer. I wanted to use the againframe feature. I setup a CUSTOM_ID to foo on the first frame. I use #foo as a BEAMER_REF in the againframe. But ox-beamer insists in using its own generated label to refer to the frame. I trace it to org-beamer--get-label which looks only for label=%s in the BEAMER_OPT property of the initial frame. IMHO, it should look for a CUSTOM_ID too. That would make it more consistent. Am I missing something ? Fabrice
Re: [O] line numbers in org src blocks?
John Kitchin andrew.cmu.edu> writes: > > Does anyone know if it is possible to get line numbering only in code > blocks in an org-file? > When exporting? Or in the buffer? If the latter, I don't know. If the former, -n does that but it is position-sensitive I think: --8<---cut here---start->8--- * A code block for exporting with line number #+BEGIN_SRC python -n :exports code import sys sys.exit(0) #+END_SRC #+BEGIN_EXAMPLE -n import sys sys.exit(0) #+END_EXAMPLE --8<---cut here---end--->8--- works, but putting it at the end of the BEGIN_SRC line does not. See (info "(org) Literal examples") for more. -- Nick
