aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/highlighting.ts
Commit message (Collapse)AuthorAgeFilesLines
* Improved compatibility with themeseaglgenes1012020-02-201-4/+4
|
* vscode: press ; to respect semicolonsVeetaha2020-02-171-1/+1
|
* Simplify startupAleksey Kladov2020-02-171-2/+3
|
* Simplify TS reload logicAleksey Kladov2020-02-171-1/+1
| | | | Fixes #3164
* Merge #3024bors[bot]2020-02-051-0/+2
|\ | | | | | | | | | | | | | | 3024: vscode: eliminate floating promises and insane amount of resource handle leaks r=matklad a=Veetaha Khm, yeah ... Co-authored-by: Veetaha <[email protected]>
| * vscode: eliminate floating promises and insane amount of resource handle leaksVeetaha2020-02-051-0/+2
| |
* | vscode: yet another refactor commitVeetaha2020-02-041-4/+4
|/
* Use simple prng instead of a dependencyAleksey Kladov2020-02-031-3/+22
| | | | closes #2999
* vscode extension cleanup: migrate to prefer-const tslint ruleVeetaha2020-02-021-3/+3
|
* Fix seedrandom in packaged extensionbjorn32020-02-011-2/+1
| | | | Fixes #2971
* Add semicolonsAleksey Kladov2019-12-311-6/+6
|
* Refactor server lifecycleAleksey Kladov2019-12-311-25/+31
|
* Refactor status activationAleksey Kladov2019-12-311-22/+20
|
* Drop support for legacy colorizationAleksey Kladov2019-12-311-65/+41
|
* Rename fileAleksey Kladov2019-12-311-1/+1
|
* Switch impure functional style to pure imperativeAleksey Kladov2019-12-311-3/+5
|
* Rearrange codeAleksey Kladov2019-12-311-106/+105
|
* Use Ctx in highlighterAleksey Kladov2019-12-301-5/+10
|
* Reformat with tsfmtAleksey Kladov2019-12-301-26/+26
|
* Privatize highlightingAleksey Kladov2019-12-301-2/+38
|
* Thoughtlessly copy-paste a fix to a problem I don't understandAleksey Kladov2019-12-301-1/+2
|
* Add config to CtxAleksey Kladov2019-12-301-1/+1
|
* Encapsulate highlighting activationAleksey Kladov2019-12-301-1/+21
|
* Fix ↵Seivan Heidari2019-12-231-2/+2
| | | | | | https://github.com/rust-analyzer/rust-analyzer/pull/2061#discussion_r348716036 Fix https://github.com/rust-analyzer/rust-analyzer/pull/2061/files/68a5ff050faf514e9d122212a66703ca8ce66ab7#r361019340
* Merge branch 'master' into feature/themesSeivan Heidari2019-12-231-12/+18
|\
| * Fix highlighting token namesAleksey Kladov2019-12-171-4/+4
| |
| * removed `type.alias`Omer Ben-Amram2019-12-141-0/+1
| |
| * added decorationsOmer Ben-Amram2019-12-141-0/+6
| |
| * Code: enable prettier trailing commasLaurențiu Nicola2019-12-091-8/+8
| |
| * Code: bump depsLaurențiu Nicola2019-12-081-3/+4
| |
* | Probably a better approach to check for values before assigning lest we ↵Seivan Heidari2019-11-101-3/+27
| | | | | | | | replace something.
* | Vscode wasn't running the linter automatically so ran `npm run fix` - wonder ↵Seivan Heidari2019-11-091-52/+29
| | | | | | | | if it's related to `tslint` being deprecated.
* | See if this satisfies the CI.Seivan Heidari2019-11-051-5/+5
| |
* | Fix typo.Seivan Heidari2019-11-041-1/+1
| |
* | Logging fallback tag in case scopes are missing.Seivan Heidari2019-11-041-3/+5
| |
* | * Adding scope mapping configuration manifest in `package.json`Seivan Heidari2019-11-041-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * Loading configurable scope mappings from settings. * Updating Readme with `rust-analyzer.scopeMappings`. `rust-analyzer.scopeMappings` -- a scheme backed JSON object to tweak Rust Analyzer scopes to TextMate scopes. ```jsonc { //Will autocomplete keys to available RA scopes. "keyword.unsafe": ["keyword", "keyword.control"], //Values are string | TextMateScope | [string | TextMateScope] "comments": "comment.block" } ```
* | Adding better debugging for testing themes missing tags and which scopes ↵Seivan Heidari2019-10-311-1/+4
| | | | | | | | | | | | didn't map. Since this file is no longer being pushed upstream, double down on monads.
* | Adding debugging to figure out missing scopes from theme.Seivan Heidari2019-10-271-5/+4
| |
* | Introducing a Scopes Mapper to map from RA scopes to TextMate scopes with ↵Seivan Heidari2019-10-271-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fallbacks. Current scopes defined: ``` ['keyword.unsafe', ['storage.modifier', 'keyword.other', 'keyword.control']], ['function', ['entity.name.function']], ['parameter', ['variable.parameter']], ['type', ['entity.name.type']], ['builtin', ['variable.language', 'support.type', 'support.type']], ['text', ['string', 'string.quoted', 'string.regexp']], ['attribute', ['keyword']], ['literal', ['string', 'string.quoted', 'string.regexp']], ['macro', ['support.other']], ['variable.mut', ['variable']], ['field', ['variable.object.property']], ['module', ['entity.name.section']] ``` Need to complement with further fallbacks as some themes fail.
* | Proof of concept theming and 'tokenColorCustomizations' support.Seivan Heidari2019-10-241-25/+69
|/
* underline mutable bindingsAleksey Kladov2019-07-191-27/+34
|
* highlight mutable variables differentlyEkaterina Babshukova2019-07-181-0/+1
|
* Make rainbows optionalPascal Hertleif2019-05-271-5/+6
|
* Semantic highlighting spikePascal Hertleif2019-05-271-3/+42
| | | | | | | | | | Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request?
* Improve highlighting of name refsLaurențiu Nicola2019-05-231-1/+6
|
* Address feedbackLaurențiu Nicola2019-05-211-3/+2
|
* Use ThemeColor and add support for light themesLaurențiu Nicola2019-05-211-13/+22
|
* highlight macro identsAleksey Kladov2018-12-281-1/+2
|
* Remove error publishing through publishDecorationsAdolfo Ochagavía2018-10-101-7/+0
|
* Run prettier on all filesDaniel McNab2018-10-081-17/+28
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 08:34:26 +0000