Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14245 > unrolled thread
| Started by | L A Walsh <bash@tlinx.org> |
|---|---|
| First post | 2018-06-17 00:18 -0700 |
| Last post | 2018-06-17 00:18 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: history shows edited lines not the lines actually ran L A Walsh <bash@tlinx.org> - 2018-06-17 00:18 -0700
| From | L A Walsh <bash@tlinx.org> |
|---|---|
| Date | 2018-06-17 00:18 -0700 |
| Subject | Re: history shows edited lines not the lines actually ran |
| Message-ID | <mailman.2116.1529219947.1292.bug-bash@gnu.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 top | Article view | gnu.bash.bug
csiph-web