unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Dunn <dunn.alex@gmail.com>
To: Etienne Prud'homme <e.e.f.prudhomme@gmail.com>, emacs-devel@gnu.org
Subject: Re: SCSS parser ideas
Date: Tue, 05 Apr 2016 14:05:55 -0700	[thread overview]
Message-ID: <m2vb3vpxzg.fsf@snow.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20160405165154.72ba85b9@ThinkPax>

I think better built-in support for SCSS would be very welcome,
especially since development of both the scss-mode
(https://github.com/antonj/scss-mode) and sass-mode
(https://github.com/nex3/sass-mode) external packages seems to have
ceased.

Etienne Prud'homme <e.e.f.prudhomme@gmail.com> writes:

> Since I study in the field of Front-End web development, I find it sad
> that Emacs lacks features that would otherwise be included in other
> text-editors.
>
> One feature that is lacking is discovering SCSS variable values. I’m
> thinking something like Eldoc is doing for function declarations in C
> or Emacs lisp.
>
> Given that SCSS is a Preprocessor, it’s possible to evaluate a variable
> by simply parsing a file. Unless a file changes, a variable will always
> stay the same.
>
> I made a basic prototype parser in elisp that did a hash map of all
> variable declarations from a buffer. However, I don’t think it’s
> suitable in the long-term.
>
> Since I’ve got no experience in grammar parsing implementation, I was
> wondering if it could be worth making a CEDET Semantic SCSS parser
> (and thus CSS one). It would give much more flexibility. We could
> include variables from other files, functions and mixins support or
> even a CSS tree structure of a project.
>
> Best regards,



  reply	other threads:[~2016-04-05 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 20:51 SCSS parser ideas Etienne Prud'homme
2016-04-05 21:05 ` Alex Dunn [this message]
2016-04-06  2:00   ` Stefan Monnier
2016-04-06 16:23     ` Etienne Prud'homme
2016-04-06 20:37       ` Simen Heggestøyl
2016-04-07 12:23       ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2vb3vpxzg.fsf@snow.i-did-not-set--mail-host-address--so-tickle-me \
    --to=dunn.alex@gmail.com \
    --cc=e.e.f.prudhomme@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).