Package Details: lagrange 1.17.6-1

Git Clone URL: (read-only, click to copy)
Package Base: lagrange
Description: Beautiful Gemini Client
Upstream URL:
Licenses: BSD
Submitter: Roshless
Maintainer: Roshless
Last Packager: Roshless
Votes: 37
Popularity: 0.098835
First Submitted: 2020-10-10 19:45 (UTC)
Last Updated: 2024-01-16 13:31 (UTC)

Pinned Comments

Roshless commented on 2020-11-04 08:20 (UTC) (edited on 2022-08-23 13:45 (UTC) by Roshless)

Instead of flagging this package out of date please send patches to repo using mailing list linked in


Latest Comments

1 2 3 4 5 6 7 Next › Last »

yochananmarqos commented on 2023-04-28 20:54 (UTC)

@Roshless: Since the maintainer likes to belittle anyone commenting here and project, I'll just post my improved PKGBUILD.

Roshless commented on 2023-01-25 21:31 (UTC)

@yochananmarqos people like you are the single biggest reason there is always maintainer shortage.

What account? Did you really bother to type all this text into aur before checking what mailing list really is? You only need mail account and git installed- that's the point, no need for account on gitlab/sourcehut

Flagging package out of date is not contribution, sending a patch with updated version is. Yes I have rss feeds, but there is this thing called real life that can take some time off my non-paid time keeping packages up to date.

I don't need your high horse spiel about out of date flag purpose and aur helpers- I know, Ive been around for ~10y on this site.

Instead of being all smart in your comment, maybe next time send a patch? If you know what you are doing, it takes comparable amount of time to flagging package out of date and copy pasting link to release.

On topic: libunistring is required- it's specified multiple times in README and cmakelist. if pcre is fine I don't see the reason to change it.

yochananmarqos commented on 2023-01-25 17:21 (UTC)

This is missing the libwebp dependency. I'm not sure that libunistring is required.

It looks for pcre first and if it can't find it then it looks for pcre2. I would change the dependency to the latter.

yochananmarqos commented on 2023-01-25 00:12 (UTC)

@Roshless: No, I won't create an account for a random mailing list. Yes, I will flag the package out of date.

That being said, nothing wrong with inviting community contribution via whatever method works best for you. I'm a package maintainer and don't always catch everything. I do appreciate it when a user lets me know I missed something so I can correct it.

Either way, package maintainers should already be signed up for release notifications from upstream to be notified of new versions. Flagging a package out of date both serves the purpose of letting the Maintainer know when a package is out of date and also let's users know one of their packages are out of date (with an AUR helper that has the feature).

TrialnError commented on 2022-06-08 11:52 (UTC)

It isn't entirely impossible to have different build steps for split packages. In such cases the source directory will be duplicated.
One example for such a split package is doublecmd from the repos.
I may take a look at this. Depends if I'm getting to my system, don't forget it etc :D

m040601 commented on 2022-05-29 15:36 (UTC) (edited on 2022-05-29 16:16 (UTC) by m040601)

... and tried creating separate package for clagrange,...
....  now I'm even wondering how it's building ...

I must also add that the Lagrange developer is very receptive and willing to help and troubleshoot any issues attempting this.

Although he doesnt like github, he mirrors Lagrange there. And responds to issues there.

I had opened an issue regarding "clagrange" and "lagrange-bin" previously,

Might be usefull for future AUR maintainers.

... I'm planning to make a binary TUI release, too, but I want to polish it still a bit more....

Regarding the "AppImage" and "Flatpaks" binaries he releases:

    On Archlinux it fails with "segmentation fault". ... meant to be used only on Ubuntu right ? ...

... It's not Ubuntu-specific, however AppImages are not fully self-contained so it's not universal either


    wanted to install some man page in root "/", like "/lagrange/resources.lgr" and "/man/lagrange". Probably needs some adjustment.

Oops, let me fix that...

Roshless commented on 2022-05-28 17:28 (UTC)

Hey @m040601,

Wow, didn't know lagrange had cli version. I gave it a go and tried creating separate package for clagrange, since split packages can't have different build steps. Unfortunately I failed, can't get CMake to work, now I'm even wondering how it's building the_Fundation by itself in this package and why sealcurses can't get the same treatment.

I have to admit I'm not using lagrange very much these days, so I don't plan to spend much more time on researching CMake magic, if anyone is up for the task feel free to create clagrange package! :)

m040601 commented on 2022-05-26 07:25 (UTC) (edited on 2022-05-26 07:36 (UTC) by m040601)

First of all thank you for maintaining this PKGBUILD for this extraordinary piece of software.

And a small request.

As you can see at,

Compiling the TUI version

Lagrange has an optional text-mode interface that enables running the app in the terminal.
 This is disabled by the default build settings. Setting the ENABLE_TUI option to YES 
will replace the SDL dependency with a library called SEALCurses 
that implements the required parts of the SDL API on top of Curses. The resulting executable is called clagrange.

The requirements for building the TUI version are the same as with the GUI, 
except ncurses is required instead of SDL. HarfBuzz 
and all the image and audio dependencies are excluded from the TUI build.


Build options
ENABLE_TUI  Build the TUI version (clagrange). The SEALCurses library is required: it is used instead of SDL.

It's not a different repo or project. It's the same source code as for the GUI version, that this "lagrange" PKGBUILD already fetches.

I'm very limited in understanding "cmake", "make", editing flags etc. But I desperately wanted to test this TUI version. So I just went ahead, git cloned, and just used the,

.... The helper script is provided for building the TUI version. ....

It compiled OK, but wanted to install some man page in root "/", like "/lagrange/resources.lgr" and "/man/lagrange". Probably needs some adjustment.

Anyway. In the end you get an executable "clagrange".

Wow !!! What a nice piece of software for all the command line users lovers. It works with keyboard hints, key "f", for clicking the links. Just like Qutebrowser and Firefox Tridactyl etc. A must have for all keyboard fanatics. Really, really, snappy, performant and smooth experience. I think it even has some kind of acceleration. I havent seen another polished piece of terminal browser CLI software being developed lately.

I am not an expert in PKGBUILD's so my request would be:

  • Could you also build the "clagrange" from this same PKGBUILD ?
  • Or alternative provide a different/complementary PKGBUILD "clagrange" ? (That of course doesnt "clash" with the GUI Lagrange)

Thanks in advance.

Roshless commented on 2022-02-14 17:09 (UTC)

@dpirate Hi, according to this commit it should be autodetected. If it's not detected, you should probably report this on

dpirate commented on 2022-02-14 05:37 (UTC)

Please consider adding -DTFDN_ENABLE_SSE41=OFF so this package doesn't SIGILL on AMD x86_64 CPUs older than Bulldozer.