Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ctrl-p conflict with detach-keys #28

Open
coryschwartz opened this issue Nov 17, 2022 · 1 comment · May be fixed by docker-library/docs#2231
Open

ctrl-p conflict with detach-keys #28

coryschwartz opened this issue Nov 17, 2022 · 1 comment · May be fixed by docker-library/docs#2231

Comments

@coryschwartz
Copy link

When using irssi in docker using the instructions on dockerhub, ctrl-p does not work correctly.

The instruction on dockerhub suggests we run like this:

$ docker run -it --name my-running-irssi -e TERM -u $(id -u):$(id -g) \
    --log-driver=none \
    -v $HOME/.irssi:/home/user/.irssi:ro \
    -v /etc/localtime:/etc/localtime:ro \
    irssi

However, the hotkey to move to a previous window ctrl-p is buffered by the docker pseudo-terminal, which causes it not to work as expected.

see https://docs.docker.com/engine/reference/commandline/attach/#description which states the that If the container was run with -i and -t, you can detach from a container and leave it running using the CTRL-p CTRL-q key sequence.

I think the instructions on docker-hub should be updated to change the detach-keys to something that doesn't interfere with irssi default bindings, like this:

$ docker run -it -e TERM -u $(id -u):$(id -g) \
    --log-driver=none \
    -v $HOME/.irssi:/home/user/.irssi:rw \
    -v /etc/localtime:/etc/localtime:ro \
    --detach-keys="ctrl-q,ctrl-q" \
    irssi
@coryschwartz coryschwartz linked a pull request Nov 17, 2022 that will close this issue
@hit0wnzzz
Copy link

how could i reattach?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants