From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: How to make Emacs popular again: Use monospaced fonts less Date: Thu, 15 Oct 2020 10:48:32 -0400 Message-ID: References: <87ft6lgw5y.fsf_-_@gnus.org> <1F8F3522-1E6C-40A3-B61A-B9B84FC0AD18@gnu.org> <87blh9gthg.fsf@gnus.org> <87tuv1f2y9.fsf@gnus.org> <87o8l9f1dl.fsf@gnus.org> <83lfgc50gb.fsf@gnu.org> <875z7gflpl.fsf@gnus.org> <83imbf2xux.fsf@gnu.org> <87lfgbarkk.fsf@gnus.org> <83zh4q195b.fsf@gnu.org> <87sgah1mjz.fsf@gnus.org> <83r1q0zwlp.fsf@gnu.org> <837drszozo.fsf@gnu.org> <83lfg7y4ka.fsf@gnu.org> <83d01jy35d.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5890"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: larsi@gnus.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 15 16:50:12 2020 Return-path: Envelope-to: ged-emacs-devel@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 1kT4a4-0001Nm-JI for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Oct 2020 16:50:12 +0200 Original-Received: from localhost ([::1]:59548 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kT4a3-00045z-HD for ged-emacs-devel@m.gmane-mx.org; Thu, 15 Oct 2020 10:50:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41656) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kT4ZK-0002wB-7R for emacs-devel@gnu.org; Thu, 15 Oct 2020 10:49:26 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:24594) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kT4ZG-0001X7-Uv; Thu, 15 Oct 2020 10:49:25 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id C0C7B441122; Thu, 15 Oct 2020 10:49:16 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 2CDB844038A; Thu, 15 Oct 2020 10:48:34 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1602773314; bh=SvWBGSvRXykW7NRq8bwmpTmzRUXBnHzfrNDyYX5JPfc=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=QXTd06cpuuXhSmQV8NfFJSImeqmUMjt8M0WZ5fdPL9OSHSpEtXyaa2CMRqQzqI7zv IxQyY5FhaSZVG4livIddDtdudawUTKXEWJmY50ktUi8ncGHi35s0K9fLGJAygtSklg 3RXXowri1pFwblMJ8CjnpqE6k27TDN5NIfJXTm7wstyOGtH4xazn03iHfACS0KqsVT C9g1Dn14pypxmLiaVQLMdEalk4BZhCMZUCR0oIOvmWwmBHH7jfmeS6du2IgYXAK7Q7 AsnR4zsJkXX9jJ5FNr2Tpl8STCr2TJ8dKrZmZUhgpXg0eH7OCBjXiK780+/6tfzcyG uZBP2MHV0OAOw== Original-Received: from alfajor (unknown [157.52.9.240]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id A71CF12023B; Thu, 15 Oct 2020 10:48:33 -0400 (EDT) In-Reply-To: <83d01jy35d.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 15 Oct 2020 17:28:30 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/15 08:25:01 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:257740 Archived-At: > I don't think this will be much simpler than just the first method > above: the way to find where the property started is just one > previous-single-property-change call away, right? Not necessarily if the property ends up split into two (or more) sections. Or rather, yes that's what it would boil down to in the redisplay, but in terms of resulting behavior we'd have bugs whenever the property span gets split into several spans. Stefan