| 2012-01-28 03:27:08 |
Neal McBurnett |
description |
As a fix for bug 776743, the byobu-ctrl-a program was added, and is now run the first time the user types "ctrl-a".
But it seems to be dumb. I had a working byobu/screen configuration (as I have had for many many years) which sets ctrl-j as the screen escape character. I upgraded to oneiric, and ctrl-j was working fine.
But the first time I pressed ctrl-a, and byoby-ctrl-a ran, it still asked me what I wanted to do, as documented in bug 887387. I selected "1" to pick the emacs behavior. It then proceeded to change my escape key to F12, and ctrl-j stopped working.
If byobu-ctrl-a notices that the user has a non-ctrl-a it should do one of these things:
* simply exit without talking to the user at all, realizing that there is no issue, or
* not stomp over an existing configuration by changing it to F12, or
* clarify what it plans to do better and offer another option of "do nothing", perhaps after clarifying the current settings.
For anyone else in this situation, the workaround is to just use the F9 (or other Menu screen command key sequence you've configured, typically visible on the bottom right) and change the "Change escape sequence" setting. |
As a fix for bug 776743, the byobu-ctrl-a program was added, and is now run the first time the user types "ctrl-a".
That is nice for naive users, but the implementation seems to be dumb. I had a working byobu/screen configuration (as I have had for many many years) which sets ctrl-j as the screen escape character. I upgraded to oneiric, and ctrl-j was working fine.
But the first time I pressed ctrl-a, and byoby-ctrl-a ran, it still asked me what I wanted to do, as documented in bug 887387. I selected "1" to pick the emacs behavior. It then proceeded to change my escape key to F12, and ctrl-j stopped working.
If byobu-ctrl-a notices that the user has a non-ctrl-a escape character, it should do one of these things:
* simply exit without talking to the user at all, realizing that there is no issue, or
* not stomp over an existing configuration by changing it to F12, or
* clarify what it plans to do better and offer another option of "do nothing", perhaps after clarifying the current settings.
For anyone else in this situation, the workaround is to just use the F9 (or other Menu screen command key sequence you've configured, typically visible on the bottom right) and change the "Change escape sequence" setting. |
|
