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

Error using arara as compiler-method #2861

Closed
mms-neuro opened this issue Jan 1, 2024 · 5 comments · Fixed by #2862
Closed

Error using arara as compiler-method #2861

mms-neuro opened this issue Jan 1, 2024 · 5 comments · Fixed by #2862
Labels

Comments

@mms-neuro
Copy link
Contributor

mms-neuro commented Jan 1, 2024

Description

Using arara as a compile_method suddenly broke down a few months ago. :VimtexCompile now results in an error - on different computers with different tex-files.

Steps to reproduce

Somehow, github does not like .vim/.tex files (anymore?).
So here the content:

cat minimal.tex

% arara: lualatex
\documentclass{minimal}
\begin{document}
Hello world!
\end{document}

cat minimal.vim

filetype plugin indent on
syntax on
call plug#begin('~/.vim/plugged')
Plug 'lervag/vimtex'
let g:vimtex_compiler_method = 'arara'
call plug#end()

arara has version 7.0.4 (latest on Fedora 38, but not latest in general).

Steps to reproduce:

  1. Run nvim -u minimal.vim minimal.tex in bash
  2. Execute :VimtexCompile in neovim.

Expected behavior

Document compiles using arara.

Actual behavior

The following error is raised immediately:

Fehler beim Ausführen von "function vimtex#compiler#compile[6]..vimtex#compiler#start[17]..38[10]..52":
Zeile    1:
E714: List benötigt

Sorry - I couldn't change the language from German to English. The translation is:

Error while executing "function vimtex#compiler#compile[6]..vimtex#compiler#start[17]..38[10]..52":
Line   1:
E714: List required
  • Calling arara directly in neovim (:!arara %) works perfectly fine.
  • Changing the compile-method to latexmk (let g:vimtex_compiler_method = 'latexmk') results also in error-free behaviour.

Do you use a latexmkrc file?

No

VimtexInfo

System info:
  OS: Fedora release 38 (Thirty Eight)
  Vim version: NVIM v0.9.4
  Has clientserver: true
  Servername: /run/user/1000/nvim.56974.0

VimTeX project: minimal
  base: minimal.tex
  root: /home/matthiasms
  tex: /home/matthiasms/minimal.tex
  main parser: current file verified
  document class: minimal
  compiler: arara
    options:
      --log
  viewer: General
  qf method: LaTeX logfile
@mms-neuro mms-neuro added the bug label Jan 1, 2024
@muwizayeon
Copy link

muwizayeon commented Jan 2, 2024

I have the same situation here with my own LaTeX files.

VimtexInfo

System info:
  OS: Ubuntu 22.04.3 LTS
  Vim version: NVIM v0.10.0-dev-2000+g6fa0f303d
  Has clientserver: true
  Servername: /run/user/1001/nvim.31564.0

VimTeX project: syllabus_main
  base: syllabus_main.tex
  root: /home/muwizayeon/Projects/UCM/dsa5200/syllabus
  tex: /home/muwizayeon/Projects/UCM/dsa5200/syllabus/syllabus_main.tex
  main parser: current file verified
  document class: article
  source files:
    syllabus_main.tex
    title_page.tex
  compiler: arara
    options:
      --log
  viewer: General
  qf method: LaTeX logfile

The actual behavior is the same as the ones @mms-neuro. What I found is that

  • the function join in call b:vimtex.compiler.start(expandcmd(join(a:000))) of vimtex#compiler#start(...) in compiler.vim returns an error E714: List required even though a:000 is the empty list.

I am not familiar with the Vimtex script, so it is only what I figured out now.

@mms-neuro
Copy link
Contributor Author

Thanks for the tip!

I think the problem comes from 06e1767 which makes also sense time-wise.

The problem ist the join(a:opts) in

\ . ' ' . join(a:opts)
- removing the join to a:opts (as is done for the other compile methods) solves the problem for me.

@mms-neuro
Copy link
Contributor Author

I created a pull request which should fix the problem.

lervag added a commit that referenced this issue Jan 2, 2024
@lervag
Copy link
Owner

lervag commented Jan 2, 2024

Thanks! And sorry for introducing this bug; clearly an oversight by me during an earlier refactoring.

@mms-neuro
Copy link
Contributor Author

No worries - thanks for the amazing software and the effort you put into it!

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

Successfully merging a pull request may close this issue.

3 participants