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

LF filetype Vim plugin #365

Merged
merged 1 commit into from
Jul 6, 2021
Merged

LF filetype Vim plugin #365

merged 1 commit into from
Jul 6, 2021

Conversation

HugoForrat
Copy link
Contributor

@HugoForrat HugoForrat commented Jun 10, 2021

This is a little Vimscript code to add a Lingua Franca filetype to (neo)vim that I've written that others may benefit from.
It brings basic syntax highlighting and rudimentary text-object support for the target code blocks.

It can be installed by copying the three directories (ftplugin, ftdetect, syntax) and their content into:

  • ~/.vim/ if you're using Vim
  • ~/.config/nvim/ if you're using Neovim
  • Or really anywhere in your Vim 'runtimepath'

(One can of course, simply copy the content of the directories if they already exist).

Copy link
Collaborator

@cmnrd cmnrd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! @lhstrh should we merge this?

@lhstrh lhstrh merged commit 54db272 into lf-lang:master Jul 6, 2021
@Soroosh129
Copy link
Contributor

I noticed that this really great feature is undocumented. Would it be possible to document this under Downloading and Building on the Wiki, alongside Eclipse and IntelliJ?

I think vim + lfc is a very viable development flow. What do you guys think @lhstrh @cmnrd @HugoForrat?

@HugoForrat
Copy link
Contributor Author

HugoForrat commented Jul 23, 2021

I think vim + lfc is a very viable development flow.

Yes absolutely, this has been very convenient especially when working within Autoware's ADE image.
I can write some documentation which is indeed lacking. This should amount to little more than what's in the first message of this PR.

However, as @Feliix42 said in Slack, having this in its own repository in the LF organisation could make the install process even more straightforward, provided that the plugin repository is public. But I've noticed that all repos there are private; is this a conscious decision or a simple coincidence?

@Feliix42
Copy link
Collaborator

Regarding the latter: I already prepped a repository and moved the code in there with some rudimentary documentation. If there's no opposition, I can create a public repository in the LF organization and push the code. :)

@Feliix42
Copy link
Collaborator

The repository is there now; just let me know when we can make it public, then I'll also remove the plugin from the util folder.

@edwardalee
Copy link
Collaborator

The lfc+vim plugin should be documented in Downloading and Building, at a minimum with a pointer to documentation in the new repo.

@HugoForrat
Copy link
Contributor Author

I've edited the Downloading and Building wiki page, making the assumption that the plugin repository will be made public. We'll need to correct the page if we choose to keep it private.

@cmnrd
Copy link
Collaborator

cmnrd commented Jul 26, 2021

Thanks @Feliix42! I don't think there is any reason to keep it private ;) Did you already remove the plugin within the LF repo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants