yalesov / vim-emblem Goto Github PK

View Code? Open in Web Editor NEW

22.0 2.0 6.0 26 KB

Adds emblem support to vim.

Vim Script 100.00%

vim-emblem's Introduction

vim-emblem

vim-emblem adds emblem support to vim.

Features:

detects .em and .emblem files as emblem
- if vim-ember-script is also included, then .em will not clash with ember-script, i.e. .emblem = emblem and .em = ember-script
sets standard coding style (two-space indentation)
syntax highlighting

This plugin contributes to vim-polyglot language pack.

Todo:

indentation

Install

Vundle

Get vundle.

.vimrc:

Bundle 'yalesov/vim-emblem'

Launch vim, :BundleInstall.

Pathogen

Get pathogen.vim.

$ cd ~/.vim/bundle
$ git clone https://github.com/yalesov/vim-emblem.git

Manual install

Download and extract all scripts into ~/.vim / $HOME\vimfiles.

License

ISC

vim-emblem's People

Contributors

Stargazers

Watchers

Forkers

andorov kxcrl sheerun jakesjews alexparker

vim-emblem's Issues

Extra text operator highlighted on second line onwards

Known bug:

| text text text
  | more text
| another line of text

All the |'s will be highlighted as operators, although the one in the second line shouldn't be.

Different colors for helpers?

Note sure if this is by design or not, but why the different colors for each vs. linkTo? I think it should just be a unified color if it's not an html5 tag. Thoughts?

New Iteration Style Breaks Highlighting

With the old style each iterator, functions were highlighted like this (note the class binding):

However, the new each todo in model style breaks this highlighting:

Today I discovered a promising looking command in vim called :TOhtml which will generate marked up HTML for syntax-highlighted code examples. This would be so awesome to have for Emblem, and I'm not sure where you can plug into it, but presently, it doesn't add any span tags to the code itself other than wrapping each line, e.g.:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>~/code/yext/rails/yeah.emblem.html</title>
<meta name="Generator" content="Vim/7.3">
<meta name="plugin-version" content="vim7.3_v10">
<meta name="syntax" content="emblem">
<meta name="settings" content="number_lines,use_css,expand_tabs">
<style type="text/css">
<!--
pre { font-family: monospace; color: #000000; background-color: #ffffff; }
body { font-family: monospace; color: #000000; background-color: #ffffff; }
.lnr { }
-->
</style>
</head>
<body>
<pre>
<span class="lnr">1 </span>
<span class="lnr">2 </span>p OMG OMG I can't #{omg} believe this works! Holy shit
<span class="lnr">3 </span>
<span class="lnr">4 </span>#asijasd.aosdiasod.sdofijd: p: span: p Holy shit #{omgomg}
</pre>
</body>
</html>

Any idea what's involved to get this working? I'd be eternally grateful.

Multiline attribute syntax is not highlighted

A component in this form is highlighted correctly:

= component-name attr-one=value attr-two="text value"

But a component in this form is not:

= component-name [
  attr-one=value
  attr-two="text value"
]

I have made a small fix in my local copy of the syntax file. I'd be happy to submit a pull request.

Title of this repo says `ember-script`

Using vim-emblem with tcomment does not comment out code correctly

Using https://github.com/vim-scripts/tComment with vim-emblem does not seem to work. Sometimes inserts # instead of /. Works with all other languages.

Colorize `in` to be same color as `each`

e.g.

Smart indentation

Todo.

Not detecting *.em files

Text blocks have color after first line

e.g.:

Weirdly enough though, if i add a line above this block, it will correctly display:

multiline comments

My preference is for additional lines to not have preceding slashes, which is still considered to be a comment while still indented.

But obviously they should still be greyed out.

The preference probably varies from developer to developer, so perhaps this can be a vimrc configuration?

Update Readme

The readme states that the plugin detects *.em files as emblem. But it can actually detect .emblem files.

Assign this project to another maintainer

Clearly this project is not maintained anymore

Using parenthesis to contain code with spaces breaks highlighting for line

If you have the following:

= input type="text" placeholder=(t 'foo.bar') class="foo bar" id="foo" value=foo_var

Everything after the end of the placeholder parenthesis (class, id and value) is highlighting like part of the text instead of more attributes.

Here is a visual example:

Glimmer Components

Seems very close to Custom tags here: https://github.com/yalesov/vim-emblem/blob/master/syntax/emblem.vim#L143

From emblemjs.com

/ render Glimmer components
%MyComponent @text="Hello World"

but looks like the regex only matches lower case.
Would this be an easy change if you're still maintaining this?