![]() Only forward slashes ( /, not backslashes) are used as path separators and octothorpes ( #) or semicolons ( ) are used for comments. The section names are filepath globs (case sensitive), similar to the format accepted by gitignore. File Format DetailsĮditorConfig files use an INI format that is compatible with the format used by Python ConfigParser Library, but are allowed in the section names. (note the trailing dot), which Windows Explorer will automatically rename to. editorconfig file within Windows Explorer, you need to create a file named. Properties from matching EditorConfig sections are applied in the order they were read, so properties in closer files take precedence.įor Windows Users: To create an. editorconfig files will stop if the root filepath is reached or an EditorConfig file with root=true is found.ĮditorConfig files are read top to bottom and the most recent rules found take precedence. editorconfig in the directory of the opened file and in every parent directory. When opening a file, EditorConfig plugins look for a file named. indent_style = space indent_size = 2Ĭheck the Wiki for some real-world examples of projects using EditorConfig files. ![]() end_of_line = lf insert_final_newline = true # Matches multiple files with brace expansion notation Whacky stuff.Root = true # Unix-style newlines with a newline ending every file It’s working again, that’s a relief anyway. ![]() Then installing the Alpha version of the new LiveStyle, both in Chrome and Sublime.įeels like a socket error, and Chrome has been getting pretty hard core about their security and plugins, so without digging deeper, I still don’t know the real cause. I’ve got it working again properly (for now), however it required uninstalling the Chrome extension (from Chrome obviously), and the Sublime package for LiveStyle (from Sublime obviously). Something has broken between the new version of Chrome, the latest version of Sublime Text 3, and the current version of LiveStyle. If it is of any use, once again just on the really big off-chance that another X user runs into the same trouble and stumbles on this post seeking an answer… I do not advise using Brackets for WordPress sites though.įurther to this, I have since discovered that the problem is not quite as simple as a bit of parse error in the CSS. Note that Brackets is a separate thing from Sublime and LiveStyle, they do not work in conjunction with each other (although you could theoretically use them for the same purpose at the same time). It’s possible to do exactly the same thing using a program called Brackets, although this is tied directly into Chrome itself (also requires Node.js), and uses a huge amount of local system memory: If you add to this a Sublime extension called Sublime SFTP, you can also save/sync your custom styles to the server (including dev/staging or production), without even being logged into the WP Admin. When correctly configured, you can edit your CSS in “real time”, so any changes are visible on the page immediately, without saving or refreshing. If there are any advanced users out there who might be interested in these tools, and if the question comes up in the search filters, then this is what I am speaking about:Īlong with a Chrome extension called LiveStyle (it doesn’t work in other browsers except for Safari): ![]() There was one single extra bracket in a media query, which didn’t cause a problem with the display on the front end of the site, but bizarrely it prevented LiveStyle via Sublime from working. So the coincidence in timing to the upgrade was a red herring, it was my own mistake. In the unlikely event someone else stumbles on this post with the same question, the problem was being caused by a single parse error hidden in my 2000 lines of custom CSS, stemming from a small error in the custom SASS file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |