I just had a huge conflict I needed to resolve when rebasing a feature branch after the main branch received large scale reformatting.

Unfortunately I can only choose to resolve the whole file using ours/theirs but not individual conflicts, which now makes me wade through the conflicts in my editor (Sublime of course).

It would be helpful to have conflict-level options (like hunk-based when staging regular commits) there.

Highlight match_selection not only one word but multiply words too (with spaces beetwin words).

It would be great if Sublime Text can be deployed over a web browser. Although not that well known (yet), VSCode can be deployed on a server and be accessed completely over a web browser, which will make it that much more flexible to use across any platform.

To give some context... I've switched from developing on Windows, to a Mac, to now ChromeOS with a lot of the dev applications deployed from a server and accessed over a web browser. It keeps the local system light and battery-friendly, while still getting the high-performance I need. A lot of this is driven by VSCode being able to be deployed on a web browser with complete access to the terminal. I can still run Sublime Text on Crostini, and I still love Sublime Text, but sadly VSCode beats Sublime Text on usage as it can be deployed on a server and used over a web browser.

Is there a way to map force quit for the default close of the application? I am looking for a way to be able to close the app in one click with automatically save of all opened documents, and have those documents reopened next time I opened the app.

These used to show up in Sublime as just a vertical red line, now they display as <0x200c> highlighted in red so the Indian, Khmer and Farsi files I work on are full of them and I'd like very much to find the setting or what ever changed with an update that caused this change. I realize it's probably just a setting but I'm just a casual user, not a coder, so any help appreciated, thanks.

Try in markdown in any indented text, eg
```
asdf {}|
```
Try shift-tab cursor at the eol - it creates untrimmed space, as if doing unindent, but also Tab at the same time.
Regression?

It's not possible to search text in the output window. You can copy it and paste it in a new window, but that's of limited use when the output is still being produced. A more useful alternative would be to have an option to filter lines, This would be useful, for example, to see if a certain message has been produced, or if a certain file has been processed.

The docs state

// By default, auto complete will commit the current completion on enter.
// This setting can be used to make it complete on tab instead.
// Completing on tab is generally a superior option, as it removes
// ambiguity between committing the completion and inserting a newline.

If completing on tab is recognised to be "generally a superior option", which I couldn't agree more strongly with, why is the default enter? The autocomplete is an awesome and very powerful feature, however it does seem a little over enthusiastic and I had to google around to find out how to stop random things appearing at the ends of my lines - I'm sure other people will be doing the same.