tbabej / vit

Placeholder to demostrate issue porting for VIT.
0 stars 0 forks source link

[VT-67] VITtk; ids mode #67

Closed tbabej closed 6 years ago

tbabej commented 6 years ago

David Patrick on 2011-04-25T02:19:16Z says:

There are as of yet no keybindings for the number keys. Why not use them for input that is assumed to be an ids command? After typing any number, echoing it in the status area, the keyboard focus moves to command composition mode.

243,133-136

and just hit should assume the info command and produce a sequential listing of the info for each task referenced.

keep typing and compose a command exactly as you would at the CLI, and should have exactly the same outcome as the CLI, right?

hit and the keyboard goes back to normal vittk one-key behavior, and you can issue a command for a group

tbabej commented 6 years ago

Migrated metadata:

Created: 2011-04-25T02:19:16Z
Modified: 2014-02-09T02:23:41Z
tbabej commented 6 years ago

steve rader on 2011-04-25T11:53:42Z says:

If there are bindings for numbers, they should behave like they do in Vi: they should execute various existing commands N times.

tbabej commented 6 years ago

David Patrick on 2011-04-25T14:38:41Z says:

steve rader wrote:

If there are bindings for numbers, they should behave like they do in Vi: they should execute various existing commands N times.

While I agree with that from a vim-using, path-of-least-astonishment perspective, but I challenge you to come up with a use-case. Looking at a VITtk screen, which arbitrary command could be executed N times ?

At the same time, what you are perhaps overlooking here, is the opportunity to enter arbitrary commands, with the full power of the CLI string, upon tasks that were visually selected. It's like defending yourself with a sling-shot because you are using the shotgun for a coat-rack.

tbabej commented 6 years ago

steve rader on 2011-04-25T16:14:01Z says:

While I agree with that from a vim-using, path-of-least-astonishment perspective, but I challenge you to come up with a use-case. Staring at a VITtk screen which arbitrary command could be executed N times ?

...wanting scroll to the task five down, instead of doing jjjjj, I would do 5j.

At the same time, what you are perhaps overlooking here, is the opportunity to enter arbitrary commands, with the full power of the CLI string, upon tasks that were visually selected.

I'm not overlooking it--I think it's a VERY rare use case and thus am not motivated to add it.

It's like defending yourself with a sling-shot because you are using the shotgun for a coat-rack.

Good one. But reall VITtk, as stated in the description, is a samurai sword (that is also useful as a coat-rack.)

tbabej commented 6 years ago

David Patrick on 2011-04-25T20:54:24Z says:

steve rader wrote:

I'm not overlooking it--I think it's a VERY rare use case and thus am not motivated to add it.

Nevermind rare, nonexistent is more like it, but if you are suggesting that none of us would appreciate the ability to fire off a full taskwarrior command, while using VITtk, I might contend that it would be well liked and well used.

It's like defending yourself with a sling-shot because you are using the shotgun for a coat-rack.

Good one. But reall VITtk, as stated in the description, is a samurai sword (that is also useful as a coat-rack.)

touche !

tbabej commented 6 years ago

steve rader on 2011-04-26T14:42:03Z says:

would like the ability to fire off a full taskwarrior command, while using VITtk

Well, that's something entirely different and I like it. There's a good chance I'll add ":!some shell command" support (just like Vi/VIM)

tbabej commented 6 years ago

steve rader on 2012-11-24T18:51:58Z says:

VITtk bugs have been deprecated by [[vit|Vit]].

In [[vit|Vit]], the numerical keys will be used to move/scroll to tasks by their ID number.

I will close this request when that functionality is available.

tbabej commented 6 years ago

steve rader on 2012-11-30T17:56:26Z says:

":N" or just "N" (jumps to ":N") can be used to select tasks by ID as of v0.4