A small bug with the auto-complete update when you edit a new C++ file (I've checked this only on Mac): When you start writing #in... Sublime will suggest you

A small bug with the auto-complete update when you edit a new C++ file (I've checked this only on Mac): When you start writing #in... Sublime will suggest you #include ... pressing Enter will actually double the pound sign. You end up with something like ##include .... I've noticed the same pattern for int m... the suggested completion was main(). Pressing Enter ends up repeating the return type of the main function, something like: int int main(int argc, char *argv[]) ... Maybe this a Mac only bug or it has something to do with the way the C++ syntax is parsed by the Auto-complete algorithm.