- python:
sublime.KIND_ID_AMBIGUOUS
, .sublime-completions:"ambiguous"
- python:
sublime.KIND_ID_KEYWORD
, .sublime-completions:"keyword"
- python:
sublime.KIND_ID_TYPE
, .sublime-completions:"type"
- python:
sublime.KIND_ID_FUNCTION
, .sublime-completions:"function"
- python:
sublime.KIND_ID_NAMESPACE
, .sublime-completions:"namespace"
- python:
sublime.KIND_ID_NAVIGATION
, .sublime-completions:"navigation"
- python:
sublime.KIND_ID_MARKUP
, .sublime-completions:"markup"
- python:
sublime.KIND_ID_VARIABLE
, .sublime-completions:"variable"
<?xml version="1.0" encoding="UTF-8"?> | |
<plist version="1.0"> | |
<dict> | |
<key>scope</key> | |
<string>text.html.markdown markup.heading - meta.whitespace.newline.markdown</string> | |
<key>settings</key> | |
<dict> | |
<key>showInSymbolList</key> | |
<integer>1</integer> | |
<key>symbolTransformation</key> |
import importlib | |
import os | |
__pkg_path = os.path.join( | |
os.path.dirname(os.path.dirname(os.path.dirname(__file__))), | |
'Packages', | |
'Package Control', | |
'package_control' | |
) | |
__file_path = os.path.join(__pkg_path, '__init__.py') |
import sublime, sublime_plugin | |
import re | |
import threading | |
# This is an example plugin that simulates a completion interaction with an | |
# LSP server, while correctly apply any edits that are received from the | |
# server. This is trickier than you'd expect, due to the async nature the | |
# server communication, the async auto complete system in Sublime Text, and | |
# the use of row+col offsets within the LSP protocol. |
This gist will no longer be updated as the changelog will be on the official website.
- Sublime Text/Merge Official Discord chat server: https://discord.gg/D43Pecu
- Sublime Text/Merge 中文 Telegram 交流群組: https://t.me/sublime_tw
Converted via https://domchristie.github.io/turndown
Continuing the post from: https://forum.sublimetext.com/t/how-to-replace-dots-with-slashes-when-using-file-regex/45764
I managed to do it as described on the first post. I just need to patch exec.py
to allow it to copy the new settings to the output view, and create these new settings on my project build:
My.sublime-project
{
"folders":
[
{ "path": ".", },
This work is released under a Creative Commons Attribution-NoDerivatives 4.0 International License.
"OpenPGP" refers to the OpenPGP protocol, in much the same way that HTML refers to the protocol that specifies how to write a web page. "GnuPG", "SequoiaPGP", "OpenPGP.js", and others are implementations of the OpenPGP protocol in the same way that Mozilla Firefox, Google Chromium, and Microsoft Edge refer to software packages that process HTML data.
[ | |
// VCS badges | |
{ | |
"class": "vcs_status_badge", | |
"parents": [{"class": "file_system_entry", "attributes": ["untracked"]}], | |
"layer0.texture": "Theme - Default/common/status_untracked.png", | |
"layer0.tint": "color(var(--yellowish) blend(rgb(255, 255, 255) 60%))", | |
"layer0.opacity": 1.0, | |
"content_margin": 6 | |
}, |
#!/bin/bash | |
# A wrapper script to make sublime_merge work more nicely | |
# when used as a git-mergetool | |
WORKDIR=`git rev-parse --show-toplevel` | |
REAL_HOME="$HOME/" | |
# Replace a leading homedir with ~/ to match the window title | |
REAL_WORKDIR=${WORKDIR/"^$REAL_HOME"/"~/"} | |
sublime_merge $REAL_WORKDIR |
#!/bin/bash | |
CLEAR='\033[0m' | |
RED='\033[0;31m' | |
function usage() { | |
if [ -n "$1" ]; then | |
echo -e "${RED}👉 $1${CLEAR}\n"; | |
fi | |
echo "Usage: $0 [-n number-of-people] [-s section-id] [-c cache-file]" |