Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14245

Re: history shows edited lines not the lines actually ran

Path csiph.com!goblin3!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From L A Walsh <bash@tlinx.org>
Newsgroups gnu.bash.bug
Subject Re: history shows edited lines not the lines actually ran
Date Sun, 17 Jun 2018 00:18:55 -0700
Lines 29
Approved bug-bash@gnu.org
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>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 7bit
X-Trace usenet.stanford.edu 1529219948 17736 208.118.235.17 (17 Jun 2018 07:19:08 GMT)
X-Complaints-To action@cs.stanford.edu
Cc kermit@new.rednsx.org, bug-bash@gnu.org
To chris <kermit@rednsx.org>
Envelope-to bug-bash@gnu.org
User-Agent Thunderbird
In-Reply-To <alpine.LRH.2.21.1806170036570.424@rednsx.org>
X-detected-operating-system by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] [fuzzy]
X-Received-From 173.164.175.65
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.21
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <http://lists.gnu.org/archive/html/bug-bash/>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref csiph.com gnu.bash.bug:14245

Show key headers only | View raw



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


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