Treat application settings differently

Open
#379 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
tooling

Research direction

Start by locating the completion and settings-validation logic for syntax-specific and other per-view settings, then compare it with Preferences.sublime-settings. The change is complete when application-wide settings such as theme and overlay_scroll_bars are excluded from per-view completions or clearly marked as misplaced rather than misspelled.

Written by the indexing model from the issue text.

Description

enhancement

There are some settings that can only be set in Preferences.sublime-settings, such as theme or overlay_scroll_bars and similar, that affect the entire application across all windows. These settings should not be considered for completions in syntax-specific and other settings that boild down to a per-view level.

In fact, we can even mark these settings as "unknown" in these other settings files, although I would try to annotate that the settings aren't misspelled but misplaced.

Will probably need to be a hardcoded list of settings.

Dominant language
Python
Stars
455
Forks
86
Avg merge
7d 10h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SublimeText/PackageDev

All issues in SublimeText/PackageDev

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.