From: james <garftd@verizon.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Empty project: LXDE
Date: Wed, 10 Aug 2016 21:16:22 -0500 [thread overview]
Message-ID: <cf26fc28-67c4-5e11-f67d-593e9c454064@verizon.net> (raw)
In-Reply-To: <CAOdo=SxQnRnF8W6HgqRNdrNOQ9j+SRzM6VqjZ-Jbad+o=M62Ug@mail.gmail.com>
On 08/10/2016 04:07 PM, Tom H wrote:
> On Wed, Aug 10, 2016 at 5:06 PM, james <garftd@verizon.net> wrote:
>>
>> I have not had the time to migrate things to lxqt, despite tinkering
>> around with it. The next system I install, will go direct to lxqt. I
>> left KDE for many bloated reasons. I sure hope lxqt is light weight,
>> easy to setup and config and stable.
>
> If LXQT's too bloated for you, try Lumina:
>
> https://lumina-desktop.org/
>
> There's an ebuild.
>
>
Yep the ebuild is clean and well written; I shall put that one in my
EAPI-6 reference folder....
I looked at some of the code (https://github.com/trueos/lumina),
impressive, clean and well organized. I do like what I've seen on quick,
first glance.
I did a quick search and did not find a comparison of lumina to lxqt.
I'd like to see a feature comparison to lxqt; gotta ref on the
comparison? I'm interested but cannot commit to a timeline for some test
deployments. For sure this DE is aimed at security and flexibility
and I do like that.
thx Tom,
James
next prev parent reply other threads:[~2016-08-11 2:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 8:22 [gentoo-dev] Empty project: LXDE Pacho Ramos
2016-08-10 5:46 ` Raymond Jennings
2016-08-10 12:12 ` james
2016-08-10 14:44 ` Nathan Zachary
2016-08-10 16:18 ` james
2016-08-10 18:46 ` Pacho Ramos
2016-08-10 21:06 ` james
2016-08-10 21:07 ` Tom H
2016-08-11 2:16 ` james [this message]
2016-08-12 12:30 ` Tom H
2016-08-11 3:16 ` Hanno Böck
2016-08-14 5:39 ` Hanno Böck
2016-08-14 8:38 ` Pacho Ramos
2016-08-17 8:51 ` Raymond Jennings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf26fc28-67c4-5e11-f67d-593e9c454064@verizon.net \
--to=garftd@verizon.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox