Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #12245
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Fwd: Default time for unmarked history lines |
| Date | 2016-01-18 17:21 -0500 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.2537.1453155718.843.bug-bash@gnu.org> (permalink) |
| References | (1 earlier) <5693BA99.2050509@case.edu> <CAOnWdoivjUdXyytyVXHRwtGEYjLm8kCTkzfEceEpER+E0C4+KA@mail.gmail.com> <56990FB1.4090004@case.edu> <CAOnWdoj8WB+daCACiOpOinRqAsEU5YZOL3UJ3NYFyOoiChdE0g@mail.gmail.com> <CAOnWdoiRg2UbXhG=ud+HKm6V4kaChcWL7xaX8=pBY-StgYM8jg@mail.gmail.com> |
On 1/18/16 11:53 AM, Reuben Thomas wrote: > So, how about instead interpreting a missing/0 date as a NaD (Not A Date), > rather as readline does anyway with time 0, and providing a slightly more > meaningful message than the current "??". Then a) I would be able to remove > all my bogus "1" timestamps, and b) both "0" and missing timestamps would > give the user a clue that data was missing and/or zero? I think that a more meaningful error string would be useful. We'll try reporting on invalid dates if the timestamp string in the history entry is non-empty. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar
Re: Fwd: Default time for unmarked history lines Chet Ramey <chet.ramey@case.edu> - 2016-01-18 17:21 -0500
csiph-web