Date: Wed, 25 Mar 2020 06:01:29 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 227967] [usability] x11-servers/xorg-server ships with black background which makes debugging X hard Message-ID: <bug-227967-7141-SaZ9udLw9U@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227967-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-227967-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227967 Alexey Dokuchaev <danfe@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danfe@FreeBSD.org --- Comment #5 from Alexey Dokuchaev <danfe@FreeBSD.org> --- (In reply to Chris Rees from comment #4) > I agree, but this is a bit of an intrusive change for a port. Just was unpleasantly astonished by this myself and found this PR. Personally I'd rather have "retro" pattern left by default and never touched (in accordance to "don't try to fix what ain't broken" rule), but then we'd have to do something about the "-retro" option (e.g. remove this bogosity) = and *that* already becomes intrusive. On the other hand, if upstream makes a stupid decision (and replacing traditional X pattern with black inconclusive blank vagueness is certainly stupid, if not idiotic) then we, downstream packagers, should correct it for the benefit of our end-users. If upstream had decided to use solid color, why not make it the same as your favourite bikeshed? Dark purple seems fine. :-) This way, "-retro" option would still behave as expected, requiring no intrusive changes to the port other than simple s/black/$somecolor/ one-line patch. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227967-7141-SaZ9udLw9U>