Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Liri-Terminal Doesn't Save Settings #44

Open
drew-bc opened this issue Jun 12, 2020 · 2 comments
Open

Liri-Terminal Doesn't Save Settings #44

drew-bc opened this issue Jun 12, 2020 · 2 comments

Comments

@drew-bc
Copy link

drew-bc commented Jun 12, 2020

Settings for Opacity and Font size are saved. Settings for Font Family and Color Scheme are not - i.e. after exiting and then re-opening Terminal, the Settings for Font Family and Color Scheme have reverted to some unintelligible default setting.

Manjaro Linux with Budgie DE, both completely up to date.

Liri-Terminal was installed using makepkg and this PKGBUILD:

``pkgname=liri-terminal
pkgver=0.2.0.r96.g4488847
pkgrel=1
pkgdesc="Terminal for Liri"
arch=("x86_64")
url="https://github.com/lirios/terminal"
license=("GPL")
depends=('fluid' 'qt5-gsettings')
makedepends=(git liri-cmake-shared)
replaces=('papyros-terminal')
_commit=4488847e19345f220992cd6752934cb22e2c43e6
source=("git+https://github.com/lirios/terminal.git#commit=$_commit")
sha256sums=('SKIP')

pkgver() {
cd "${srcdir}/terminal"
git describe --long --tags | sed 's/^v//;s/([^-]*-g)/r\1/;s/-/./g'
}

prepare() {
cd "terminal"
mkdir -p build
}

build() {
cd "terminal/build"
cmake ..
-DCMAKE_BUILD_TYPE=Release
-DCMAKE_INSTALL_PREFIX=/usr
-DBUILD_TESTING:BOOL=OFF
-DINSTALL_SYSCONFDIR=/etc
-DINSTALL_LIBDIR=/usr/lib
-DINSTALL_LIBEXECDIR=/usr/lib
-DINSTALL_QMLDIR=/usr/lib/qt/qml
-DINSTALL_PLUGINSDIR=/usr/lib/qt/plugins
make
}

package() {
cd "terminal/build"
make DESTDIR="$pkgdir" install
}

Screenshots available if needed.

@plfiorini plfiorini transferred this issue from lirios/appcenter Aug 19, 2020
@drew-bc
Copy link
Author

drew-bc commented Oct 5, 2020

Any progress?

@mikoducky
Copy link

I see this has been an issue for almost 2 years. Guess it won't get fixed lol. It's a shame, as this was a super clean terminal I wanted to use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants