Using ├, ─, │, └ characters to describe the tree structure of a pip installable python module. It looks a bit better at http://stackoverflow.com/questions/8247605/configuring-so-that-pip-install-can-work-from-github
Here is how this post looks with GFM
foo
├── foo
│ ├── __init__.py
│ └── bar.py
└── setup.py
And here how it would have looked with normal +, -, |
foo
+-- foo
| +-- __init__.py
| +-- bar.py
+---setup.py
I remember when I started programming, borland, pascal, dos. 1983 or so, the borland editor had a mode that allowed me, to use the arrows and "draw" any path I wanted using block characters.
Think F1 means single line block character mode, F2 means double line block character mode, and as soon as you enter the mode the editor would see the neighboring chars and would use the appropriate chartacter to make the whole thing look nice. The fonts for the single line were the 4 corners, 2 straits, 4 T and 1 cross. 11 all and all. + 11 for the double line, plus a higher number to deal with single-double line joints. The funny thing is that I remember more time playing with it than using it. It was very cool.
(Note to self - is there a sublime plugin that does sth similar? is there a font set wit similar characters? or the need for these chars disappeared with the influx CGA-> VGA and graphical (as opposed to text+block chars-based) windows...
wikipedia
DOS
In all MS-DOS code pages, box drawing characters are present, but their number is limited to 40 (for example in code page 437):
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | C | D | E | F | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
B | │ | ┤ | ╡ | ╢ | ╖ | ╕ | ╣ | ║ | ╗ | ╝ | ╜ | ╛ | ┐ | |||
C | └ | ┴ | ┬ | ├ | ─ | ┼ | ╞ | ╟ | ╚ | ╔ | ╩ | ╦ | ╠ | ═ | ╬ | ╧ |
D | ╨ | ╤ | ╥ | ╙ | ╘ | ╒ | ╓ | ╫ | ╪ | ┘ | ┌ |
No comments:
Post a Comment