Re: Don't suggest completion functions when 'correcting' on non-existant commands

[Bart Schaefer <schaefer@brasslantern.com>]

On Jan 2, 11:54pm, Frank Terbeck wrote:
}
} > On Dec 31,  7:12pm, Frank Terbeck wrote:
} > } 
} > } <http://bewatermyfriend.org/posts/2007/12-26.11-50-38-tooltime.html>
} > 
} > That's not really a solution; it just replaces the correction prompt
} > with a different prompt.
} 
} Well, to me it's not really another prompt, because you're not
} actually prompted for anything.

It nevertheless stops whatever is going on and makes you hit enter, which
is not that much better than answering "N" to a request to correct the
command name.

} E.g.: If it's due to a not-yet-installed piece of software you can
} push-input the current cmdline, aptitude-install (or whatever way your
} OS does it) and then just hit enter to have the pushed command
} executed - with the missing program installed.
} 
} > It might be interesting for other reasons.
} 
} What would those reasons be? ...maybe you see use-cases I didn't see,
} yet. :-)

Well, on Ubuntu under bash when a command is not found you get told what
to do to install it (e.g. what package to apt-get install).  This could
be the basis for something like that for zsh.