Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
Newsgroups: comp.os.linux.advocacy
Subject: Re: Neofetch/neowofetch
Date: Fri, 18 Oct 2024 20:30:03 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 16
Message-ID: <slrnvh5gpc.3njae.candycanearter07@candydeb.host.invalid>
References: <vetjv3$3a0jm$1@dont-email.me>
 <vcl4hjdojteaspaojm6g519ta1a7g69ujj@4ax.com> <vetldi$3a0jm$4@dont-email.me>
 <slrnvh5dfv.3k6ja.candycanearter07@candydeb.host.invalid>
 <6712bf58$0$5195$426a74cc@news.free.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 18 Oct 2024 22:30:04 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="5c0a0c5d29fa32ce6d29bf2e3bbaa9a4";
	logging-data="3647903"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19K0B7My8qJUGfDtEKm/R4GXUFEMDxIqdbnsbr/+yZjBg=="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:n7NX1XXMCv44dTFcC6go9r2sIr8=
X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]%
 b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx
 `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e
 ZrQsWJ >|l^I_[pbsIqwoz.WGA]<D
Bytes: 2083

Stéphane CARPENTIER <sc@fiat-linux.fr> wrote at 20:04 this Friday (GMT):
> Le 18-10-2024, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> a écrit :
>>
>> Isn't neofetch considered unsupported? Not that it matters that much,
>> but still.
>
> It looks like it is from github, but it's the first time I heard about it. I've
> never saw any warning from archlinux about it. If there is no bug and if
> there is nothing to improve maybe it's the reason it's archived in
> github.


That would make sense. It's simple enough that the dev probably wasn't
working on it for years.
-- 
user <candycane> is generated from /dev/urandom