Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#20429 - [bash] Default /etc/bash.bashrc has an overly strict terminal matching

Attached to Project: Arch Linux
Opened by Mantas Mikulėnas (grawity) - Tuesday, 10 August 2010, 13:10 GMT
Last edited by Allan McRae (Allan) - Wednesday, 02 February 2011, 05:27 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Allan McRae (Allan)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

The tests in /etc/bash.bashrc (core/bash/system.bashrc) only match a few most commonly used terminal types.

It's not a problem for me at all, but if we have bash4, why not use its features? (See attachment.)
   system.bashrc-matching.diff (0.5 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Wednesday, 02 February 2011, 05:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  bash-4.1.009-4 in [testing]
Comment by Jeremiah Dow (jeremdow) - Friday, 10 December 2010, 15:49 GMT
Should this be higher priority now? urxvt-unicode package defaults to 256 color now, so $TERM = rxvt-unicode-256color, this must be affecting a lot more users.
Comment by Allan McRae (Allan) - Friday, 10 December 2010, 23:06 GMT
If this gets fixed it will more likely be removing that entire section rather than making it more general.
Comment by Jeremiah Dow (jeremdow) - Friday, 10 December 2010, 23:45 GMT
Fine by me anyway, as long as PROMPT_COMMAND gets set - why did it check the term in the first place?

Loading...