Causes errors when removing screen-profiles or sharing .screenrc across hosts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
screen (Ubuntu) |
Fix Released
|
High
|
Dustin Kirkland | ||
screen-profiles (Ubuntu) |
Fix Released
|
High
|
Dustin Kirkland |
Bug Description
Binary package hint: screen-profiles
Hi,
I keep my .screenrc in sync between multiple hosts; when I first got screen-profiles automatically via an update, it automatically changed my .screenrc to source .screenrc-profiles; this was transparent on this host, but causes a message on other hosts where screen-profiles wasn't installed.
Secondly, when removing screen-profiles, .screenrc-profiles was left in place as a dangling symlink; so now I get an error when starting screens.
I think screen-profile integration should be reworked. One way could be to extend the screenrc config format to check for a file's existence before source-ing it, or adding some dynamic logic to it. Another way would be to flip the implementation around so that the screen binary (which is a shell script when screen-profile is installed) would default to ~/.screenrc-
I think this should be handled before people start upgrading to jaunty and hence get screen-profiles installed by default.
Bye,
Changed in screen-profiles: | |
milestone: | none → ubuntu-9.04-beta |
Thanks for the bug report, Loic. You raise a couple of important issues.
I would like to patch screen itself to handle missing source'd files more gracefully, perhaps as you say by checking for its existence before sourcing it. I'm going to add a task for 'screen' to this bug for this item.
We could go the other route, with having the /usr/bin/screen shell script call a -c "$HOME/ .screenrc- profiles" , I suppose, but I think that's going to be considerably more difficult from a maintenance perspective.
Either way, I agree, this should be fixed ASAP, well before beta.
:-Dustin