sublimetext-io / docs.sublimetext.io Goto Github PK

Stumbled upon this cool yet undocumented feature yesterday:

• Create multiple selections
• ctrl + shift + p and enter "Arithmetic"
• enter an expression like:
  • 1+i to create numbers like 1,2,3,4,5,6,7,8,9,...
  • 30+(i%3) to create numbers like 30,31,32,30,31,32,33,...

The searchbar in the website isn't queriable via address URIs, so I can't add the docs as a search engine on my chromium browser.

Sure would be nice if I could. It's a basic feature most docs do support.

It should guide me to:

• a built-in command when I type the name of that command
• a global setting when I type the name of a setting

@Ultra-Instinct-05 has compiled a list of newly added context keys in SublimeText/PackageDev#315 that we would want to add to the documentation.

However, since the docs for ST4 are still not public, I'm not sure how to proceed with this information just yet, so I'm leaving this issue instead.

Steps to reproduce

1. In Firefox 104.0
2. Navigate to https://docs.sublimetext.io/guide/extensibility/completions.html#how-to-use-completions

Actual behavior:

Characters render incorrectly, leaving the reader confused.

Expected behavior:

1. The characters should display properly
2. When characters fail to display the content should still be readable

Completions can be inserted in two ways:

• Through the completions list. Note: the completions list can be activated by pressing control and spacebar (Ctrl ␣), or
• by pressing the foo key (f).

When working on the initial config.js, I had to restart the local dev server a lot because vuepress couldn't handle the config changes it appeared. I don.t think there is an immediate solution to that, but I wanted to track it as an issue for myself at least.

The vuepress devs have been working on vite and vitepress for a while, which is probably worth monitoring, as it follows the same principles but promises to work on exactly these pain points of vue.

What
Should we update the Google Analytics setup for this? Or should we remove it.

1. Do we care about how people are locating the website?
2. Do we want to track the amount of traffic that we are experiencing?

<script type="text/javascript">

  var _gaq = _gaq || [];
  _gaq.push(['_setAccount', 'UA-20962303-1']);
  _gaq.push(['_setDomainName', '.sublimetext.info']);
  _gaq.push(['_trackPageview']);

  (function() {
    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
  })();

</script>

Nice work on these docs. It looks like the save command is outdated. When looking in my console with sublime.log_commands(True), it has an additional argument:

command: save {"async": true}

Per the vuepress documentation, we should be able to add line highlights, but they don't seem to work (in #16 at least – not sure if there are used anywhere else).

References:

• https://vuepress.vuejs.org/guide/markdown.html#line-highlighting-in-code-blocks
• https://github.com/vuejs/vuepress/blob/master/packages/%40vuepress/markdown/lib/highlightLines.js

I have just installed Sublime Text 3 on Windows 10. After opening a folder, my simple mind cannot figure out the criteria used by ST3 to open new tabs for files: I am able to browse through my source code with the various goto anywhere, symbols, etc (fantastic), but I cannot open two tabs with two files.

Better said: I can.

• If I select a file f1 in a folder and a file f2 in another folder, the ST3 open two tabs, one per file.
• If I have one tab and modify the content, then I can open a new file.

But: how can I open, for example, three different tabs without modifying any of them? If I open a file in a folder and do not modify it, all the other files in the same folder are assigned to the same tab of the first file.

I looked for this information both on the official website and here, but could not find any info.

Please don't get upset if the question is too silly, but -really- I got exhausted trying to figure out the algorithm.

What
Mobile navigation on the default theme reflects green menu items.

I'm currently working on a custom syntax, and editing the tmPreferences. When defining increaseIndentPattern regex, it includes an open bracket {. I attempt to escape it with \ however sublime throws an error:

error loading meta info from Packages/User/goku.tmPreferences: Expected element key.

