Dmytro Maluka

> so that I can tell any hidden tabs in space-indented files For that purpose, wouldn't `hltaberrors` be more useful?

To be clear, when I suggested reusing `indentchar`, I thought your intention was to extend the definition of "indentation character" to all blank characters with `X % tabsize == 0`,...

> If we're going to keep adding more of these maybe grouping them together under one setting would be better for discoverability? Similar to what vim does with `listchars`. Good...

> I will need an example in order to implement grouping for the options. Something like `tab=>,space=.,itab=|,ispace=|` ? I'm not sure what would be the name of this generic option...

> since we don't want to do string parsing in every display call Hah, you are sure it would be slower than the settings map lookup? Especially considering _how many_...

`specialchars` maybe?

> _for instance [#431 (comment)](https://github.com/zyedidia/micro/issues/431#issuecomment-382627101) is asking for displaying a hex code, that's not gonna be done in this PR_ Ah, I misread that comment, I thought it was just...

> No, I meant parsing the value of `tab=>,space=.,itab=|,ispace=|` into individual options everytime when we do `displayBuffer()` is inefficient compared to reading a non-grouped settings map Well, it may slower...

> Or maybe `replacechars` (Inspired by `invisiblereplace`) since we are "replacing" the characters that match the condition with the ones we set? That would be a pretty unconventional usage of...

> I think `NewBufferFromFileWithCommand` is a weird API to have That was my first though too, but after a closer look, it looks like quite a sane generalization of `AtLoc`....