Skip to main content
13 events
when toggle format what by license comment
Mar 20, 2017 at 10:18 history edited CommunityBot
replaced http://superuser.com/ with https://superuser.com/
Jan 26, 2015 at 9:16 history edited Peter Mortensen CC BY-SA 3.0
Copy edited. Removed meta information. (its = possessive, it's = "it is" or "it has". See for example <http://www.wikihow.com/Use-its-and-it's>.) Used the official names of Stack Overflow - see http://stackoverflow.com/legal/trademark-guidance (the last section).
Jan 14, 2015 at 16:30 comment added Ramhound @MatthijsWessels - I can't use chat feature from my current location. I will get back with you on that.
Jan 14, 2015 at 15:46 comment added Matthijs Wessels Let us continue this discussion in chat.
Jan 14, 2015 at 15:18 comment added Ramhound @MatthijsWessels - Questions that require somebody to state an opinion are bad questions. When the question that you linked to, was asked, somebody would have had to sate an opinion. Even today the question cannot be answered without stating an opinion, although the fact the console host itself is being updated, is an answer to an unasked question ( i.e. can the command prompt support copy and paste functionality ). You wanted the communities opinion on the reason the question you linked to was closed, we have shared that, at least those of us willing to speak up. Which I know regret.
Jan 14, 2015 at 15:11 comment added Matthijs Wessels Well the question could specify the version of Windows its using. About: "We don't know the reason why it wasn't originally implemented.". Who is "we"? And if nobody knows, then that basically means the question remains unanswered, as with any other question on any other site, right? Is a question bad because no-one happens to know the answer? It is not inherent to the type of question or this question specifically that nobody knows.
Jan 14, 2015 at 14:38 comment added Ramhound @MatthijsWessels - As I said. Windows 10 will have new a command prompt. Its possible if the question was worked on, that it could be answered today, but only because those changes are being talked about. As I said its very topic specific, as for the reason, that's the problem with question. We don't know the reason why it wasn't originally implemented. Apparently Powershell and the command shell both use console host which is what actually is being updated.
Jan 14, 2015 at 14:33 comment added Matthijs Wessels Ok, replace PowerShell with Command Prompt everywhere
Jan 14, 2015 at 14:29 comment added Ramhound @MatthijsWessels - Except the question wasn't specifically about PowerShell, while question itself mentions PowerShell, it only is using it as a comparison to the command shell itself.
Jan 14, 2015 at 14:18 comment added Matthijs Wessels But how about that: "the powershell design team is also on the internet; they might have written a blog post somewhere about it or put it somewhere in the specs/RFC doc; and there might be an obvious reason why it's not implemented.". I know that on SO questions have been answered by someone from "the team", so I think it's not completely unlikely to happen here as well.
Jan 14, 2015 at 13:50 comment added Ramhound @MatthijsWessels - Its possible. Still doesn't change the fact any answer wouldn't be based on fact. It entirely depends on the topic. In this case the topic, is asking why a windows feature doesn't support another windows feature ( keyboard shortcut ), we can only speculate. In this case the question your asking about cannot be salvaged.
Jan 14, 2015 at 13:47 comment added Matthijs Wessels So if the question is worded differently, it could be salvaged?
Jan 14, 2015 at 12:29 history answered Ramhound CC BY-SA 3.0