News for hackers. Stuff that matters.
Re:Eshell as a main shell by AnIdiotOnTheNet on Wednesday May 09, 2018 @08:18AM (#17029217)
I was going to be all "yeah, but I don't run a Linux desktop because I'm not a masochist, so my only use for a terminal is over SSH from Windows.", but you actually support win32 so I assume I can use it with SSH from there.

Unfortunately all it does is complain about not having any session types configured, offering precisely no guidance as to what to do about this. The documentation doesn't mention it at all either.

Re:Eshell as a main shell by rauhl on Wednesday May 09, 2018 @10:23AM (#17030044)
> I was going to be all "yeah, but I don't run a Linux desktop because I'm not a masochist, so my only use for a terminal is over SSH from Windows."

I purchased a Windows laptop a couple of years ago as an additional machine (my main platform is Linux), and honestly it’s using Windows which feels masochistic: ads, system prompts which pop up beneath windows[0], ads, the login screen swallowing my first few characters, ads, massive over-use of the trackpad (but this could be my fault, ads, very poor update experience (compared to Debian), ads, sluggishness, IE, Edge, ads, lack of free software and — oh yes, lest I forget — ads. Did I mention that an OS I paid for shows me ads all the time? ’Cause it does.

By comparison, my Debian machines are a joy to use. Every time I have to use my Windows laptop I physically deflate; every time I return to one of my GNU/Linux machines I sit up straight & smile.

0: When I'm using a site which requires a smart card login, Windows pops the smart card certificate & PIN prompt up beneath the current browser window — so it appears that nothing is happening, unless I move the mouse down to the taskbar & hover, revealing the waiting prompt. This is … odd … behaviour.

Re:Eshell as a main shell by AnIdiotOnTheNet on Wednesday May 09, 2018 @10:57AM (#17030305)
Don't get me wrong, Windows has it's issues and lately Microsoft seems to be doing their best to make it worse, but Linux is just completely unsuitable for the ways I use a Desktop OS. And apparently the other 90% of people who also don't use Linux as a Desktop.
Re:Eshell as a main shell by TeMPOraL on Wednesday May 09, 2018 @08:21AM (#17029231)
> I don't run a Linux desktop because I'm not a masochist

Just run Ubuntu, like I do. Almost as easy to maintain as Windows.

Anyway, with Emacs as your OS, whether Linux or Windows is your bootloader is of secondary concern ;).

Re:Eshell as a main shell by p3llin0r3 on Wednesday May 09, 2018 @09:58AM (#17029834)
Agreed. I've run Linux for years with no issues whatsoever.

I feel that people who criticize the platform have yet to try it...

Though to be fair, if your are running Photoshop or final cut Linux is not a great use case

Re:Eshell as a main shell by AnIdiotOnTheNet on Wednesday May 09, 2018 @10:09AM (#17029941)
> I've run Linux for years with no issues whatsoever.

So clearly no one else has issues, right? None of the people complaining about poor power management, insane application deployment model, poor support for high-end GPUs, general fragmentation, poor backwards and forwards compatibility, or any of the other innumerable problems have ever tried a Linux desktop.

This attitude of "it works for me, therefore it is good enough for everybody" is one of the biggest problems I have with Linux. It isn't so much that there are flaws, it's that the community refuses to recognize that there are flaws.

Re:Eshell as a main shell by MightySCollins on Wednesday May 09, 2018 @11:41AM (#17030655)
I think there are many problems running Linux like everything you said and things like HiDPi but I just don't think I could dev on windows.
Re:Eshell as a main shell by AnIdiotOnTheNet on Wednesday May 09, 2018 @01:33PM (#17031839)
That's fair, as long as you aren't an evangelical trying to convert me to the linux desktop I don't have a problem with you using whatever you want.
Re:Eshell as a main shell by AnIdiotOnTheNet on Wednesday May 09, 2018 @09:35AM (#17029647)
> Just run Ubuntu

Doesn't actually solve any of the problems I have with Linux as a Desktop. And if I listed those problems someone would just tell me to use a different distribution, which is itself a problem. Or alternatively try to convince me they aren't actually problems "for most people" as though I should give a damn what is and isn't a problem for someone else.

Re:Eshell as a main shell by sime2009 on Wednesday May 09, 2018 @08:45AM (#17029345)
I have to make a small apology here. Only cygwin is supported on Windows and there was once a useful error message but it died during recent development. This week I've been working on Windows console app support (think: cmd.exe, powershell) and WSL support. Then at the very least you would get a cmd.exe session by default.

For Windows users though, the shell integration stuff is only going to work with WSL and cygwin because anything Windows console based doesn't use or pass VT style escape codes, thus I can't extend the protocol there. This may change in the future as the MS console team is working to add more support for VT and unix style terminals. Making Extraterm into an SSH client itself is also an option for Windows but I've having trouble gauging how important a feature that is and whether it should get some prio.

Re:Eshell as a main shell by AnIdiotOnTheNet on Wednesday May 09, 2018 @09:45AM (#17029725)
That's a shame, but understandable. I think plink does in fact pass raw escape sequences though, so I think that could be wrapped.
Re:Eshell as a main shell by sime2009 on Wednesday May 09, 2018 @10:12AM (#17029961)
The thing is that on Windows it isn't really possible to make a terminal/console app which talks directly to the shell (cmd.exe etc) running in it. What everyone is doing is opening a hidden 'console' component which runs cmd.exe/powershell.exe and then screen-scraping the contents out of it and rendering it elsewhere. Most emulators on Windows which support cmd.exe and friends are using a little bit of software which handles the hidden console, monitors its contents and then outputs a VT style stream of the updates. It is not pretty. MS have been working to improve the situation though: https://github.com/Microsoft/console/issues/57

The bizarre twist to this story is that it is going to be easier to add shell integration features to PowerShell Core running on every platform which ISN'T Windows.

Re:Eshell as a main shell by AnIdiotOnTheNet on Wednesday May 09, 2018 @10:53AM (#17030278)
What you're describing is necessary when going the opposite direction and trying to translate windows console buffers into VT data streams, but that's not really necessary for something like this since the native console interaction isn't used. Just grab plink's stdin and stdout and you'll get precisely what comes through SSH, escape codes and all. Well, almost, I think plink does some EoL conversion.