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, Or
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 m
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
Fabrice Popineau writes:
> This is a pity. Things would be more straightforward.
Straightforward for what? Use againframes? Or force label?
Regards,
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
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, th
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-fra
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 obviou
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
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
>
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
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:
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.
>
> Regard
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:
:BEAM
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
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
>
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 |
|
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 |
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!
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
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:
>
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 "Project
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 w
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 her
24 matches
Mail list logo
