I'm curious if someone has made a Serde like serializer/deserializer for emacs-module-rs or if that's something that might be possible to implement?

Provides a fix for #34 . This will remain in a draft state until I can import this repo into travis-ci.com.

Closing this based on the discussion in #34.

A new PR will be opened once #40 is solved.

Travis CI is failing.

Example failure: https://travis-ci.org/github/emacsorphanage/terraform-mode/builds/741800912

Closing this since we're migrating away from Travis. #40 supersedes this issue.

After the discussion in #34 we want to migrate to Github Actions. This issue supersedes #34.

Github Actions should test incoming code in a similar manner that was done with Travis.

More links:

• https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
• https://www.theregister.com/2020/11/02/travis_ci_pricng

If we want to move to Github Actions I can investigate that instead of Travis.

Please do that. I'll start investigating myself soon too.

travis-ci.org is shutting down on 12/31/2020.

If we want to move to Github Actions I can investigate that instead of Travis.

This application will be able to read and write all public and private repository data.

This is not gonna happen.

Currently the build is based on travis-ci.org which is shutting down.

But it still works right now? (Until when?)

I am comfortable with the permissions requested by travis-ci.org as it doesn't want access to private repositories.

In the long run I think we should migrate to Github Actions instead.

Travis CI is failing.

Example failure: https://travis-ci.org/github/emacsorphanage/terraform-mode/builds/741800912

Thanks for setting that part up.

I've run into one more issue. Since I'm not an org member, I cannot see/configure repos under emacsorphanage in Travis. Would it be possible to become an org member or have an org member configure the build?

Should work now.

I was able to send a request for access. It looks like its pending approval from the org owners:

Provides a fix for #34 . This will remain in a draft state until I can import this repo into travis-ci.com.

I have given you temporary admin rights for this repository only. If that isn't enough, then I will have to make the changes for you and would appreciate it if you could guide me through the process.

@tarsius I requested access to the emacsorphanage org to integrate travis-ci.com.

Currently the build is based on travis-ci.org which is shutting down.

@googlebot I signed it!

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

<!-- need_sender_cla -->

This patch does the following.

1. Use when instead of if
2. Fixed indentation

It seems not obvious as how to compile the example at the tip. I managed to do it by:

sed 's/~rest:`Log//' -i **/*.ml
mv example/dune{.example,}
dune build example/hello_world.so
emacs -Q -L _build/default/example --batch --eval "(progn (require 'hello_world) (say-hello \"emacs\"))"

I suspect that an alternative would be to run v0.14 to compile against the async that's in opam so that I wouldn't need to drop rest. What's the recommended way of running those at home?

Data in imenu comes with quotation marks.