Fast Access to TODO States without C-t

Fast Access to TODO States without C-t

[Esben Stien]

I'm trying to figure out how to bind fast access to TODO states, without
using C-t.

The reason is that I have C-t as escape code for my screen session.

The command org-todo is bound to C-c t here, so when I try to fast
access to the TODO state DONE(d!), I can't get to it. 

C-c t d just puts 'd' in the buffer after switching to the next state. 

According to the manual, I'm supposed to hit C-c C-t d

Any pointers as to how I can do this?

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
           sip:b0ef@   e     e 
           jid:b0ef@    n     n

Re: Fast Access to TODO States without C-t

[Eric Abrahamsen]

Esben Stien <b0ef@esben-stien.name> writes:

> I'm trying to figure out how to bind fast access to TODO states, without
> using C-t.
>
> The reason is that I have C-t as escape code for my screen session.
>
> The command org-todo is bound to C-c t here, so when I try to fast
> access to the TODO state DONE(d!), I can't get to it. 
>
> C-c t d just puts 'd' in the buffer after switching to the next state. 
>
> According to the manual, I'm supposed to hit C-c C-t d
>
> Any pointers as to how I can do this?

I may be misunderstanding here, but screen will send the escape key to
the running program if you hit it twice, right? I use the StumpWM window
manager, with the escape key also set to C-t, and I think both of them
behave the same way: first escape is caught, second is sent to the
program. So you'd do C-c C-t C-t d. How does that work?

Also, if you set `org-use-speed-commands' to t, you can use single
keystrokes when point is to the left of headline stars. I find this
immensely useful. Get point to the left margin and hit "t", that's all
you need.

Yours,
Eric

Re: Fast Access to TODO States without C-t

[Esben Stien]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> I may be misunderstanding here, but screen will send the escape key to
> the running program if you hit it twice, right? I use the StumpWM window
> manager, with the escape key also set to C-t, and I think both of them
> behave the same way: first escape is caught, second is sent to the
> program. So you'd do C-c C-t C-t d. How does that work?

No, C-t C-t switches between screen windows.

> Also, if you set `org-use-speed-commands' to t, you can use single
> keystrokes when point is to the left of headline stars. I find this
> immensely useful. Get point to the left margin and hit "t", that's all
> you need.

This speedy gonzales command was really cool and I think I'll use that
for a lot of things;)

, but I don't see how I can have fast access to TODO states.

If I hit 't' over a TODO item, it just changes the state to the next
state. How can I jump to DONE(d!), f.ex?

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
           sip:b0ef@   e     e 
           jid:b0ef@    n     n

Re: Fast Access to TODO States without C-t

[Eric Abrahamsen]

Esben Stien <b0ef@esben-stien.name> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I may be misunderstanding here, but screen will send the escape key to
>> the running program if you hit it twice, right? I use the StumpWM window
>> manager, with the escape key also set to C-t, and I think both of them
>> behave the same way: first escape is caught, second is sent to the
>> program. So you'd do C-c C-t C-t d. How does that work?
>
> No, C-t C-t switches between screen windows.

Well there's got to be some way to send the escape sequence to the
running process! Googling indicates it might be C-t t -- does C-c C-t t
d work?

>> Also, if you set `org-use-speed-commands' to t, you can use single
>> keystrokes when point is to the left of headline stars. I find this
>> immensely useful. Get point to the left margin and hit "t", that's all
>> you need.
>
> This speedy gonzales command was really cool and I think I'll use that
> for a lot of things;)
>
> , but I don't see how I can have fast access to TODO states.
>
> If I hit 't' over a TODO item, it just changes the state to the next
> state. How can I jump to DONE(d!), f.ex?

I think I get the menu because I have org-use-fast-todo-selection set to
t. Look at the docstring for that variable and try a few different
values -- I think you're almost there.

Re: Fast Access to TODO States without C-t

[Esben Stien]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Well there's got to be some way to send the escape sequence to the
> running process! Googling indicates it might be C-t t 

You're right;)

C-c C-t t sends C-c C-t to emacs. I can see it says C-c C-t in the
mode-line. 

> does C-c C-t t d work?

Funnily enough, no, it does not work. It just inserts 'd' into the
buffer. 

If I do M-x describe-function, I see: 

org-todo is an interactive compiled Lisp function in `org.el'.

It is bound to C-c C-t, <menu-bar> <Org> <TODO Lists> <TODO/DONE/->,
C-c t.

, so basically, it should have worked.

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
           sip:b0ef@   e     e 
           jid:b0ef@    n     n

Re: Fast Access to TODO States without C-t

[Eric Abrahamsen]

