Sometimes the code review post will ask why something doesn't work but often it will be that they implemented something in a way where the design could be improved. There's a lack of abstractions. Or they aren't familiar with certain language features. There's a lot of overlap with aspects of writing skills.
@Cerberus I'm not a skilled enough writer for my opinion to be worth much, but I'd guess that it could work effectively for a certain scope. Reviewing beginner to intermediate writing (thinking of ESL folks) of limited length probably involves fairly common objective errors.
@Cerberus Thanks–it didn't seem like such a thing existed but I figured I'd check. It's interesting if people are willing to review code for free but not English writing.
@Heslacher I feel like a downvote is a bit harsh since overall the response is good. Posting a comment seems like it could be easily missed by other readers. I think it'd be best if the reviewer edited their post to fix it. Maybe this is impractical though
To clarify: say the answer addresses different points with numbers (1.. 2... 3..) and point 1 & 2 are high quality but 3 is factually incorrect. Should 3 be edited?
What's the appropriate way to respond to errors in portions of a reviewers answer? Comments? If the answer is factually incorrect, should the answer itself be edited?
@Mat'sMug why not improve it if there are reasonable ways to improve it though? i don't think it's popular enough to warrant a new post. i see SE codereview as something to potentially show to future employers so that's why I'd like to document improvements
I want to add a new improvement after accepting my own answer. Would it be better to submit as a new answer or edit my existing answer? I'd imagine add new answer since the new answer is unrelated and it seems like it might be wrong to edit an already accepted answer. codereview.stackexchange.com/questions/145168/…
i just mean, it seems like it'd be a useful feature. i'm surprised it doesn't exist, so i could imagine maybe the philosophy is that they prefer not to have to pull reviews into an editor. maybe i'm wrong and the it just doesn't have enough demand to be a feature
"That, more than anything else, is why I deleted it. I would have edited it with some more information on how to use the plugin if it was a solution to the answer."
So it seems reasonable that someone else might come to the same conclusion and find it useful. Maybe not. But it seems a bit overboard to delete it. Why not let voting decide if it's useful?
@Carpetsmoker I arrived at the thread via google with the same problem as OP and my solution was that I found an alternative plugin that solved that problem. I decided that I would rather use a plugin that offers that functionality than maintain a fork or add random hacks to my vimrc. The accepted answer literally says
>It seems to work but I don't know how reliable it is.
oops, futility=utility above. either way, i'm not angry, just looking for clarification and how to better contribute in the future. i appreciate the work you guys do moderating
tldr; OP wants to open netrw with ranger, he found a plugin is missing that functionality in a certain situation and the rest of the discussion is focused on sort of work-around hacks to make that happen
either way, i came to the posting wanting the same thing and found a plugin that solved my problem (and what it seems the OP is trying to do). i don't really understanding the futility in deleting the post
in my view, my response directly responded to what the OP was looking for. his title doesn't quite match what he actually wants to do. he basically wants to replace netrw with ranger, but the plugin he's using doesn't offer that, so he's resorting to a workaround