Skip to main content
replaced http://superuser.com/ with https://superuser.com/
Source Link

Recently, I received this answerthis answer and a comment asking me to run a particular command to get the precise Last Modified timestamp of a file:

wmic datafile where name="c:\\foo.txt" get lastmodified

When attempting to run this on the example ("e:\\test1\testIMG.JPG"), I got a message which just said "Node - " followed by the computer name and then "

ERROR:
Description = Invalid query

The solution was to use double-slashes for every slash, not just the one after the drive letter (which is sometimes different). I tried specifying this in an editedit and even explained the change in the edit comment, but that effort was rejected as "This edit does not make the post even a little bit easier to read, easier to find, more accurate or more accessible. Changes are either completely superfluous or actively harm readability."

The edit changed that line from producing an error to producing an answer, which in my opinion makes it more accurate and accessible rather than harming things.

Why do these kinds of things get rejected?

Recently, I received this answer and a comment asking me to run a particular command to get the precise Last Modified timestamp of a file:

wmic datafile where name="c:\\foo.txt" get lastmodified

When attempting to run this on the example ("e:\\test1\testIMG.JPG"), I got a message which just said "Node - " followed by the computer name and then "

ERROR:
Description = Invalid query

The solution was to use double-slashes for every slash, not just the one after the drive letter (which is sometimes different). I tried specifying this in an edit and even explained the change in the edit comment, but that effort was rejected as "This edit does not make the post even a little bit easier to read, easier to find, more accurate or more accessible. Changes are either completely superfluous or actively harm readability."

The edit changed that line from producing an error to producing an answer, which in my opinion makes it more accurate and accessible rather than harming things.

Why do these kinds of things get rejected?

Recently, I received this answer and a comment asking me to run a particular command to get the precise Last Modified timestamp of a file:

wmic datafile where name="c:\\foo.txt" get lastmodified

When attempting to run this on the example ("e:\\test1\testIMG.JPG"), I got a message which just said "Node - " followed by the computer name and then "

ERROR:
Description = Invalid query

The solution was to use double-slashes for every slash, not just the one after the drive letter (which is sometimes different). I tried specifying this in an edit and even explained the change in the edit comment, but that effort was rejected as "This edit does not make the post even a little bit easier to read, easier to find, more accurate or more accessible. Changes are either completely superfluous or actively harm readability."

The edit changed that line from producing an error to producing an answer, which in my opinion makes it more accurate and accessible rather than harming things.

Why do these kinds of things get rejected?

edited tags
Link
Braiam
  • 4.7k
  • 14
  • 18
Tweeted twitter.com/super_user/status/830846596057284609
Changed summary version to match issue focused on in top-voted answer
Source Link
WBT
  • 1.9k
  • 1
  • 11
  • 7

Why was this edit suggestion rejected Should users suggest technical edits?

Recently, I received this answer and a comment asking me to run a particular command to get the precise Last Modified timestamp of a file:

wmic datafile where name="c:\\foo.txt" get lastmodified

When attempting to run this on the example ("e:\\test1\testIMG.JPG"), I got a message which just said "Node - " followed by the computer name and then "

ERROR:
Description = Invalid query

The solution was to use double-slashes for every slash, not just the one after the drive letter (which is sometimes different). I tried specifying this in an edit and even explained the change in the edit comment, but that effort was rejected as "This edit does not make the post even a little bit easier to read, easier to find, more accurate or more accessible. Changes are either completely superfluous or actively harm readability."

The edit changed that line from producing an error to producing an answerThe edit changed that line from producing an error to producing an answer, which IMOin my opinion makes it more accurate and accessible rather than harming things.

Why do these kinds of things get rejected?

Why was this edit suggestion rejected?

Recently, I received this answer and a comment asking me to run a particular command to get the precise Last Modified timestamp of a file:

wmic datafile where name="c:\\foo.txt" get lastmodified

When attempting to run this on the example ("e:\\test1\testIMG.JPG"), I got a message which just said "Node - " followed by the computer name and then "

ERROR:
Description = Invalid query

The solution was to use double-slashes for every slash, not just the one after the drive letter (which is sometimes different). I tried specifying this in an edit and even explained the change in the edit comment, but that effort was rejected as "This edit does not make the post even a little bit easier to read, easier to find, more accurate or more accessible. Changes are either completely superfluous or actively harm readability."

The edit changed that line from producing an error to producing an answer, which IMO makes it more accurate and accessible rather than harming things.

Why do these kinds of things get rejected?

Should users suggest technical edits?

Recently, I received this answer and a comment asking me to run a particular command to get the precise Last Modified timestamp of a file:

wmic datafile where name="c:\\foo.txt" get lastmodified

When attempting to run this on the example ("e:\\test1\testIMG.JPG"), I got a message which just said "Node - " followed by the computer name and then "

ERROR:
Description = Invalid query

The solution was to use double-slashes for every slash, not just the one after the drive letter (which is sometimes different). I tried specifying this in an edit and even explained the change in the edit comment, but that effort was rejected as "This edit does not make the post even a little bit easier to read, easier to find, more accurate or more accessible. Changes are either completely superfluous or actively harm readability."

The edit changed that line from producing an error to producing an answer, which in my opinion makes it more accurate and accessible rather than harming things.

Why do these kinds of things get rejected?

Add ?
Link
WBT
  • 1.9k
  • 1
  • 11
  • 7
Loading
Source Link
WBT
  • 1.9k
  • 1
  • 11
  • 7
Loading