Summary: | app-shells/bash - bashrc has bad code setting app-misc/screen title | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Leonid Evdokimov <leon+gentoo> |
Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | trivial | CC: | dschridde+gentoobugs, jer, swegener |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=359389 https://bugs.gentoo.org/show_bug.cgi?id=223641 https://bugs.gentoo.org/show_bug.cgi?id=550104 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | bashrc patch |
Description
Leonid Evdokimov
2008-02-03 06:52:56 UTC
Created attachment 163101 [details, diff]
bashrc patch
Is there anything wrong with this trivial patch?
i dont particularly care ... if the screen maintainer says it's ok, then it may be committed I'm totally against dynamically changing the screen window title. The screen window title is actually a name for a window and not something where auxiliary information can be shown. It reflects how the user names his/her screen windows and it can be used to jump to windows by name. Hence it should be constant and never changed by an application. The hardstatus, which is what we currently set, is the correct way for such information. For xterm we also set the hardstatus and xterm propagates it up as the X window title. I agree, hardstatus may be better place than window name. Maybe, the bug should be resolved as `invalid'. i think that's what Sven was going for :) This should probably be documented, or even configurable via useflag. looks like this was done via bug 359389 http://sources.gentoo.org/app-shells/bash/files/bashrc?r1=1.21&r2=1.22 |