unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: johnw@gnu.org, tom@tromey.com, emacs-devel@gnu.org
Subject: Re: Heads-up: Emacs 26.1 RC1
Date: Tue, 20 Mar 2018 09:08:26 +0200	[thread overview]
Message-ID: <83fu4vmdg5.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ogK5u=_K8SAxKm37XO=Hm9B00+2WLTyUTkc9dHhE7Q4Ug@mail.gmail.com> (message from Richard Copley on Mon, 19 Mar 2018 21:33:12 +0000)

> From: Richard Copley <rcopley@gmail.com>
> Date: Mon, 19 Mar 2018 21:33:12 +0000
> Cc: John Wiegley <johnw@gnu.org>, Emacs Development <emacs-devel@gnu.org>, Tom Tromey <tom@tromey.com>
> 
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30295#11 
> 
> Please try this in CSS mode:
> 
> div: {
>   #87e087
> }
> 
> I hope you'll agree it's bad

Actually, doesn't look too bad here.

> It's also easy and safe to fix.

I don't see any proposed patches in the bug report.  What did I miss?

> As ever I'm reluctant to provide a patch (though I do have one and I'll certainly be using it), because I haven't
> assigned copyright, but I did make concrete suggestions for a fix.

If someone can present a patch, I promise to review it.

Thanks.



  reply	other threads:[~2018-03-20  7:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 15:59 Heads-up: Emacs 26.1 RC1 Eli Zaretskii
2018-03-19 18:46 ` Pierre Téchoueyres
2018-03-19 19:28   ` Eli Zaretskii
2018-03-19 19:59     ` Pierre Téchoueyres
2018-03-19 20:12       ` Eli Zaretskii
2018-03-20  6:10         ` Eric Abrahamsen
2018-03-20  7:16           ` Eli Zaretskii
2018-03-20  8:25             ` Eric Abrahamsen
2018-03-20  9:18               ` Eli Zaretskii
2018-03-20 23:22                 ` Eric Abrahamsen
2018-03-20 23:33                   ` Dmitry Gutov
2018-03-21  0:11                     ` Eric Abrahamsen
2018-03-21  6:34                   ` Eli Zaretskii
2018-03-21  9:48                     ` Eric Abrahamsen
2018-03-21  9:57                       ` Eric Abrahamsen
2018-03-21 12:54                       ` Eli Zaretskii
2018-03-21 13:50                         ` Eric Abrahamsen
2018-03-22 19:38                           ` Pierre Téchoueyres
2018-03-19 21:00 ` Michael Heerdegen
2018-03-20  7:03   ` Eli Zaretskii
2018-03-26 18:53     ` Eli Zaretskii
2018-03-26 20:05       ` Michael Heerdegen
2018-03-27  0:01         ` Michael Heerdegen
2018-03-27  2:40           ` Eli Zaretskii
2018-03-27  2:58             ` Michael Heerdegen
2018-03-27  3:12               ` Eli Zaretskii
2018-03-19 21:04 ` Phillip Lord
2018-03-19 21:11   ` Noam Postavsky
2018-03-20  7:05     ` Eli Zaretskii
2018-03-20 10:31       ` Phillip Lord
2018-03-19 21:33 ` Richard Copley
2018-03-20  7:08   ` Eli Zaretskii [this message]
2018-03-20  9:52 ` Robert Pluim
2018-03-20 12:32   ` Eli Zaretskii

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83fu4vmdg5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@gnu.org \
    --cc=rcopley@gmail.com \
    --cc=tom@tromey.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).