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!
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!
FS#36664 - [bash] PROMPT_DIRTRIM issue
Attached to Project:
Arch Linux
Opened by Amit Mendapara (cristatus) - Sunday, 25 August 2013, 06:58 GMT
Last edited by Allan McRae (Allan) - Sunday, 25 August 2013, 12:12 GMT
Opened by Amit Mendapara (cristatus) - Sunday, 25 August 2013, 06:58 GMT
Last edited by Allan McRae (Allan) - Sunday, 25 August 2013, 12:12 GMT
|
DetailsDescription:
PROMPT_DIRTRIM variable doesn't work properly. See the bellow to reproduce the same. Tested on Fedora 19 and it works fine, so seems to be some issue with build configuration. Additional info: * bash-4.2.045-4 Steps to reproduce: Here is the output of a bash prompt (no custom .bashrc) <code> $ export PROMPT_DIRTRIM=0 $ export PS1='[\w]\$ ' $ cd /usr/share/man </code> shows <code> [/usr/share/man]$ </code> but with this <code> $ export PROMPT_DIRTRIM=2 $ export PS1='[\w]\$ ' $ cd /usr/share/man </code> shows <code> [.../sare/mman]$ </code> |
This task depends upon
Closed by Allan McRae (Allan)
Sunday, 25 August 2013, 12:12 GMT
Reason for closing: Fixed
Additional comments about closing: bash 4.2.045-5 in [testing]
Sunday, 25 August 2013, 12:12 GMT
Reason for closing: Fixed
Additional comments about closing: bash 4.2.045-5 in [testing]
BAD - glibc-2.18
And I can not replicate in virtualbox so it is probably some asm optimization to s string function... sigh.
https://sourceware.org/git/?p=glibc.git;a=commit;h=2d48b41c