Sublime Forum

API Suggestions

#159

##Add --{installed-}packages-path command line option to subl

Importance: Medium

Motivation: Lots of plugin installation instructions (the “non Package Control way”) tell the user to “go to their packages folder”, sometimes supplying the full paths for Linux, macOS, Windows. This is pointless as this can just as well be provided by Sublime itself in the form a simple command line option. If Sublime provides it as a command-line option, every plugin author can just write something along the lines of:

If you want to install my package manually, run

$ cd `subl --packages-path`

and then

$ git clone https://github.com/author/package

Proposed solution #1:

Calling

$ subl --packages-path

will print the full path to Sublime’s packages folder. Calling

$ subl --installed-packages-path

will print the full path to Sublime’s installed packages folder.

2 Likes
#160

Way faster IMO

alias st="cd '$APPDATA/Sublime Text 3/Packages'"
0 Likes
#161

Doesn’t that only work on osx?

0 Likes
#162

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

0 Likes
#163

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

0 Likes
#164

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.
.

7 Likes
#165

Originally posted on:

  1. #25346 Combine Windows?

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

  1. 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() )
0 Likes
#166

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.

1 Like
#167

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:

0 Likes
#168

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

0 Likes
#169

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

0 Likes
#170

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

0 Likes
#171

Glad to see another XEDITer here :slight_smile:

0 Likes
#172

##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()

0 Likes
#173
More sorting methods
Importance: Minor

1 Like
#174

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.

image.png778×254 24.1 KB

2 Likes
#175

Okay Thanks.

0 Likes
#176

This is pretty much implemented now.

0 Likes
split this topic #178

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

0 Likes
#181

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': '/*'}
]
1 Like