Package Details: sublime-text-dev 4.4173-2

Git Clone URL: https://aur.archlinux.org/sublime-text-dev.git (read-only, click to copy)
Package Base: sublime-text-dev
Description: Sophisticated text editor for code, html and prose - dev build
Upstream URL: https://www.sublimetext.com/dev
Licenses: custom
Conflicts: sublime-text
Provides: sublime-text
Submitter: realitygaps
Maintainer: SunRed (edub4rt)
Last Packager: SunRed
Votes: 516
Popularity: 0.000018
First Submitted: 2011-11-10 18:32 (UTC)
Last Updated: 2024-04-08 21:00 (UTC)

Pinned Comments

SunRed commented on 2022-02-20 11:30 (UTC)

Please note that the dev branch of this software requires a license to be purchased from the website. If you want to support this software, please consider doing so.

You can use the stable branch available at sublime-text-4 or the official package for free.

SunRed commented on 2021-05-21 13:04 (UTC)

To cut down the amount of packages to be maintained and to decrease confusion, this package is now used for the 'dev' branch of Sublime Text that is kept up to date with the most recent version. Users who want to stay on the latest legacy versions or the most recent stable release should stick to the respective stable release packages (sublime-text-3, sublime-text-4) or use the official repos provided by Sublime Text.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 22 Next › Last »

<deleted-account> commented on 2016-04-29 16:35 (UTC)

Are there any plugins to support pkgbuild syntax highlighting?

sender commented on 2016-04-18 22:15 (UTC) (edited on 2016-04-18 22:17 (UTC) by sender)

@Rodori I agree with what @Marcel_K wrote. This package is meant to be installed side-by-side with ST2. You can fix your situation permanently in several ways on your own system.

Marcel_K commented on 2016-04-18 16:29 (UTC)

Technically, that's possible, but you shouldn't install files during post_install, as those are not tracked by pacman. What's more difficult, is that it is allowed to install ST2 after you installed ST3, which either isn't possible then, because of the symlink, or it will simply overwrite the symlink, which is not what you want: when uninstalling ST3, post_remove will delete `subl`, assuming it still is the symlink created during post_install. This seems like an edge case, but it really is undesired behaviour.

Rodori commented on 2016-04-18 13:56 (UTC)

Please, could you include a function to check whether you have Sublime Text 2 installed or not and create a symlink from `subl` to `subl3` if possible? It's because I always have to do it manually, and I have aliases pointing to "subl" instead of "subl3". I don't know if there's any way to specify that during the `makepkg` process though. Thank you in advance.

sender commented on 2016-04-17 12:26 (UTC)

@nmstoker It's a very unfortunate situation. No idea on the timing. You can raise this issue upstream. BTW nothing wrong with moving to the -nightly ;)

nmstoker commented on 2016-04-16 20:41 (UTC)

Hi @sender - any idea on the timing that Beta might move to build 3109 (or above)? The SSL error is causing me a few issues, but I suspect I probably shouldn't just switch to Dev (-nightly) especially if it's coming any time soon.

gadicc commented on 2016-03-30 16:36 (UTC)

thanks @sender! and for your ongoing maintenance of this package.

sender commented on 2016-03-30 15:35 (UTC)

@gadicc and others: the ssl-linux issue has been resolved in ST3 build 3109 (available via the nightly channel: https://aur.archlinux.org/packages/sublime-text-nightly). Thanks Esgariot.

gadicc commented on 2016-03-12 07:11 (UTC)

For me, some plugins (that depend on SSL) stopped working on updating from openssl 1.0.2.f-1 -> 1.0.2.g-3. No error messages outside the console, but there I found messages about being unable to import _ssl, and upon manually adding the "Linux SSL" package (in sublime), errors about OPENSSL_1.0.0 not being defined in libssl1.0.0. The quick fix was to downgrade with `pacman -U /var/cache/pacman/pkg/openssl-1.0.2.f-1-x86_64.pkg.tar.xz`, reload sublime, and everything worked again. Since this was a minor update, I imagine existing libraries should still work? Maybe someone who understands OpenSSL better can open an appropriate bug report, if relevant.

sender commented on 2016-02-17 08:37 (UTC)

There seems to be a lot of confusion about the ST packages. This is because the author switched names for branches. Packages: Sublime Text 3 Beta - package: sublime-text-dev - Upstream: www.sublimetext.com/3 Sublime Text 3 Dev (used to be called nightly) - package: sublime-text-nightly - upstream: www.sublimetext.com/3dev - NOTE: for registered users only If you want the absolute latest get *sublime-text-nightly*. Note that you have to be licensed to use this!

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 22 Next › Last »