exa/xtests/file_names_x

ansi: [[31m\u{1b}[0m[34mblue[31m\u{1b}[0m[0m]  ascii: hello            backspace: [[31m\u{8}[0m]
bell: [[31m\u{7}[0m]                    emoji: [🆒]              escape: [[31m\u{1b}[0m]
form-feed: [[31m\u{c}[0m]               invalid-utf8-1: [<5B>]     invalid-utf8-2: [<5B>(]
invalid-utf8-3: [<5B>(]             invalid-utf8-4: [<5B>(<28>(]  [1;34mlinks[0m
[1;34mnew-line-dir: [[0m[31m\n[1;34m][0m               new-line: [[31m\n[0m]          return: [[31m\r[0m]
tab: [[31m\t[0m]                        utf-8: pâté             vertical-tab: [[31m\u{b}[0m]
-												Only highlight escaped characters in file names

Rather than the *entire* file name.

The current method is extremely inefficient, but having control characters in file names is also extremely uncommon; it’s something that should be fixed, only eventually.

											
										
										
											2017-05-01 14:06:37 +00:00
+								ansi: [[31m\u{1b}[0m[34mblue[31m\u{1b}[0m[0m]  ascii: hello            backspace: [[31m\u{8}[0m]
 								bell: [[31m\u{7}[0m]                    emoji: [🆒]              escape: [[31m\u{1b}[0m]
 								form-feed: [[31m\u{c}[0m]               invalid-utf8-1: [<5B>]     invalid-utf8-2: [<5B>(]
-												Also escape characters in links and headings

Doing this meant that the escaping functionality got used in three places, so it was extracted into a generalised function in its own module.

This is slighly slower for the case where escaped characters are displayed in the same colour as the displayable characters, which happens when listing a directory’s name when recursing. Optimise this, yeah?

											
										
										
											2017-05-01 20:54:53 +00:00
+								invalid-utf8-3: [<5B>(]             invalid-utf8-4: [<5B>(<28>(]  [1;34mlinks[0m
 								[1;34mnew-line-dir: [[0m[31m\n[1;34m][0m               new-line: [[31m\n[0m]          return: [[31m\r[0m]
 								tab: [[31m\t[0m]                        utf-8: pâté             vertical-tab: [[31m\u{b}[0m]