Improve Jade syntax highlighting. Colors currently are mostly blue.

Hi,

the Seti-Syntax-Theme is awesome, but in the VI-mode the cursor is barely visible:

Please make it a little brighter (read: more visible).

In index.less: Use the atom-text-editor tag instead of the editor-colors class.

Hello and thank you for this package. I'm wondering how I can make appear the extension icon inside the sidebar (javascript, coffee, jade...). I have set up Seti UI and Seti Syntax and selected them as UI Theme and Syntax Theme but here is what I get:

You need to press end twice in order to see the last character on the widest line.

The background and foreground colors in a Ruby regex seem to be the same rendering it unreadable.

In index.less: Use the selector atom-text-editor[mini] to select mini-editors.
In index.less: Use the atom-text-editor tag instead of the editor class.
In index.less: Use the atom-text-editor tag instead of the editor-colors class.

In index.less: Use the selector atom-text-editor[mini] to select mini-editors.

Current line and line are not highlighted as shown

Please refer the screen shot.

In index.less: Use the atom-text-editor tag instead of the editor-colors class.

In index.less: Use the atom-text-editor tag instead of the editor class.

In index.less: Use the selector atom-text-editor[mini] to select mini-editors.

When using Dark Atom Syntax, the gutter width is 49px; with Seti Syntax it's 43px.
When there is a line with .git-line-added, the .icon-right div gets cut (see screenshot).
I have been unable to pinpoint the exact css property that is causing this difference.

Hi there,

Love the theme, I have one slight issue however:

I'm currently working on a ruby project and text wrapped in quotes in these files are meant to be blue, however whenever I open a html file the quoted text in the .rb files turns white as well. It's a minor gripe but the blue highlighting makes it that bit easier to read.

This issue seems to be happening when I split the windows and have a html file open in one of them, I can't seem to recreate with just one window reliably...

Thanks

OMG, look at all the blue:

Otherwise, I love Seti. Thanks so much for making it!

In index.less: Use the atom-text-editor tag instead of the editor class.

In index.less: Use the atom-text-editor tag instead of the editor class.

Hi,

while I really like the Seti theme, the syntax style is really strange. I have the feeling it is heavily javascript optimized and not really tested for other languages.

For Ruby the highlightings seems totally arbitrary. Just a few examples:

• Member variables in ruby always begin with a '@' character. The '@' character is highlighted in blue while the rest of the name is highlighted in green. I assume that the ruby plugin of atom marks '@' as keyword, which is wrong, although for some other plugins it may be helpful to distinguish between the variable name prefix and the rest of the name.
• function arguments are colored blue, while local variables are colored white. Function arguments are blue, too
• common functions (I guess they are marked as keyword internally, again somewhat wrong) are colored green like member variables, which is really strange
• class names are colored blue like functions and arguments and strings and regexps

I think I stop here. In general there are very few colors. Often, the same color is used for completely different syntax elements (class names and strings), while different colors are used for very similar syntax elements (arguments and local variables)

I am working on some BSON files for dummy data on my server. Mongo can spit out a JSON file but I prefer to go straight to them without parsing and checking or manually adding parameters. Plus a Mongo file icon might look nice with the others, just saying. After all it's a simple expansion, if I knew how to do it I'd do it myself and push it to you guys.

Atom 0.135
OS Ubuntu 14.04 (source-build)

In index.less: Use the atom-text-editor tag instead of the editor-colors class.

In index.less: Use the atom-text-editor tag instead of the editor-colors class.

Hello...

First, i love your Seti package. Man, this is soooo great! 👍

Second, i'm using Language GFM syntax.

Last, my markdown syntax is not highlighted.

Is there a way to fix it?

Thanks

In index.less: Use the atom-text-editor tag instead of the editor-colors class.

index.less
Use the atom-text-editor tag instead of the editor-colors class.
Use the atom-text-editor tag instead of the editor class.
Use the selector atom-text-editor[mini] to select mini-editors.

This image says it all:

Versions

• Atom: 0.172.0
• Atom-Shell: 0.20.5
• OS: linux 3.18-2.dmz.1-liquorix-amd64
• Misc
  • apm 0.119.0
  • npm 1.4.4
  • node 0.10.35
  • python 2.7.8
  • git 2.1.4

So I've been reading the files on this project for a couple of weeks, but I don't get most stuff yet. So it'd be helpful to get a hand. Maybe take over expanding for for other languages on my free time.

In index.less: Use the atom-text-editor tag instead of the editor-colors class.

In C++, if there is a space between function name and bracket, then two brackets' color will be different.
Will it be solve or not

i have installed seti today and i really like it but there is on thing that i don't like about

as you can see normal text inside

& the type button are in the same color wich is confusing in case of long lines of codes

is there is any way to change that color of "button" and others ? ??

I opened up an issue with the C++ language guys, but according to them it's an issue with the theme and not the parser: atom/language-c#30 (comment)

Original:

The syntax highlighting of parenthesis in function calls does not work properly, as demonstrated in the image below.

http://imgur.com/KfDzDrj

In index.less: Use the selector atom-text-editor[mini] to select mini-editors.

In index.less: Use the selector atom-text-editor[mini] to select mini-editors.

as title says

In index.less: Use the atom-text-editor tag instead of the editor class.

defunkt/Zen#22

Hopefully we see some more activity soon in here. ejs might be a bit tricky with the whole html + javascript thing but it'd be awesome to have built-in.

In index.less: Use .bracket-matcher .region to select highlighted brackets.

Hi !
love your theme!
In bracket matcher... the underline is not showing ...
!
screen shot 2014-06-16 at 15 20 29

You think you can improve this ?

In index.less: Use the selector atom-text-editor[mini] to select mini-editors.

The "?" and the ":" in the ternary operator appear in white. Maybe green will be more appropiate

I'm having an issue with seti-syntax and atom-sublime-select. When doing a vertical selection of text or individual multi-line selections, the selection is inserted to the right of the cursor.

The gif explains it pretty well.

I'm posting this on atom-sublime-select's issues as well.

In index.less: Use the atom-text-editor tag instead of the editor, editor-colors class.

In index.less: Use the atom-text-editor tag instead of the editor-colors class.

In index.less: Use the atom-text-editor tag instead of the editor class.

Not sure how to describe it , but ever since update 0.2.0, i cannot read text unless my cursor is on the row due to the gray screen placed over the syntax, its like highlighting is reversed

Im assuming this has to do with the Shadow DOM in the changelog?

In index.less: Target the selector :host, atom-text-editor instead of .editor for shadow DOM support.

The way the borders on multi-line selected text make it a little harder to read text, so I'm trying to override it. I found the LESS that sets the border, but I can't seem to override it with my styles.less override.

It should be:

.editor, :host {
  .selection .region { border: 0; }
}

…but it doesn't work. Not even with !important. Any ideas?

The bracket matcher classes appear to have changed, I fixed the issue temporarily by putting the following in my stylesheet:

.theme-seti-syntax {
  .bracket-matcher {
    border: 0;
    margin: 0;
    > .region {
      border-bottom: 1px solid #55b5db;
      margin-top: 2px;
    }
  }
}

In index.less: Target the selector :host, atom-text-editor instead of .editor-colors for shadow DOM support.

Using the latest version of everything.

index.less
Use the `atom-text-editor` tag instead of the `editor-colors` class.
Use the `atom-text-editor` tag instead of the `editor` class.
Use the selector `atom-text-editor[mini]` to select mini-editors.