GNU bug report logs -
#9454
24.0.50; thingatpt.el should be updated to respect field boundaries
Previous Next
Reported by: "Drew Adams" <drew.adams <at> oracle.com>
Date: Tue, 6 Sep 2011 23:20:03 UTC
Severity: wishlist
Found in version 24.0.50
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
I'm no expert on fields, to put it mildly. But my impression is that
thing-at-point functions should not cross field boundaries.
I ran into this using a thing-at-point function (actually, a
thing-near-point function) in the minibuffer. Now that (forward-line 0)
takes you across the field boundary and into the prompt field, I ended
up with "Text is read-only" errors.
(And just why is it an improvement to have two fields here? What was
wrong with the (simple) situation before?)
To fix this I ended up splattering my own thing-at-point code with
`constrain-to-field' calls. Butt ugly, but unless I'm missing something
(quite possible), unavoidable.
Anyway, this is a heads-up that you might want to take a look at
thingatpt.el and DTRT wrt field boudaries. FWIW, my own code is here:
http://www.emacswiki.org/emacs/download/thingatpt%2b.el. Among other
things, it contains fixes for Emacs bugs #8667, #8628, and #9300 (fixes
already communicated, but still not applied to vanilla Emacs).
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2011-09-05 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.5) --no-opt'
This bug report was last modified 3 years and 349 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.