From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Protesilaos Stavrou Newsgroups: gmane.emacs.bugs Subject: bug#43944: 28.0.50; Update modus-operandi, modus-vivendi themes to v0.13.0 Date: Sat, 17 Oct 2020 10:13:12 +0300 Message-ID: <87362dl3zr.fsf@protesilaos.com> References: <874kn0ympd.fsf@protesilaos.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35706"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 43944@debbugs.gnu.org To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Oct 17 09:15:06 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kTgQj-00099Q-Ez for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 17 Oct 2020 09:15:05 +0200 Original-Received: from localhost ([::1]:44636 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kTgQi-00067k-Fq for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 17 Oct 2020 03:15:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37036) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kTgPi-0005AN-O9 for bug-gnu-emacs@gnu.org; Sat, 17 Oct 2020 03:14:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49809) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kTgPi-0004Kg-9E for bug-gnu-emacs@gnu.org; Sat, 17 Oct 2020 03:14:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kTgPi-0004lA-1g for bug-gnu-emacs@gnu.org; Sat, 17 Oct 2020 03:14:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Protesilaos Stavrou Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 17 Oct 2020 07:14:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43944 X-GNU-PR-Package: emacs Original-Received: via spool by 43944-submit@debbugs.gnu.org id=B43944.160291880318227 (code B ref 43944); Sat, 17 Oct 2020 07:14:01 +0000 Original-Received: (at 43944) by debbugs.gnu.org; 17 Oct 2020 07:13:23 +0000 Original-Received: from localhost ([127.0.0.1]:33118 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kTgP5-0004jv-IV for submit@debbugs.gnu.org; Sat, 17 Oct 2020 03:13:23 -0400 Original-Received: from relay12.mail.gandi.net ([217.70.178.232]:50075) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kTgP3-0004jg-Ln for 43944@debbugs.gnu.org; Sat, 17 Oct 2020 03:13:22 -0400 Original-Received: from kronos (unknown [213.207.159.38]) (Authenticated sender: public@protesilaos.com) by relay12.mail.gandi.net (Postfix) with ESMTPSA id 8D711200007; Sat, 17 Oct 2020 07:13:14 +0000 (UTC) In-Reply-To: (Stefan Kangas's message of "Fri, 16 Oct 2020 10:13:58 -0700") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:190758 Archived-At: --=-=-= Content-Type: text/plain On 2020-10-16, 10:13 -0700, Stefan Kangas wrote: > Protesilaos Stavrou writes: > >> + The two themes are also available in GNU ELPA. What is the best way >> to ensure that we sync between emacs.git and elpa.git? GNU ELPA has >> hitherto pulled from dedicated branches on my upstream git repository. >> Maybe it would be better/easier to start building directly from the >> Emacs source? This would reduce the overall workload. > > What does "start building directly from the Emacs source" mean here? "Build" is the wrong term here. Sorry about that! My intent is to find an easy way/workflow to get the files from Emacs into GNU ELPA. And by "easy" I mean not to duplicate the work we do here. So I would not have to contact the GNU ELPA maintainers separately and have them pull from my git source. > FWIW, I don't think we should feel too bound to any particular process; > this seems like a practical matter where we should try to do whatever > is most practical. Good to know. I have no particular preference on the matter and shall adapt to whatever you and others may recommend. >> + Sending attachments with large diffs has the downside of losing the >> commit history. Do Emacs maintainers wish to keep track of it? If >> so, what would be the best way to preserve it, seeing as I am >> developing them on my own upstream? > > I don't think we generally worry about preserving history for packages > managed externally. We just sync the latest version. > > (If one really would like to preserve it, it could perhaps be done with > some git magic. I'm not sure it's worth the extra effort.) Syncing the latest version works fine for me. I have thus far published tagged releases on a monthly cadence. Expect the next one in mid to late November. >> + Should the texinfo file be mentioned in the NEWS entry about the two >> themes? The attached patch does not include such a change. > > We could of course add a NEWS entry for it. Would you like to propose > one? I attach a possible rewording that also corrects "colour" and adds an explicit reference to the WCAG AAA accessibility spec. Please note that I do not know how to properly reference an Info node: I used 'C-u 0 x', which calls 'Info-copy-current-node-name'. -- Protesilaos Stavrou protesilaos.com --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=0001-Update-Modus-themes-NEWS-entry.patch >From 4b235a54973570aeb9330c15315f47682b7f121f Mon Sep 17 00:00:00 2001 From: Protesilaos Stavrou Date: Sat, 17 Oct 2020 09:50:48 +0300 Subject: [PATCH] Update Modus themes' NEWS entry * etc/NEWS: Reword entry about new 'modus-operandi' and 'modus-vivendi' themes. Include reference to their manual. --- etc/NEWS | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/etc/NEWS b/etc/NEWS index 1838b6b38a..d782e6c12c 100644 --- a/etc/NEWS +++ b/etc/NEWS @@ -1403,9 +1403,11 @@ mode, as are other data files produced by Emacs. It's a library to create, query, navigate and display hierarchy structures. ** New themes 'modus-vivendi' and 'modus-operandi'. -These themes are designed for colour-contrast accessibility. You can -load the new themes using 'M-x customize-themes' or 'load-theme' from -your init file. +These themes are designed to conform with the highest standard for +color-contrast accessibility (WCAG AAA). You can load either of them +using 'M-x customize-themes' or 'load-theme' from your init file. +Their on-line documentation describes the customization options they +provide. Consult '(info "(modus-themes) Top")'. * Incompatible Editing Changes in Emacs 28.1 -- 2.28.0 --=-=-=--