Closed gucci-on-fleek closed 3 years ago
It seems like the job.files.run(...)
function will only run context
and not arbitrary programs now. The original commit causes tons of errors if the highlighted text is invalid ConTeXt. I was using a test file that only contained valid TeX commands, so I didn't notice that it was running context
on the highlighted text in the background.
However, just removing the code that calls this function seems to fix the error. This code probably was doing something before, so this will likely cause errors somewhere else, but I haven't noticed any problems when testing it with some fairly complex documents.
Thank you for the bug report and patch. I am on vacation and will look at it when I am back. However, I don't think that simply removing jobs.files.run
is the way to go as that function is responsible for caching the content. So, if we remove that caching will not work.
The change that caused this has been reverted in context upstream (see https://github.com/contextgarden/context-mirror/commit/d3d93bc4f0d21a259fdafee5ba1a744999474c28#diff-0aac9f9e71a36725439103dfcc9110e42ff63722bca66c4deec2c9d49baedb99R93), so this will be fixed automatically at the next release.
The error is now fixed with the latest release of ConTeXt, so I am closing this issue. Thank you for reporting and tracking down the error which made it easy to fix.
The
vim
module is broken in the most recent (2021.08.06) LMTX beta. It fails with the following message:The recent ConTeXt Beta (LMTX 2021.08.04) changes the signature of the Lua function
job.files.run
. It now takes a table instead of a string and a table.This PR duplicates
t-filter.mkiv
intot-filter.mkxl
, then changes line 461 to use the newjob.files.run
signature.