From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Musings on creating an HTML-based WYSIWYG mode Date: Wed, 02 May 2018 11:50:43 +0200 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1525254647 25663 195.159.176.226 (2 May 2018 09:50:47 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 2 May 2018 09:50:47 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 02 11:50:42 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fDoPJ-0006Zh-8q for ged-emacs-devel@m.gmane.org; Wed, 02 May 2018 11:50:41 +0200 Original-Received: from localhost ([::1]:49364 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fDoRQ-0007ew-AS for ged-emacs-devel@m.gmane.org; Wed, 02 May 2018 05:52:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49509) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fDoPZ-0006Qn-4w for emacs-devel@gnu.org; Wed, 02 May 2018 05:50:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fDoPU-0001XC-7w for emacs-devel@gnu.org; Wed, 02 May 2018 05:50:57 -0400 Original-Received: from hermes.netfonds.no ([80.91.224.195]:45348) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fDoPU-0001Vg-0F for emacs-devel@gnu.org; Wed, 02 May 2018 05:50:52 -0400 Original-Received: from cm-84.212.221.165.getinternet.no ([84.212.221.165] helo=stories) by hermes.netfonds.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1fDoPL-0001DO-Rr; Wed, 02 May 2018 11:50:46 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEVqhlq8HEWOwMzqJzbx JDbnITb4+DtnYFi6GS+/LkGpFTKDCUjkD3+EP1uBqoLTHj/f+5OGAAACV0lEQVQ4jV3TTWgTURAA 4AeC0YtQ8OhpL6EgvWSR2nqRzvbXEIQs+IMUWtlzscpShV7s4WU9JGigTUE8NIclFy+WSJ4/CN4S D0ohgiyIl9DLnhq6TQ9x5r39S+a28+28mXnZsIlrHRnfYSTmWAy5UWFhvtMRYNSdfsMZnLkzpVIC 38SOcVjm7nngOM5gkEBbfFCHjx/VFjsAhttwpl+WnZKT7qEjHATO9Ec3GNSAdZLmGCcGQA6MJe36 GMhYfvBL01LwecK7qmA3O5UGz/N+SshrWqrCI/DkwFoM7U8/PAVFKvgn4RbBYd5LKvL2EwL9Du5W Lyg4UkDCdFgUog5578/G5T6EgML05dYsAsxdtKx1Ca8RthEW9VnxFWDewnishlUA8Ko1A3DDkpHL 0UwhnNNthGBZNomCFYL5GOS0EgpjEO6BSXmxKQj3wEVSsNZLYKUFSXdNy8bwUH4GqsmaRhJV1OVt U37dpomyCgrd51Up9C125Rpqql3sdhD93t1wDYQlms+uJoD3QVA8lbCZAupzzO6zjBRdwe2uhEnO KgwDH56GJXdRtKk9zlgIW5CI9ps7LJYwb5r3mpNBDJkYDHM14DwGFoFpmsMhQiOCzFZUYAZY0YiB bZ55VQnD8ijQYEU6ig5yEniLkD2BIp5EHSJ4Awu2aNpH2AFnwvcRarVa5QLAQla8EM9wplUeQr9I n/7NSk/YzXfYQXYmCN5j/pSxnmhu+P7xkEcwcPFPytiVXlNs+75/iXNXHcXLJuAN+70vNub9v6pD o8V433zECOh9jH2ZF+I/QIbz8E4uSaIAAAAASUVORK5CYII= In-Reply-To: (Stefan Monnier's message of "Tue, 01 May 2018 21:45:00 -0400") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 80.91.224.195 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:225026 Archived-At: Stefan Monnier writes: >> This is, of course, not like what Emacs does normally when editing text, >> and would break a lot of invariants that people are used to. > > I don't think so, actually. At least, I don't think it should be very > serious issue (and in the worst case we could do a comparison between > the old and new rendering to try and modify only the "relevant" portion > of the buffer). > IOW, nothing too worrisome. I was thinking about things, like, "what does it mean to kill a rectangle in a buffer that's auto-reformatted"? Do we re-render after each "piece" that's been killed? (Probably not.) What about when the user types `M-x query-replace-regexp RET ^foo RET bar'... If we re-render after each replacement (or not), then there might be lines starting with "foo" after it has run, anyway (because things will be re-flowing). Stuff like that. I'm not saying that these are insurmountable obstacles or anything, but there will be these things that people are used to using that may or may not work the same in a WYSIWYG context, and that dealing with them will probably require just living with it a bit, thinking about each case, and adjusting things as we go along. >> But like I said, I don't have time at the moment. :-) > > Sounds like the ideal moment to start hacking then! :-) I think it'll have to wait until my next holiday. But if anybody else wants to take a stab at it, don't wait for me. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no