Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Inside the Windows Console

blogs.msdn.microsoft.com

Post reply on HN
Print view View original

211–220 of 259 posts

Re: Inside the Windows Console

#211

Post by GordonS »

ShinTakuya wrote: post #85
GordonS wrote: post #64

Earlier quoted context omitted.

I regularly use both Windows and Linux, and I can't say that I've ever noticed a performance problem?

The terminals you use in Linux must either be painfully slow or you must be very insensitive to latency issues because the latency on Windows console is really high. When I type something I expect it to appear immediately ( A lot of basic commands in general run more slowly on Windows but I don't think that's the terminal's fault so much as it's lack of optimisation on the command itself.

So, I mainly use Cmder on Windows 10 these days (which uses ConEmu under the hood). I just tried typing in Windows cmd, Cmder and WSL, as well as a CentOS terminal. If I really try to notice it, I concede that there is tiny bit of latency in the Windows cmd console.

Maybe it is just me (willing to accept it is!), but I actually have to try to notice any difference, and even then, it's barely noticeable.

Re: Inside the Windows Console

#212

Post by chungy »

jwilk wrote: post #129
chungy wrote: post #35

Technical errors regarding how UTF encodings work: * UTF-8 is at maximum four bytes per codepoint (which aren't characters, since multiple codepoints can make up a single character... see combining diaretics or ZWJ emoji things). "additional 1-4 bytes" should be "additional 1-3 bytes" (Historically, UTF-8 did support 5- and 6-byte sequences, and if you read up on it, the implementation is obvious, but that was before…

> Actually, U+10FFFD is the maximum legal codepoint, the last two codepoints on every plane are reserved and declared as noncharacters. Few parsers are really so strict. This is what Unicode 11.0, §2.4 says: Noncharacter code points are reserved for internal use, such as for sentinel values. They have well-formed representations in Unicode encoding forms and survive conversions between encoding forms. This allows sen…

Hmm, alright. I have seen parsers reject them, presumably from misinterpreting the standard.

Thanks for the correction :)

Re: Inside the Windows Console

#213

Post by pjmlp »

msla wrote: post #210
pjmlp wrote: post #168

Earlier quoted context omitted.

Even when compared against Amiga toolkits and Win16, Xlib with Athena or Motif were anything but pleasant. X Windows is the main reason of "The Year of Desktop Linux" failure. It is quite telling that ChromeOS and Android have ditched it. Also the only UNIX that was actually a pleasure to code for was NeXTSTEP, guess what, it also didn't care for X Windows other than compatibility purposes.

> X Windows ... doesn't exist, of course.

Funny guy, everyone understood that I meant The X Window System™.

Re: Inside the Windows Console

#214

Post by philo23 »

3rdAccount wrote: post #178
philo23 wrote: post #144

Earlier quoted context omitted.

I tend not to use the file menu in Windows Explorer, but yeah it'd be nice if that option swapped it there too. I found out recently you can just type "cmd" in the Explorer address bar and hit enter and it'll open cmd.exe to the current directory, so long as you're not in a special shell folder or an unmapped network share. That's saved me a bunch of time.

I didn't know that. I usually just hit "ctrl + r" and then type in "cmd" and press "enter" and then navigate to the directory I want with "cd". Your pointer will save me time.

I believe it should work with any executable in your PATH but I've never tried it with anything beyond cmd.exe to be honest.

Re: Inside the Windows Console

#215

Post by ocdtrekkie »

blkhawk wrote: post #76
ocdtrekkie wrote: post #15

Earlier quoted context omitted.

Not the parent, but personally, my only real pet peeve with PowerShell as an IT admin is that the right click start menu replaced cmd with PowerShell despite it still being drastically slower to load on many PCs. There's a setting to change it back, but if you are working on other computers all the time, that's not useful at all. This is my main peeve with the Settings panel as well: It's slower to get things done wi…

> Like with 1803 being forced to come up with security questions when creating the local account on a PC you're about to domain join. Security Questions are a really bad anti feature that nonetheless is really persistent. I don't need 5 more random alphanumeric Passwords in case I forget that other random alphanumeric password I can barely remember. In most places online where they are used the rip open huge security…

Yeah, and it was introduced for local accounts in Windows 10 just in the last few months. Beyond the general irritation of it being a poor security system, making me do it for a user account that isn't personal to me is additionally quite silly: I told the installer I was going to domain join the PC.

I end up mashing the keyboard for each one to create hopefully suitably random answers that even I myself don't know. But it's still arguably an additional security hole that I have to simply hope Microsoft hasn't somehow stored in plaintext somewhere.

Re: Inside the Windows Console

#216

Post by zaat »

I'm late to the party, but maybe the console guys are still lurking. If so, than first and foremost I wanted to thank you for the amazing walk you guys took the console so far.

That said, as someone who uses your product for hours on daily basis, I have two pain points that I would love to have fixed, if that possible at all:

1. selection of text and deletion - works in PowerShell, doesn't work in cmd. Is this curable?

2. Customizing the console is pain. I don't mind doing it once but it is impossible to save theme and copy it between computers. It is also impossible to export registry keys - not only do they differ for various consoles, the color settings are not saved there. The only way I found so far for achieving this is copying the shortcut for the specific console - the colors are saved to the .lnk file in binary form. Seriously, can we have at least color exportable themes in a format that can be edited with a text editor?

Re: Inside the Windows Console

#217

Post by bitcrazed »

zaat wrote: post #216

I'm late to the party, but maybe the console guys are still lurking. If so, than first and foremost I wanted to thank you for the amazing walk you guys took the console so far. That said, as someone who uses your product for hours on daily basis, I have two pain points that I would love to have fixed, if that possible at all: 1. selection of text and deletion - works in PowerShell, doesn't work in cmd. Is this curabl…

Hey @zaat. Thanks for your kind words :D

Alas, deleting text is an operation controlled via the shell. PowerShell's (awesome) PSReadLine does it for PowerShell, but introducing that kind of behavioral change is unlikely to be possible in Cmd because, as pointed out in the posts, Cmd is in maintenance mode, is extremely fragile, and it's key MO is backward compat, which includes behaviors because many tools, and scripts depend on behaviors (even broken ones) as "Features" ;)

