Setting HISTCONTROL twice in /etc/skel/.bashrc

Bug #465500 reported by Kevin Knerr on 2009-10-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bash (Ubuntu)

Bug Description

Binary package hint: bash

Filing a new bug because the Karmic version no longer serves the purpose of "documenting" an alternative usage.

Although its stated purpose is to avoid clobbering Midnight Commander's setting, the net effect is to set the same option twice, albeit with different semantics. To my mind, this eliminates whatever value may have been previously provided by showing both of the ignoredupes and ignoreboth options.

Since the final effective setting is still "ignoreboth", which seems to be the sanest default setting, I suggest we simply set it once and refer the user to the man page for more details, e.g.

# don't put duplicate lines (or lines starting with space) in the history.
# See bash(1) for more options

ProblemType: Bug
Architecture: amd64
Date: Fri Oct 30 15:18:48 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: bash 4.0-5ubuntu2
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: bash
Uname: Linux 2.6.31-14-generic x86_64

Kevin Knerr (ld-barthel) wrote :
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bash - 4.1-1ubuntu2

bash (4.1-1ubuntu2) lucid; urgency=low

  * Allow special characters in home path in /etc/bash.bashrc
    (LP: #330664)
  * skel.bashrc: Don't set HISTCONTROL twice
    (LP: #465500)
 -- Bryce Harrington <email address hidden> Wed, 10 Feb 2010 23:10:50 -0800

Changed in bash (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers