Closed
Bug 642239
Opened 14 years ago
Closed 13 years ago
GCLI should have history retention
Categories
(DevTools :: General, defect)
DevTools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jwalker, Assigned: fitzgen)
References
Details
(Whiteboard: [estimate:best=2d,likely=3d,worst=8d])
GCLI should retain a history of commands executed, and the values that they returned, for use in other commands.
|
Reporter | |
Updated•14 years ago
|
Blocks: GCLI-EXPERIMENT
Whiteboard: [estimate:best=2d,likely=3d,worst=8d]
|
|
Reporter | |
Updated•14 years ago
|
No longer blocks: GCLI-EXPERIMENT
|
|
Reporter | |
Updated•14 years ago
|
Blocks: GCLI-FUTURE
|
|
Reporter | |
Updated•13 years ago
|
|
Assignee | |
Updated•13 years ago
|
Assignee: nobody → nfitzgerald
|
|
Assignee | |
Comment 1•13 years ago
|
||
Things to consider:
Should we handle history on a per command basis? For example, in the following, we cycle backwards through echo's particular history:
> echo "hi"
> eval 1 + 1
> echo <up>
> echo "hi"
We could also possibly take advantage of type information. The ast will have the types. This seems like it would be useful if we had specific types (such as git repositories), but problematic with generic types (such as strings).
|
|
Assignee | |
Comment 2•13 years ago
|
||
Basic implementation at https://github.com/fitzgen/gcli/tree/642239-history
|
|
Assignee | |
Comment 3•13 years ago
|
||
Joe,
Can we close this issue, now that my implementation has been merged in to master?
|
|
Reporter | |
Comment 4•13 years ago
|
||
Yes - go ahead
|
|
Assignee | |
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
||
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•