It's free real estate!
There's also a syntax file (https://github.com/BarrensZeppelin/tiger.vim), but it's been archived and I can't vouch for its quality.
https://github.com/vim/vim/pull/19202
(2 files)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Any references please?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
References for what? WP:NOTABLE? It's useful enough at least for someone to go to the trouble of writing a tree-sitter parser for: https://github.com/ambroisie/tree-sitter-tiger
Here's the results of a Github search for *.tig files: https://github.com/search?q=path%3A*.tig&type=Code&ref=advsearch&l=&l=
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Yes, but what is Tiger?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@chrisbra it's the teaching language used by these compiler textbooks - https://www.cs.princeton.edu/~appel/modern/
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Oh, sorry, I thought the link from the plugin was enough. Tiger is a programming language used as an example in a popular book teaching how to write compilers: https://www.cambridge.org/core/books/modern-compiler-implementation-in-c/0F85704413FC010C1D1C691C4D2A0865.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@mdellison90-stack approved this pull request.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Thanks. The reason I ask for a reference (which I try to add to such commits) is that if we later need to understand why this was merged (for example due to a file extension clash with another language), we have the origin documented and can see which language the extension was intended for. Assuming the website still exists, we can refer to the specification in case we need to add detection heuristics to distinguish between different languages. If it vanishes, that is a strong argument to drop it or adjust the filetype detection later.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Yes, that makes sense, sorry for misunderstanding earlier!
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()