Package Details: lite 1.11-2

Git Clone URL: (read-only, click to copy)
Package Base: lite
Description: A lightweight text editor written in Lua
Upstream URL:
Licenses: MIT
Submitter: alerque
Maintainer: alerque
Last Packager: alerque
Votes: 4
Popularity: 0.000000
First Submitted: 2020-05-31 19:25 (UTC)
Last Updated: 2024-03-28 00:01 (UTC)

Dependencies (1)

Required by (0)

Sources (2)

Latest Comments

webreflection commented on 2021-04-30 07:43 (UTC)

anyone with an idea regarding HiDPi screens? I'd love to have it 200%, otherwise I can't really use it. Thanks in advance for any kind of pointer.

Terence commented on 2020-11-29 21:54 (UTC) (edited on 2020-11-29 21:54 (UTC) by Terence)

For those interested I created a new aur package : which is a fork of lite. It aims to be more user friendly, improve the quality of the font rendering and reduce CPU usage.

More info:

The package includes the .desktop. I will also add the plugin @properlypurple mentions.

DISCLAIMER: I'm not the fork author, just packaging it.

Terence commented on 2020-11-29 12:51 (UTC) (edited on 2020-11-30 11:01 (UTC) by Terence)

Hey I modified the package to also install a .desktop file using 6r1d SVG icon:

EDIT: don't forget to add "gendesk" to the makdepends.

diff --git a/PKGBUILD b/PKGBUILD
index 98cdd97..14e6658 100644
@@ -9,15 +9,27 @@ url="$pkgname"
-        "$pkgname-path-fix.patch")
+        "$pkgname-path-fix.patch"
+   # credits to 6r1d for the svg icon
+   "")
-            'a874de709bf2201816f96807aa50f6b1a15a19aa7989084f01422dd5fe488055')
+            'a874de709bf2201816f96807aa50f6b1a15a19aa7989084f01422dd5fe488055'
+            '504d2ccd74f1c5b631b5b83a4f4319c74edb705fc383b3058f4b2d9354093b53')

 prepare() {
     cd "$pkgname-$pkgver"
     patch -p1 < "$srcdir/$pkgname-path-fix.patch"
     sed -i -e '/^cflags=/s/"/"$CFLAGS /' \
            -e '/^lflags=/s/"/"$LDFLAGS /'
+  # XDG desktop file
+  gendesk -n -f \
+          --pkgname "$pkgname" \
+          --pkgdesc "$pkgdesc" \
+          --name Lite \
+          --categories "Utility;TextEditor;Development" \
+          --mimetype "text/plain"

 build() {
@@ -30,5 +42,8 @@ package() {
     install -Dm755 -t "$pkgdir/usr/bin/" $pkgname
     install -d "$pkgdir/usr/share/$pkgname"
     cp -a data/* "$pkgdir/usr/share/$pkgname/"
+    install -Dm 644 "../${pkgname}.svg" -t \
+   "${pkgdir}/usr/share/icons/hicolor/scalable/apps"
+    install -Dm 644 "${pkgname}.desktop" -t "${pkgdir}/usr/share/applications"
     install -Dm644 -t "$pkgdir/usr/share/licenses/$pkgname/" LICENSE

properlypurple commented on 2020-11-26 10:15 (UTC) (edited on 2020-11-26 10:15 (UTC) by properlypurple)

It would be great to package this additional plugin so we could put our plugins and such in $HOME

alerque commented on 2020-08-11 08:08 (UTC) (edited on 2020-08-11 10:56 (UTC) by alerque)

@yochananmarqos All valid points, and now fixed — thank you. While originally working on the packaging I kind of got distracted trying to convince upstream to actually fix some of their weird build and install issues, but that hasn't happened yet.

yochananmarqos commented on 2020-08-10 23:47 (UTC)

@caleb: This depends on sdl2 according to namcap.

It doesn't seem to qualify as an 'any' package and isn't using the system LDFLAGS:

lite E: ELF file ('usr/bin/lite') found in an 'any' package.
lite W: ELF file ('usr/bin/lite') lacks FULL RELRO, check LDFLAGS.

You forgot the license.

RaxIxor commented on 2020-06-04 20:42 (UTC)

@caleb Ah, alright. We'll just have to hope and see, then. Thanks, and good luck to you.

alerque commented on 2020-06-04 14:22 (UTC)

@Raxlxor There isn't an easy/obvious way. The upstream project is deliberately keeping this difficult to install as a system package and pushing hard for per-user home directory "installations". See issue here. I think right now you'd either have to build the plugin as a package itself and add it to /usr/share/lite/plugins or symlink that system folder to your user or some other shared location. There is probably a one-line fix that could add a $HOME relative path to the plugin search, but it would have to be a patch we applied unless ou can convince the upstream project to co-operate.

RaxIxor commented on 2020-06-04 12:10 (UTC)

How would we go about using plugins and w/e?