Lars Ingebrigtsen writes: > Mauro Aranda writes: > >> Yes. I think there were two suggestions, which if I'm not mistaken can >> be summarized as: >> - Display newline as \n, tab as \t, etc. >> - Display newline as C-j (or ?\\C-j, or \\C-j, etc), tab as C-i, etc. >> >> To those suggestions, I add one of mine: >> - Display newline as ^J, tab as ^I, etc. >> >> That is what Isearch does, and I think it would not be much of a >> trouble to implement that. Furthermore, we already display other >> non-printable characters like that, so my suggestion would just >> change newline and tab, I think. > > Isearch is a bit special here (being interactive)... > > My guess is that more people understand that \n is newline than people > remember that ^J is newline. (The same goes for \t/^I, but probably to > a lesser degree.) Those are good points. A couple of questions: - Do we change the display for the space character as well? We could display it as ?\s, or leave it as " ", which makes the character widget appear empty, when it's not. - What do we do with the other escape sequences, like ?\r and ?\f? Right now, we display those as ^M and ^L respectively. If we keep this representation, maybe somebody will feel there is some inconsistency, because some characters we display as ^M, while others as \n. Perhaps is not a big deal, though.