Re: Inside the Windows Console

#218

Post by msla »

pjmlp wrote: post #213
msla wrote: post #210

Earlier quoted context omitted.

> X Windows ... doesn't exist, of course.

Funny guy, everyone understood that I meant The X Window System™ .

Well, it goes to demonstrating expertise, doesn't it?

Hard to know something if you don't know what it's called, innit?

Re: Inside the Windows Console

#219

Post by zaat »

bitcrazed wrote: post #217
zaat wrote: post #216

I'm late to the party, but maybe the console guys are still lurking. If so, than first and foremost I wanted to thank you for the amazing walk you guys took the console so far. That said, as someone who uses your product for hours on daily basis, I have two pain points that I would love to have fixed, if that possible at all: 1. selection of text and deletion - works in PowerShell, doesn't work in cmd. Is this curabl…

Hey @zaat. Thanks for your kind words :D Alas, deleting text is an operation controlled via the shell. PowerShell's (awesome) PSReadLine does it for PowerShell, but introducing that kind of behavioral change is unlikely to be possible in Cmd because, as pointed out in the posts, Cmd is in maintenance mode, is extremely fragile, and it's key MO is backward compat, which includes behaviors because many tools, and scrip…

Thank you for answering. Any chances on number 2, especially color themes?

Re: Inside the Windows Console

#220

Post by pjmlp »

msla wrote: post #218
pjmlp wrote: post #213

Earlier quoted context omitted.

Funny guy, everyone understood that I meant The X Window System™ .

Well, it goes to demonstrating expertise, doesn't it? Hard to know something if you don't know what it's called, innit?

If it makes you feel better, by all means.
Post reply on HN