As mentioned above, users who purchased v1 after will have already received a free upgrade. This is regardless of when the SFTP v1 license was purchased. The price for upgrading a license is $15. This has been extended to cover anyone who purchased a license after the release of Sublime Text 4.
Sublime text license no longer valid upgrade#
The license policy normally only provides a free upgrade to v2 for users who purchased a license in the year before release. Before may be upgraded from v1 to v2 for $15įAQ Who will need to purchase an upgrade license?Īll users who purchased a license before will need to purchase an upgrade license for the SFTP package.Since the release of Sublime Text 4 on have been automatically upgraded - see My Account.Since Maare already valid v2 license keys.Sublime is my main/favourite editor and I use both 2 and 3 verisons at the same time (3 is a lot faster than 2).Sign in to see details on your licenses Eligible Licenses It changes size to minimal possible and I can't catch it (there are only sublime icon + window's icons) Then I can't drag the window to second display.
Also there are some problems when opened many tabs (6-7 windows, 100+ tabs). Make actions (usually with 'Filter Lines' plugin, etc). Sublime took about 40 seconds, N++ about 10 seconds.Ħ. Tried to find another record (placed almost of the end of the file). Tried to find '2019', and it took less than a second in N++. Notepad++ opens it about 8-9 seconds, Sublime opens it about 29-30 seconds. Would be better if it instantly find first record and then 'in background' search all other records.Īnother example. So, just to find first '2019' took about 140 seconds. I pressed Ctrl+F and it showed search panel in 26 seconds. Any old editor (without such highlighting) works faster. As I understand, it's because Sublime tries to find and highlight all same sequences. So, just to open file and find first required record (like ', 08:05:') may take 5 minutes (and again, it depends). After it, Sublime may become frozen for (just for example, it depends) 40 seconds. For example, I pressed Ctrl+F and entered first char. If I open 3-10 GB file (log) and then try to find something, it's almost unusable. All the corner cases we're aware of where it does become slow are algorithmic problems where a change in language really wouldn't help :) > I know you're just taking a fun jab but from personal experience its behaved pretty well with multi-GB files. On Thursday, 28 February 2019 at 06:54:32 UTC, Benjamin Schaaf wrote:
Though I'd love to, we don't use D internally for anything.
If you don't have a license you can still use the new syntax highlighting before the next stable build by cloning the repository and symlinking the `D` folder into your Sublime Text "Packages" directory (Details in the README).įull disclosure: I work for Sublime HQ. If you do find a bug with the syntax highlighting or just something that could be done better please leave a bug report on the repository, I'll be maintaining it for the foreseeable future: You can find the pr here: / sublimehq/ Packages/ pull/1850 * Arguments are highlighted as actual arguments * Automatic indentation is no longer broken (Typing `} catch.` would re-indent the line) * Attributes, including UDAs, are highlighted properly * Token strings actually highlight tokens now * Strings are now properly highlighted, including postfixes and delimited strings * `.` no longer highlights as a floating point * Function/Template calls are properly marked, making GoTo Reference work properly * Functions, classes, interfaces, enums, structs, unions, templates and aliases are now properly indexed, making GoTo Definition work properly Here's a very incomplete list of everything that's been fixed/improved: This has since been deployed in the most recent development version 3192 (license required) and will be shipping with the next stable.Īnyone trying Sublime Text has probably noticed the poor D support. I've recently gotten a massive rewrite of the D syntax highlighting merged into the Sublime Text default packages.
0 kommentar(er)
