Package Details: liquidprompt 2.2.0_release-2

Git Clone URL: https://aur.archlinux.org/liquidprompt.git (read-only, click to copy)
Package Base: liquidprompt
Description: A useful adaptive prompt for Bash & Zsh
Upstream URL: https://github.com/nojhan/liquidprompt
Keywords: bash info prompt status zsh
Licenses: AGPL3
Conflicts: liquidprompt-git
Submitter: phantom94
Maintainer: xuanruiqi
Last Packager: xuanruiqi
Votes: 42
Popularity: 0.177441
First Submitted: 2014-10-07 15:59 (UTC)
Last Updated: 2024-06-19 08:06 (UTC)

Dependencies (25)

Required by (0)

Sources (1)

Pinned Comments

phantom94 commented on 2018-04-25 15:12 (UTC)

Note: this package follows the releases as shown on https://github.com/nojhan/liquidprompt/releases

You can install liquidprompt-git if you want to run the master branch.

Latest Comments

1 2 Next › Last »

xuanruiqi commented on 2024-06-20 08:30 (UTC)

Yeah, looks like a conda issue: maybe open an issue there

awagner commented on 2024-06-20 07:41 (UTC)

@xuanruiqi I feel so stupid (!!!) and must apologize for the noise - it was a conda venv that I had activated. I didn't realize that it would affect the terminfo database and that it would spread across terminal emulator sessions and reboots. Maybe at one point I will have a look at why conda did copy terminfo for some terms when creating the venv, but not for others. But anyway, it WAS a matter of my local config. Sorry for the fuzz! And thanks for caring!

xuanruiqi commented on 2024-06-19 08:03 (UTC)

It could be - it could also be an upstream issue. But unlikely a packaging issue.

awagner commented on 2024-06-19 08:01 (UTC)

@xuanruiqi thanks for looking into this. As you say you cannot reproduce it with alacritty, wouldn't this suggest it's an issue with my configuration (rather than an upstream issue)? I will experiment a bit and report back...

xuanruiqi commented on 2024-06-19 07:50 (UTC)

@awagner - I can reproduce it neither with alacritty nor my main terminal kitty. Pretty sure it's an upstream issue.

milouse commented on 2024-06-18 21:09 (UTC)

@awagner can you check how it behaves with another terminal (like foot)? If you still don’t have color, it looks like it is a packaging issue (a missing dependency, somehow). If you get color, it will means that this is probably more an upstream issue with alacritty.

Also, before reporting another issue, can you confirm that both alacritty and ncurses package are up-to-date on your system?

awagner commented on 2024-06-18 16:02 (UTC)

I guess since the update 2.2.0_rc.2-1 → 2.2.0_release-1 it seems lp no longer understands that my TERM (alacritty) can handle colors. I get an error message: "liquidprompt: terminal 'alacritty' does not support foreground colors" (twice) and indeed it no longer shows colors in the prompt. Other tools like, say, systectl do show colors in the terminal (and so did lp before the update).

Is this something related to packaging or should I open an issue upstream?

xuanruiqi commented on 2023-08-24 09:27 (UTC)

Thank you. Let me take a look.

milouse commented on 2023-08-24 09:21 (UTC)

Also, the right license name is AGPL3. The current AGPLv3 is not recognized as a common license and appear as an error by namcap.

Here is an updated PKGBUILD, including the license fix, the dependency issue reported by @szebenyib and my proposal to include tests and default themes: https://git.umaneti.net/pkgbuilds/tree/my_liquidprompt/PKGBUILD

szebenyib commented on 2023-08-23 10:10 (UTC)

Without inetutils there is an errormessage on opening a new shell: hostname command not found. Can you please add it as a dependency?