3 ms·
Oh I'll just call Microsoft and ask them to install an indentation guides plug-in to the GitHub merge request diff view, one sec
by mort96 2y ago
Oh I'll just call Microsoft and ask them to install an indentation guides plug-in to the GitHub merge request diff view, one sec
- mixmastamyk 2y ago[flagged]
- mort96 2y agoHow do I enable that feature in the GitHub merge request diff view?
- mixmastamyk 2y agoI just explained why that question is nonsensical. What do you hope to achieve by repeating it?
- mort96 2y agoYou said: > Everything outside of notepad already supports it—that was the point, dumbass. As a response to me pointing out that it's not supported in the GitHub diff view. That response is nonsensical unless you meant to say that it's supported in the GitHub diff view.
- mixmastamyk 2y agoNo one is using block markers or indentation guides in a diff view because that doesn’t make sense. The two+ views would conflict with each other, so vast majority of such tools don’t even try to understand blocks. (difftastic however, on the terminal tries.) If a diff is particularly complex (it shouldn’t but assuming) you’ll need to look at the destination in full and confirm tests etc have passed. Any non-theoretical issues you’d like to discuss?
- mort96 2y agoLet me try again. You said: > Everything outside of notepad already supports it—that was the point, dumbass. As a response to me pointing out that it's not supported in the GitHub diff view. That response is nonsensical unless you meant to say that it's supported in the GitHub diff view
- mixmastamyk 2y agoIt's clear that my original statement referred to editors of source code. You then moved the goal posts to "merge diff" views on a website. Despite that, I explained this didn't make sense, diffs being line-based and not block-based and all that. That's two fundamental problems with your line of argument. This is my last reply.
- mort96 2y agoLet me try again. You said: > Everything outside of notepad already supports it—that was the point, dumbass. As a response to me pointing out that it's not supported in the GitHub diff view. That response is nonsensical unless you meant to say that it's supported in the GitHub diff view
- necovek 2y agoIgnoring the tone of the other poster, the point they are making is that there is no clear value for indentation markers in a (unified) diff view, which is based around lines being removed and added. Similarly, you might not even see braces for the corresponding block, so the braces-vs-spaces is not really a win for "braces". However, I am guessing you are mostly using side-by-side diff view (as opposed to unified diff view), which might have some value to indicate indentation change for a bigger chunk of the code. But again, if you are not seeing where the block starts or ends with braces in the diff block, why is whitespace in any way "worse"?