Even copy + paste from sublime docs into tmPreferences throws the error.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>name</key>
  <string>Goku Preferences</string>
  <key>scope</key>
  <string>source.goku</string>
  <key>settings</key>
  <dict>
      <key>increaseIndentPattern</key>
      <string>\:\w+\s?\{</string>
  </dict>
  <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>
       <dict>
        <key>name</key>
        <string>TM_COMMENT_DISABLE_INDENT</string>
        <key>value</key>
        <string>no</string>
      </dict>
    </array>
  </dict>
  <key>uuid</key>
  <string>4ce04eed-6bf9-43db-81c8-576fdcbe5dca</string>
</dict>
</plist>

There's a typo in the Description tab for Goto Anything Operators shortcuts. Maybe a escaping mistake on markdown.

https://docs.sublimetext.io/guide/usage/file-management/navigation.html#goto-anything-operators

The completions page doesn't mention any of the new fields added in ST4 to change how a completion is displayed, such as the annotation or kind.

https://docs.sublimetext.io/reference/completions.html#file-format
https://www.sublimetext.com/docs/completions.html#completion-files

Referring to file - https://github.com/sublimetext-io/docs.sublimetext.io/blob/master/docs/guide/extensibility/plugins/README.md

The first plugin section asks the reader to save the file as hello_world.py.
Names the class - ExampleCommand.
Runs the command - view.run_command('example')

How does sublime connect the string 'example' with the file hello_world.py and class ExampleCommand? Isn't clear how this mapping is happening. Can it be clarified? Thanks!

配置了 alt +d 然后无法覆盖默认的 { "keys": ["ctrl+shift+k"], "command": "run_macro_file", "args": {"file": "res://Packages/Default/Delete Line.sublime-macro"} }, 这个配置..

Default.sublime-commands

[
    { "caption": "Open Recent: Clear Recent Files", "command": "clear_recent_files" },
]

Default (Windows).sublime-keymap

{ "keys": ["ctrl+k", "ctrl+h"], "command": "clear_recent_files" },

There are a few important details regarding the interaction between auto_complete_selector and auto_complete_triggers. It would be good to have a section about this.

This had been raised in guillermooo/sublime-undocs#273.
@FichteFoll If you could give an example on how you would like to see this being documented, I can take a shot at completing it.

I keep forgetting what the differences are. And what the exact effects are. The ST3 docs are pretty much useless in this regard.

The API reference has been updated and uses a different format now.

1. Methods now have anchors that can be targetted directly.
2. Methods of base classes are now documented at that base clase instead of in every subclass.

Notably the Input Handlers guide has a couple links that needs to be updated.

It says __init__() got an unexpected keyword argument 'hide_phantoms_only'

https://docs.sublimetext.io/reference/commands.html#exec

Currently, the community docs lacks information on mousemap files (and the official docs also don't have any information on them).
I have made a small gist of whatever I know about them here :- https://gist.github.com/Ultra-Instinct-05/e1ca9a4d48641cc6c0af46fec0010611
May be this can be used as a starting point for some concrete information on mousemap files.

We used to have a grid of contributors on the landing page with their GitHub avatar & user name. After the latest dependency bump & build fixes (today), this list is now very much empty.

With the switch to vitepress, we lost the automatic glossary plugin and I haven't found a proper replacement yet. Since the tokens that used the glossary feature are still in the docs (searchable using :[\w_]+:), we ought to either replace them manually with direct links into the glossary or use a custom markdown-it plugin to replace these links with what we want.

https://docs.sublimetext.io/guide/extensibility/packages.html#merging-and-order-of-precedence

The :shipped_package:shipped_packages: syntax does not work in the current configuration.

Not sure where to put this in, but creating an issue so it isn't forgotten.

Following is the current state of internal scope to kind mapping (for symbols)

keyword:
    keyword
    storage.modifier
    storage.type
    keyword.declaration
    variable.language
    constant.language
type:
    entity.name.type
    entity.name.class
    entity.name.enum
    entity.name.trait
    entity.name.struct
    entity.name.impl
    entity.name.interface
    entity.name.union
  weak:
    support.type
    support.class
function:
    entity.name.function
    entity.name.method
    entity.name.macro
    meta.method entity.name.function
  weak:
    support.function
    meta.function-call variable.function
    meta.function-call support.function
    suport.method
    meta.method-call variable.function
namespace:
    entity.name.module
    entity.name.namespace
  weak:
    support.module
    support.namespace
navigation:
    entity.name.definition
    entity.name.label
    entity.name.section
markup:
    entity.other.attribute-name
    entity.name.tag
    meta.toc-list.id.html
variable:
    entity.name.constant
  weak:
    constant.other
    support.constant
    variable.other
    variable.parameter
    variable.other.member
    variable.other.readwrite.member

The weak inferences factor other things into the match, since those tend to be callsites instead of definitions

via Discord

https://docs.sublimetext.io/reference/commands.html#commands

There is a colon starting the first paragraph of command description.
Is this some formatting marker that went wrong, convention or just a bug?

It leads to a 404 page https://docs.sublimetext.io/github.com/sublimetext-io/docs.sublimetext.io/blob/master/docs/contributing.md

See sublimehq/sublime_text#105 (comment) for details.

the context is derived from the position of the mouse rather than the focused control but is otherwise identical.

The Key component uses various unicode symbols to represent the keys as they are commonly printed on keyboards for improved visualization. We should ensure that the glyphs we use are available to the client system by providing a font that includes them

See #19 and #64 for reports of this with ⭾.

With the switch to vitepress, we lost the ability to use the definition list syntax as it's also shown in the demo page. I tried explicitly importing and adding it to the config, but it had no effect.

See title.

Now, I have a problem. When writing java code, I need to introduce selenium related jars. I don't know how to introduce it into the project.

It's hard to find any info about built-in chain command. Would be useful to include it in the reference.

On my machine (Arch Linux), neither Chromium nor Vivaldi render bold text. The CSS selectors set font-weight: 500 (links) or 600 (string tags) respectively, but they are rendered like normal text. This also applies to headings such as h5, which is by the way even smaller than the normal text size and that really shouldn't happen.

The same problem also exists in the default vuepress theme, so it's likely an upstream issue, but I wanted to track it regardless until I find out which upstream repo I should take this to.