unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Musings on creating an HTML-based WYSIWYG mode
Date: Wed, 02 May 2018 11:50:43 +0200	[thread overview]
Message-ID: <m3r2mus7ws.fsf@gnus.org> (raw)
In-Reply-To: <jwvtvrqj0n7.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Tue, 01 May 2018 21:45:00 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> 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



  reply	other threads:[~2018-05-02  9:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 14:54 Musings on creating an HTML-based WYSIWYG mode Lars Ingebrigtsen
2018-05-01 19:00 ` Søren Pilgård
2018-05-01 20:11   ` Lars Ingebrigtsen
2018-05-02  8:16     ` Søren Pilgård
2018-05-02  9:22     ` Joost Kremers
2018-05-02  9:36       ` Van L
2018-05-02  1:45 ` Stefan Monnier
2018-05-02  9:50   ` Lars Ingebrigtsen [this message]
2018-05-02 10:36     ` Yuri Khan
2018-05-02 10:43       ` Lars Ingebrigtsen
2018-05-02 10:49         ` Yuri Khan
2018-05-02 20:32   ` Michael Heerdegen
2018-05-02  3:11 ` Richard Stallman
2018-05-02  3:50   ` Van L

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=m3r2mus7ws.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).