Quantcast
Channel: How to deal with meta-duplicates (disparate problems with the same root cause)? - Meta Stack Overflow
Viewing all articles
Browse latest Browse all 2

How to deal with meta-duplicates (disparate problems with the same root cause)?

$
0
0

By meta-duplicates for the lack of better term I mean seemingly different questions (sometimes from completely different domains) which discuss issues with the same root cause and therefore could be answered with the same canonical answer.

For example I have seen literally hundreds and hundreds of questions seemingly about different issues with different shell commands complaining about wrong parameters (or anything else for that matter) which are actually caused by just improper use of quoting and/or special symbol escaping. One popular use case is a development for Android where one develops on a computer and then deploys the build artifacts to a mobile device for testing. Frequently both deployment and testing require running some Android shell commands.

Usually people are just trying to follow somebody else's instructions and they do not have a deep understanding of what's going on. They just copy-n-paste some command from the guide verbatim but it does not work. Then they come to SE and post another The COMMAND does not work!!! question.

And the actual reason for the failure was that the command was meant to be run in the Android shell directly and the asker was trying to run it from their host PC instead by prepending the command with adb shell. What they failed to realize was that the command was now parsed twice and depending on the host PC OS (and/or version of the shell/command interpreter) some symbols deemed special by the outer (i.e. host computer) shell had been already altered (removed/substituted/etc) before they got to the inner Android shell for processing. A slight variation of that scenario would be the case where the original command was already prepared for shell nesting but it was meant for a different outer shell.

AFAIK the proper canonical answer does not exist for this specific issue. And I might be inclined to write one up. But I get the feeling that closing of questions as duplicates of it would be almost universally rejected by the majority of people who come to SE looking for copy-n-paste recipes for their specific problem and are not particularly interested in finding the root cause and having to do a tiny bit of research of their own in order to apply the generic solution to their specific case. And frequently even close vote reviewers do not bother to understand the common root cause and reject the flag.

So, what should be the proper way of handling such questions?


Viewing all articles
Browse latest Browse all 2

Latest Images

Trending Articles





Latest Images