Closed
Bug 300025
Opened 19 years ago
Closed 19 years ago
editline can add non-unique lines to history
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mrbkap, Assigned: mrbkap)
Details
Attachments
(1 file)
1.78 KB,
patch
|
shaver
:
review+
|
Details | Diff | Splinter Review |
I tracked down a newer version of editline than the one we use, and after reading the diffs between the newer version and our version it became apparent that the only real differences were: - mccabe removed the tab-completion stuff. Bringing it back now seems pointless. - a potential crash fix if tgetstr() returned NULL. I'll slip that into this patch for completeness. - by going back in history and typing the last line in history, it is possible to add non-unique entries to the line history back-to-back. The fix is fairly trivial. Unfortunately, there weren't any fixes for the wrapping problem that Brendan and I both see. I may take a crack at that to see if I can dig anything up, later.
Assignee | ||
Comment 1•19 years ago
|
||
Attachment #188608 -
Flags: review?(shaver)
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Comment on attachment 188608 [details] [diff] [review] patch v1 Strictly, you know, this doesn't prevent non-unique lines. Just non-unique _consecutive_ lines. I'll let you off with a warning, though. r=shaver
Attachment #188608 -
Flags: review?(shaver) → review+
Assignee | ||
Comment 3•19 years ago
|
||
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Flags: testcase-
You need to log in
before you can comment on or make changes to this bug.
Description
•