From owner-freebsd-x11@freebsd.org Wed Mar 25 06:01:45 2020 Return-Path: Delivered-To: freebsd-x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9F2CD277033 for ; Wed, 25 Mar 2020 06:01:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 48nHZ04X3Mz4lTy for ; Wed, 25 Mar 2020 06:01:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 6450127701E; Wed, 25 Mar 2020 06:01:37 +0000 (UTC) Delivered-To: x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5EBED27701D for ; Wed, 25 Mar 2020 06:01:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48nHYr2FLpz4lRZ for ; Wed, 25 Mar 2020 06:01:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1E7AEDB62 for ; Wed, 25 Mar 2020 06:01:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 02P61TmR007109 for ; Wed, 25 Mar 2020 06:01:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 02P61TvQ007108 for x11@FreeBSD.org; Wed, 25 Mar 2020 06:01:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f 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 Date: Wed, 25 Mar 2020 06:01:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: danfe@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: x11@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Mar 2020 06:01:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227967 Alexey Dokuchaev changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danfe@FreeBSD.org --- Comment #5 from Alexey Dokuchaev --- (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.=