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

Treat 'Vagrantfile' files as Ruby code #7112

Merged
merged 1 commit into from
May 26, 2023
Merged

Treat 'Vagrantfile' files as Ruby code #7112

merged 1 commit into from
May 26, 2023

Conversation

bcspragu
Copy link
Contributor

@bcspragu bcspragu commented May 22, 2023 •
edited
Loading

Vagrantfiles are configuration files for the vagrant tool, and they are written in Ruby. Even as vagrant is ported to Go, Vagrantfiles will be written in Ruby

When a Vangrantfile is created, it starts with these lines:

# -*- mode: ruby -*-
# vi: set ft=ruby :

But since Helix (quite reasonably) doesn't change editor behavior based on file contents, adding this to languages.toml seems like a reasonable way to get this functionality.

@bcspragu
Treat 'Vagrantfile' files as Ruby code
483aa15 
`Vagrantfile`s are configuration files for the [vagrant](https://www.vagrantup.com/) tool, and they are written in Ruby. Even as vagrant [is ported to Go](https://www.hashicorp.com/blog/toward-vagrant-3-0), `Vagrantfile`s [will be written in Ruby](https://developer.hashicorp.com/vagrant/docs/experimental/vagrant_go)

When a Vangrantfile is created, it starts with these lines:

```
```

But since Helix (quite reasonably) doesn't change editor behavior based on file contents, adding this to `languages.toml` seems like a reasonable way to get this functionality.
@kirawi kirawi added the A-language-support Area: Support for programming/text languages label May 24, 2023
@pascalkuthe pascalkuthe merged commit 16375cd into helix-editor:master May 26, 2023
aotarola pushed a commit to aotarola/helix that referenced this pull request May 28, 2023
@bcspragu @aotarola
Treat 'Vagrantfile' files as Ruby code (helix-editor#7112)
079dba9 
`Vagrantfile`s are configuration files for the [vagrant](https://www.vagrantup.com/) tool, and they are written in Ruby. Even as vagrant [is ported to Go](https://www.hashicorp.com/blog/toward-vagrant-3-0), `Vagrantfile`s [will be written in Ruby](https://developer.hashicorp.com/vagrant/docs/experimental/vagrant_go)

When a Vangrantfile is created, it starts with these lines:

```
```

But since Helix (quite reasonably) doesn't change editor behavior based on file contents, adding this to `languages.toml` seems like a reasonable way to get this functionality.
aotarola pushed a commit to aotarola/helix that referenced this pull request May 28, 2023
@bcspragu @aotarola
Treat 'Vagrantfile' files as Ruby code (helix-editor#7112)
b0a0eb9 
`Vagrantfile`s are configuration files for the [vagrant](https://www.vagrantup.com/) tool, and they are written in Ruby. Even as vagrant [is ported to Go](https://www.hashicorp.com/blog/toward-vagrant-3-0), `Vagrantfile`s [will be written in Ruby](https://developer.hashicorp.com/vagrant/docs/experimental/vagrant_go)

When a Vangrantfile is created, it starts with these lines:

```
```

But since Helix (quite reasonably) doesn't change editor behavior based on file contents, adding this to `languages.toml` seems like a reasonable way to get this functionality.
Triton171 pushed a commit to Triton171/helix that referenced this pull request Jun 18, 2023
@bcspragu @Triton171
Treat 'Vagrantfile' files as Ruby code (helix-editor#7112)
2ddd53b 
`Vagrantfile`s are configuration files for the [vagrant](https://www.vagrantup.com/) tool, and they are written in Ruby. Even as vagrant [is ported to Go](https://www.hashicorp.com/blog/toward-vagrant-3-0), `Vagrantfile`s [will be written in Ruby](https://developer.hashicorp.com/vagrant/docs/experimental/vagrant_go)

When a Vangrantfile is created, it starts with these lines:

```
```

But since Helix (quite reasonably) doesn't change editor behavior based on file contents, adding this to `languages.toml` seems like a reasonable way to get this functionality.
wes-adams pushed a commit to wes-adams/helix that referenced this pull request Jul 4, 2023
@bcspragu @wes-adams
Treat 'Vagrantfile' files as Ruby code (helix-editor#7112)
3595bb0 
`Vagrantfile`s are configuration files for the [vagrant](https://www.vagrantup.com/) tool, and they are written in Ruby. Even as vagrant [is ported to Go](https://www.hashicorp.com/blog/toward-vagrant-3-0), `Vagrantfile`s [will be written in Ruby](https://developer.hashicorp.com/vagrant/docs/experimental/vagrant_go)

When a Vangrantfile is created, it starts with these lines:

```
```

But since Helix (quite reasonably) doesn't change editor behavior based on file contents, adding this to `languages.toml` seems like a reasonable way to get this functionality.
mtoohey31 pushed a commit to mtoohey31/helix that referenced this pull request Jun 2, 2024
@bcspragu @mtoohey31
Treat 'Vagrantfile' files as Ruby code (helix-editor#7112)
c78ad2b 
`Vagrantfile`s are configuration files for the [vagrant](https://www.vagrantup.com/) tool, and they are written in Ruby. Even as vagrant [is ported to Go](https://www.hashicorp.com/blog/toward-vagrant-3-0), `Vagrantfile`s [will be written in Ruby](https://developer.hashicorp.com/vagrant/docs/experimental/vagrant_go)

When a Vangrantfile is created, it starts with these lines:

```
```

But since Helix (quite reasonably) doesn't change editor behavior based on file contents, adding this to `languages.toml` seems like a reasonable way to get this functionality.
smortime pushed a commit to smortime/helix that referenced this pull request Jul 10, 2024
@bcspragu
Treat 'Vagrantfile' files as Ruby code (helix-editor#7112)
f52d616 
`Vagrantfile`s are configuration files for the [vagrant](https://www.vagrantup.com/) tool, and they are written in Ruby. Even as vagrant [is ported to Go](https://www.hashicorp.com/blog/toward-vagrant-3-0), `Vagrantfile`s [will be written in Ruby](https://developer.hashicorp.com/vagrant/docs/experimental/vagrant_go)

When a Vangrantfile is created, it starts with these lines:

```
```

But since Helix (quite reasonably) doesn't change editor behavior based on file contents, adding this to `languages.toml` seems like a reasonable way to get this functionality.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pascalkuthe pascalkuthe pascalkuthe approved these changes

@the-mikedavis the-mikedavis the-mikedavis approved these changes

Assignees
No one assigned
Labels
A-language-support Area: Support for programming/text languages
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@bcspragu @the-mikedavis @pascalkuthe @kirawi