Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements #36

Open
wants to merge 31 commits into
base: master
Choose a base branch
from
Open

Improvements #36

wants to merge 31 commits into from

Conversation

evandrocoan
Copy link
Contributor

I think I worked around every big issue I could find.

# Conflicts:
#	Preferences.sublime-settings
opens itself up to 1 second after the build has started.
# Conflicts:
#	Preferences.sublime-settings
Preferences.sublime-settings
evandrocoan/ITE 108 - Expand Region keybind is not working on stable version
Sublime Text Restart. Fixes rctay#23 - The
`Build output` tab is not reused after project change or Sublime
Text Restart
whether automatically change your current view to the `Build
output` creating a new build.
by deprecating the Default *.sublime-keymap files with the
on_window_command() event listener.
window and fixed it not saving the scroll positon when the view is
closed.
# [1] https://sublimetext.userecho.com/topics/1930-add-panel-param-to-hide_panel-command/
# [2] https://forum.sublimetext.com/t/output-panel-hotkey/15628/2
def hide_panel():
window.run_command("hide_panel")
sublime.set_timeout(hide_panel, 1)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason why hiding of the Build panel is dropped?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because you can explicitly disable the build panel with show_panel_on_build. We could say that when someone explicitly enables this package with "buildview.enabled": true, they should disable the build panel with "show_panel_on_build": false.

Due the bug:

  1. show_panel_on_build setting isn't loaded from syntax specific settings sublimehq/sublime_text#679 show_panel_on_build setting isn't loaded from syntax specific settings

Sublime Text is not loading the setting show_panel_on_build from the user projects settings. Then, if someone enables this package per project only, they will not be able to stop the build panel from showing up. However, the fix is very simple, as explained on the issue (sublimehq/sublime_text#679) and can be performed by any user. For example, my Sublime Text is already patched against that.

I got tired of living with those small glitches/bugs which can be extremely easy fixed by the Sublime Text developers. Then, I decided to stop patching our packages with very ugly and hardly working hacks, and let the affected users directly patch Sublime Text files. Of course, only if they can. Otherwise we would still have to keep our packages with those very ugly hacks.

@rctay
Copy link
Owner

rctay commented Aug 7, 2019 via email

@rctay
Copy link
Owner

rctay commented Sep 29, 2019

Hi @evandrocoan would it be OK for you to rebase your branch on top of this repo's master?

@rctay rctay reopened this Sep 29, 2019
@evandrocoan
Copy link
Contributor Author

I think I did not understand correctly.

There are few ways to integrated my branch on your master:

  1. You can merge this pull request squashing (all my commits would become a single).
  2. You can merge this pull request without squashing (all my commits are kept).
  3. You can rebase this pull request and no merge commit would be created and it would be like I was committing directly to your master.
  4. You can cherry pick only the commits you would like, directly into your master
  5. You can cherry pick only the commits you would like, into some other branch and either merge it, squash it or rebase it into your master.

For me, you can merge this any ways you would like.

the head commit today as the last supported version of Sublime
Text 3. This is used to start developing the migration for Sublime
Text 4. New updates to Sublime Text 3 should no happen. If required, a tag 3998 should be created inside settings.json with
the changes required for this new version.
Traceback (most recent call last):
  File "F:\SublimeText\Lib\python33\sublime_plugin.py", line 308, in reload_plugin
    m = importlib.import_module(modulename)
  File "./python3.3/importlib/__init__.py", line 90, in import_module
  File "<frozen importlib._bootstrap>", line 1584, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1565, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1532, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 584, in _check_name_wrapper
  File "<frozen importlib._bootstrap>", line 1022, in load_module
  File "<frozen importlib._bootstrap>", line 1003, in load_module
  File "<frozen importlib._bootstrap>", line 560, in module_for_loader_wrapper
  File "<frozen importlib._bootstrap>", line 868, in _load_module
  File "<frozen importlib._bootstrap>", line 313, in _call_with_frames_removed
  File "F:\SublimeText\Data\Packages\BuildView\commands.py", line 7, in <module>
    from pipe_views import PipeViews, proxy_settings
ImportError: No module named 'pipe_views'
# Conflicts:
#	README.md
#	commands.py
#	pipe_views.py
@rctay
Copy link
Owner

rctay commented Oct 15, 2021

Thanks for the new commits, @evandrocoan , I'll look at integrating them

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

Successfully merging this pull request may close these issues.

2 participants