Ubuntu
bash package

/etc/skel/.bashrc sets HISTCONTROL twice in succession.

Bug #76807 reported by Constantine Evans
16
Affects Status Importance Assigned to Milestone
bash (Ubuntu)
Triaged
Wishlist
Matthias Klose

Bug Description

Binary package hint: bash

The current .bashrc in feisty has export HISTCONTROL=ignoredups, then has a one line comment, and then has export HISTCONTROL=ignoreboth. This is terribly confusing and unnecessary. The correct way to set this, I believe, would be to just have HISTCONTROL=ignoreboth, which has the effect of combining ignoredups and ignorespace. There is no point in setting one first and then setting ignoreboth.

This was probably caused by bug #66539.

Revision history for this message
Chris Rose (chris-vault5) wrote :

Agreed, its daft setting it one way and then the other.

Changed in bash:
status: Unconfirmed → Confirmed
Chris Rose (chris-vault5)
Changed in bash:
importance: Undecided → Wishlist
Revision history for this message
Dan O'Huiginn (daniel-ohuiginn) wrote :
Changed in bash:
assignee: nobody → daniel-ohuiginn
status: Confirmed → In Progress
Dan O'Huiginn (daniel-ohuiginn)
Changed in bash:
assignee: daniel-ohuiginn → nobody
status: In Progress → Confirmed
Revision history for this message
Stephan Rügamer (sruegamer) wrote :

Attached find a debdiff to fix this bug.

Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

Subscribed ubuntu-main-sponsors

Changed in bash:
status: Confirmed → Triaged
Nicolas Valcarcel (nvalcarcel)
Changed in bash:
assignee: nobody → nxvl
assignee: nxvl → nobody
Matthias Klose (doko)
Changed in bash:
assignee: nobody → doko
status: Triaged → In Progress
Revision history for this message
Matthias Klose (doko) wrote :

the two lines are there by intent to document the two options.

Changed in bash:
status: In Progress → Won't Fix
Revision history for this message
Constantine Evans (cevans) wrote :

I'm afraid I didn't notice this bug closure, and I hope I won't be offending anyone by reopening it. The documentation explanation doesn't make sense to me, because not only is the repetition terribly confusing and unnecessary (having both lines uncommented makes it seem as though they are both doing something, etc), but it also appears that the comments explaining the lines are actually completely wrong. Setting ignoredups *already* ignores same successive entries. Setting ignoreboth adds ignorespace, which causes *lines beginning with spaces* to be ignored. If the intent is documentation, then the implementation is very poor, to the point of being a bug in itself.

Changed in bash:
status: Won't Fix → Confirmed
Revision history for this message
Daniel Hahler (blueyed) wrote :

Setting to Triaged, because it's completely right. See bug 218947, which I'm marking as duplicate.

Changed in bash:
status: Confirmed → Triaged
Revision history for this message
Mika Fischer (zoop) wrote :

Also, there is a typo in the comments: sucessive -> successive, see bug 239948.

Revision history for this message
Lesmana Zimmer (lesmana) wrote :

i see that this bug is fixed but the changelog credits bug #465500

oh well i think it is best to mark this bug as duplicate

Revision history for this message
Lesmana Zimmer (lesmana) wrote :

lol. thanks to bug #78596 i have to reassign dupes by hand. sorry for the bugmail spam this will cause.

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

Other bug subscribers

Remote bug watches

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