From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "João Távora" <joaotavora@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Text property searching
Date: Mon, 16 Apr 2018 20:07:45 +0000 [thread overview]
Message-ID: <20180416200745.GC5637@ACM> (raw)
In-Reply-To: <877ep7x77s.fsf@mouse.gnus.org>
Hello, Lars.
On Mon, Apr 16, 2018 at 21:49:11 +0200, Lars Ingebrigtsen wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > Very much so. If there is a category text property at some point, and
> > the symbol it uses has a foo property, that will normally get seen by
> > the text property primitives. However, if you put a foo text property
> > there with a nil value, that nil value will mask the intent of the
> > category property.
> Hm. I am completely unfamiliar with the category stuff -- how is this
> used in practice?
I don't really know, in general.
In C++ and Java Modes, < and > which are template/generic delimiters are
given category text properties, symbols foo and bar, whose syntax-table
properties gives the < and > parenthesis syntax. This parenthesis syntax
is regularly "switched off" on all such characters simply by changing
the value of foo's and bar's syntax-table properties to punctuation.
This enables syntactic searching where template/generic < and > need not
to be seen.
Having implemented this, I don't recommend the technique. It has
disadvantages, in that it collides with syntax-ppss. To be fair, Stefan
advised me not to go ahead with it at an early stage. I'll probably
remove it from CC Mode at some stage.
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-04-16 20:07 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 22:56 Text property searching Lars Ingebrigtsen
2018-04-16 0:00 ` T.V Raman
2018-04-16 4:40 ` Dmitry Gutov
2018-04-16 12:01 ` Lars Ingebrigtsen
2018-04-16 13:04 ` Dmitry Gutov
2018-04-16 15:11 ` Lars Ingebrigtsen
2018-04-16 18:06 ` Eli Zaretskii
2018-04-16 18:30 ` Lars Ingebrigtsen
2018-04-16 14:30 ` Drew Adams
2018-04-16 17:52 ` Eli Zaretskii
2018-04-16 18:31 ` Lars Ingebrigtsen
2018-04-16 15:16 ` João Távora
2018-04-16 16:09 ` Lars Ingebrigtsen
[not found] ` <CALDnm52qb5jfjC181pS+UTwfFES95m=EYtyXJzya7pdBMz8rxA@mail.gmail.com>
[not found] ` <87d0yz15a3.fsf@mouse.gnus.org>
2018-04-16 16:54 ` João Távora
2018-04-16 16:57 ` Lars Ingebrigtsen
2018-04-16 17:30 ` João Távora
2018-04-16 17:35 ` Lars Ingebrigtsen
2018-04-16 18:26 ` Lars Ingebrigtsen
2018-04-16 18:52 ` Eli Zaretskii
2018-04-16 19:01 ` Lars Ingebrigtsen
2018-04-16 19:48 ` Eli Zaretskii
2018-04-16 19:53 ` Lars Ingebrigtsen
2018-04-16 19:59 ` Eli Zaretskii
2018-04-16 21:56 ` Clément Pit-Claudel
2018-04-16 21:58 ` Lars Ingebrigtsen
2018-04-16 22:06 ` João Távora
2018-04-16 22:21 ` Clément Pit-Claudel
2018-04-16 19:02 ` Lars Ingebrigtsen
2018-04-16 19:50 ` Eli Zaretskii
2018-04-16 19:56 ` Lars Ingebrigtsen
2018-04-16 20:05 ` Drew Adams
2018-04-16 20:11 ` Lars Ingebrigtsen
2018-04-16 20:40 ` Lars Ingebrigtsen
2018-04-16 20:48 ` Stefan Monnier
2018-04-16 21:17 ` João Távora
2018-04-16 21:21 ` Lars Ingebrigtsen
[not found] ` <CALDnm51Hgs6b_Q=A0mZ=UMnOeOUX2fGE+dTf2JP4HOMF11-z8A@mail.gmail.com>
2018-04-16 21:32 ` Lars Ingebrigtsen
2018-04-17 19:10 ` Alan Mackenzie
2018-04-17 19:16 ` Lars Ingebrigtsen
2018-04-17 20:31 ` Alan Mackenzie
2018-04-17 20:42 ` Lars Ingebrigtsen
2018-04-16 19:40 ` Alan Mackenzie
2018-04-16 19:49 ` Lars Ingebrigtsen
2018-04-16 20:07 ` Alan Mackenzie [this message]
2018-04-16 20:31 ` Lars Ingebrigtsen
2018-04-16 21:18 ` Lars Ingebrigtsen
2018-04-16 21:28 ` João Távora
2018-04-16 22:09 ` Lars Ingebrigtsen
2018-04-17 13:01 ` Stefan Monnier
2018-04-17 13:04 ` Lars Ingebrigtsen
2018-04-16 16:59 ` Lars Ingebrigtsen
2018-04-16 18:03 ` 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
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=20180416200745.GC5637@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=larsi@gnus.org \
/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).