Skip to main content
Super User

Return to Question

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

This question is closed because it's opinion based.

It basically asks why Ctrl + V paste is not implemented in PowerShell.

There's a comment below, "This can't really be answered by anyone except the PowerShell design team."

In my opinion, that doesn't mean a question should be closed.

For one, the PowerShell design team is also on the Internet; two, they might have written a blog post somewhere about it or put it somewhere in the specifications/RFC documentation; and three, there might be an obvious reason why it's not implemented.

I've seen many questions about why certain things are implemented in a certain way with good answers.

Examples:

Even if people add opinionated answers, then the problem are the answers, not the question.

This question is closed because it's opinion based.

It basically asks why Ctrl + V paste is not implemented in PowerShell.

There's a comment below, "This can't really be answered by anyone except the PowerShell design team."

In my opinion, that doesn't mean a question should be closed.

For one, the PowerShell design team is also on the Internet; two, they might have written a blog post somewhere about it or put it somewhere in the specifications/RFC documentation; and three, there might be an obvious reason why it's not implemented.

I've seen many questions about why certain things are implemented in a certain way with good answers.

Examples:

Even if people add opinionated answers, then the problem are the answers, not the question.

This question is closed because it's opinion based.

It basically asks why Ctrl + V paste is not implemented in PowerShell.

There's a comment below, "This can't really be answered by anyone except the PowerShell design team."

In my opinion, that doesn't mean a question should be closed.

For one, the PowerShell design team is also on the Internet; two, they might have written a blog post somewhere about it or put it somewhere in the specifications/RFC documentation; and three, there might be an obvious reason why it's not implemented.

I've seen many questions about why certain things are implemented in a certain way with good answers.

Examples:

Even if people add opinionated answers, then the problem are the answers, not the question.

replaced http://superuser.com/ with https://superuser.com/
Source Link
Community Bot
Community Bot
  • 1

This questionThis question is closed because it's opinion based.

It basically asks why Ctrl + V paste is not implemented in PowerShell.

There's a comment below, "This can't really be answered by anyone except the PowerShell design team."

In my opinion, that doesn't mean a question should be closed.

For one, the PowerShell design team is also on the Internet; two, they might have written a blog post somewhere about it or put it somewhere in the specifications/RFC documentation; and three, there might be an obvious reason why it's not implemented.

I've seen many questions about why certain things are implemented in a certain way with good answers.

Examples:

Even if people add opinionated answers, then the problem are the answers, not the question.

This question is closed because it's opinion based.

It basically asks why Ctrl + V paste is not implemented in PowerShell.

There's a comment below, "This can't really be answered by anyone except the PowerShell design team."

In my opinion, that doesn't mean a question should be closed.

For one, the PowerShell design team is also on the Internet; two, they might have written a blog post somewhere about it or put it somewhere in the specifications/RFC documentation; and three, there might be an obvious reason why it's not implemented.

I've seen many questions about why certain things are implemented in a certain way with good answers.

Examples:

Even if people add opinionated answers, then the problem are the answers, not the question.

This question is closed because it's opinion based.

It basically asks why Ctrl + V paste is not implemented in PowerShell.

There's a comment below, "This can't really be answered by anyone except the PowerShell design team."

In my opinion, that doesn't mean a question should be closed.

For one, the PowerShell design team is also on the Internet; two, they might have written a blog post somewhere about it or put it somewhere in the specifications/RFC documentation; and three, there might be an obvious reason why it's not implemented.

I've seen many questions about why certain things are implemented in a certain way with good answers.

Examples:

Even if people add opinionated answers, then the problem are the answers, not the question.

Good edit before, but not sure why the first link was changed to italics.
Source Link
Matthijs Wessels
Matthijs Wessels
  • 881
  • 4
  • 7

This question is closed because it's opinion based.

It basically asks why Ctrl + V paste is not implemented in PowerShell.

There's a comment below, "This can't really be answered by anyone except the PowerShell design team."

In my opinion, that doesn't mean a question should be closed.

For one, the PowerShell design team is also on the Internet; two, they might have written a blog post somewhere about it or put it somewhere in the specifications/RFC documentation; and three, there might be an obvious reason why it's not implemented.

I've seen many questions about why certain things are implemented in a certain way with good answers.

Examples:

Even if people add opinionated answers, then the problem are the answers, not the question.

This question is closed because it's opinion based.

It basically asks why Ctrl + V paste is not implemented in PowerShell.

There's a comment below, "This can't really be answered by anyone except the PowerShell design team."

In my opinion, that doesn't mean a question should be closed.

For one, the PowerShell design team is also on the Internet; two, they might have written a blog post somewhere about it or put it somewhere in the specifications/RFC documentation; and three, there might be an obvious reason why it's not implemented.

I've seen many questions about why certain things are implemented in a certain way with good answers.

Examples:

Even if people add opinionated answers, then the problem are the answers, not the question.

This question is closed because it's opinion based.

It basically asks why Ctrl + V paste is not implemented in PowerShell.

There's a comment below, "This can't really be answered by anyone except the PowerShell design team."

In my opinion, that doesn't mean a question should be closed.

For one, the PowerShell design team is also on the Internet; two, they might have written a blog post somewhere about it or put it somewhere in the specifications/RFC documentation; and three, there might be an obvious reason why it's not implemented.

I've seen many questions about why certain things are implemented in a certain way with good answers.

Examples:

Even if people add opinionated answers, then the problem are the answers, not the question.

Copy edited. Applied some formatting. (its = possessive, it's = "it is" or "it has". See for example <http://www.wikihow.com/Use-its-and-it's>.)
Source Link
Peter Mortensen
Peter Mortensen
  • 12.3k
  • 16
  • 11
Tweeted twitter.com/#!/super_user/status/555361727471427585
added 41 characters in body
Source Link
Matthijs Wessels
Matthijs Wessels
  • 881
  • 4
  • 7
Source Link
Matthijs Wessels
Matthijs Wessels
  • 881
  • 4
  • 7