Sublime Forum

Dev Build 3137

#20

I am using build 3139 on Fedora 25, and I have noticed the recent update has caused issue with the folder arrows in the sidebar, using Material theme v4.0.6 and SideBarEnhancements v5.0.12

It looks like the background highlighting of the folder icon has changed, there are now boxes around the folder arrows.

I am not sure if this is a bug in one of the packages or due to the application update?
Has anyone else seen this?

0 Likes
#21

Check your console to see if any messages were printed about parsing the theme.

0 Likes
#22

Japanese input with IBUS still broken.

0 Likes
#23

The following messages appear in the console:

Errors parsing theme:
icon_folder is missing layer0.opacity, setting to 1.0 for backwards compatibility
icon_folder_loading is missing layer0.opacity, setting to 1.0 for backwards compatibility
icon_folder is missing layer0.opacity, setting to 1.0 for backwards compatibility
icon_folder is missing layer0.opacity, setting to 1.0 for backwards compatibility
icon_folder_loading is missing layer0.opacity, setting to 1.0 for backwards compatibility
icon_folder is missing layer0.opacity, setting to 1.0 for backwards compatibility
icon_folder is missing layer0.opacity, setting to 1.0 for backwards compatibility
(repeats a few more times)
icon_file_type is missing layer0.opacity, setting to 1.0 for backwards compatibility
icon_file_type is missing layer0.opacity, setting to 1.0 for backwards compatibility

So do the themes and icon package need to be updated?

0 Likes
#24

You don’t need to post this on every build. I am aware that IME issues will need some attention, but it won’t be happening in this dev cycle.

1 Like
#25

This issue has been ongoing since 2012:

What does it take to get a fix?

0 Likes
#26

On Windows (7), it seems like the font "Consolas Bold" is not rendered as bold any more, just slightly larger than normal "Consolas"

0 Likes
#27

is there any chance we could get MiniHTML parse errors in the console to display a call stack (traceback) or show that it is a MiniHTML related parse error please?

>>> view.show_popup('<')
Parse Error:  code: Unexpected EOF

i.e. I’d be easier to debug if it said

MiniHTML Parse Error:  code: Unexpected EOF
  File "<string>", line 1, in <module>
3 Likes
#28

At this point you’ll have to wait until a dev cycle where I can spend some time unravelling the myriad of libraries, options and implementation requirements related to IME on Linux and Windows. We have some cursory implementation right now that sort-of works with scim on Linux, but apparently something about the API calls we are using doesn’t play nice with IBUS, and we don’t currently have a way to show the preedit string.

2 Likes
Support chinese input method
Japanese IME input on windows no longer working after build 3126
Type Japanese into sublime
Make Japanese input in ST more convenient
#29

Thanks, I’ll check it out

1 Like
#30

I have noticed when I do a Preferences -> Font -> Reset that Sublime removes the font_size option from my user preferences file.

Is there some way to stop this from deciding to fall back to global font_size options?

When I do Preferences -> Font -> Reset I expect Sublime would reset the font_size from some value NOT defined in my user preferences to the value I have defined there.

I don’t know any other application than simply terminates user preferences like this :expressionless:

0 Likes
#31

You can replace the menu entry with your own implementation which do what you want to.
But I do not know I easy way of just replacing one menu entry without override the whole default menu.

Perhaps this should be a feature request on the default menus. They could add some tags to each menu entry, and if the user defines a configuration file which specifies that tag, that menu entry is overwritten.

Or you could just write a command call My Default Font Reset and add it to the command palette and call it when you fell like.

0 Likes
#32

The command that does this is reset_font_size, which is in Default/font.py. As you mentioned, by default it erases the customized setting from your user preferences, which takes it back to the default given in the default settings. You can modify this behaviour as you see fit, which is one of the great things about Sublime.

For example, you can install PackageResourceViewer and OverrideAudit, and then follow these steps:

  1. Select PackageResourceViewer: Open Resource from the command palette
  2. Select Default
  3. Select font.py
  4. Replace the ResetFontSizeCommand code at the end of the file with the code below
  5. Save the file and close it
  6. Add a setting to your Preferences.sublime-settings named default_font_size and set it to the font size you want to use by default

Optionally you can replace the default font size of 12 in this code with a setting of your choosing; this sets what the font size gets set to when the new setting is not present.

class ResetFontSizeCommand(sublime_plugin.ApplicationCommand):
    def run(self):
        s = sublime.load_settings("Preferences.sublime-settings")
        default = s.get("default_font_size", 12)
        s.set("font_size", default)

        sublime.save_settings("Preferences.sublime-settings")

Now the menu command will replace the settings in your user preferences with your configured default. The install of OverrideAudit will warn you if future updates to Sublime make changes to the Default/font.py file that you modified, so that you can incorporate any new changes.

Note that this command will have no effect if you have a syntax specific setting for font size (e.g. make the font in html files smaller than other files), because in those cases the font size isn’t coming from the preferences. The potential complications of the interactions of various settings is probably one of the reasons this works the way it does by default.

2 Likes
#33

I use the plugin Revert Font Size to prevent this very thing.

0 Likes
#34

Hi, I seem to be able to consistently induce a crash in dev build 3139 whenever I have an open parenthesis followed (not necessarily immediately) by an ó character in the “Find” box (with regular expressions on). It happened when I typed “d(o|ó”, didn’t happen if I closed the parenthesis first before adding the ó in between, but then did happen if I subsequently typed another opening parenthesis at the start. I’m trying to work so I haven’t checked other non-ASCII characters, but either way, clearly some sort of regex bug here.

2 Likes
#35

Build output window doesn’t seem to scroll on output any more with 3139 on Sierra.

0 Likes
#36

I have that too. First thought it was on successful builds, but it doesn’t seem to auto-scroll at all anymore.

0 Likes
#37

Regards to IBus, it has serious issue from 1.5.
They had removed three methods, enable(), disable() and is_enable() in InputContext class.

This is the expected result. IBus won’t have the disabled mode. IBus switches xkb engines and input methods instead: https://live.gnome.org/GnomeShell/Design/Guidelines/SystemStatus/InputLanguage I think this way is similar with the current Mac OS and the Chrome OS.

https://code.google.com/archive/p/ibus/issues/1419

So almost Japanese users left IBus.

You can forget about IBus.
It is not Input Method anymore, it is just IME switcher now.

1 Like
#38

I appreciate the replies about the font_size being removed from the User Preferences. But it really shouldn’t require a custom plugin to stop bad application behaviour.

The User Preferences should be immutable to the application. Only changed by the User.

0 Likes
#39

The application SourceTree used to do unwelcome messing with my .gitconfig file and so I set it to read-only at the filesystem level.

0 Likes