Package Details: sublime-text-4 4.4169-1

Git Clone URL: (read-only, click to copy)
Package Base: sublime-text-4
Description: Sophisticated text editor for code, html and prose - stable build
Upstream URL:
Licenses: custom
Conflicts: sublime-text
Provides: sublime-text
Submitter: SunRed
Maintainer: SunRed
Last Packager: SunRed
Votes: 73
Popularity: 3.12
First Submitted: 2021-05-21 11:53 (UTC)
Last Updated: 2023-11-23 23:00 (UTC)

Latest Comments

1 2 3 4 Next › Last »

SunRed commented on 2023-11-07 13:47 (UTC)

@magicgoose At least for me I couldn't reproduce it so far, may it be in the wayland or X11 session and with GDK_BACKEND=wayland set or unset. Have you tried launching it with a new user, empty .config/sublime-text or empty cache (~/.cache/sublime-text or the entire ~/.cache directory)? Sometimes it's just a polluted user environment.

magicgoose commented on 2023-11-07 10:16 (UTC)

There was this problem with KDE for a while: after the desktop session is locked and unlocked, ST window is all broken: only a portion of it is rendered and it can't be interacted with any more, until I quit and re-launch ST. Has anyone else seen it?

SunRed commented on 2023-08-07 16:00 (UTC)

@yurikoles Thanks, I pointed this out myself in my message just before yours that it would have been better to just add this to the source field. Anyway, I added it now so people hopefully stop complaining due to their filled up caches. A pkgrel bump should not be necessary.

esh commented on 2023-08-07 11:04 (UTC)

Quick fix for Paru and Yay users: rm -fv ~/.cache/{yay,paru/clone}/sublime-text-4/sublime_text_build*.tar.xz

yurikoles commented on 2023-08-07 06:07 (UTC)

Guys, are you able to read or just write?

The problem is known, the solution is known, but some people keep posting their logs while thinking they invented the wheel.

putilatex commented on 2023-08-07 05:29 (UTC)

Hello, one problem this morning:

Building sublime-text-4... ==> Making package: sublime-text-4 4.4152-2 (Mon 07 Aug 2023 07:26:13 AM CEST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found sublime_text_build_4152_x64.tar.xz ==> Validating source_x86_64 files with sha512sums... sublime_text_build_4152_x64.tar.xz ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build sublime-text-4

yurikoles commented on 2023-08-05 14:05 (UTC)

To avoid situations like this, you may add $pkgrel to the local filename part, e.g., prepend "$pkgname-$pkgver-$pkgrel_x64.tar.xz:: before artifact URL, so each release of the package will have a unique filename.

SunRed commented on 2023-08-05 13:30 (UTC)

Oh sorry, I could've made use of the feature in the source field to rename the local file but this problem also usually does not occur.

sharun commented on 2023-08-05 03:45 (UTC)

for paru, I had to delete .cache/paru/clone/sublime-text-4 folder. it worked after that