forked from sachac/emacs-notes
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathbaby-steps-org.html
executable file
·754 lines (678 loc) · 30 KB
/
baby-steps-org.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!-- 2016-12-18 Sun 16:09 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>A Baby Steps Guide to Managing Your Tasks with Org</title>
<meta name="generator" content="Org-mode" />
<meta name="author" content="Sacha Chua" />
<style type="text/css">
<!--/*--><![CDATA[/*><!--*/
.title { text-align: center;
margin-bottom: .2em; }
.subtitle { text-align: center;
font-size: medium;
font-weight: bold;
margin-top:0; }
.todo { font-family: monospace; color: red; }
.done { font-family: monospace; color: green; }
.priority { font-family: monospace; color: orange; }
.tag { background-color: #eee; font-family: monospace;
padding: 2px; font-size: 80%; font-weight: normal; }
.timestamp { color: #bebebe; }
.timestamp-kwd { color: #5f9ea0; }
.org-right { margin-left: auto; margin-right: 0px; text-align: right; }
.org-left { margin-left: 0px; margin-right: auto; text-align: left; }
.org-center { margin-left: auto; margin-right: auto; text-align: center; }
.underline { text-decoration: underline; }
#postamble p, #preamble p { font-size: 90%; margin: .2em; }
p.verse { margin-left: 3%; }
pre {
border: 1px solid #ccc;
box-shadow: 3px 3px 3px #eee;
padding: 8pt;
font-family: monospace;
overflow: auto;
margin: 1.2em;
}
pre.src {
position: relative;
overflow: visible;
padding-top: 1.2em;
}
pre.src:before {
display: none;
position: absolute;
background-color: white;
top: -10px;
right: 10px;
padding: 3px;
border: 1px solid black;
}
pre.src:hover:before { display: inline;}
/* Languages per Org manual */
pre.src-asymptote:before { content: 'Asymptote'; }
pre.src-awk:before { content: 'Awk'; }
pre.src-C:before { content: 'C'; }
/* pre.src-C++ doesn't work in CSS */
pre.src-clojure:before { content: 'Clojure'; }
pre.src-css:before { content: 'CSS'; }
pre.src-D:before { content: 'D'; }
pre.src-ditaa:before { content: 'ditaa'; }
pre.src-dot:before { content: 'Graphviz'; }
pre.src-calc:before { content: 'Emacs Calc'; }
pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
pre.src-fortran:before { content: 'Fortran'; }
pre.src-gnuplot:before { content: 'gnuplot'; }
pre.src-haskell:before { content: 'Haskell'; }
pre.src-java:before { content: 'Java'; }
pre.src-js:before { content: 'Javascript'; }
pre.src-latex:before { content: 'LaTeX'; }
pre.src-ledger:before { content: 'Ledger'; }
pre.src-lisp:before { content: 'Lisp'; }
pre.src-lilypond:before { content: 'Lilypond'; }
pre.src-lua:before { content: 'Lua'; }
pre.src-matlab:before { content: 'MATLAB'; }
pre.src-mscgen:before { content: 'Mscgen'; }
pre.src-ocaml:before { content: 'Objective Caml'; }
pre.src-octave:before { content: 'Octave'; }
pre.src-org:before { content: 'Org mode'; }
pre.src-oz:before { content: 'OZ'; }
pre.src-plantuml:before { content: 'Plantuml'; }
pre.src-processing:before { content: 'Processing.js'; }
pre.src-python:before { content: 'Python'; }
pre.src-R:before { content: 'R'; }
pre.src-ruby:before { content: 'Ruby'; }
pre.src-sass:before { content: 'Sass'; }
pre.src-scheme:before { content: 'Scheme'; }
pre.src-screen:before { content: 'Gnu Screen'; }
pre.src-sed:before { content: 'Sed'; }
pre.src-sh:before { content: 'shell'; }
pre.src-sql:before { content: 'SQL'; }
pre.src-sqlite:before { content: 'SQLite'; }
/* additional languages in org.el's org-babel-load-languages alist */
pre.src-forth:before { content: 'Forth'; }
pre.src-io:before { content: 'IO'; }
pre.src-J:before { content: 'J'; }
pre.src-makefile:before { content: 'Makefile'; }
pre.src-maxima:before { content: 'Maxima'; }
pre.src-perl:before { content: 'Perl'; }
pre.src-picolisp:before { content: 'Pico Lisp'; }
pre.src-scala:before { content: 'Scala'; }
pre.src-shell:before { content: 'Shell Script'; }
pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
/* additional language identifiers per "defun org-babel-execute"
in ob-*.el */
pre.src-cpp:before { content: 'C++'; }
pre.src-abc:before { content: 'ABC'; }
pre.src-coq:before { content: 'Coq'; }
pre.src-groovy:before { content: 'Groovy'; }
/* additional language identifiers from org-babel-shell-names in
ob-shell.el: ob-shell is the only babel language using a lambda to put
the execution function name together. */
pre.src-bash:before { content: 'bash'; }
pre.src-csh:before { content: 'csh'; }
pre.src-ash:before { content: 'ash'; }
pre.src-dash:before { content: 'dash'; }
pre.src-ksh:before { content: 'ksh'; }
pre.src-mksh:before { content: 'mksh'; }
pre.src-posh:before { content: 'posh'; }
/* Additional Emacs modes also supported by the LaTeX listings package */
pre.src-ada:before { content: 'Ada'; }
pre.src-asm:before { content: 'Assembler'; }
pre.src-caml:before { content: 'Caml'; }
pre.src-delphi:before { content: 'Delphi'; }
pre.src-html:before { content: 'HTML'; }
pre.src-idl:before { content: 'IDL'; }
pre.src-mercury:before { content: 'Mercury'; }
pre.src-metapost:before { content: 'MetaPost'; }
pre.src-modula-2:before { content: 'Modula-2'; }
pre.src-pascal:before { content: 'Pascal'; }
pre.src-ps:before { content: 'PostScript'; }
pre.src-prolog:before { content: 'Prolog'; }
pre.src-simula:before { content: 'Simula'; }
pre.src-tcl:before { content: 'tcl'; }
pre.src-tex:before { content: 'TeX'; }
pre.src-plain-tex:before { content: 'Plain TeX'; }
pre.src-verilog:before { content: 'Verilog'; }
pre.src-vhdl:before { content: 'VHDL'; }
pre.src-xml:before { content: 'XML'; }
pre.src-nxml:before { content: 'XML'; }
/* add a generic configuration mode; LaTeX export needs an additional
(add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
pre.src-conf:before { content: 'Configuration File'; }
table { border-collapse:collapse; }
caption.t-above { caption-side: top; }
caption.t-bottom { caption-side: bottom; }
td, th { vertical-align:top; }
th.org-right { text-align: center; }
th.org-left { text-align: center; }
th.org-center { text-align: center; }
td.org-right { text-align: right; }
td.org-left { text-align: left; }
td.org-center { text-align: center; }
dt { font-weight: bold; }
.footpara { display: inline; }
.footdef { margin-bottom: 1em; }
.figure { padding: 1em; }
.figure p { text-align: center; }
.inlinetask {
padding: 10px;
border: 2px solid gray;
margin: 10px;
background: #ffffcc;
}
#org-div-home-and-up
{ text-align: right; font-size: 70%; white-space: nowrap; }
textarea { overflow-x: auto; }
.linenr { font-size: smaller }
.code-highlighted { background-color: #ffff00; }
.org-info-js_info-navigation { border-style: none; }
#org-info-js_console-label
{ font-size: 10px; font-weight: bold; white-space: nowrap; }
.org-info-js_search-highlight
{ background-color: #ffff00; color: #000000; font-weight: bold; }
.org-svg { width: 90%; }
/*]]>*/-->
</style>
<link rel="stylesheet" type="text/css"
href="http://sachachua.com/blog/wp-content/themes/sacha-v3/foundation/css/foundation.min.css"></link>
<link rel="stylesheet" type="text/css" href="http://sachachua.com/org-export.css"></link>
<link rel="stylesheet" type="text/css" href="http://sachachua.com/blog/wp-content/themes/sacha-v3/style.css"></link>
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js"></script>
<script type="text/javascript">
/*
@licstart The following is the entire license notice for the
JavaScript code in this tag.
Copyright (C) 2012-2013 Free Software Foundation, Inc.
The JavaScript code in this tag is free software: you can
redistribute it and/or modify it under the terms of the GNU
General Public License (GNU GPL) as published by the Free Software
Foundation, either version 3 of the License, or (at your option)
any later version. The code is distributed WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE. See the GNU GPL for more details.
As additional permission under GNU GPL version 3 section 7, you
may distribute non-source (e.g., minimized or compacted) forms of
that code without the copy of the GNU GPL normally required by
section 4, provided you include this license notice and a URL
through which recipients can access the Corresponding Source.
@licend The above is the entire license notice
for the JavaScript code in this tag.
*/
<!--/*--><![CDATA[/*><!--*/
function CodeHighlightOn(elem, id)
{
var target = document.getElementById(id);
if(null != target) {
elem.cacheClassElem = elem.className;
elem.cacheClassTarget = target.className;
target.className = "code-highlighted";
elem.className = "code-highlighted";
}
}
function CodeHighlightOff(elem, id)
{
var target = document.getElementById(id);
if(elem.cacheClassElem)
elem.className = elem.cacheClassElem;
if(elem.cacheClassTarget)
target.className = elem.cacheClassTarget;
}
/*]]>*///-->
</script>
</head>
<body>
<div id="preamble" class="status">
<a name="top" id="top"></a>
</div>
<div id="content">
<h1 class="title">A Baby Steps Guide to Managing Your Tasks with Org</h1>
<div id="table-of-contents">
<h2>Table of Contents</h2>
<div id="text-table-of-contents">
<ul>
<li><a href="#orgd7a373a">Some notes</a></li>
<li><a href="#orgd638dac">Things you don't have to worry about</a></li>
<li><a href="#org1bf5b0d">Start with an outline</a></li>
<li><a href="#org64a7632">Finish tasks</a></li>
<li><a href="#orgd96d9d2">Automatically open your todo.org every time you start Emacs</a></li>
<li><a href="#define-shortcuts">Define shortcuts for managing TODO states</a></li>
<li><a href="#orgdb8e566">Organize your tasks into projects</a></li>
<li><a href="#org63c0a18">Schedule your tasks and use the agenda</a></li>
<li><a href="#org060ee39">Automatically open your agenda whenever you start Emacs</a></li>
<li><a href="#orge2346c8">Sections to be written</a></li>
<li><a href="#org5d0ad37">Notes</a></li>
</ul>
</div>
</div>
<p>
Work in progress. Questions/ideas? <a href="mailto:[email protected]">[email protected]</a>
</p>
<p>
You can find this document at <a href="http://sach.ac/baby-steps-org-todo">http://sach.ac/baby-steps-org-todo</a>. Github: <a href="https://github.com/sachac/emacs-notes">https://github.com/sachac/emacs-notes</a>
</p>
<p>
(c) 2014 Sacha Chua - Creative Commons Attribution License (feel free to use, share, remix)
</p>
<div class="figure">
<p><a href="http://sachachua.com/blog/wp-content/uploads/2014/02/2014-02-08-A-path-toward-taming-your-TODO-list.png"><img src="http://sachachua.com/blog/wp-content/uploads/2014/02/2014-02-08-A-path-toward-taming-your-TODO-list-640x486.png" alt="2014-02-08-A-path-toward-taming-your-TODO-list-640x486.png" /></a>
</p>
</div>
<div class="figure">
<p><a href="http://sachachua.com/blog/wp-content/uploads/2014/02/2014-02-16-Org-TODO-basics.png"><img src="http://sachachua.com/blog/wp-content/uploads/2014/02/2014-02-16-Org-TODO-basics-640x482.png" alt="2014-02-16-Org-TODO-basics-640x482.png" /></a>
</p>
</div>
<p>
<a href="http://sachachua.com/blog/2014/01/tips-learning-org-mode-emacs/">Getting started with Org</a>
</p>
<div id="outline-container-orgd7a373a" class="outline-2">
<h2 id="orgd7a373a">Some notes</h2>
<div class="outline-text-2" id="text-orgd7a373a">
<p>
I'll assume you're using Emacs 24 or later, and you've gone through
the Emacs Tutorial with <code>C-h t</code> (<code>help-with-tutorial</code>). Assuming
standard Emacs configuration (no evil-mode, etc.). I'll give the
commands as well as the keybindings just in case you've remapped
things.
</p>
</div>
</div>
<div id="outline-container-orgd638dac" class="outline-2">
<h2 id="orgd638dac">Things you don't have to worry about</h2>
<div class="outline-text-2" id="text-orgd638dac">
<p>
Don't worry about the fancy ways that other people use Org. Don't
worry about synchronization, integration, duplication of information,
mobile devices, or whether this will be ultimately worth it. =) You
can start off by using Org to manage a small part of your life - maybe
one of your projects.
</p>
</div>
</div>
<div id="outline-container-org1bf5b0d" class="outline-2">
<h2 id="org1bf5b0d">Start with an outline</h2>
<div class="outline-text-2" id="text-org1bf5b0d">
<p>
Start with a single file (probably <code>~/todo.org</code>). I recommend using this kind of Org structure:
</p>
<div class="org-src-container">
<pre class="src src-org"><span class="org-org-level-1">* Tasks</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Most important thing that you have to do</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Second most important thing that you have to do</span>
You can also take notes underneath each heading, like this
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Etc.</span>
</pre>
</div>
<p>
The single <code>*</code> at Tasks makes it a top-level heading, while <code>**</code> means
that the TODOs are second-level headings under the <code>Tasks</code> heading.
Technically, you don't need to do this yet, but it's a good habit to
get into.
</p>
<p>
Use <code>M-up</code> (<code>org-metaup</code>) and <code>M-down</code> (<code>org-metadown</code>) to move headings up or down.
</p>
<p>
<code>M-S-return</code> (<code>org-insert-todo-heading</code>) inserts a new heading at the same level as the previous one, which is handy if you're creating a whole bunch of TODOs in a row. This keyboard shortcut might not work if you're using Emacs on a console.
</p>
<p>
When you're starting out, you can get rid of finished tasks by using <code>C-k</code> (<code>org-kill-line</code>) to delete the line. Later, you'll see how you can keep them around for reference.
</p>
</div>
</div>
<div id="outline-container-org64a7632" class="outline-2">
<h2 id="org64a7632">Finish tasks</h2>
<div class="outline-text-2" id="text-org64a7632">
<p>
If you're done with a task, change <code>TODO</code> to <code>DONE</code>. If you get tired
of doing this manually, jump ahead to the section <a href="#define-shortcuts">Define shortcuts for managing TODO states</a>.
</p>
<p>
You can look through your tasks to see what you still need to
do. If you want to see your unfinished tasks in the context of your
outline, use <code>C-c / t</code> (<code>org-sparse-tree</code> with the "<code>t</code>" option). Use
<code>S-Tab</code> (<code>org-shifttab</code>) to go through different levels of visibility.
</p>
<p>
You can use <code>M-down</code> (<code>org-metadown</code>) to move DONE tasks downwards, or
you can move them to an archive file with <code>C-c $</code>
(<code>org-archive-subtree</code>). If you get tired of moving DONE tasks
downwards manually, you can use <code>M-x org-sort-entries</code> on your <code>*
Tasks</code> heading to sort tasks by todo order (type <b>o</b> to select that
one).
</p>
<p>
Remember, Org Mode is just plain text. If you don't remember how to do
something but you know what the text should look like, you can
typically just edit it. You can also use the standard Emacs navigation
commands like <code>C-s</code> (<code>isearch-forward</code>) and <code>C-r</code> (<code>isearch-backward</code>)
to look for stuff.
</p>
</div>
</div>
<div id="outline-container-orgd96d9d2" class="outline-2">
<h2 id="orgd96d9d2">Automatically open your todo.org every time you start Emacs</h2>
<div class="outline-text-2" id="text-orgd96d9d2">
<p>
Make your life a little bit easier by automatically opening <code>~/todo.org</code> every time you open Emacs. Add this to the end of your Emacs configuration. To do that,
</p>
<ol class="org-ol">
<li><code>C-x C-f ~/.emacs.d/init.el</code> - use <code>find-file</code> to open your configuration file. If it does not yet exist, it is created.</li>
<li>Go to the end of this file. (Handy shortcut: <code>C-end</code>)</li>
<li>Add <code>(find-file "~/todo.org")</code></li>
<li>Save with <code>C-x C-s</code> (<code>save-buffer</code>).</li>
</ol>
<p>
You can test it with <code>M-x eval-buffer</code> while looking at your <code>~/.emacs.d/init.el</code>. If it works, it should show you your <code>~/todo.org</code> file.
</p>
<p>
You have just written a little Emacs Lisp. Totally not scary.
</p>
</div>
</div>
<div id="outline-container-orgfd28fda" class="outline-2">
<h2 id="define-shortcuts"><a id="orgfd28fda"></a>Define shortcuts for managing TODO states</h2>
<div class="outline-text-2" id="text-define-shortcuts">
<p>
So far, you've just been using Org Mode as a simple outliner with some
colors. The next step is to tell it a little more about how you want
to manage your TODOs. Here you're going to customize your TODO
keywords and assign keyboard shortcuts. This isn't covered until
section 5.2.4 in the Info manual (<code>(org) Fast access to TODO states</code>),
but it's useful and you should get the shortcuts into your muscle
memory as soon as you can.
</p>
<ol class="org-ol">
<li>Use <code>M-x customize-variable org-todo-keywords</code></li>
<li>Change <code>TODO</code> to <code>TODO(t)</code> and <code>DONE</code> to <code>DONE(d)</code>. The letters in
the parentheses are the shortcuts you can type to select that
state. You can change the letters if you prefer a different
shortcut, like setting it to <code>DONE(x)</code>.</li>
<li>Add other TODO states if you want. Some useful states include
<code>WAITING(w)</code> and <code>SOMEDAY(s)</code>. Make sure that the last state you
have is <code>DONE(d)</code> (or whatever keyboard shortcut you set it to),
and that all the keyboard shortcuts are unique. If you want to have
more than one DONE state, see the documentation in the manual.</li>
<li>Use <b>Apply and save</b> to save the changes so that Emacs will keep the customizations after you restart.</li>
</ol>
<p>
If you have your <code>~/todo.org</code> open, go to that buffer and reload it
with <code>M-x org-mode</code> so that it recognizes any new keywords and
shortcuts you've defined.
</p>
<p>
Now you can use <code>C-c C-t</code> (<code>org-todo</code>) to quickly set the <code>TODO</code> state
of any heading by typing its shortcut.
</p>
</div>
</div>
<div id="outline-container-orgdb8e566" class="outline-2">
<h2 id="orgdb8e566">Organize your tasks into projects</h2>
<div class="outline-text-2" id="text-orgdb8e566">
<p>
Okay. Now you have lots of tasks, and you know how to mark them as
DONE. You might even have a few additional states. At some point,
you'll probably have a really long list of tasks, and maybe you're
getting tired of searching through it for tasks that are related to a
single project.
</p>
<p>
Time to organize things better. This is how you want your Org file to look:
</p>
<div class="org-src-container">
<pre class="src src-org"><span class="org-org-level-1">* Project ABC</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> A task related to Project ABC</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Another task related to ABC</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Etc.</span>
<span class="org-org-level-1">* Project XYZ</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> A task related to Project XYZ</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Another task related to XYZ</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Etc.</span>
<span class="org-org-level-1">* Tasks</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Miscellaneous</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> tasks</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> go here</span>
</pre>
</div>
<p>
As before, one star (<code>*</code>) means it's a first-level heading, and two stars (<code>**</code>) means it's a second-level heading underneath whatever first-level heading was before it.
</p>
<p>
Unless your Tasks list is short or you're feeling particularly diligent, I recommend not worrying too much about your previous tasks and instead focusing on keeping things organized going forward. Think about the projects you're currently working and create headings for them. Create tasks underneath them, remembering to use <code>**</code>.
</p>
<p>
Here's where it gets interesting. Try pressing <code>S-tab</code> (<code>org-shifttab</code>) a few times to see how you can change the visibility of the outline for the entire buffer.
This is why we got you started with putting your tasks under the <code>* Tasks</code> heading, so all of your tasks don't clutter up the neat "everything is collapsed so I can focus on my projects" view.
</p>
<p>
Now go to one of your project headings and press <code>tab</code> (<code>org-cycle</code>). Do that a few times as well.
</p>
<p>
So now, when you're working on a project, you can press TAB to view the tasks underneath it. When you're not working on the project, you can use TAB to hide the details.
</p>
<p>
You can even go wild and have subtasks, like this. Org can deal with as many levels as you want.
</p>
<div class="org-src-container">
<pre class="src src-org"><span class="org-org-level-1">* Project ABC</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> A task related to Project ABC</span>
<span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Another task related to ABC</span>
<span class="org-org-level-3">*** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-3"> Subtask</span>
<span class="org-org-level-3">*** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-3"> Another subtask</span>
<span class="org-org-level-3">*** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-3"> A third subtask</span>
</pre>
</div>
<p>
TAB works on those headings too.
</p>
<p>
Stick with this until you start getting annoyed with jumping around to
see what tasks you need to work on today and when tasks are due.
That's in the next section, on scheduling tasks.
</p>
</div>
</div>
<div id="outline-container-org63c0a18" class="outline-2">
<h2 id="org63c0a18">Schedule your tasks and use the agenda</h2>
<div class="outline-text-2" id="text-org63c0a18">
<p>
Okay. So now you have projects and tasks, and you're jumping all over
the place to find tasks to work on or keep track of deadlines.
This is where scheduling and the Org agenda come in.
</p>
<p>
First, we need to add your <code>~/todo.org</code> to the list of files Org looks at when coming up with the agenda. Open your <code>~/todo.org</code> and type <code>C-c [</code> (<code>org-agenda-file-to-front</code>). This adds the current file to the list.
</p>
<p>
Next, we're going to schedule some tasks. Go to a task that you want
to do today. Press <code>C-c C-s</code> (<code>org-schedule</code>) and accept the default.
Schedule a couple of other tasks for today.
</p>
<p>
Schedule some tasks for tomorrow, too. This time, when you schedule
it, type <code>+1</code> for the date. You can specify <code>+2</code> for the day after
tomorrow, etc. The 28th? <code>28</code>. If you want to schedule something for
next Saturday, you can type <code>sat</code>. Two Tuesdays from now? <code>2thu</code>. A
month from now? <code>1m</code>. It's really flexible.
</p>
<p>
Anyway, scheduling should give you a task that looks something like this
</p>
<div class="org-src-container">
<pre class="src src-org"><span class="org-org-level-2">** </span><span class="ATTRLIST">TODO</span><span class="org-org-level-2"> Fix the widget</span>
<span class="org-org-special-keyword">SCHEDULED:</span> <span class="org-org-date"><2014-02-28 Fri></span>
</pre>
</div>
<p>
To see your scheduled tasks in your agenda, type <code>M-x org-agenda</code> and choose <code>a</code> (Agenda for the current week or day). You can use <code>f</code> (<code>org-agenda-later</code>) and <code>b</code> (<code>org-agenda-earlier</code>) to go forward or backward. You can use <code>t</code> (<code>org-agenda-todo</code>) to change the TODO state of a task. You can reschedule it by using <code>S-right</code> (<code>org-agenda-do-date-later</code>) and <code>M-left</code> (<code>org-agenda-do-date-earlier</code>) with <code>C-c C-s</code> (<code>org-agenda-schedule</code>). Press <code>RET</code> to jump to a task.
</p>
<p>
You will probably want to refer to your agenda often. If you haven't done so yet, add the following to your <code>~/.emacs.d/init.el</code>:
</p>
<div class="org-src-container">
<pre class="src src-emacs-lisp">(global-set-key (kbd <span class="org-string">"C-c a"</span>) 'org-agenda)
</pre>
</div>
<p>
Afterwards, load your configuration into your current Emacs with <code>M-x eval-buffer</code> (while you're in the <code>init.el</code> buffer). Now you should be able to type <code>C-c a a</code> to get to your agenda.
</p>
<p>
Org Agenda is really powerful. Check out the info manual for Org Mode with <code>C-h i</code> (<code>info</code>) to learn more, including how to customize the number of days initially displayed and what day your week starts on.
</p>
</div>
</div>
<div id="outline-container-org060ee39" class="outline-2">
<h2 id="org060ee39">Automatically open your agenda whenever you start Emacs</h2>
<div class="outline-text-2" id="text-org060ee39">
<p>
You can get Emacs to automatically open your agenda whenever you start it. Add the following lines to your <code>~/.emacs.d/init.el</code> file:
</p>
<div class="org-src-container">
<pre class="src src-emacs-lisp">(org-agenda nil <span class="org-string">"a"</span>)
</pre>
</div>
</div>
</div>
<div id="outline-container-orge2346c8" class="outline-2">
<h2 id="orge2346c8">Sections to be written</h2>
<div class="outline-text-2" id="text-orge2346c8">
</div><div id="outline-container-org73ddfcb" class="outline-3">
<h3 id="org73ddfcb">Work with deadlines</h3>
<div class="outline-text-3" id="text-org73ddfcb">
<p>
coming eventually. =)
</p>
</div>
</div>
<div id="outline-container-org5c8ae73" class="outline-3">
<h3 id="org5c8ae73">View your completed tasks</h3>
<div class="outline-text-3" id="text-org5c8ae73">
<p>
coming eventually. =)
</p>
</div>
</div>
<div id="outline-container-orgacf1df4" class="outline-3">
<h3 id="orgacf1df4">Work with multiple files</h3>
<div class="outline-text-3" id="text-orgacf1df4">
<p>
coming eventually. =)
</p>
</div>
</div>
<div id="outline-container-org94cc488" class="outline-3">
<h3 id="org94cc488">Use tags for types of tasks</h3>
<div class="outline-text-3" id="text-org94cc488">
<p>
coming eventually. =)
</p>
</div>
</div>
<div id="outline-container-org32adab1" class="outline-3">
<h3 id="org32adab1">Use different files or categories</h3>
<div class="outline-text-3" id="text-org32adab1">
<p>
See <a href="http://sachachua.com/blog/2016/12/using-categories-organize-org-agenda/">http://sachachua.com/blog/2016/12/using-categories-organize-org-agenda/</a>
</p>
</div>
</div>
<div id="outline-container-org74f4031" class="outline-3">
<h3 id="org74f4031">Filter your view</h3>
<div class="outline-text-3" id="text-org74f4031">
<p>
coming eventually. =)
</p>
</div>
</div>
<div id="outline-container-orgae5a4bf" class="outline-3">
<h3 id="orgae5a4bf">Track your time</h3>
<div class="outline-text-3" id="text-orgae5a4bf">
<p>
Coming eventually. =)
</p>
<div class="figure">
<p><a href="http://sachachua.com/blog/wp-content/uploads/2014/01/2014-01-06-Tracking-time-with-Org-mode.png"><img src="http://sachachua.com/blog/wp-content/uploads/2014/01/2014-01-06-Tracking-time-with-Org-mode-640x480.png" alt="2014-01-06-Tracking-time-with-Org-mode-640x480.png" /></a>
</p>
</div>
</div>
</div>
<div id="outline-container-orgc452581" class="outline-3">
<h3 id="orgc452581">Track your time estimates</h3>
<div class="outline-text-3" id="text-orgc452581">
<p>
coming eventually. =)
</p>
</div>
</div>
<div id="outline-container-org2a4afb8" class="outline-3">
<h3 id="org2a4afb8">Customize your agenda view</h3>
<div class="outline-text-3" id="text-org2a4afb8">
<p>
coming eventually. =)
</p>
</div>
</div>
<div id="outline-container-orgc8ea1d8" class="outline-3">
<h3 id="orgc8ea1d8">Extras</h3>
<div class="outline-text-3" id="text-orgc8ea1d8">
</div><div id="outline-container-orgb30f8b6" class="outline-4">
<h4 id="orgb30f8b6">Set up more than one TODO state for done tasks</h4>
<div class="outline-text-4" id="text-orgb30f8b6">
<p>
coming eventually. =)
</p>
</div>
</div>
</div>
</div>
<div id="outline-container-org5d0ad37" class="outline-2">
<h2 id="org5d0ad37">Notes</h2>
<div class="outline-text-2" id="text-org5d0ad37">
<p>
E-mail me at <a href="mailto:[email protected]">[email protected]</a> with questions or suggestions!
See <a href="http://sachachua.com/blog/emacs">my Emacs page</a> for more resources.
</p>
<p>
Acknowledgements: DaveP
</p>
</div>
</div>
</div>
<div id="postamble" class="status">
<style type="text/css">
.back-to-top {
position: fixed;
bottom: 2em;
right: 0px;
text-decoration: none;
color: #000000;
background-color: rgba(235, 235, 235, 0.80);
font-size: 12px;
padding: 1em;
display: none;
}
.back-to-top:hover {
background-color: rgba(135, 135, 135, 0.50);
}
</style>
<div class="back-to-top">
<a href="#top">Back to top</a> | <a href="mailto:[email protected]">E-mail me</a>
</div>
<script type="text/javascript">
var offset = 220;
var duration = 500;
jQuery(window).scroll(function() {
if (jQuery(this).scrollTop() > offset) {
jQuery('.back-to-top').fadeIn(duration);
} else {
jQuery('.back-to-top').fadeOut(duration);
}
});
</script>
</div>
</body>
</html>