Package Details: cursor-electron 0.50.5-4

Git Clone URL: https://aur.archlinux.org/cursor-electron.git (read-only, click to copy)
Package Base: cursor-electron
Description: AI Code Editor (system-wide electron)
Upstream URL: https://www.cursor.com
Licenses: LicenseRef-Cursor
Conflicts: cursor, cursor-bin
Provides: cursor, cursor-bin
Submitter: vitaliikuzhdin
Maintainer: oech3 (Oops)
Last Packager: oech3
Votes: 0
Popularity: 0.000000
First Submitted: 2025-03-08 15:13 (UTC)
Last Updated: 2025-05-20 16:46 (UTC)

Pinned Comments

oech3 commented on 2025-05-01 19:50 (UTC) (edited on 2025-05-20 17:02 (UTC) by oech3)

This supports ~/.config/electron-flags.conf. Other files are unsuppoted (you may find something at /usr/bin/cursor). -electron-latest might work better on wayland. Other ver (e.g. -electron35) will be added after requested.

Latest Comments

1 2 3 Next › Last »

oech3 commented on 2025-05-20 16:51 (UTC)

An workaround for --printsrcinfo broke build. Try again.

Oh no. Web interface hides electron* dependency now...

maru commented on 2025-05-20 16:09 (UTC)

==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Starting package_cursor-electron()... ==> ERROR: A failure occurred in package_cursor-electron(). Aborting... error: failed to build 'cursor-electron-0.50.5-3 (cursor-electron-latest)': error: packages failed to build: cursor-electron-0.50.5-3 (cursor-electron-latest)

I was able to manually run the functions, until package_cursor-electron-latest ran w/ root privileges, at which point I had to manually copy the usr/lib and usr/share directories because only bin was copied

oech3 commented on 2025-05-16 16:51 (UTC)

@Oops I completely missed/failed what should I merge to what. I should leave vanilla extracted cursor with flags. (The best layout may an PKGBUILD generates every pkg by an active user, or official support for system-wide electron with flags which will not happen.)

oech3 commented on 2025-05-16 09:38 (UTC) (edited on 2025-05-16 12:35 (UTC) by oech3)

@Oops What is ime issue? I symlink chromium-flags.conf to electron-flags.conf with --enable-wayland-ime --wayland-text-input-version=3 and no issue.

Including such flags at here enforces wrong wayland-text-input protocol.

Oops commented on 2025-05-16 09:32 (UTC)

@oech3 OK, I’m happy to be a co-maintainer and would dig into the wayland-ime issue.

oech3 commented on 2025-05-15 16:47 (UTC) (edited on 2025-05-15 16:47 (UTC) by oech3)

This is just my prefer. I don't want to statically include such logic of launcher. I know *-flags.conf is Arch's rule instead of upstream's one.

vitaliikuzhdin commented on 2025-05-15 16:43 (UTC)

Nvchecker is not relevant here. I meant that earlier, you wanted to source the launcher from extra/code without a tag, with the benefit being that we’d get alerted when the hash changes. But now you want to source it from extra/code with a tag, so there’s no such benefit, and also not much purpose (the file is already in the local repo). I don’t really see the point, but it’s possible, sure.

We don’t need to or have to specify the source of the launcher, but one option (if you want to) is to just leave a comment.

1 2 3 Next › Last »