cycling TODOs

[djp]

just a little thing, but has me stumped.

to cycle a TODO, from (because I chose it in my .vimrc) it should go from
let g:org_todo_setup='TODO NEXT STARTED | DONE CANCELED'
and according ro vimorg.txt that cycling should be done with <s-enter>
but <shift-enter> in normal mode, just starts a new heading..
what am I missing? (other than sleep)

[Herbert Sitz]

David -- Glad you got it going.

The operation of <shift-enter> depends on whether you're in normal or
insert mode. In normal mode it will cycle todos but in insert it adds
new section.

Some of the usual key combos (e.g., some <c-_> and <alt-_> combos) are
not available in console vim b/c terminals don't recognize them. And
console version may have some issues that aren't in gvim, since I
rarely use terminal version. But let me know of any problems you
have.

Cheers,

Herb

[Herbert Sitz]

On Mon, Dec 31, 2012 at 5:14 PM, djp <dava...@gmail.com> wrote:
>

> but <shift-enter> in normal mode, just starts a new heading..
> what am I missing? (other than sleep)

Just noticed you did say this was in normal mode. I'll double check,
but I think <s-enter> may be one of those unmappable keys in terminal.
I think there's different mapping for cycling todos in terminal but
can't remember at moment, if not I can add one to default config. See
:h vimorg-keybindings-terminal .

[Herbert Sitz]

On Mon, Dec 31, 2012 at 5:14 PM, djp <dava...@gmail.com> wrote:

okay, taking a quick look one solution is to use the built-in todo
dashboard. Key combo ,t brings up dashboard, then f will cycle
forward.

[djp]

cool! that works, and makes mnemonic sense too!

[djp]

y'know, if there's significant differences for commands and key-mapability, between console vim and gvim, and then differences between normal mode and edit mode, then perhaps the docs might sport some of that amazing text-table action! I might take a swing at that, just to get more familiar with the commands, and to help-out, of course :)