Different truncation behavior for "base suffix" completion in sublime-syntax

Open
#322 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Locate the completion helper for sublime-syntax files in the Python code and inspect how the base suffix is extracted from scope names. Reproduce the behavior with a scope such as text.git.config, then verify that completion offers git.config rather than only config.

Written by the indexing model from the issue text.

Description

enhancement for later consideration

This is about the completion helper when editing sublime-syntax files. There's one completion for "base suffix" that I believe is derived from the base scope (e.g. text.plain you get plain as a completion). I believe it's taking a substring of the last . to the end of the scope name.

What I would like it to do is take a substring from the first . to the end of the scope name. If I'm editing text.git.config, I want the "base suffix" completion to offer git.config, not config.

Dominant language
Python
Stars
455
Forks
86
Avg merge
7d 10h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SublimeText/PackageDev

All issues in SublimeText/PackageDev

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.