Skip to content

Add SettingsUI - #9459

Open
mfuentesg wants to merge 2 commits into
sublimehq:masterfrom
mfuentesg:add-settings-ui
Open

Add SettingsUI#9459
mfuentesg wants to merge 2 commits into
sublimehq:masterfrom
mfuentesg:add-settings-ui

Conversation

@mfuentesg

@mfuentesg mfuentesg commented Jun 23, 2026

Copy link
Copy Markdown
Contributor
  • I'm the package's author and/or maintainer.
  • I have read the docs.
  • I have tagged a release with a semver version number.
  • My package repo has a description and a README describing what it's for and how to use it.
  • My package doesn't add context menu entries.
  • My package doesn't add key bindings.
  • Any commands are available via the command palette.
  • Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
  • If my package is a syntax it doesn't also add a color scheme. (not a syntax package)
  • I use .gitattributes to exclude files from the package. (will add)

My package is a visual settings editor for Sublime Text 4. It opens a two-pane panel that lets users browse and edit Preferences.sublime-settings through typed widgets (toggles, dropdowns, color scheme / theme / font pickers) instead of editing raw JSON.

There are no packages like it in Package Control.

image image image

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

Copy link
Copy Markdown
Contributor

This PR adds SettingsUI.

Review for SettingsUI main-face212-2026.06.23.17.38.00

No failures

5 warnings:

  • Modifying sys.path is usually a bad idea and can interfere with other packages. Consider using relative imports instead.
    File: tests/conftest.py
    Line: 5, Column: 1
  • Modifying sys.path is usually a bad idea and can interfere with other packages. Consider using relative imports instead.
    File: tests/conftest.py
    Line: 6, Column: 1
  • 'Default.sublime-commands' has no settings entry using edit_settings for 'SettingsUI'. Add an entry with caption 'Preferences: SettingsUI Settings' and 'args.base_file' set to '${packages}/SettingsUI/SettingsUI.sublime-settings'.
  • 'Main.sublime-menu' has no 'Package Settings' entry for 'SettingsUI'
  • 'Main.sublime-menu' has no settings entry under 'Preferences > Package Settings > SettingsUI' to edit 'SettingsUI.sublime-settings'. Add a 'Settings' entry using edit_settings with 'args.base_file' set to '${packages}/SettingsUI/SettingsUI.sublime-settings'.

@mfuentesg

Copy link
Copy Markdown
Contributor Author

Sorry, I just updated PR to include only the required changes instead of many changes in s.json file :)

@braver

braver commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

That's pretty ambitious. Superficially I'd expect for a graphic UI at least some kind of preview screenshot in the readme :). I tried to run it locally here (stable version 4200), and I saw a flash of something that looked like a UI and then it crashed...

@mfuentesg

mfuentesg commented Jun 29, 2026

Copy link
Copy Markdown
Contributor Author

Oh is it? Sure, let me attach a screenshot :). Actually I would like to have this built in st, but for now it sounds reasonable haha.

@mfuentesg

Copy link
Copy Markdown
Contributor Author

Hey @braver , I have added three screenshots using my self theme. Please, let me know if you have any log of issue on your st. Since I wasn't able to reproduce it :)

@braver

braver commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator

Thanks, but I meant more in the README for future users of the package.

I'll have a look at trying to get it to run, or hopefully capturing a crash log 🤞🏻

@braver

braver commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator

Note that your package directory is not writable. Packages are delivered as a zip so they can safely be replaced when upgraded etc. If you want to write anything do so to the user's packages path. To get paths to files, or contents of files, inside your package use the API (sublime.find_resources(), sublime.load_resource() etc.).

Sublime loads any python file in a package's top level directory as a "plugin". There should not be an __init__ file in that top level directory.

More info about both topics in https://www.sublimetext.com/docs/packages.html.

Sublime doesn't seem to capture any logs before the crash. I've tried removing all my settings. And I've tried regenerating the schema. No luck so far.

@mfuentesg

Copy link
Copy Markdown
Contributor Author

Sure, thanks for the insights. Let me take a look to the API.

@mfuentesg

Copy link
Copy Markdown
Contributor Author

Can you please chaeck again @braver any other comment is welcomed :)

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@braver

braver commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Sorry, it still crashes immediately. Without a debug mode I can't help test and verify this package.

@braver braver added feedback provided The changes and package have been seen by a reviewer stale The author has not responded for at least 2 weeks labels Aug 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feedback provided The changes and package have been seen by a reviewer stale The author has not responded for at least 2 weeks

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants