From: Leo Liu <sdl.web@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31772@debbugs.gnu.org, tino.calancha@gmail.com
Subject: bug#31772: 26.1; (thing-at-point 'list) regression
Date: Tue, 12 Jun 2018 01:04:48 +0800 [thread overview]
Message-ID: <m1tvq945lb.fsf@gmail.com> (raw)
In-Reply-To: <83r2ldqsi4.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Jun 2018 17:58:59 +0300")
On 2018-06-11 17:58 +0300, Eli Zaretskii wrote:
> In "emacs -Q", go to the 'h' in "that" on the first line, and then:
>
> M-: (thing-at-point 'list) RET
> => #("hat" 0 3 (fontified nil face font-lock-comment-face))
>
> That's not even a word, let alone a list. Is that useful? I think
> nil is more useful, since nothing should be a list inside a comment.
I have noticed this while coding easy-kill since it built on
thingatpt.el. It was of minor annoyance so I ignored it.
It seems to make a lot of sense to fallback on `sexp' as a degenerated
case. Do you agree the previous behaviour of (thing-at-point 'list) is
mostly sane?
Additional points.
show-paren-mode works inside comments and strings. One of the craziest
things it does is if you have open paren in one string and a close paren
in another, it works too.
characters in and out of comments usually have the same syntax. so
finding a list in comments or strings is not wrong. It's smart and it's
useful. It serves us very well.
Leo
prev parent reply other threads:[~2018-06-11 17:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 3:58 bug#31772: 26.1; (thing-at-point 'list) regression Leo Liu
2018-06-10 15:03 ` Eli Zaretskii
2018-06-10 15:21 ` Tino Calancha
2018-06-11 3:17 ` Leo Liu
2018-06-11 15:06 ` Tino Calancha
2018-06-11 16:08 ` Leo Liu
2018-06-11 16:25 ` Tino Calancha
2018-09-06 10:37 ` Leo Liu
2018-09-06 19:01 ` Andreas Röhler
2018-09-07 4:42 ` Leo Liu
2018-09-07 8:17 ` Andreas Röhler
2018-09-08 0:09 ` Leo Liu
2018-09-11 8:31 ` Eli Zaretskii
2018-09-11 10:26 ` Leo Liu
2018-09-11 11:16 ` Eli Zaretskii
2018-09-11 11:52 ` Andreas Röhler
2018-09-11 12:10 ` Eli Zaretskii
2018-09-11 12:36 ` Leo Liu
2018-09-11 12:39 ` Eli Zaretskii
2018-09-14 14:55 ` Leo Liu
2018-09-15 9:06 ` Eli Zaretskii
2018-09-15 12:58 ` Leo Liu
2018-09-15 13:28 ` Eli Zaretskii
2018-06-11 16:34 ` Eli Zaretskii
2018-06-11 15:10 ` Eli Zaretskii
2018-06-11 16:36 ` Leo Liu
2018-06-11 2:32 ` Leo Liu
2018-06-11 14:58 ` Eli Zaretskii
2018-06-11 17:04 ` Leo Liu [this message]
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=m1tvq945lb.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=31772@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tino.calancha@gmail.com \
/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).