Esben Stien <b0ef@esben-stien.name> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Well there's got to be some way to send the escape sequence to the
>> running process! Googling indicates it might be C-t t 
>
> You're right;)
>
> C-c C-t t sends C-c C-t to emacs. I can see it says C-c C-t in the
> mode-line. 
>
>> does C-c C-t t d work?
>
> Funnily enough, no, it does not work. It just inserts 'd' into the
> buffer. 
>
> If I do M-x describe-function, I see: 
>
> org-todo is an interactive compiled Lisp function in `org.el'.
>
> It is bound to C-c C-t, <menu-bar> <Org> <TODO Lists> <TODO/DONE/->,
> C-c t.
>
> , so basically, it should have worked.

If you don't have org-use-fast-todo-selection set to t, all it's
supposed to do is shift the heading under point to the next defined TODO
keyword. What's your value of that variable? Does it work as expected if
you call M-x org-todo directly? Have you tried with a prefix: C-u C-c
C-t t -- it ought to let you complete on TODO keywords. Something in
there has to work...

Re: Fast Access to TODO States without C-t

[Esben Stien]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> org-use-fast-todo-selection set to t

Hehe, got it, finally. That was the missing ingredient. 

Really great, now I'm speedy gonzales on the TODOs'; thanks;)

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
           sip:b0ef@   e     e 
           jid:b0ef@    n     n

Re: Fast Access to TODO States without C-t

[Oleh]

Hi Esben,

> If I hit 't' over a TODO item, it just changes the state to the next
> state. How can I jump to DONE(d!), f.ex?

There's https://github.com/abo-abo/worf (also in MELPA) - an
alternative to org speed keys.

It's inspired by vi, so your task is handled by "cwd" (change word
DONE).  Other stuff works as well, such as "cw[tnc]" for (change word
[TODO NEXT CANCELLED]).

Similarly:
"cp" is change property,
"dp" is delete property,
"p" is move to property,
"ct" is change tag,
"hjkl" - navigate left/down/up/right
"d2j" - delete two headings down
"d3k" - delete three headings up
"yj" - copy one heading down to kill ring
"3i" - change view to summary level 3.
"wn" - make "jk" move only by NEXT keywords.
"c" - make "hjkl" behave like Meta+arrows
"cf" - make "hjkl" behave like Shift+Meta+arrows
"cs" - make "hjkl" behave line Shift+arrows
"q" - return from the four modes above

Try it out, perhaps you'll like it.

regards,
Oleh

Re: Fast Access to TODO States without C-t

[Bastien]

Oleh <ohwoeowho@gmail.com> writes:

> It's inspired by vi, so your task is handled by "cwd" (change word
> DONE).  Other stuff works as well, such as "cw[tnc]" for (change word
> [TODO NEXT CANCELLED]).
>
> Similarly:
> "cp" is change property,
> "dp" is delete property,
> "p" is move to property,
> "ct" is change tag,
> "hjkl" - navigate left/down/up/right
> "d2j" - delete two headings down
> "d3k" - delete three headings up
> "yj" - copy one heading down to kill ring
> "3i" - change view to summary level 3.
> "wn" - make "jk" move only by NEXT keywords.
> "c" - make "hjkl" behave like Meta+arrows
> "cf" - make "hjkl" behave like Shift+Meta+arrows
> "cs" - make "hjkl" behave line Shift+arrows
> "q" - return from the four modes above

Wow, this is kinda crazy, but good to know people are crazy about Org!

(Many vimers I know use neat tricks to display Org tables in vim
buffers...)

-- 
 Bastien

Re: Fast Access to TODO States without C-t

[Greg Troxel]

[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]


Esben Stien <b0ef@esben-stien.name> writes:

> I'm trying to figure out how to bind fast access to TODO states, without
> using C-t.
>
> The reason is that I have C-t as escape code for my screen session.

This isn't what you asked, but I would suggest changing your escape key
and perhaps using tmux instead of screen.  Surely screen has way to send
the escape key, but you may need to configure it.

I thought for a long time about escape keys.  screen defaults to C-a and
tmux to C-b.  As an emacs user, I use both of those quite a lot.  So I
went through all the rest of the control characters, and found the one
that I have the least use for to be C-j.  And then I set tmux so that
C-j C-j sends a single C-j to the terminal session.  The only time I
need to type this is when searching for strings that contain newlines,
which is a once/day kind of thing for me.

I also switched from screen to tmux, initially for no good reason (the
cool kids were using tmux, and they all said they liked it better), but
I've been using more and more of it and find very little to complain
about.

Here's my .tmux.conf to set the prefix to C-j: 

----------------------------------------
unbind-key C-b
bind-key C-j send-prefix
set-option -g prefix C-j
----------------------------------------


[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]

Re: Fast Access to TODO States without C-t

[Thorsten Jolitz]

Greg Troxel <gdt@ir.bbn.com> writes:

> Esben Stien <b0ef@esben-stien.name> writes:
>
>> I'm trying to figure out how to bind fast access to TODO states, without
>> using C-t.
>>
>> The reason is that I have C-t as escape code for my screen session.
>
> This isn't what you asked, but I would suggest changing your escape key
> and perhaps using tmux instead of screen.  Surely screen has way to send
> the escape key, but you may need to configure it.
>
> I thought for a long time about escape keys.  screen defaults to C-a and
> tmux to C-b.  As an emacs user, I use both of those quite a lot.  So I
> went through all the rest of the control characters, and found the one
> that I have the least use for to be C-j.  

I thought about that too and came up with C-o as tmux prefix key,
probably I actually do use the scratch buffer quite frequently:

,-------------------------------------------------------------------
| C-j runs the command eval-print-last-sexp, which is an interactive
| compiled Lisp function in `lisp-mode.el'.
`-------------------------------------------------------------------

I forgot what was originally bound to C-o, but noticed that other Emacs
users independently chose the same prefix for Tmux, so it must have been
something not used that often.

-- 
cheers,
Thorsten

Re: Fast Access to TODO States without C-t

[Nick Dokos]

Thorsten Jolitz <tjolitz@gmail.com> writes:


> I thought about that too and came up with C-o as tmux prefix key,
> probably I actually do use the scratch buffer quite frequently:
>
> ,-------------------------------------------------------------------
> | C-j runs the command eval-print-last-sexp, which is an interactive
> | compiled Lisp function in `lisp-mode.el'.
> `-------------------------------------------------------------------
>
> I forgot what was originally bound to C-o,

open-line usually.

> but noticed that other Emacs users independently chose the same prefix
> for Tmux, so it must have been something not used that often.