Article View: gnu.bash.bug
Article #404History, actually not a bug, but a documentation suggestion
From: Brian Fox
Date: Tue, 01 Aug 1989 14:35
Date: Tue, 01 Aug 1989 14:35
37 lines
1557 bytes
1557 bytes
Date: Tue, 1 Aug 89 08:25:53 EDT
From: bet@orion.mc.duke.edu (Bennett Todd)
X-Zippy: I know th'MAMBO!! I have a TWO-TONE CHEMISTRY SET!!
> even easier is to create a file '~/.bash_history', put the line
>HISTFILE=~/.bash_history in your .bashrc file and then chmod the
>file to 444 (-r--r--r--) and bash won't be able to write to the
>file so your history will not be recorded.
Sure enough, that is importantly simpler. Thanks!
Could some mention of one or another of these hacks be added to the
documentation?
-Bennett
bet@orion.mc.duke.edu
(From the Soon to be Released Major Program "Bash 1.03 - the final frontier")
/* Save the history of executed commands. */
if (interactive)
{
char *hf = get_string_value ("HISTFILE");
if (hf)
write_history (hf);
}
Which just means that saying
unset HISTFILE
in your .bashrc file will prevent the history file from being written.
Patience, good things come to those who wait.
Brian Fox
Technical Details
Message-ID:
<8908011435.AA17080@aurel.caltech.edu>Path:
arc1-ca.pugleaf.net!utzoo!telly!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!AUREL.CALTECH.EDU!bfoxReferences:
<8908011225.AA16291@orion>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!telly!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!AUREL.CALTECH.EDU!bfox From: bfox@AUREL.CALTECH.EDU (Brian Fox) Newsgroups: gnu.bash.bug Subject: History, actually not a bug, but a documentation suggestion Message-ID: <8908011435.AA17080@aurel.caltech.edu> Date: 1 Aug 89 14:35:16 GMT References: <8908011225.AA16291@orion> Sender: daemon@tut.cis.ohio-state.edu Reply-To: bfox@aurel.caltech.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 37