Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Makefile: highlighting error for include and functions #913

Closed
gcapes opened this issue May 18, 2018 · 5 comments
Closed

Makefile: highlighting error for include and functions #913

gcapes opened this issue May 18, 2018 · 5 comments
Labels
bugfix-request A request for a bugfix to be developed.

Comments

@gcapes
Copy link

gcapes commented May 18, 2018

I maintain the Software Carpentry lesson on Make, and I have noticed that the syntax highlighting doesn't work correctly for include and when using functions e.g. wildcard and patsubst.

See swcarpentry/make-novice#134 (comment) and screenshot below:
image

@stale
Copy link

stale bot commented Jun 19, 2019

This contribution has been automatically marked as stale because it has not had any activity for more than a year. It will be closed if no additional activity occurs within the next 14 days.

@stale stale bot added the stale-issue There has been no activity for a year. label Jun 19, 2019
@gcapes
Copy link
Author

gcapes commented Jun 19, 2019

@rouge-ruby
Any thoughts on this?

@stale stale bot removed the stale-issue There has been no activity for a year. label Jun 19, 2019
@pyrmont
Copy link
Contributor

pyrmont commented Jun 19, 2019

@gcapes Hmmm... seems that although the keywords are defined (see below) they're never used in any of the rules:

bsd_special = %w(
include undef error warning if else elif endif for endfor
)

This is clearly a bug in the Make lexer. I don't mean to be the bearer of bad news but I'm afraid that it's unlikely this will get fixed soon without someone submitting a PR. We're doing our best to clear up the backlog after Rouge's hiatus but there's quite a lot to get through before we start looking at addressing individual issues :(

I will say that we are reviewing the newest PRs first, so if you wanted to take a stab at this yourself, your PR would be go to the top of the pile (or stack, as it were)! I became a maintainer recently and wrote a guide to lexer development that might be of some assistance.

@pyrmont pyrmont added the bugfix-request A request for a bugfix to be developed. label Jun 19, 2019
@pyrmont
Copy link
Contributor

pyrmont commented Jun 19, 2019

Oh, and for future testing, here's the code I used to test:

include config.mk

TXT_FILES=$(wildcard books/*.txt)

@gcapes
Copy link
Author

gcapes commented May 15, 2020

Looks like this issue is now fixed. Thanks!

@gcapes gcapes closed this as completed May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix-request A request for a bugfix to be developed.
Projects
None yet
Development

No branches or pull requests

2 participants