Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14245
| From | L A Walsh <bash@tlinx.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: history shows edited lines not the lines actually ran |
| Date | 2018-06-17 00:18 -0700 |
| Message-ID | <mailman.2116.1529219947.1292.bug-bash@gnu.org> (permalink) |
| References | <20180616172359.564D074813C6@new.rednsx.org> <5B25DD8B.8090408@tlinx.org> <alpine.LRH.2.21.1806170036570.424@rednsx.org> |
chris wrote:
> On Sat, 16 Jun 2018, L A Walsh wrote:
>
>
>> As for usefulness... haven't you ever had to type in a password on the
>> command line? Or, at least had it be easier to do so, but I really don't
>> like
>> leaving it in a file, so I usually scroll up to the line w/the password and
>> just delete the line. Problem solved.
>>
>
> I use history -d for that sort of thing.
>
---
I'd have to know the offset and the manpage doesn't specify
if the offset is in bytes, lines or time difference. Offset
from what?
Whereas If I've just entered a line w/a PW on it, I'm right
there...just scroll up, and delete it and I know I got the
right line, if you type in an offset, it seems like you might
not really know if you got it or now -- maybe, but the visual
feedback seems more immediate.
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: history shows edited lines not the lines actually ran L A Walsh <bash@tlinx.org> - 2018-06-17 00:18 -0700
csiph-web