xenia/kakoune
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
ec16969609
kakoune/rc/base/screen.kak

57 lines
1.9 KiB
Plaintext
Raw Normal View History

Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
# http://gnu.org/software/screen/
# ‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾
Do not reparse %sh{...} strings Automatic reparsing of %sh{...}, while convenient in many cases, can be surprising as well, and can lead to security problems: 'echo %sh{ printf "foo\necho bar" }' runs 'echo foo', then 'echo bar'. we make this danger explicit, and we fix the 'nop %sh{...}' pattern. To reparse %sh{...} strings, they can be passed to evaluate-commands, which has been fixed to work in every cases where %sh{...} reparsing was used..
2018-05-06 23:29:52 +02:00
hook -group GNUscreen global KakBegin .* %sh{
[ -z "${STY}" ] && exit
echo "
alias global focus screen-focus
alias global new screen-new-vertical
"
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
}
rc: Clearify the behavior of multiplexers that create new clients Note: `GNU/screen` has a different interpretation of what constitutes a "vertical split", hence the inverted command descriptions, compared to the tmux/iterm etc. Closes #1626
2018-06-30 13:17:46 +02:00
define-command screen-new-vertical -params .. -command-completion -docstring "Split the current pane into two, left and right" %{
Do not reparse %sh{...} strings Automatic reparsing of %sh{...}, while convenient in many cases, can be surprising as well, and can lead to security problems: 'echo %sh{ printf "foo\necho bar" }' runs 'echo foo', then 'echo bar'. we make this danger explicit, and we fix the 'nop %sh{...}' pattern. To reparse %sh{...} strings, they can be passed to evaluate-commands, which has been fixed to work in every cases where %sh{...} reparsing was used..
2018-05-06 23:29:52 +02:00
nop %sh{
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
tty="$(ps -o tty ${kak_client_pid} | tail -n 1)"
* Crude implementation of focus: use the current region to switch to the desired window. - The proper way to do this would be to switch focus to the target client's region but GNU Screen offers no obvious way to do that. - Remove screen region after client is closed. - Assumed: Kak server runs in screen.
2017-11-17 20:40:42 +01:00
screen -X eval \
'split -h' \
'focus down' \
"screen sh -c 'kak -c \"${kak_session}\" -e \"$*\" ;
screen -X remove'" \
< "/dev/$tty"
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
}
}
rc: Clearify the behavior of multiplexers that create new clients Note: `GNU/screen` has a different interpretation of what constitutes a "vertical split", hence the inverted command descriptions, compared to the tmux/iterm etc. Closes #1626
2018-06-30 13:17:46 +02:00
define-command screen-new-horizontal -params .. -command-completion -docstring "Split the current pane into two, top and bottom" %{
Do not reparse %sh{...} strings Automatic reparsing of %sh{...}, while convenient in many cases, can be surprising as well, and can lead to security problems: 'echo %sh{ printf "foo\necho bar" }' runs 'echo foo', then 'echo bar'. we make this danger explicit, and we fix the 'nop %sh{...}' pattern. To reparse %sh{...} strings, they can be passed to evaluate-commands, which has been fixed to work in every cases where %sh{...} reparsing was used..
2018-05-06 23:29:52 +02:00
nop %sh{
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
tty="$(ps -o tty ${kak_client_pid} | tail -n 1)"
* Crude implementation of focus: use the current region to switch to the desired window. - The proper way to do this would be to switch focus to the target client's region but GNU Screen offers no obvious way to do that. - Remove screen region after client is closed. - Assumed: Kak server runs in screen.
2017-11-17 20:40:42 +01:00
screen -X eval \
'split -v' \
'focus right' \
"screen sh -c 'kak -c \"${kak_session}\" -e \"$*\" ;
screen -X remove'" \
< "/dev/$tty"
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
}
}
screen.kak: use `define-command` full name instead of `def` alias
2017-11-15 05:21:42 +01:00
define-command screen-new-window -params .. -command-completion -docstring "Create a new window" %{
Do not reparse %sh{...} strings Automatic reparsing of %sh{...}, while convenient in many cases, can be surprising as well, and can lead to security problems: 'echo %sh{ printf "foo\necho bar" }' runs 'echo foo', then 'echo bar'. we make this danger explicit, and we fix the 'nop %sh{...}' pattern. To reparse %sh{...} strings, they can be passed to evaluate-commands, which has been fixed to work in every cases where %sh{...} reparsing was used..
2018-05-06 23:29:52 +02:00
nop %sh{
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
tty="$(ps -o tty ${kak_client_pid} | tail -n 1)"
screen -X screen kak -c "${kak_session}" -e "$*" < "/dev/$tty"
}
}
screen.kak: use `define-command` full name instead of `def` alias
2017-11-15 05:21:42 +01:00
define-command -docstring %{screen-focus [<client>]: focus the given client
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
If no client is passed then the current one is used} \
-params ..1 -client-completion \
Do not reparse %sh{...} strings Automatic reparsing of %sh{...}, while convenient in many cases, can be surprising as well, and can lead to security problems: 'echo %sh{ printf "foo\necho bar" }' runs 'echo foo', then 'echo bar'. we make this danger explicit, and we fix the 'nop %sh{...}' pattern. To reparse %sh{...} strings, they can be passed to evaluate-commands, which has been fixed to work in every cases where %sh{...} reparsing was used..
2018-05-06 23:29:52 +02:00
screen-focus %{ evaluate-commands %sh{
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
if [ $# -eq 1 ]; then
printf %s\\n "
* Crude implementation of focus: use the current region to switch to the desired window. - The proper way to do this would be to switch focus to the target client's region but GNU Screen offers no obvious way to do that. - Remove screen region after client is closed. - Assumed: Kak server runs in screen.
2017-11-17 20:40:42 +01:00
evaluate-commands -client '$1' focus
"
code review: typos.
2017-11-15 15:42:37 +01:00
elif [ -n "${kak_client_env_STY}" ]; then
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
tty="$(ps -o tty ${kak_client_pid} | tail -n 1)"
* Crude implementation of focus: use the current region to switch to the desired window. - The proper way to do this would be to switch focus to the target client's region but GNU Screen offers no obvious way to do that. - Remove screen region after client is closed. - Assumed: Kak server runs in screen.
2017-11-17 20:40:42 +01:00
screen -X select "${kak_client_env_WINDOW}" < "/dev/$tty"
Integration with GNU screen; based on tmux.kak - Hack: kak sets `/proc/self/fd/0 -> /dev/null`. Get the client process tty because Screen needs to know the controlling terminal. Else Screen will use the last known tty and will open new windows on a different terminal if one is connected.
2017-09-23 16:26:57 +02:00
fi
} }
Reference in New Issue Copy Permalink