Next: Faces for TODO keywords, Previous: Fast access to TODO states, Up: TODO extensions [Contents][Index]

#### 5.2.5 Setting up keywords for individual files

It can be very useful to use different aspects of the TODO mechanism in different files. For file-local settings, you need to add special lines to the file which set the keywords and interpretation for that file only. For example, to set one of the two examples discussed above, you need one of the following lines, starting in column zero anywhere in the file:

    #+TODO: TODO FEEDBACK VERIFY | DONE CANCELED

(you may also write `#+SEQ_TODO` to be explicit about the interpretation, but it means the same as `#+TODO`), or

    #+TYP_TODO: Fred Sara Lucy Mike | DONE

A setup for using several sets in parallel would be:

    #+TODO: TODO | DONE
    #+TODO: REPORT BUG KNOWNCAUSE | FIXED
    #+TODO: | CANCELED

To make sure you are using the correct keyword, type ‘`#+`’ into the buffer and then use `M-TAB` completion.

Remember that the keywords after the vertical bar (or the last keyword if no bar is there) must always mean that the item is DONE (although you may use a different word). After changing one of these lines, use `C-c C-c` with the cursor still in the line to make the changes known to Org mode51.

#### Footnotes

### (51)

Org mode parses these lines only when Org mode is activated after visiting a file. `C-c C-c` with the cursor in a line starting with ‘`#+`’ is simply restarting Org mode for the current buffer.