Sublime Forum

**math2001** · March 10, 2017, 11:10pm

Way faster IMO

alias st="cd '$APPDATA/Sublime Text 3/Packages'"

**rwols** · March 10, 2017, 11:12pm

Doesn’t that only work on osx?

**math2001** · March 10, 2017, 11:47pm

I’m on Windows using bash from git-for-windows

**rwols** · March 11, 2017, 12:13am

Yeah, I got confused . Anyway, it’s platform dependent is my point. So Sublime should make this issue platform-independent by providing a --packages-path argument.

**ihodev** · March 26, 2017, 8:08am

Add restart command

In some cases it’s really necessary to restart Sublime Text to get plugin to work correctly.

It would be great to have the chance to ask the user to restart ST and run this command if he/she doesn’t mind.
.

**addons_zz** · July 1, 2017, 5:21pm

Originally posted on:

#25346 Combine Windows?

I opened a feature request to allow this on the Core issue tracker:

Core$1794 API to set/change/move views between different windows

After that API addition, you can create the following package/plugin to create the command gather_all_windows_here

import sublime
import sublime_plugin


class GatherAllWindowsHereCommand( sublime_plugin.TextCommand ):

    def run( self, edit ):
        windows        = sublime.windows()
        current_window = sublime.active_window()
        windows.remove( current_window )

        for window in windows:

                for view in window.views()
                    current_window.attach_view( view.id() )

**idleberg** · March 24, 2018, 7:59pm

on_pre_build / on_post_build

This would, for instance, allow running eligibility test before a build starts. One of the most frequent support requests for my packages is about compilers not being in the user’s PATH. An example for on_post_build would be asking the user whether he wants to open a successfully transpiled document in the editor.

**acheronfail** · August 5, 2018, 4:21am

I just read this whole thread and couldn’t find this suggestion, but it’s a large thread so forgive me if I missed it.

Find Previous Command

This would simply add the API to be able to find the previous occurrence of a pattern.
I would suggest adding it as a flag to the already existing API. Something like sublime.REVERSE or similar.

This feature has been requested before:

GitHub issue: https://github.com/SublimeTextIssues/Core/issues/245
Forum Thread: Find the previous occurence of a regex pattern

**avoid** · August 26, 2018, 6:55pm

Way to update the Quick Panel items

I want to perform some work in background and update quick panel list items along the way
Right now I can only take user input, make full list and show it

**slifin** · November 1, 2018, 9:59am

Minihtml is being used to create the interface for debuggers, see: https://github.com/daveleroy/sublime_db
is it possible to get some relative CSS units? So these interfaces can resize when sublime’s window resizes

**Acecool** · November 6, 2018, 5:52am

This would be useful. I already have to replace some of mine with ${x} just so it can be replaced properly later.

**ccw** · February 12, 2019, 1:11am

Glad to see another XEDITer here

**ccw** · February 12, 2019, 3:00pm

##Request to document Fold status of a region and list of folded regions
Importance: medium
Motivation: Being able to detect if a region is folded or not would allow selective processing.

Proposed solution:

Document the two view module functions view.is_folded(region) and view.folded_regions()

**ouweiya** · February 12, 2019, 2:32am

More sorting methods

Importance: Minor

**OdatNurd** · February 12, 2019, 2:26am

API functions to do that already exist, although they’re not currently officially documented (with all of the usual warnings that sort of thing entails). As such the request might better be made to promote them to being official.

**ccw** · February 12, 2019, 2:58pm

Okay Thanks.

**rwols** · April 14, 2019, 10:40am

This is pretty much implemented now.

**jbrooksuk** · May 29, 2019, 7:48am

3 posts were split to a new topic: What’s the meaning of using a position when calling view.meta_info?

**OdatNurd** · May 26, 2019, 10:03pm

Create a new tab, use Set Syntax: C, then open the console and enter view.meta_info("shellVariables", 0). The result is the C shellVariables, which gives you the comment characters for that language:

[
{'name': 'TM_COMMENT_END_2', 'value': '*/'}, 
{'name': 'TM_COMMENT_START', 'value': '// '}, 
{'name': 'TM_COMMENT_START_2', 'value': '/*'}
]

Now use Set Syntax: Python and re-run the command in the console, and it returns the Python shellVariables instead:

[
{'name': 'TM_COMMENT_START', 'value': '# '}, 
{'name': 'TM_LINE_TERMINATOR', 'value': ':'}
]

For bonus points, use Set Syntax: HTML and paste this:

<script type="text/javascript"> var x=12; </script>

When you run it with a position of 0, you get the HTML variables, because that’s the syntax at that position:

[ 
{'name': 'TM_COMMENT_END', 'value': ' -->'}, 
{'name': 'TM_COMMENT_START', 'value': '<!-- '}
]

Position 32 is inside the JavaScript portion of the buffer, so provifing that position gives you JavaScript information instead:

[
{'name': 'TM_COMMENT_END_2', 'value': '*/'}, 
{'name': 'TM_COMMENT_START', 'value': '// '}, 
{'name': 'TM_COMMENT_START_2', 'value': '/*'}
]

**BPL** · May 27, 2019, 8:57am

Thank you very much, your last example really helps to understand the thing a little bit better! So as I can see, basically meta_info is using the scope name to figure out what content from the tmPreferences to use, for instance, if we consider:

HTML\Comments.tmPreferences:

<?xml version="1.0" encoding="UTF-8"?>
<plist version="1.0">
<dict>
    <key>name</key>
    <string>Comments</string>
    <key>scope</key>
    <string>text.html</string>
    <key>settings</key>
    <dict>
        <key>shellVariables</key>
        <array>
            <dict>
                <key>name</key>
                <string>TM_COMMENT_START</string>
                <key>value</key>
                <string><![CDATA[<!-- ]]></string>
            </dict>
            <dict>
                <key>name</key>
                <string>TM_COMMENT_END</string>
                <key>value</key>
                <string><![CDATA[ -->]]></string>
            </dict>
        </array>
    </dict>
</dict>
</plist>

Javascript\Comments.tmPreferences:

<?xml version="1.0" encoding="UTF-8"?>
<plist version="1.0">
<dict>
    <key>name</key>
    <string>Comments</string>
    <key>scope</key>
    <string>source.js, source.json</string>
    <key>settings</key>
    <dict>
        <key>shellVariables</key>
        <array>
            <dict>
                <key>name</key>
                <string>TM_COMMENT_START</string>
                <key>value</key>
                <string>// </string>
            </dict>
            <dict>
                <key>name</key>
                <string>TM_COMMENT_START_2</string>
                <key>value</key>
                <string>/*</string>
            </dict>
            <dict>
                <key>name</key>
                <string>TM_COMMENT_END_2</string>
                <key>value</key>
                <string>*/</string>
            </dict>
        </array>
    </dict>
</dict>
</plist>

In your example at position 32 you’ll get 'text.html.basic source.js.embedded.html source.js storage.type.js ' as scope_name, source.js appears there and that’s why it’s using the javascript shellVariables fragment.

Now, here’s another question, in a language like c++, would it be possible to have scope_names different than the ones living in C++\Comments (C++).tmPreferences (<string>source.c, source.c++, source.objc, source.objc++</string>)?

API Suggestions

Add restart command

Find Previous Command

More sorting methods

Importance: Minor