EMACS.NET?

dbox wrote:



I think the curses angle is a red herring.

There are two kinds of emacs users: those who start up emacs in a top-level window and use M-x shell to do shell work, and those who live in tcsh/ksh/bash and crank up emacs -nw to take over their console/terminal window.

I was always in the former camp, and I believe that's the design point for Doug's project.  If you look up and down our hallway, all other remaining emacs users are in that former camp as well.

A more interesting angle is how we'll support console APIs in WPF

DB

Ohh, now your talking.  Have been waiting for this for a couple years.  Welcome Don.

Now let me think, was more of a vi user back in the day, so don't have much emacs history.  But let me think, f# with its "shell" like ability has finally pushed the IDE folks into submission.  Sure PSH should have already done that, but that is ok.  Now VB will probably be easier to shell-ize, but hopefully c# gets some love too.

I have always wanted the IDE "Macro-ized" in a language neutral way.  So I can use PSH or c# macros behind buttons or keys and have a Runspace context to hold objects and Servlets, etc..  A seamless shell/editor in the same window will be cool.

I have to say, as an editor, VS does pretty much what I need to do, so not sure I have much bandwidth or desire to learn a totally new editor these days, but always open to progress.

This would be cool to type someday into the "console":

> $server = new
{  // Volta service
   public string GetName() { return "DB"; }
}

> $server.GetName()
DB
>

// And.

> $sproc = ()=>
{  # Sql lambda run and cached and persisted (optional) at server.
      var q = from emp in $sqldb.Emps
                  where emp.Active == true
      return q.ToList();
}

> $sqldb.AddFunction($sproc, "GetEmps")
> $sqldb.GetEmps() | out-json | out-editor


1) IDE windows that act like PowerGadgets from the shell.
2) Excel and grid Gadgets as output windows (sql results, etc).
3) Easy and simple progress bars for console tasks.
4) Graphical thread and lock monitors driven from the console.
5) Norton commander like UI Forms controls driven by .Net "scripts" as code behind.  New kind of WinForms environment, but for the Console.  Thinking AIX "Admin" app.  But if Console is a WPF canvas, we don't really need blocks anymore? hmm.
6) Could I send my console context to a co-worker?
7) Easy way to share my VS console window (multi-share) or attach to another from the command line.  Console Remote Desktop?  Not sure.
8) Save the console Context between IDE close (or crash...).
9) IDE Console .profile to setup IDE, buttons, and keys from script.