Later this was updated using backspaces and retyping to preserve the “bold” print feature of printing terminals without messing up the display on CRT terminals. In some command line monitors (including Unix, for things like man), “bold” print could be implemented by doing a carriage return without line feed and retyping the characters needing emboldening. More importantly, most non-printing terminals had no way of displaying overlapping characters. Or… can a script be added to git that either fixes, flags or bounces crappy pull requests that include space indented lines?
NOTEPAD++ LINUX FILE FORMAT CODE
Or… if you discover that mixed indentation has been piling up for the last 10 years unnoticed because everyone used the same tab width just run it through a code beautifier. better yet, maybe it brightly flags space characters that occur somewhere within a region of whitespace that is on the begining edge of a line? Then you know when somebody is a jerk right away and can deal with it. How about a text editor plugin that sightly shades tabs? Or. do you enjoy worrying about problems when nobody even notices them? If a tree falls in the woods… or if a problem goes unnoticed is it really even a problem?
if someone else has a different tab width it can be dealt with once they notice it. If your tab character width matches that of the dummy that mixed in spaces then the problem might go unnoticed. Switching away from using tabs does nothing to fix the problem of people not doing what they are supposed to. They either painstakingly fix it all or they deny the pull request with a message to go read the f’n style guide. If it’s an open source project then it depends on how desperate the maintainer is to attract coders. What do you do when your standard is to use 25 spaces per indent (cause that seems to be the direction things are headed) and some dummy submits a million lines of code with only 15? If it’s a workplace the manager reminds them of the company policy and they have to fix it. Honestly it’s just another variation of the same problem! Obviously you do the same thing that you do with code that has the incorrect number of spaces. That is a really common and yet stupid excuse to use spaces instead of tabs. That is a way better solution than trying to figuratively club everyone over the head until they agree to use YOUR favorite number of space characters. WTF?!?! With tabs we can ALL have our way! Just configure your editor to display tabs the way YOU like them and leave ME alone about it. different people see things differently! That’s why we need to use tabs!īut… all the style guides these days push spaces instead of tabs for indents. I know some people have told me that they find my narrower indents harder to see. All that left/right movement makes me tend to lose my place. I find that incredibly distracting when I try to read the code. Kids these days like huge indents with large numbers of spaces. That’s it, no more than 3! I preferred 3 because that is also how far I was taught to indent the beginning of a new paragraph in English class. We didn’t have wide screens for coding, those were for watching movies! In college my Computer Science professors varied, some wanted 2 spaces per indent, some wanted 3. Huge indents meant line wrapping and nobody wanted that. I grew up when monitors and resolution were much smaller.
We can configure that in our editors’ preferences and each see the same source code in the way we want to see it. That’s perfect! How much whitespace I want to see per level of indentation is my business and how much you want to see is yours. Posted in Linux Hacks, News Tagged Notepad++, The Greatest Thing Ever Post navigationĮxactly! Tabs should represent levels of indentation. Rejoice, the greatest problem in technology has now been solved.
NOTEPAD++ LINUX FILE FORMAT WINDOWS
Starting with the current Window 10 Insider build, Notepad now supports Unix line endings, Macintosh line endings, and Windows line endings. Opening a Windows text file in anything else puts little rectangles at the end of each line. Opening a Unix text file in Windows produces a solid block of text without any whitespace. The end result of this toppling of the Tower of Babel for End of Line characters is a horrific mess Windows users can’t read Unix text files in Notepad, and everything is just terrible. Unix text documents use LF for line endings, and Macs use CR for line endings. Previously, Windows Notepad only supported Windows End of Line Characters - a Carriage Return (CR) and Line Feed (LF). Where were you when Kennedy was assassinated? Where were you when Neil Armstrong set foot on the moon? Where were you when Challenger blew up? Where are you now? In what is probably this century’s greatest advancement in technology, Windows Notepad now supports Unix line endings.
0 kommentar(er)
