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.

Sign up for GitHub

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

Jump to bottom

[LaTeX] Separate Quote and Footnote scopes #1472

Closed
alfureu opened this issue Mar 23, 2018 · 6 comments
Closed

[LaTeX] Separate Quote and Footnote scopes #1472

alfureu opened this issue Mar 23, 2018 · 6 comments

Comments

@alfureu
Copy link

alfureu commented Mar 23, 2018

Hi, I am really missing the quote and footnote scopes from the LaTeX syntax. It would be great if the scope can be for

  • ``some text'' and `some other text' the scope text.tex.latex meta.group.brace.latex quote.latex
  • \footnote{some footnote} the scope text.tex.latex meta.group.brace.latex footnote.latex

... or something similar. It would help immensely to introduce new syntax highlighting for these two scopes.
@alfureu alfureu changed the title [LaTeX] Quote and Footnote scopes [LaTeX] Separate Quote and Footnote scopes Mar 23, 2018
@randy3k
Copy link
Contributor

randy3k commented Apr 1, 2018

It should not be very difficult to support these. Any contributions are appreciated.

@alfureu
Copy link
Author

alfureu commented Apr 2, 2018

Great to hear that. Can you please kindly provide any starting point for this? Which file needs editing?

@r-stein
Copy link
Contributor

r-stein commented Apr 5, 2018

You need to edit this file: https://github.com/sublimehq/Packages/blob/master/LaTeX/LaTeX.sublime-syntax
However setting up your editor such that you can create a PR and learning the syntax definition syntax will take way longer than adding this feature.

@alfureu
Copy link
Author

alfureu commented Apr 10, 2018

I see, so can you @r-stein add these features pls? 🥇

@r-stein r-stein mentioned this issue Apr 21, 2018
Merged
@deathaxe
Copy link
Collaborator

Fixed by merged PR #1509.

deathaxe pushed a commit to deathaxe/sublime-packages that referenced this issue Aug 25, 2019
[GitHub] Close obsolete issues
f2f95c2 
This PR proposes to close some already fixed issues, which were not (correctly) referenced in the fixing pull requests.

Closes sublimehq#442
Closes sublimehq#685
Closes sublimehq#691 (invalid)
Closes sublimehq#795
Closes sublimehq#807
Closes sublimehq#903
Closes sublimehq#1141
Closes sublimehq#1172
Closes sublimehq#1245
Closes sublimehq#1257
Closes sublimehq#1286
Closes sublimehq#1320
Closes sublimehq#1357
Closes sublimehq#1382 (wontfix)
Closes sublimehq#1403
Closes sublimehq#1451
Closes sublimehq#1453 (maybe)
Closes sublimehq#1472
Closes sublimehq#1495
Closes sublimehq#1540
Closes sublimehq#1542
Closes sublimehq#1565
Closes sublimehq#1576
Closes sublimehq#1625
Closes sublimehq#1880
Closes sublimehq#1898
Closes sublimehq#1940 (invalid)
@deathaxe deathaxe mentioned this issue Sep 7, 2019
Closed
@wbond
Copy link
Member

wbond commented Oct 24, 2019

This issue has been solved by a previous commit, hence it is being closed.

@wbond wbond closed this as completed Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@wbond @randy3k @alfureu @r-stein @deathaxe