Re: cmdEX.exe - augmenting the existing CMD.EXE
From: Ndi (NoSpam_at_Ndi.ro)
Date: 08/25/04
- Next message: Tom: "Start selections lost"
- Previous message: Doug: "invalid command.com"
- In reply to: Stuart Carnie: "Re: cmdEX.exe - augmenting the existing CMD.EXE"
- Next in thread: Stuart Carnie: "Re: cmdEX.exe - augmenting the existing CMD.EXE"
- Reply: Stuart Carnie: "Re: cmdEX.exe - augmenting the existing CMD.EXE"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Aug 2004 22:04:53 +0300
> I have been reviewing the code, and I expect I'll provide some COM
> interfaces to get to the edit buffer. This will make it easy for code
> written in Delphi, C++ or .Net to interact with the environment.
I hate COM. But then again we all need to face our fears, right? :)
> Now if you type ROUTE on the command line and press TAB, your
plugin
> will cycle through the keywords 'PRINT, DELETE, ADD or CHANGE'. Much more
> intelligent than cycling through the current directories or files. zsh
can
> do this. Now, we stop on CHANGE and press the TAB key again. A standard
> 'list' text dialog pops above or below your command line, and highlights
the
> first IP in the ROUTE table, and as you continue to press the tab, it
> changes the selection. How cool is that?
As cool as implementing a command parameters list for each case. Since
there is no way of getting available commands or parameters, someone needs
to implement completion for each and every extended command.
Also, for those who have many options (like devcon), It's easier to type
than to tab it.
I guess it could help people who issue the same command over and over
again ...
> NET START is another good example - imagine getting a list of the
> services available and selecting the one you wish to start.. Very
> productive..
Someone needs to actually have a NET plugin, or, even worse, a NET START
plugin. But one could do something like implement c:\options.txt as tab
options and then NET start > c:\options. That way TAB would complete started
services.
I currently use an interfaced version (it has this GUI that hogs stdIN,
stdOut and stdErr) but there's this limitation on using -say- Telnet where
you type at certain positions on the screen. Having a GUI means always
making input line-by-line... But certain thigs ar cooler, Ctrl+` popping in
and then out so you'd get
Ctrl+`
ping localhost
Ctrl+`
-- Andrei "Ndi" Dobrin Brainbench MVP www.Brainbench.com
- Next message: Tom: "Start selections lost"
- Previous message: Doug: "invalid command.com"
- In reply to: Stuart Carnie: "Re: cmdEX.exe - augmenting the existing CMD.EXE"
- Next in thread: Stuart Carnie: "Re: cmdEX.exe - augmenting the existing CMD.EXE"
- Reply: Stuart Carnie: "Re: cmdEX.exe - augmenting the existing CMD.EXE"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|