Josh links to the VSCMDShell project, which is an effort to provide an addin to Visual Studio to host the command prompt as a tool window. Very useful, plus a trivial WinForms app makes it a replacement to the default cmd.exe as well. I know there are thousands of you with lots of spare time on your hands 🙂 so why not join the GotDotNet workspace and make this a kick-ass component?
Monad should shake things up and prove that the command line interface is as powerful and useful as ever, but one often overlooked element of the command line is the user interface. It goes without saying that what we currently have is pretty crude and outdated. Besides the elimination of the column-centric non-resizable window and the poor selection (and copy & paste) model I’d personally like to see much better use of syntax highlighting, Visual Studio style autocomple, better font selection, splitters, multiple buffers, mouse support, etc. There’s a lot of potential and room for new ideas; if you have any I’ll make sure the Monad team sees your comments. No need to wait for Longhorn either – add them yourself to VSCMDShell!
The tip of the day today is adding extra fonts to use from the command line – stop being limited to “raster fonts” and Lucida Console! The trick is to add string values under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont. Each string value must increment the 0’s, for example:
0 (reg_sz) Lucida Console
00 (reg_sz) Andale Mono
000 (reg_sz) Your Monospaced Font
You get the idea, although not all monospaced fonts work. Yes, as discoverable and usable as the command line itself! 😛