You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am aware that usability can become never ending story. Anyway, as I feel the vim-docker-tools is hitting the need of couple of users, here is my humble contribution to that topic:
Consider changing key mapping in status buffer as follows:
# ------------------------------------------------------------------------------
# s: start container
# d=>S: stop container
# r=>R: restart container
# x=>d: delete container
# p=>-: pause container
# u=>-: unpause container
# >=>!: execute command to container
# <=><CR>: show container logs
# a: toggle show all/running containers
# =>r: reload status
# =>q: close status (this window)
# ?: toggle help
# ------------------------------------------------------------------------------
Reasoning:
My proposal is heavily inspired by Fugitive key mapping which is very popular and many users are likely to have these keys already in muscle memory.
start/stop (s/S)
Uppercase often means the opposite, resp. the uppercase is often more difficult to enter so it is used for more dangerous actions.
delete (d)
While x is standard vim "delete", it aims at character level. As one image is represented by a line, d seems more intuitive.
restart image (R)
not using r to reserve r for "refresh status" (for more see later).
R includes stop, so it is consistent with the "shift" being present in "S"top.
pause/unpause (-/-)
This assumes that it is easy to ensure "toggle" behaviour with pause/unpause.
It follows the "add/remove" logic at Fugitve.
The "-" is mnemonic to pause symbol on players and behaves the same style.
Execute command in container (!)
! is common in vim for executing something.
Personally I have difficulties to think, which of > and < are for execution and which for logs. ! is easy to remember.
Show container logs (<CR>)
<CR> is often used to "open the file". Log represents the running image (and has an advantage there is up to one log per image).
Reload status (r)
Following the Fugitive style.
Close status (q)
q makes :DockerToolsClose so simple to call.
The text was updated successfully, but these errors were encountered:
I am aware that usability can become never ending story. Anyway, as I feel the
vim-docker-tools
is hitting the need of couple of users, here is my humble contribution to that topic:Consider changing key mapping in status buffer as follows:
Reasoning:
My proposal is heavily inspired by Fugitive key mapping which is very popular and many users are likely to have these keys already in muscle memory.
start/stop (
s
/S
)Uppercase often means the opposite, resp. the uppercase is often more difficult to enter so it is used for more dangerous actions.
delete (
d
)While
x
is standard vim "delete", it aims at character level. As one image is represented by a line,d
seems more intuitive.restart image (
R
)not using
r
to reserver
for "refresh status" (for more see later).R
includes stop, so it is consistent with the "shift" being present in "S"top.pause/unpause (
-
/-
)This assumes that it is easy to ensure "toggle" behaviour with pause/unpause.
It follows the "add/remove" logic at Fugitve.
The "-" is mnemonic to pause symbol on players and behaves the same style.
Execute command in container (
!
)!
is common in vim for executing something.Personally I have difficulties to think, which of
>
and<
are for execution and which for logs.!
is easy to remember.Show container logs (
<CR>
)<CR>
is often used to "open the file". Log represents the running image (and has an advantage there is up to one log per image).Reload status (
r
)Following the Fugitive style.
Close status (
q
)q
makes:DockerToolsClose
so simple to call.The text was updated successfully, but these errors were encountered: