Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Apr 08 2018 02:35
    TaqwaR opened #33
  • Sep 07 2017 14:13
    prathprabhudesai opened #32
  • Aug 01 2017 16:04
    coopermaruyama commented #31
  • Aug 01 2017 14:31
    Jose4gg opened #31
  • May 08 2017 19:05
    coopermaruyama closed #30
  • May 08 2017 19:05
    coopermaruyama commented #30
  • May 08 2017 04:36
    Elmapul opened #30
  • Mar 13 2017 23:10
    coopermaruyama closed #29
  • Mar 13 2017 23:10
    coopermaruyama commented #29
  • Mar 13 2017 01:56
    arrowfunxtion opened #29
  • Jul 08 2016 18:27

    coopermaruyama on develop

    updat readme. Prepare 1.10.6 release (compare)

  • Jul 08 2016 18:27

    coopermaruyama on v1.10.6

    (compare)

  • May 27 2016 22:40
    coopermaruyama closed #26
  • May 27 2016 22:36
    coopermaruyama closed #24
  • May 27 2016 22:36
    coopermaruyama commented #24
  • May 27 2016 22:35
    coopermaruyama closed #28
  • May 27 2016 22:35
    coopermaruyama commented #28
  • May 27 2016 22:34

    coopermaruyama on v1.10.5

    (compare)

  • May 27 2016 22:34

    coopermaruyama on develop

    fix: Forgot to check in a new f… Prepare 1.10.5 release (compare)

  • May 17 2016 19:08
    alice-em commented #28
Cooper Maruyama
@coopermaruyama
If anyone has suggestions/feedback to improve this theme, please post it here!
Tom Hirashima
@thirashima
great theme, but the color for comments is too dark. it works if you only use comments to comment out code, but not so great if you use comments to describe code. would be nice if you could maybe configure it.
Tom Hirashima
@thirashima
fwiw i set comments to be #6E6E88 in my user stylesheet, and it looks pretty good
Cooper Maruyama
@coopermaruyama
@thirashima thanks for the suggestion! It does seem a bit dark, so I just pushed out a new version with lighter comments. The old comment color had a 30% lightness value and the color you mentioned is 48%; I went up to 36% as I don't want to change it too much for people using it currently. If you want to use your color it's as simple as putting .source .comment { color: #e6e88; } which should override what's in the theme. Eventually I plan on adding a few options to increase or decrease the overall brightness of a few things as well as the saturation.
Tom Hirashima
@thirashima
thanks. one more thing i've noticed: when working with text that is italicized, it is very hard to determine the actual cursor location. but what's even weirder, is if i switch the theme, and then switch back, the issue seems to go away?
Cooper Maruyama
@coopermaruyama
@thirashima that's a first. Do you have a screenshot?
Tom Hirashima
@thirashima
@coopermaruyama http://cl.ly/bB9y here is an example. the cursor overlaps the letters, and it looks like it could be between the "e" and the "s", but it's actually between the "s" and the "t".
Cooper Maruyama
@coopermaruyama

This is actually caused by an Atom issue, as their character measuring for fonts only happens on initial load, and even then it happens too early (atom/atom#4200 ) . However, Apathy has some code in it that forces characters to be re-measured in order to work around this.

I just checked with that code on my end and the cursor is lined up correctly, so it looks like you're experiencing a bug.

First of all, try closing the file and then re-opening it and see if that still happens. If closing/reopening the file fixes the issue, then it's probably a bug in Apathy. If it happens even after re-opening the file, then it's likely that another package or maybe your custom stylesheet is causing it.

Also, if you increase/decrease the font size, it's possible that it will misalign the cursor. However, simply re-opening the file should fix this, too. If you have a font size other than 15px, try setting it to 15 px and see if that fixes the issue.

One last thing you can try is to open the inspector cmd+alt+I and try running this code in the console:

var editor, editorView, i, len, ref, ref1, ref2, ref3, ref4;

ref = atom.workspace.getTextEditors();
for (i = 0, len = ref.length; i < len; i++) {
  editor = ref[i];
  editorView = (ref1 = atom.views) != null ? typeof ref1.getView === "function" ? ref1.getView(editor) : void 0 : void 0;
  if ((ref2 = editorView.component) != null) {
    if ((ref3 = ref2.linesComponent) != null) {
      if (typeof ref3.remeasureCharacterWidths === "function") {
        ref3.remeasureCharacterWidths();
      }
    }
  }
  if ((ref4 = editorView.component) != null) {
    if (typeof ref4.remeasureCharacterWidths === "function") {
      ref4.remeasureCharacterWidths();
    }
  }
}

If one of the above fixed it, let me know which as it means it's a bug in Apathy.

If none of the above fix it, I really have to believe that it's not an issue with Apathy, and you should check your stylesheets or packages for anything that would be adding the following styles:

  • letter-spacing
  • custom font
  • font-smoothing
  • borders or anything that would cause the size of any element within the text editor pane to change
...
@SourceAura
Cursor issue, similar to [jesseweed/seti-syntax#106] <- i think apathy may be experiencing the same 'clash'...can someone help me fix it, or point me in the direction of a solution?? ...i love this theme...
...
@SourceAura
or nah ;)…i’m about two beginner complexes from fixing it myself.
Cooper Maruyama
@coopermaruyama
Hey man, sorry i didnt see this, but it got fixed in a recent release @SourceAura
...
@SourceAura
@coopermaruyama i noticed bro, it’s cool…im still studying, can’t wait to qualify for serious contribution