I have a list of TODO items, and I'm trying to have 2 TODO lists in the same file, but can't seem to end the first one.
FIRST LIST: TODAY
* TODO Item 1
Description
* TODO Item 2
Description
SECOND LIST: TOMORROW
* TODO Item 3
Description
* TODO Item 4
Description
Unfortunately, SECOND LIST: TOMORROW is now part of the description of TODO Item 2. By this, I mean that when I hit shift-tab, I no longer see the text SECOND LIST: TOMORROW because it folds under TODO Item 2. What I see is..
FIRST LIST: TODAY
* TODO Item 1
* TODO Item 2
* TODO Item 3
* TODO Item 4
While what I'd like to see is...
FIRST LIST: TODAY
* TODO Item 1
* TODO Item 2
SECOND LIST: TOMORROW
* TODO Item 3
* TODO Item 4
How can I escape out of the description mode and start a new, independent list?
EDIT/UPDATE I added spaces in between the lists in response to comments. From here, 'A list ends whenever every item has ended, which means before any line less or equally indented than items at top level. It also ends before two blank lines'---From this, I suspect there must be a way to have more than one list in a .org file. However, in my example, I notice 2 blank lines is not ending the list, but continues on as if a description.
Is this a feature of it being somehow an agenda rather than a plain list? I know that the following enumerated /does/ end the list on the other hand:
FIRST LIST: TODAY
1. Item 1
Description
2. Item 2
Description
Second LIST: Tomorrow
1. Item 3
Description
2. Item 4
Description
I really don't mean any disrespect to you emacs wizards (who amaze me) in that I keep insisting on finding a way to do this, and I understand there's a lot of power to this tool I don't understand yet. But I would like to have 2 independent non-enumerated todo lists in one .org file, so I can quickly (for me) shuffle unfinished tasks from today to tomorrow without going into depth setting dependencies and due dates.
Very simple, just make the two headers become list items themselves., like so:
* first todo list.
** first item in list.
** second item in list
* second todo list
** first item and so on...
This additionally gives you the ability to fold the lists.
You cannot do so within a single file. Org treats all content under a headline as belonging to it until you reach another headline of the same level. There is no way to end a headline short of starting a new one.
This does have a few shortcomings in that you have to use blank headlines if you want a sub-heading and then to return to the parent level without any new headline. This means the only text that does not belong to a headline is the text before the first heading, which essentially is the equivalent of an abstract.
The two solutions I can think of would be
Use a solution such as the one offered by daramarak
Use 2 separate Org files then use the Agenda as a way of keeping track of the multiple TODOs in independent lists that can still be put together to see an overview.
Plain lists start with '-' and they end at white-space lines:
First list
- Item 1
- Item 2
Second List
- Item 1
- Item 2
But TODO's can only be recognized in a headlines (starting with a *). I think this is a part of the org-mode design. You can quickly turn a list into headings by marking the lines and pressing C-c *.
A similar but more light-weight feature to TODO's, "checkboxes", can however be used in plain lists for having a list of subtask.
List a
- [X] Item 1
- [ ] Item 2
List B
- [ ] Item 1
- [ ] Item 2
C-c C-c Toggles a list item. Also lists can be nested and show the satus of their children.
- [ ] List A
- [ ] Item 1
- [ ] Item 2
- [-] List B
- [X] Item 1
- [ ] Item 2
Another possibility is using inline tasks C-c C-x t they have a specific ending
List 1
*************** TODO Item 1
*************** END
*************** TODO Item 2
*************** END
List 2
*************** TODO Item 1
*************** END
*************** TODO Item 2
*************** END
*************** TODO
*************** END
More discussion can be found here
Related
I'm helping my fiancé clean up some MS Word documents with a structure something like...
<example>
1. Level 1 Heading
Paragraph text.
Paragraph text.
2. Level 1 Heading
Paragraph text.
2.1. Level 2 Heading
Paragraph text.
List item
List item
List item
2.2. Level 2 Heading
Paragraph text.
List item
List item
List item
3. Level 1 Heading
Paragraph text.
3.1. Level 2 Heading
Paragraph text.
3.1.1. Level 3 Heading
Paragraph text.
List item
List item
List item
Paragraph text.
List item
List item
List item
3.1.2. Level 3 Heading
Paragraph text.
List item
List item
List item
</example>
As I'm trying to do it, those hierarchical headings should be automatically numbered, & the numbered lists should be independent of the numbering of the headings.
I can do this easily in Apple's Pages, but am finding it impossible in Word. What happens is the numbered lists continue from the numbering of the heading above, then the heading below inherits from the last item of a list.
Advice needed.
I'm creating README.md file for my Repo in github, but i cant indent the code blocks as much as my list items has indent from the left, I'm trying as bottom and i want this block of code to start with indention of list items.
* list
* Item one
* ``` codes here..```
also it didn't worked :( don't know why.
Skip a line and indent eight spaces. Eight spaces will trigger the code block.
List
Item one
This is
a code block
I had to manually indent these lines
Item three
The above is the output of
* List
* Item one
* ```
This is
a code block
I had to manually indent these lines
```
* Item three
Does this help?
You need to add blank lines to make it work with the 8 spaces. Now because your item one is already 4 spaces in you need to add 12 spaces (4 + 8 = 12) like so
* list
* item one
codes here..
Which will then look like:
list
item one
codes here..
I write this in org-mode
SomeTopic
Anything I can click here to automatically create the below 1.
Anything I can click here to automatically create the below 1. automatically indented below?
1.
For example, I have this line (non header, text):
1. some item
I want to click something so it will open 2. so after I click that something I will have:
1. some item
2.
Try M-RET which is bound to org-meta-return which in list context calls
org-insert-item. E.g.
* foo
Let's have a list:
1. itemX
where X marks the position of the cursor.
Now press M-RET:
* foo
Let's have a list:
1. item
2.
The Plain lists section of the manual explains this and many other things that you can do with lists.
Suppose we have this in org file:
* Shopping
I'm going to buy these items in the grocery;
1. item1
wow, fantasy
2. item2
emmmmm
when i <tab> the headline Shopping, it display the details of plain list items.
what i want is below instead:
* Shopping
I'm going to buy these items in the grocery;
1. item1...
2. item2...
I have try add both #+STARTUP: overview and property :VISIBILITY: folded, but neither of them works for me.
(setq org-cycle-include-plain-lists 'integrate) should fix your issue.
From the docs: If this variable is set to integrate, plain list items will be treated like low-level headlines.
I have a heading in my orgmode file. It is automatically updated periodically with new children. I want the heading line to show the number of children.
So if I have one child it would say something like (1)
* Heading (1)
** Subheading
After it gets updated with another subheading the number should automatically be changed to (2)
* Heading (2)
** Subheading
** A new added subheading
I want it to do this because the toplevel heading will normally be collapsed. I want to be able to see if any new children were added to it without having to expand it
What's most similar to what you're searching are called statistics cookies. They're described at the end of this page in the manual. At first meant for lists, but that can also count headlines. Just put [/] at the end of your header, like so :
* Main header [/]
** sub-header 1
** sub-header 2
** sub-header 3
And press C-c C-c on the cookie to update it (make it update its count). What you do need to add to what you describe to be your use-case is TODO keywords to your headers, because what the cookie will count is how many are done over how many are to do. Therefore I suggest you mark them all as DONE, like so :
* Main header [3/3]
** DONE sub-header 1
** DONE sub-header 2
** DONE sub-header 3
Then, the counter will show you what you want.
You could probably adapt these cookies' code to meet your precise needs.