On Wed, Feb 28, 2018 at 12:25 AM Nicolas Goaziou
wrote:
> Hello,
> Allen Li writes:
> >> > I modified the example a bit and made the undesired behavior unclear.
> >> >
> >> > * foo
> >> > :PROPERTIES:
> >> > :ID: a
> >> > :END:
> >> > * bar
> >> > :PROPERTIES:
> >> > :ID: b
> >> > :END:
> >> >
>> What - if any - would be the recommended way to implement numbering only
>> second-level headlines in an exported document with running numbering
>> (resets with first-level headline change)?
>
> You haven't said what export target you are using. In any case, I would
> suggest you look at usin
You probably want this:
#+BEGIN_SRC emacs-lisp
(defun my-redo ()
(interactive)
(org-map-entries
(lambda ()
(org-todo "TODO"))
"TODO=\"DONE\"" ;; the match argument
'tree)) ;; the scope
#+END_SRC
Then call:
M-x my-redo
in the tree you want to reset.
John
-
If there is any interest, I've created a patch adding support for a
:absolute-paths functionality.
As I said, I don't have much experience writing Elisp, so any
suggestions on how to improve the code would be appreciated. If there
is any interest in adding this feature to Org I could try to clean i
I have a subtree that contains a daily list of things to do (which I keep as
TODOs rather than checklist form for more granular time tracking). I want to
reset all of the DONE to TODO every day when I start it. Right now I have this
piece of code I copypasted from somewhere now lost (possibly th
On Wednesday, 28 Feb 2018 at 16:33, Sharon Kimble wrote:
[...]
> However with Eric's code snippet the footnotes are shown at the end of
> '#+end_ingredients', so how can I get it back at the foot of the page
> when exported to latex and built into a PDF again please?
Untested but see my other re
On Wednesday, 28 Feb 2018 at 15:16, Sharon Kimble wrote:
[...]
> Thanks very much Eric, its working perfectly.
You're welcome. Glad it worked! Might be fragile, especially because
of the use of minipages and if you have long recipes, so you might like
to look at using the mdframed package: htt
Sorry for the ignorance, but where could I look up how to use a parse
tree filter? And where would these modifications make sense?
Any pointers towards documentation, functions, or any help of any kind
would be appreciated. I must say I am a bit lost.
Thank you in advance,
Daniel
On Wed, Feb 28,
On Wednesday, 28 Feb 2018 at 18:04, Jarmo Hurri wrote:
> Greetings.
>
> What - if any - would be the recommended way to implement numbering only
> second-level headlines in an exported document with running numbering
> (resets with first-level headline change)?
You haven't said what export target
Hello,
Daniel P Gomez writes:
> If I include a file child.org in parent.org using the #+INCLUDE
> derivative, and the following two conditions are true:
>
> 1. child.org and parent.org are not in the same directory nor share
> directory structure,
> 2. child.org contains file links with relative
Eric S Fraga writes:
> On Wednesday, 28 Feb 2018 at 09:56, Sharon Kimble wrote:
>> I have this as a recipe -
>
> [...]
>
>> How can I have the ingredients in a left-most column and the method in a
>> right-most column please? So that everything below the index entries is
>> in 2-column mode which
Greetings.
What - if any - would be the recommended way to implement numbering only
second-level headlines in an exported document with running numbering
(resets with first-level headline change)?
BTW, here is a full programming course (used to teach kids of different
ages) written almost entire
Eric S Fraga writes:
> On Wednesday, 28 Feb 2018 at 09:56, Sharon Kimble wrote:
>> I have this as a recipe -
>
> [...]
>
>> How can I have the ingredients in a left-most column and the method in a
>> right-most column please? So that everything below the index entries is
>> in 2-column mode which
Akater writes:
> Sharon Kimble writes:
>
>> How can I have the footnote number in an org-mode file, exported to
>> latex and then built as a PDF file, be underlined please?
>
> Try adding the following LaTeX directive.
>
> #+latex_header: \renewcommand{\thefootnote}{\underline{\arabic{footnote}}
Dear org users,
If I include a file child.org in parent.org using the #+INCLUDE
derivative, and the following two conditions are true:
1. child.org and parent.org are not in the same directory nor share
directory structure,
2. child.org contains file links with relative file paths,
then exportin
Sharon Kimble writes:
> How can I have the footnote number in an org-mode file, exported to
> latex and then built as a PDF file, be underlined please?
Try adding the following LaTeX directive:
#+latex_header: \renewcommand{\thefootnote}{\underline{\arabic{footnote}}}
Note: both footnote numbe
Sharon Kimble writes:
> How can I have the footnote number in an org-mode file, exported to
> latex and then built as a PDF file, be underlined please?
Try adding the following LaTeX directive.
#+latex_header: \renewcommand{\thefootnote}{\underline{\arabic{footnote}}}
Note: both footnote numbe
On Wednesday, 28 Feb 2018 at 09:56, Sharon Kimble wrote:
> I have this as a recipe -
[...]
> How can I have the ingredients in a left-most column and the method in a
> right-most column please? So that everything below the index entries is
> in 2-column mode which ends after the citation. And it
When I have a chance, I enjoy the following development workflow: the
code is written in org files and is tangled into conventional source
code files more or less regularly.
I find that source blocks mostly fall into three categories, numbered
here for further reference:
- examples/test cases/desi
I have this as a recipe -
--8<---cut here---start->8---
** Date Bread
\index[pies]{Date bread}\index[menu]{Bread!date}\index[cook]{Bake!date
bread}\index{Fruit!dates}
/12 ounces stoned dates/\\
/1 teaspoonful bicarbonate of soda/\\
/1 cupful boiling water/\\
/
Hello,
Allen Li writes:
>> > I modified the example a bit and made the undesired behavior unclear.
>> >
>> > * foo
>> > :PROPERTIES:
>> > :ID: a
>> > :END:
>> > * bar
>> > :PROPERTIES:
>> > :ID: b
>> > :END:
>> >
>> > Folded, this looks like
>> >
>> > * foo...
>> > * bar...
>> >
>> > With point
21 matches
Mail list logo
