[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Improving 'pcase' documentation
|
From: |
Dmitry Gutov |
|
Subject: |
Re: Improving 'pcase' documentation |
|
Date: |
Mon, 20 Nov 2023 15:54:16 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 |
On 19/11/2023 22:14, Jim Porter wrote:
Does anyone have any particular feedback on these ideas, suggestions of
what would be the most beneficial, etc?
I don't have much to add at the moment, but the list sounds great.
Number 6 might be more difficult to do than the rest, since we currently
don't have any support for context-local syntax (another example would
be 'should' forms in ert tests) in completion/font-lock, and any such
logic would have consider the level of quoting/unquoting, but ultimately
it can be done.
> (I also think it'd be nice to font-lock anything that looks like
",SYMBOL", even outside of 'pcase', but maybe others would find that
annoying.)
And that sounds like a part of more general feature where local
variables would be highlighted with font-lock-variable-name-face and
font-lock-variable-use-face. To determine that ,foo is a variable
declaration (inside a pcase form or anywhere) and not just a reference,
font-lock would have to do some macro-expansion. I wonder what would be
the performance implications of such general approach.