Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Simply Doesn't Work #86

Closed
1 task done
buck-ross opened this issue Oct 29, 2018 · 3 comments
Closed
1 task done

Simply Doesn't Work #86

buck-ross opened this issue Oct 29, 2018 · 3 comments

Comments

@buck-ross
Copy link

Prerequisites

Description

Atom is not highlighting "TODO" statements at all.

Steps to Reproduce

  1. Open Atom
  2. Open or create any file (tested with ".js" and ".c")
  3. Type "// TODO: test", "// TODO test", "// todo: test", or "// todo test"

Expected behavior:
"TODO" should have been highlighted (last I recall, in a purple color, I think)

Actual behavior:
"TODO" looks like just any other word in a comment: gray and boring

Reproduces how often:
100% of the time (it used to work, but today I noticed that it had stopped working. Don't actually know how long it's been since it stopped working, but it was working last Sunday).

Versions

Atom : 1.32.0
Electron: 2.0.12
Chrome : 61.0.3163.100
Node : 8.9.3

Additional Information

No errors were reported in the Developer Console while I was testing it, except for some warning that started with:

Electron Security Warning /usr/lib/electron/re...ity-warnings.js
Security Policy Set or a policy with "unsafe-eval" enabled. This exposes users of this app to unnecessary security risks

@beingmrkenny
Copy link

Noticed same issue. When viewing the HTML in the editor window (i.e. opening the dev tools panel and looking at the DOM), I can see that TODO tags have not been wrapped in any kind of span element with the .syntax--todo, .syntax--fixme etc classnames.

Atom 1.32.0
Electron 2.0.9
Chrome 61.0.3163.100
Node 8.9.3

I'm also on OS X 10.11.6.

@Ben3eeE
Copy link

Ben3eeE commented Oct 29, 2018

Thanks for taking the time to contribute!

We noticed that this is a duplicate of #82. You may want to subscribe there for updates.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.

For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.

@chittolina

This comment has been minimized.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants