3 ms·
Sorry - I used '>' first but instinctively changed it to a block since HN didn't actually format it any differently. (And I use a Chrome extension to restyle HN
by EddieRingle 9y ago
Sorry - I used '>' first but instinctively changed it to a block since HN didn't actually format it any differently. (And I use a Chrome extension to restyle HN, so code blocks don't have the issues you described.)
- akvadrako 9y ago> Sorry - I used '>' first but instinctively changed it to a block since HN didn't actually format it any differently. Indeed HN has miserable quoting constructs. I prefer the italics with ">", but dedicated support would be nice.
- Philomath 9y agoWhat Chrome extension do you use?
- gjm11 9y agoI also find quoting on HN annoying when I need to do it. But it occurs to me that this may be (at least in part) a deliberate move to discourage quote-heavy styles of discussion, which are always tempting but would probably not be good for HN. I'm thinking of this sort of thing, as found in the good ol' days on Usenet: > > Sorry - I used '>' first > You should have trusted your first instincts. > > but instinctively changed it to a block > So you tried the right thing and changed it to the wrong thing? What's wrong with you? > > since HN didn't actually format it any differently. > You didn't request any formatting and you're surprised HN didn't give you what you didn't ask for? ... and so on. (For the avoidance of doubt, the snarky tone of the above does not reflect my actual opinions. It's just what tends to happen in the comment-on-fragments kind of interaction, which is one reason why discouraging it here might be wise.)