Closed Bug 568371 Opened 15 years ago Closed 15 years ago

Nonexistent commands autocomplete to "undefined"

Categories

(Skywriter Graveyard :: Command Line, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pcwalton, Unassigned)

Details

Attachments

(1 file)

Type a nonexistent command, press tab, and the command line replaces it with "undefined".
It appears tip doesn't have this exact problem anymore. However, autocomplete for nonexistent commands (and for params with no hint, etc...) has the annoying property of clearing the CLI input. I think it should act like bash (and most? other shells) and just leave the current input alone if there is no valid completion. On my local copy of the repo, I just check if CliInputView has something useful in _completion before allowing complete() to change _inputer.value
Pushed as changeset 58738ea3466d, thank you!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: