F5 doesn't work if you choose a different escape sequence

Bug #368937 reported by Marius Gedminas
4
Affects Status Importance Assigned to Milestone
byobu
Fix Released
Wishlist
Unassigned
screen-profiles (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: screen-profiles

I've chosen ctrl-B as my escape sequence in screen-profile's config menu, and now <f5><enter> no longer works.

The tool generated a ~/.screen-profiles/keybindings file with the following content:

  source /usr/share/screen-profiles/keybindings/common
  escape ^Bb
  register n ^b^c^bA

However the common file also has

  register r "^a:source $HOME/.screen-profiles/profile" # | Goes with F5 definition

which now no longer works with ^b as the escape sequence.

Whichever bit of code is clever enough to redefine register n in ~/.screen-profiles/keybindings, should also redefine register r.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: screen-profiles 1.44-0ubuntu1.1
PackageArchitecture: all
ProcEnviron:
 LC_CTYPE=lt_LT.UTF-8
 PATH=(custom, user)
 LANG=lt_LT.UTF-8
 SHELL=/bin/bash
SourcePackage: screen-profiles
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
Marius Gedminas (mgedmin) wrote :
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Right, so that's an unfortunate side effect of monkeying with the escape sequence.

I tried to note in the documentation that non-standard escape sequences will disable some of your keybindings.

I'll mark this Confirmed and Wishlist. I'm not sure this is going to be trivially solvable. I'll take a look at it though.

:-Dustin

Changed in screen-profiles (Ubuntu):
importance: Undecided → Wishlist
status: New → Confirmed
Changed in screen-profiles:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Fix committed, r387. Will be in the 1.52 release.

:-Dustin

Changed in screen-profiles:
status: Confirmed → Fix Committed
Changed in screen-profiles (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package screen-profiles - 1.52-0ubuntu1

---------------
screen-profiles (1.52-0ubuntu1) karmic; urgency=low

  * bin/updates-available: drop leading "Inst" in detailed report
  * bin/logo: add logo for altlinux
  * screen: drop the -t title, causes hangs if user defines shelltitle,
    LP: #368925
  * profiles/profile.skel: swap the position of ip-address and menu
  * screen-profiles.1: document all notifications, LP: #369040
  * profiles/common, screen: create a temp file to use on screen launch,
    consisting of the profile plus the windows, but don't source default
    windows otherwise as this breaks F5-refresh, LP: #368786
  * screen-profiles: ensure that all registered keybindings get updated
    if the user changes their escape sequence, LP: #368937
  * screen-launcher-install, screen-launcher-uninstall: support
    screen-by-default installation for zsh users, LP: #368960

 -- Dustin Kirkland <email address hidden> Wed, 29 Apr 2009 02:28:48 -0500

Changed in screen-profiles (Ubuntu):
status: Fix Committed → Fix Released
Changed in screen-profiles:
status: Fix Committed → Fix Released
Revision history for this message
lebedov (lebedov) wrote :

This still seems to be a problem for certain non-standard escape sequences. Using

escape ``

in my .screenrc file (which sets the escape sequence to the ` key) causes the pressing of the F5 key to result in

$ :source /home/lebedov/.screen-profiles/profile
bash: :source: command not found
$

(I'm using 1.52.)

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

If you're manually setting your escape sequence, then you're responsible for manually fixing your keybindings.

We're doing the best we can automating this, if you use the "supported" mechanism for changing your escape sequence in the screen-profiles configuration menu. See F9->Change Escape Sequence.

:-Dustin

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.