slim-template/emacs-slim

Syntax highlighting for Slim

emacs-slim's Issues

Access problem

Hi, @minad!

After the repo was moved I no longer seem to have commit privileges for it.

Hi, subword-mode can not work.

When enable subword-mode, subword-backward-kill is not work correct, it behavior same as original backward-kill-word.

Thanks.

Proposal for maintainership

Hi,

As a long time slim and emacs user, I’d like to propose my candidature as a new co-maintainer for this package. Along with reviewing pending MR and issues and watching for new ones, I’d like to make a new release and propose this package in the new nongnu elpa repository.

Have a great day.

More like a question...

Hi, first of all thanks for a great plugin :)

I was wondering if you know this, probably being very skilled in emacs and its modes:

I have rinari installed (for rails and ruby) and, for some reason, when the slim mode activates i lose kinari (i.e. no longer can "CTRL+C ; " for navigation within the rails project). Do you have any idea what could cause that what can i do to solve it?

Thanks in advance,
Pedro

JavaScript Block Indentation

When working with javascript: blocks within a slim file the indentation can get out of hand since there doesn't seem to be awareness that you're in a JS block and not slim.

It would help if there was some basic indentation help. Also when using (newline-and-indent) within a slim buffer within a JS block it indents 2 characters forward as if you're working in slim still.

Slim Mode Does not auto indent Rails View Files.

I am using slim templates in Ruby on Rails.
I have some files with name scheme such as index.html.slim or show.html.slim

None of these files auto-indent new line. When I press enter, the cursor just goes to beginning of line instead of correctly auto-indenting.

Fix it

It is very outdated

Using == within = lines

When using == in code inside a = block the syntax gets thrown off a bit.

Attributes in Square Brackets

Slim allows:

a[href="http://google.com"
  data-id="google-link"
  data-clicked="false"] Go to Bing

Slim-mode doesn't treat this differently than nesting plain tags, so no functionality is broken here, but it would be huge boon to readability if the attributes were highlighted in the same way they are on a single line.

Some conflicts could occur, however:

div[class="hidden"
    style="display: none;"] You can't see me!

style is a tag as well as an attribute.

I'm not versed in Emacs Lisp, so I'm unsure how this would manifest in the code itself, but I can try my hand at it (I've got some handy Clojure experience.)

Thoughts?

Edit:
I just realized proper indentation would also be necessary. The above code look like this in slim-mode:

div[class="hidden"
  style="display: none;"] You can't see me!

slim-backspace-backdents-nesting is ignored

With slim-backspace-backdents-nesting set to nil, slim-electric-backspace will indent code following current line.

Happens using slim-mode-20130614.2240 from elpa.

single quote line indicator breaks highlighting

When I add single quoted line it breaks further markup highlighting. My complete Emacs config could be found at [email protected]:alecnmk/remacs.git

I'm attaching screenshot which indicates issue on test.slim example.

Thank you!

Please specify the license for this package

Could you please specify the license used for this package?

Assuming that you want to release under "the GPL v3 or any later version", the best way to do that would be to add this permission statement to the library header:

;; This file is free software; you can redistribute it and/or modify
;; it under the terms of the GNU General Public License as published by
;; the Free Software Foundation; either version 3, or (at your option)
;; any later version.

;; This file is distributed in the hope that it will be useful,
;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
;; GNU General Public License for more details.

;; You should have received a copy of the GNU General Public License
;; along with this program.  If not, see <http://www.gnu.org/licenses/>.

Also consider adding a LICENSE file containing the text of the GPL-3. You could add just that file without also adding the above persmission statement, but if you do that, then the "or (at your option) any later version" bit won't be known. So I recommend that you add both the actual license and the permission statement.

If you find the permission statement to be too noisy, then you could instead add one of these following lines to the header. If you do that, then it becomes more important to also add the LICENSE file - a judge might decide that such a line by itself is not sufficient. Still, adding just such a line is better than not specifing the license at all.

;; License: GNU General Public License version 3, or (at your option) any later version
;; License: GNU General Public License version 3, or any later version
;; License: GNU GPL version 3, or (at your option) any later version
;; License: GPL version 3, or (at your option) any later version
;; License: GPL version 3, or any later version
;; License: GPL v3, or (at your option) any later version
;; License: GPL v3, or any later version
;; License: GPL-3+