-
Notifications
You must be signed in to change notification settings - Fork 107
Adding syntax highlighting support for Liquid tags #145
Comments
I think this is best solved by adding markdown files to the filetypes recognized by the Another solution would be to include |
@burodepeper Ah, I just tried that and it failed. See instead the GFM syntax highlighting was removed entirely from the md file I was editing and |
@fusion809 Ah yes, you are probably right; of source it only uses a single grammar at the time. My bad. It shouldn't be too difficult to add it similar to this: https://github.com/burodepeper/language-markdown/blob/master/grammars/language-markdown.json#L1500-L1506 |
Na I'm afraid my knowledge of programming is limited. So that would be a big help, thanks. |
No problem. Could you create an issue over here and supply me with some liquid content so I can test if it works? |
Shall do. |
@burodepeper Thanks, it's just is there anyway to translate your |
@burodepeper I have got a list of snippets related to liquid and would like to add snippets for them. where should I send the PR? |
@puranjayjain If they're purely related to liquid, I'd say send the PR to https://github.com/kieranmasterton/language-liquid |
@fusion809 You can create a PR that adds this little bit to the |
@burodepeper thanks but that repository seems to be dead as there is no update for the past 11 months, some issues and PRs are still open. What can be done about that? Any other suggestions or help would be appriciated |
@puranjayjain Have you tried contacting the maintainer for the possibility of transferring ownership to yourself? According to the |
@burodepeper I had contacted the maintainer on his email id but seems there was no response. I'll try to contact him on twitter, if not I'll fork it and start a new package (which I'm not really sure if I want to). |
@puranjayjain I hope it works out via Twitter. I agree that forking and publishing as a new package is more of a last resort. I'm not personally invested in liquid, but I don't mind helping out. It looks rather straight forward. |
My understanding of CoffeeScript and JS is so limited, especially when it comes to Atom packages, that I wouldn't be of much help. I'm more helpful in suggesting features than anything else. I wouldn't even know how to implement the necessary changes to this package (I know @burodepeper gave me that file link to indicate something about what needs to be done, but my knowledge of Atom packages isn't really enough for me to know what to do with that file I have tried to fork this package locally and work on it but I just don't understand CoffeeScript/JS enough to really follow its code). |
@fusion809 @puranjayjain I don't mind maintaining the package if the two of you aren't comfortable with that. |
@burodepeper @fusion809 I'm waiting for the author's response and am giving him a grace period of 24 hours to respond after which I'll start a fork and post here for any updates or ask you to start a fork and that's it I guess for now. |
@puranjayjain 24 hours is a bit short. Give it at least a week. Forking only directly helps yourself and isn't in the interest of the already established user group. |
@burodepeper you are right I'll give him a week's period, sorry for the hassle 😥 |
@puranjayjain No problem. Just actively trying to avoid unnecessary stress ; ) We'll talk later. |
@puranjayjain @burodepeper Unless I'm mistaken it's been two weeks, anyone gonna start working on an improvement for this package? Sorry if I come across as bossy, it's just these features would really help me at least and I doubt I'm the only one that would benefit from them. |
@fusion809 sorry for taking so long i'm creating a fork of the language liquid package and adding @burodepeper to it and then publishing it to atom. |
@puranjayjain You sure you should have forked |
@fusion809 Sure since it is part of liquid language extending the gfm sytax. We'll include gfm in it to extend the support and to gain advantage of color highlighting. |
@fusion809 I have left out some prs so you can add what you think is relevant. Now moving the conversation to the relevant repo. |
@puranjayjain No, I think @fusion809 is correct. For his request, you don't need to fork You don't want to include |
@burodepeper @fusion809 ok can you review my latest commit there and tell me if I can go ahead with a PR here? i'm only talking about the snippet file |
@puranjayjain Sure, if you create a PR for |
Precisely, sorry for being unclear, I honestly thought we were all on the same page. |
@fusion809 @burodepeper I was just now added to the original repo of language-liquid so it is now being maintained again. |
@fusion809 @puranjayjain created a PR in #154. |
Hi,
I use this package quite frequently when writing posts in my Jekyll site (The Hornery — source) and it would help big time if this package had syntax-highlighting and autocompletion support for Liquid tags. If it helps, there is a language-liquid package available for Atom, it has syntax-highlighting support for HTML files with Liquid tags in it.
Thanks for your time,
Brenton
The text was updated successfully, but these errors were encountered: