← Back to team overview

desktop-packages team mailing list archive

[Bug 1378151] Re: Commands not saved to .bash_history when a leading space is present


While not that obvious this can be a quite useful feature, for instance if you need to run
$ command --username=myuser --password=mysecretpassword
which you don't want to show up in history.

I've taken the liberty to close this issue. Feel free to report any bugs
you may come across in the future.

** Changed in: gnome-terminal (Ubuntu)
       Status: New => Invalid

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.

  Commands not saved to .bash_history when a leading space is present

Status in gnome-terminal package in Ubuntu:

Bug description:
  If typing a command in gnome-terminal that contains a leading space,
  that command is not in the scroll back history and not saved to
  .bash_history. The command is executed as expected.

  An example as follows
  $ date
  Tue Oct  7 11:09:23 EST 2014

  but no scroll back history exists.
  After closing gnome-terminal and opening again, the command is still not present in .bash_history or the scroll back.

  $ lsb_release -rd
  Description:	Ubuntu 14.04.1 LTS
  Release:	14.04

  $ apt-cache policy gnome-terminal
    Installed: 3.6.2-0ubuntu1
    Candidate: 3.6.2-0ubuntu1
    Version table:
   *** 3.6.2-0ubuntu1 0
          500 http://au.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
          100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct  7 11:04:32 2014
  InstallationDate: Installed on 2014-07-07 (91 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
   PATH=(custom, no user)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to: