From: Efraim Flashner <efraim@flashner.co.il>
To: Gottfried <gottfried@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Desktop Enlightment
Date: Thu, 1 Dec 2022 11:29:03 +0200 [thread overview]
Message-ID: <Y4hz31XgVWRpFmFq@3900XT> (raw)
In-Reply-To: <e51ba923-dcdb-6251-d0b2-48e4b11860cc@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
On Wed, Nov 30, 2022 at 07:28:18PM +0000, Gottfried wrote:
> Hi Guixers,
>
> I have got the desktop Enlightment installed
>
> There are again and again certain problems.
> It seems to me that Enlightment isn't well developed yet.
There is a complaint against Enlightenment (and EFL) that they overuse
void pointers to swallow errors, so it's hard to squash bugs.
> E.g.because of a second monitor which I connected to the laptop.
> Other problems I have already forgotten, because I haven't used it
> therefore.
I haven't tried hooking up a second monitor yet. There is a popup about
no ACPI program/daemon running when enlightenment first starts but it's
been working well enough for me despite that for several years.
> Now I can't open the package "MuseScore". It can't find the right path.
I don't use musescore, but I was able to launch it without problems.
> Is there somebody who is using Enlightment?
>
> Have you got also sometimes problems?
I find that it does sometimes crash on me and cause me to reopen
windows. It happens mostly with nheko and with flatpaks. I've apparently
been using Enlightenment on Guix System since early 2018 so I've
probably learned to ignore any issues that still exist.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-01 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 19:28 Desktop Enlightment Gottfried
2022-12-01 9:29 ` Efraim Flashner [this message]
2022-12-01 16:37 ` Gottfried
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y4hz31XgVWRpFmFq@3900XT \
--to=efraim@flashner.co.il \
--cc=gottfried@posteo.de \
--cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).