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

init.lua does not work properly #18

Closed
wqferr opened this issue Jul 23, 2019 · 0 comments · Fixed by #19
Closed

init.lua does not work properly #18

wqferr opened this issue Jul 23, 2019 · 0 comments · Fixed by #19

Comments

@wqferr
Copy link
Contributor

wqferr commented Jul 23, 2019

The image below exemplifies the issue.

The require call in (1) shows the cloned directory name is not the issue.

issue-img

The require call in (2) fails not because it can't find the init.lua file, but due to an error inside it. The call to str.match with the file arguments is incorrect. ... contains two values: first the string used in require (which corresponds to the directory cloned directory, in this case), and the relative path of the init file.

A simple solution is to rewrite the init.lua file so as to use the first argument as it is.

image

I have already created a pull request and linked it to this issue.

@wqferr wqferr mentioned this issue Jul 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant