Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ryan Boehning
    @y0ssar1an
    Mic check 1-2 1-2
    Matijs Brinkhuis
    @matijs
    Is this thing on?
    Ryan Boehning
    @y0ssar1an
    Loud and clear :)
    Matijs Brinkhuis
    @matijs
    Cool :) First off wanted to thank you for making the CSS3 syntax highlighter. That said. Have you ever considered porting it to be a SCSS syntax highlighter?
    The ones that are out there are outdated and frankly quite horrible.
    Ryan Boehning
    @y0ssar1an
    Yeah, I've thought about it. It could be done, but it would take some effort. The hardest part would be nested selectors. Selectors were tricky to get right in CSS3.
    It's just a question of time. CSS3 2.0 was mostly done over a two week summer vacation. Maybe I could try to tackle SCSS3 over Christmas break.
    Full time jobs, amirite?
    Ryan Boehning
    @y0ssar1an
    I'm not a front-end guy. Are most FE devs using things like SASS and SCSS instead of vanilla CSS?
    Matijs Brinkhuis
    @matijs
    I used to prefer CSS and not really see the benefit of SCSS. Mostly because it's so easy to write nested SCSS that would result in the most horrible CSS imaginable :smile:
    However. When used correctly, the benefits of especially variables as well as nesting no deeper than one level ( pseudo-elements or pseudo-classes) are worth it.
    But to get back to your question. I do think most projects these days have tool chains involving Sass or Less with Sass (SCSS) being the most popular one. It's only anecdotal evidence of course but I have yet to see my first Less project :)
    Ryan Boehning
    @y0ssar1an
    Ok, thanks. That's the feedback I've been getting from the FE people I know.
    Matijs Brinkhuis
    @matijs
    Cool
    Ryan Boehning
    @y0ssar1an
    I'll definitely consider it. I just need time to work on it. If I decide to do it, it will probably be over Xmas break.
    It would be cool to work full time on improving language support in Sublime. There are a lot of languages with mediocre language definitions. Will Bond has done a lot to improve the default language definitions, but he can't do it all.
    Matijs Brinkhuis
    @matijs
    True. And using TextMate syntax definition seems like a bit of a cop out.
    I've started looking at writing a a syntax file for SCSS myself based on your work but it is quite daunting.
    Ryan Boehning
    @y0ssar1an
    Yeah, it's a big ball of wax. If I'd known how much work it was gonna take to make CSS3, I probably wouldn't have started.
    The sublime-syntax system is much better, but it's still not easy.
    Jason Murray
    @Jason-Murray
    hello, I've started using the CSS3 package but I'm not sure it's working right. Will it narrow the values based on the property? As for me it appears to be suggesting any value for any property.
    Sorry if this is not the right place for this.
    In fact I'm pretty sure it's not working, based on this.
    Jason Murray
    @Jason-Murray
    Jan-28-2017 20-44-11.gif
    Jason Murray
    @Jason-Murray
    I have it working now, it was incompatibility with 'All Automplete' - sorry I should've tested that sooner.
    Thanks for the plugin.
    Ryan Boehning
    @y0ssar1an
    Hey, sorry I missed your message, but I'm glad you figured it out. Sublime Text pools together completions from multiple packages. The CSS3 completions are comprehensive. Anything added by another package will either be a duplicate or be incorrect. I wish there were a way I could disable completions from outside packages to prevent bugs like these. Thanks for making me aware about the incompatibility with All Autocomplete.
    Arsène L.
    @SevDevv
    Hello, I've noticed that all of the grid properties aren't supported by the CSS3 Package, e.g. there have "grid-gap" that gets highlighted in red, ... If this isn't where I should report this, may I have a link to report it somewhere else ? Thank you and good day!
    Ryan Boehning
    @y0ssar1an
    This is due to a recent change to the Grid spec.
    grid-gap        -> gap
    grid-column-gap -> column-gap
    grid-row-gap    -> row-gap
    johndennismaher
    @johndennismaher
    Worked with Sublime Text 5 years ago. Forgotten most of it. Now have ST3. For now, I'm trying to add some of the top rated Packages related to HTML and CSS3. Need some basic help, please. I disabled CSS, then installed CSS3. These further instructions on the CSS3 Install page state: "I also strongly recommend adding these two settings to your User Settings (the general settings, not the package settings). By default, Sublime will not offer completions inside other completions. In other words, the completions menu is suppressed when you're tabbing through a snippet. This blocks most of the CSS3 completions from appearing. To fix this, set these keys to true:
      "auto_complete_commit_on_tab": true,
      "auto_complete_with_fields": true,
    What KEYS are they talking about, and where do I find them, or where do I insert these two lines?
    Ryan Boehning
    @y0ssar1an
    Go to your Sublime Text preferences. This is a JSON file named Preferences.sublime-settings. On a Mac, you can open it with Cmd+,. If you're on Windows or Linux, just search for it in the menu at the top of the screen.
    It should look like this.
    Ryan Boehning
    @y0ssar1an

    The left pane is your default Sublime Text settings. They're read-only. You can't change them. It's just there as a guide, to show you all the different options you have. The right pane is where you make the changes. Everything you put in the right pane will override the defaults in the left pane.

    Does that make sense?

    johndennismaher
    @johndennismaher
    Thanks for responding. Yes, I had it up to this point. Where the uncertainty cam in is WHERE on the "Preferences.sublime-settings--User" tab do I actually insert it? It currently looks like this: {
    "auto_complete_commit_on_tab": true,
    "auto_complete_with_fields": true,
    "ignored_packages":
    [
    "CSS",
    "Vintage"
    ]
    }
    Where in this sequence of lines do they get pasted in?
    And does your answer hold true to any other s that need to be inserted for other Packages I choose to install?
    johndennismaher
    @johndennismaher
    @johndennismaher
    johndennismaher
    @johndennismaher
    OK. I think I just realized why I was getting confused. When I click on "Preferences" in the top bar, the drop-down menu gives a choices of "Settings" and "Settings--Syntax Specific", and further down another choice of "Package Settings." Under "Settings," it brings up a screen that shows the "Default" settings on the left, and on the right, the User settings. THERE, it shows those two lines installed. However, previously I wasn't looking under "Settings." I looked under "Settings--Syntax Specific" [thinking that it would go there since one of the last installation instructions is to go to "View > Syntax > Open All With Current Extension as... > CSS3" (having previously Disabled CSS).] But when I clicked on "Settings--Syntax Specific" it brings up a different split screen showing the "Default" on the left, and the "Plain Text.Sublime--Settings" on the right. The only thing showing there was: {
    {--}. Then I clicked on "Package Settings > Package Control > Settings User" and this brought up a 3rd split screen. On the left it shows the "Package Control.sublime-settings", under which are the following eleven lines: {
    "bootstrapped": true,
    "in_process_packages":
    [
    ],
    "installed_packages":
    [
    "CSS3",
    "Package Control"
    ]
    }
    johndennismaher
    @johndennismaher
    Soooooo...am I right in thinking everything is in order, with those two lines appearing where they SHOULD be appearing--under the 1st category of "Settings"?
    Ryan Boehning
    @y0ssar1an

    Sounds like you've got it. For CSS3, you don't need to touch Package Settings or Syntax-Specific settings. You only need to edit your global Sublime Text -- User settings.

    1) Add "CSS" to the list of "ignored_packages". This disables the default CSS package, so it won't conflict with CSS3.
    2) Add these keys. These will ensure that, as you're typing, you get all the completions offered to you. This can significantly speed up writing CSS.

    "auto_complete_commit_on_tab": true,
    "auto_complete_with_fields": true,
    Ajay
    @hello-ajayrawat
    After disabling css package internal style lost syntax highlighting
    @y0ssar1an can you help me please.