Re-compiled the file engines - #241
Merged
Merged
Conversation
Merged
Member
|
This looks great! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
tl;dr: The file engine binary was failing on macOS 10.15, and the outdated version of the Go compiler was a likely culprit: the recompiled binaries are in this PR, as well as binaries for MIPS architectures.
Hi everyone, hi @cometsong,
Nice work doing this extension! :D
As soon as I installed CtrlSpace though, it started to dysfunction when I wanted to look at the file list. After digging a little, I realized that the
file_enginethat was in the binary folder was crashing over and over again. See the enclosed error messages for more detail.After looking around at what the error messages meant, it dawned on me that the version of Go that was used to compile the engine — 1.5.1, per the error messages — was severely outdated: I could go nowhere if I didn't recompile the engine to a newer version first.
And so I did, and now the engine works as intended! I'm surmising that the newest versions of macOS that have shipped in the mean time — I am running Catalina — have made some Go programs nonoperational.
Anyway, here are the two following pull requests:
file_engine_binaries(File engine binaries #240): I recompiledfile_engine.gowith go 1.13, and with the newest stable version of gox. This yielded a few more binaries than usual, notably Linux computers running on MIPS chips. I included them in addition to the recompiled binaries.master(this PR): the four main binaries are recompiled with the newest go toolchain, and I adjusted the documentation to account for the new MIPS binaries.Error Messages
In both cases, I went around the error messages inside vim by manually doing the work of this line in
engine.vim:So I generated the
contextstring, and passed it to thefile_enginebinary. Here are the two results I was getting over and over again.