From: Lars Ingebrigtsen <larsi@gnus.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: 19085@debbugs.gnu.org
Subject: bug#19085: 25.0.50; eww: text fields and undo
Date: Tue, 02 Feb 2016 16:30:39 +1100 [thread overview]
Message-ID: <87twlr4r28.fsf@gnus.org> (raw)
In-Reply-To: <87mvrj1yv4.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 02 Feb 2016 16:10:23 +1100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Ah, I see it now. The bug is actually when doing `M-t' after the last
> word in the field. Which should just signal an error instead of doing
> anything. I wonder why it's not doing that -- the "Seach" button should
> be read-only...
It's rather fascinating. If you insert this into a buffer and then
`M-t' between the words (with debugging switched on):
(insert "foo " (propertize "bar\nzot" 'read-only t))
You'll get a buffer with
bar foobar
zot
while showing the backtrace. But continuing restores what was there,
because it's called in `atomic-change-group' form.
However, when doing the restoration, the `after-change-functions'
function isn't run, so eww doesn't restore the length. Is that a bug in
`atomic-change-group'?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-02 5:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 18:51 bug#19085: 25.0.50; eww: text fields and undo Mark Oteiza
2014-11-27 16:26 ` Lars Magne Ingebrigtsen
2014-11-27 17:26 ` Mark Oteiza
2014-12-02 14:02 ` Ivan Shmakov
2016-02-02 4:28 ` Lars Ingebrigtsen
2016-02-02 4:30 ` Lars Ingebrigtsen
2016-02-02 4:45 ` Mark Oteiza
2016-02-02 5:00 ` Lars Ingebrigtsen
2016-02-02 5:06 ` Mark Oteiza
2016-02-02 5:10 ` Lars Ingebrigtsen
2016-02-02 5:30 ` Lars Ingebrigtsen [this message]
2016-02-02 5:51 ` Lars Ingebrigtsen
2016-02-02 6:07 ` Lars Ingebrigtsen
2016-02-02 7:04 ` Lars Ingebrigtsen
2016-02-04 4:30 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twlr4r28.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=19085@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.