Live data from Hacker News

Search: .lenght - Github

github.com

91–100 of 106 posts

Re: Search: .lenght - Github

#91
post #81

For the record, Github's search index is wayyy out of date sometimes. The second user here is me and I deleted that user like two years ago: http://cl.ly/0y271f0T3G0X2J1L022E

Same here, I contacted support two times in two years and they said "we're working on it". Obviously, that isn't true and they just don't care about the outdated search index.

Your latter statement is unequivocally false, for what it's worth. On both counts.

Re: Search: .lenght - Github

#92
post #64
post #62

Earlier quoted context omitted.

Uhm. Why is this annoying, other than the fact that it shows up in your git commits?

If you use Vim from the terminal to edit text (which I do), trailing whitespace shows up as big white blocks. It's slightly visually distracting, but it's really just an OCD thing.

No.

Absence or presence of trailing whitespaces is sometime significant, such as in big ereg in re.VERBOSE mode in Python.

Therefore, it must be visible, and if it is visible it must be removed when it has no use.

Re: Search: .lenght - Github

#93
post #31

I thought this is actually interesting but I would like to know if >4k misspellings is a lot or not. Here is one way to do it: LANGUAGE #LENGHT #LENGTH = #LENGHT/#LENGTH JavaScript 4252 2907459 = 0.0015 C 18981 2902857 = 0.0065 Java 7706 2348900 = 0.0033 Ruby 10789 1690604 = 0.0064 C++ 9458 1315552 = 0.0072 PHP 3116 1167924 = 0.0027 C# 1352 937647 = 0.0014 Python 3662 737292 = 0.0050 Ruby 1232 380484 = 0.0032 Perl 12…

    LANGUAGE   #LENGHT    #LENGTH    = #LENGHT/#LENGTH  
    C#            1352     937647    = 0.0014   

Re: Search: .lenght - Github

#95

Earlier quoted context omitted.

I prefer using the vim-trailing-whitespace plugin and fixing it manually: https://github.com/bronson/vim-trailing-whitespace

Or you can use my competing plugin: https://github.com/bitc/vim-bad-whitespace which has some advantages (described in the README)

One advantage taken from the readme:

  This plugin is better than using the builtin vim 'list' command because it
  doesn't show an annoying highlight while you are typing in insert mode at the
  end of a line.

Re: Search: .lenght - Github

#96
post #26

Earlier quoted context omitted.

I wrote that bot! https://github.com/Miserlou/WhitespaceBot Feel free to fork it to do whatever you want, that's why I made it.

Hey, some of us actually use trailing whitespace! :-) I use it to create useful indentation guides in Komodo. If the whitespace is stripped away, the indentation guides have gaps where there's a blank line in an indented block. Maybe Komodo could use a different method to decide where to draw the lines that didn't depend on trailing whitespace. It looks like Sublime Text 2 has a different approach for its indentation…

From a quick look at the source, WhitespaceBot already excludes Markdown files:

    banned = ['.git', '.py', '.yaml', '.patch', '.hs', '.occ', '.md', '.markdown', '.mdown']

Re: Search: .lenght - Github

#98
post #75
post #26

Earlier quoted context omitted.

I wrote that bot! https://github.com/Miserlou/WhitespaceBot Feel free to fork it to do whatever you want, that's why I made it.

Is there any equivalent of the robots.txt standard for public code repositories? Being able to opt-in to certain bots might be helpful (opt-out being the default, of course).

That's a really cool suggestion and I would love to see some sudo-standard on this.

Re: Search: .lenght - Github

#99
post #91
post #81

Earlier quoted context omitted.

Same here, I contacted support two times in two years and they said "we're working on it". Obviously, that isn't true and they just don't care about the outdated search index.

Your latter statement is unequivocally false, for what it's worth. On both counts.

Perhaps some info about the progress being made would be more helpful as elk3 has mentioned contacting support over the past 2 years.

Re: Search: .lenght - Github

#100
In the LaTex editor that I'm using (WinEdt), I have a custom color highlighting that marks \rigth and \heigth in red+bold+strikeout, so I don't have to wait to compile and see a strange error to spot the mistake.
Post reply on HN