Hi @stowball, we are holding back because we think wether to add the whitespace after the colon may be a project or user specific preference. The preferences story is currently being worked on: https://trello.com/c/kqFFDqhR/523-3-infrastructure-for-project-file-scoped-preferences

I’m all for adding preferences to let the user control as much as they want in the app (in fact I’d love it), but with all the developers I’ve worked with, and all the third party code I’ve used (plugins etc), I have never seen anyone who doesn’t use a space after the colon. It seems to be the default in every editor I’ve used also.

Brackets source LESS files even have the space after the colon. So, if Brackets really is built with Brackets, this will save the developers thousands of keystrokes every year :)

My 2 cents

Maybe we could set it to add a space after the colon by default, but this could be changed to "no space after colon" in the preferences ;)

I agree that this is a useful improvement. Trying to get approval from the team.

+1 for what @SAplayer said. I never saw anyone omitting the space after the colon.

There is a thread on brackets-dev on this: https://groups.google.com/forum/?fromgroups#!topic/brackets-dev/oSft7wZGgb0 Planning to go ahead and merge the pull request by end of day today if I don't hear any objections.

Holding back the merge until #6392 is resolved

Tested again, in particular made sure #6392 does not come back. Looking good, merging now.

Here, I found the guilty ones. Just because Dreamweaver uses Brackets I can't upgrade to the new version for about 6 years because now there is always a space after a colon in CSS.
To put a space or not, this should be in the settings.
After all, maybe those who have been writing code for 2-3 years haven't noticed it, but I've been doing it since the first version of DW and all these new things with spaces are very annoying.
Thank you.