Orgmode syntax: Difference between revisions

From wikinotes
Line 23: Line 23:
== Tasks ==
== Tasks ==
<blockquote>
<blockquote>
<syntaxhighlight lang="bash">
** WAITING [#B] Clean Kitchen                    :kitchen:irl:
DEADLINE: <2023-01-29 Sun> SCHEDULED: <2023-01-29 Sun>
:LOGBOOK:
CLOCK: [2023-01-31 Tue 00:12]--[2023-01-31 Tue 00:13] => 0:01
CLOCK: [2023-01-30 Mon 23:54]--[2023-01-30 Mon 23:54] => 0:00
CLOCK: [2023-01-30 Mon 23:53]--[2023-01-30 Mon 23:54] => 0:01
- State "TODO"      from "DONE"      [2023-01-29 Sun 18:27]
- State "DONE"      from "TODO"      [2023-01-29 Sun 18:27]
</syntaxhighlight>
<syntaxhighlight lang="yaml">
* `**` indicates the task nest-depth
* `[#B]` is the priority
* `:kitchen:irl:` are both tags assigned to this task
* `DEADLINE` is when task must be done
* `SCHEDULED` when task will show up in agenda (to be done)
* `:LOGBOOK:` includes information about state transitions, and clocked time
</syntaxhighlight>
=== Dates ===
=== Dates ===
<blockquote>
<blockquote>
Line 29: Line 49:


<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
** WAITING [#B] Test                                                  :test:foo:
** TODO Clean Kitchen
   DEADLINE: <2022-01-01 Sat> SCHEDULED: <2021-01-15 Wed>
   DEADLINE: <2022-01-01 Sat> SCHEDULED: <2021-01-15 Wed>
</syntaxhighlight>
</syntaxhighlight>
You can also schedule recurring tasks, by adding a <code>+2d</code> or <code>+1w</code>.
Each time this task is completed, it will be scheduled for it's next date.
</blockquote><!-- Dates -->
</blockquote><!-- Dates -->



Revision as of 03:03, 1 February 2023

Documentation

syntax docs https://orgmode.org/quickstart.html
export-options https://orgmode.org/manual/Export-Settings.html

Components

Export Options

Headers

Tasks

** WAITING [#B] Clean Kitchen                    :kitchen:irl:
 DEADLINE: <2023-01-29 Sun> SCHEDULED: <2023-01-29 Sun>
 :LOGBOOK:
 CLOCK: [2023-01-31 Tue 00:12]--[2023-01-31 Tue 00:13] => 0:01
 CLOCK: [2023-01-30 Mon 23:54]--[2023-01-30 Mon 23:54] => 0:00
 CLOCK: [2023-01-30 Mon 23:53]--[2023-01-30 Mon 23:54] => 0:01
 - State "TODO"       from "DONE"       [2023-01-29 Sun 18:27]
 - State "DONE"       from "TODO"       [2023-01-29 Sun 18:27]
* `**` indicates the task nest-depth
* `[#B]` is the priority
* `:kitchen:irl:` are both tags assigned to this task
* `DEADLINE` is when task must be done
* `SCHEDULED` when task will show up in agenda (to be done)
* `:LOGBOOK:` includes information about state transitions, and clocked time

Dates

  • deadlines
  • scheduled
** TODO Clean Kitchen
   DEADLINE: <2022-01-01 Sat> SCHEDULED: <2021-01-15 Wed>

You can also schedule recurring tasks, by adding a +2d or +1w. Each time this task is completed, it will be scheduled for it's next date.

Tags

Markup

# export-options at top of file
#+title: My Paper
#+author: Darth Vader

# headers
* Heading 1
** Heading 2

# markup
*bold*
/italic/
_underline_
+strikethrough+
~code~
=verbatim=

# lists
1. Foo
  - item a
  - item b
2. Bar
  - item a
  - item b

- [ ] check me
- [x] checked

# links
[[http://google.com]]
[[http://google.com][google]]
[[file:~/Pictures/foo.png]]

# code-blocks

#+begin_src python
def foo():
    print('hi')
#+end_src

Tags

https://orgmode.org/manual/Tags.html

  • tags support inheritance
  • you may pre-define tags globally, and complete them
  • you may pre-define tags for a specific file, and complete them
#                         +---+---- these are both tags
#                        /   /
** My Heading     :testing:heading: