Vim 7.3.1000
ftp.vim.org
Vim 7.3.1000
1–10 of 53 posts
Re: Vim 7.3.1000
#2Here's to another 1000 commits for the world's best text editor. Cheers!
Re: Vim 7.3.1000
#3[deleted]
Re: Vim 7.3.1000
#4NOTE: If you experience troubles with more complicated regular expressions in the next time, it might be because of the new engine.
:h two-engines
:h 're'
Re: Vim 7.3.1000
#5Pretty ugly bug. Where did it happen? Anyway, congrats & long life!
Re: Vim 7.3.1000
#6Best editor
Re: Vim 7.3.1000
#7I guess I should be thankful 98% of my programming life is in higher-level languages than C, but...am I the only one whose terrified of the magic numbers? In hex? Can anyone provide context about what's so special about 0xfb20 and 0xfb4f?
Re: Vim 7.3.1000
#8I guess I should be thankful 98% of my programming life is in higher-level languages than C, but...am I the only one whose terrified of the magic numbers? In hex ? Can anyone provide context about what's so special about 0xfb20 and 0xfb4f?
Given that it's in a regex source file, and the variable is named c, they're probably character codes for Unicode ranges.
Re: Vim 7.3.1000
#9I guess I should be thankful 98% of my programming life is in higher-level languages than C, but...am I the only one whose terrified of the magic numbers? In hex ? Can anyone provide context about what's so special about 0xfb20 and 0xfb4f?
Given that it's in a regex source file, and the variable is named c, they're probably character codes for Unicode ranges.
This might be a good case for unicode character literals. Code dealing with unicode can be a nightmare to work with, even if you already know what those numbers are (arguably as this bug demonstrates).
Re: Vim 7.3.1000
#10I guess I should be thankful 98% of my programming life is in higher-level languages than C, but...am I the only one whose terrified of the magic numbers? In hex ? Can anyone provide context about what's so special about 0xfb20 and 0xfb4f?
All my programming life has been in higher-level languages, yet with Rust I'm being inexplicably drawn to down and dirty systems programming. It's cool to finally be able to use :make and all the C-oriented things like [i and ]i, ctags and the like. It's interesting seeing how much 'dogfooding' vim has in that tons of stuff are undoubtedly geared towards his own needs developing vim (and C applications in general.) Pretty much how I work with coding products, I work my best when I'm the use case, and great open source products like vi/vim and emacs excel in that legions of people share the creator's use case (and well, configurability right down to the bone.) I've found that a non-trivial amount of people do share the use case for the first project I've launched[1], I only hope for it to hold true for my most ambitious ones in the working.
I don't know Bram, but I can't help but wonder why such a distinguished open source figure has ultimately ended up working for Google. Maybe he enjoys the access to resources. I wish donations could still support him directly rather than his idea of aid (well it does seem to have a bend towards education at least). I wish he wouldn't need a day job and could yet breed other new and great contributions to the world. I don't feel particularly endeared towards Google, despite all the collateral good it has done while doing a lot of evil (i.e. something to do with the looming ad empire strengthening big corporations.)