Re: cmdEX.exe - augmenting the existing CMD.EXE

From: Stuart Carnie (stuart_carnie_at_hotmail.com)
Date: 08/24/04


Date: Tue, 24 Aug 2004 09:38:44 -0700


"Walter Briscoe" <wbriscoe@ponle.demon.co.uk> wrote in message
news:5q3UpSHg$wKBFwKc@ponle.demon.co.uk...
> In message <cgdpia$bh7@odah37.prod.google.com> of Mon, 23 Aug 2004
> 15:02:50 in microsoft.public.win2000.cmdprompt.admin, Stu Carnie
> <stuart.carnie@gmail.com> writes
> [snip]
>
> >A number of you are aware of the existing shell functions like F7 to
> >bring up the history list, F8 to search the history list and tab-key
> >directory / file completion. This not only works with cmd.exe, but
> >other command line tools like FTP, NETSH and TELNET. In fact any
> >console app that uses the ReadConsole kernel32 API has this
> >functionality.
> I don't think I knew that but use none of them interactively.
>
> [snip]
>
> >I'm curious how many would be interested in such an enhancement. I'm
> >not planning on charging for it, but perhaps 'donation ware'..
> I am sorry to see any reference to money.
I'm sorry you feel that way. I don't expect anything - but if someone feels
they'd like to donate, it would certainly not go unappreciated.

>
> >
> >V1.0 will be a public version, but will not support user enhancements.
> I infer from that that you do not propose to release source code.
> It makes the product much less attractive to some.
>
There is no suggestion I won't release the source code. I simply have a
vision for the product that it will support extensions via 'plugins', and
initially this won't be available in the 1.0 release. I am even considering
sourceforge. I have the infrastructure in place to hook the kernel32
functions, and have basic editing.

> >V2.0 is planned to allow 3rd parties to customize their own shortcuts,
> >allow context sensitive user defined command completion (like zsh),
> >.Net plugins and many others.
> Immediately, I can only think of two applications of such a facility:
> 1) I have some commands which require DOS filenames (c:\foo\bar) and
> some which require UNIX (c:/foo/bar). It would be nice to have something
> which would take either and select the appropriate format.
> 2) ^<newline> handling. e.g. The following does one command but puts two
> entries in the DOSKEY command history:
> C:\) dir ^
> More? /ad
> 3) Make that 3. It would be nice to be able to preload that history. ;)
This will all be available. The history will also be persistent between
commands too, so CMD.EXE, FTP.EXE and TELNET.EXE will each have their own
command histories, just like today, but more powerful.

One of the major intentions is to provide more interactivity via shortcut
keys, just like the many other shells out there.

Enhanced globbing will also be a feature - but sensitive to context.

There is a LOT we can do with this framework to enhance the console
experience.

> --
> Walter Briscoe



Relevant Pages

  • Re: About interactivity.
    ... So I need a very low level of interactivity. ... The pattern most of us at FORTH, Inc. is to keep both SwiftForth or SwiftX *and* our favorite editor open all the time. ... If we're working in SwiftX, we maintain a live cross-target link to the target at all times, so when we type target commands in the command window they're executed on the target. ...
    (comp.lang.forth)
  • RE: Source Server failing to realise its almost worked in VS 2008
    ... the command line/URL is limited. ... I've a custom source indexing process (we use MKS - not ... VS 2008 will download from the ... "Source code cannot be displayed" stop box. ...
    (microsoft.public.vc.debugger)
  • Re: circular dependency - some tools ?
    ... >>functions this circular dependency is. ... > You could look at the source code of depmod to see how depmod is ... I'm using modprobe to load my modules so on the command line ...
    (comp.os.linux.development.system)
  • Re: Compiled with MS FORTRAN 5 my Program executes in colour but not with g95
    ... ANSI.SYS was a TSR that stayed in the background and "trapped" screen writes and looked at what was written to see if it was a command for it to do something. ... COLOR, otoh is a shell command at the user command line so when you write to standard output, it never "sees" the character string and so has no opportunity to do anything. ... source code compiled to a 16 bit executable. ... there isn't ANSI.SYS support for 32-bit, only that for some reason there isn't. ...
    (comp.lang.fortran)
  • Re: How can one distinguish an IDE/ATA(PI) drive from a SCSI drive?
    ... If you dig around in the source code, you'll find that the values are mapped and re-assembled into an OpenVMS device specification deep down at the bottom of the cdrecord.exe source code. ... You can lob SCSI commands at the device and retrieve this data yourself, but OpenVMS doesn't present this data to the user. ... The cdrecord.exe port that the HP folks provided includes mappings for these, and a command procedure wrapper. ...
    (comp.os.vms)