Understanding preset Headers

[MarshCastle]

I'm loving this - thanks for a wicked project :D. I'm having a bit of a struggle understanding preset headers though. The way I understood it was that it's a way to tag / set tasks via their placement in the doc - is that right? as in... I have a project:

- GrowACarrot:
consisting of 5 tasks:
- [ ] dig soil
- [ ] plant seed
- [ ] add water
- [ ] dig carrot
- [ ] eat carrot

The way I understood it is that I can add tags by organising the tasks in Vimwiki - so I can do this with a Preset Header via:

== Carrot Growing || project GrowACarrot ==
A Project growing carrots
=== Prep || +preparation ===
- [ ] dig soil
=== Work || +work ===
- [ ] plant seed
- [ ] add water
- [ ] dig carrot
=== Enjoy || +enjoy ===
- [ ] Eat Carrot

I'm expecting that my tasks get tagged accordingly - Am I off the plot (I've very likely misread / misunderstood it), or is it just not working?

I think I got confused around the bit that said:

...it sets a filter for all viewports and default attributes for all new tasks in the corresponding section.

I've got to know - am I right in my thinking?

[tbabej]

Hi there,

try the following:

== Carrot Growing || project:GrowACarrot ==
A Project growing carrots

=== Prep | +preparation ===
* [ ] dig soil

=== Work | +work ===
* [ ] plant seed
* [ ] add water
* [ ] dig carrot

=== Enjoy | +enjoy ===
* [ ] Eat Carrot

reasons for changes I introduced:

1. The enumeration symbol for taskwiki tasks is '*'
2. A empty line should occur between subheadings
3. Only the very first header makes sense as the preset-only header, the subheaders should use regular filters (which also manifest themselves as defaults) to actually also list the tasks that match the filter (i.e. such that a task added via CLI inserts itself into the file)

[patosullivan]

I also have a question about preset headers, and it seems this might be the best place to ask it:

Should I be able to move tasks between preset headers and have those defaults get updated on the tasks? I.e., move "dig soil" from "Prep" to "Work" in the example given above?

I'm trying to use taskwiki in a GTD workflow, so I'm moving some tasks from one category to another pretty frequently. I've noticed that the change won't persist if I move a task from one tag to another in a task wiki page.

[roccowong95]

I also have a question about preset headers, and it seems this might be the best place to ask it:

Should I be able to move tasks between preset headers and have those defaults get updated on the tasks? I.e., move "dig soil" from "Prep" to "Work" in the example given above?

I'm trying to use taskwiki in a GTD workflow, so I'm moving some tasks from one category to another pretty frequently. I've noticed that the change won't persist if I move a task from one tag to another in a task wiki page.

+1 on this. It doesn't seem to work as expected...

[folofjc]

I also have a question on preset headers. For viewports, when you press <CR> it shows the viewport info in a buffer as well as showing the tags that were hidden on the line. However, for preset headers, when I press <CR> it actually makes it a link (which is the vimwiki syntax of pressing enter on some item). It does show the hidden tags for the header, but only if I press enter on the markdown header syntax (i.e. the ## in front). If I press enter anywhere else on the line, it simply makes a link and does not show the hidden tags.