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

Intim errors while opening tex file #1

Closed
alaindanet opened this issue Oct 27, 2017 · 2 comments
Closed

Intim errors while opening tex file #1

alaindanet opened this issue Oct 27, 2017 · 2 comments
Assignees

Comments

@alaindanet
Copy link
Contributor

last_screen_shot

Cette erreur survient avec lorsque j'essaie d'ouvrir un fichier tex avec lusty-explorer, mais pas tout le temps.
Je n'arrive pas à la reproduire régulièrement, cependant cette erreur ne me gène pas du tout

@iago-lito
Copy link
Owner

Hmm, you say it seems to be a conflict between lusty-explorer package and intim while opening a .tex file.

Based on your screenshot, I have tried

  • installing lusty-explorer
  • creating two dummy files presentation.md and main.tex next to each other
  • compiling main.tex with pdflatex
  • opening presentation.md with vim
  • using <header>lf to launch lusty-explorer interface
  • entering main.tex<cr> to select the other file

.. but I cannot reproduce the problem :\

Do you have any mappings defined in your .vimrc that would conflict with any of the defaults listed at :help intim-default-hotkeys<cr>? This shouldn't be a problem, but who knows..
Can you describe more accurately the steps that lead you to this error?


Also, in order to provide native errors on your screenshots, please set your locale environment language to english. This is typically just a matter of

LANG=en_US.UTF-8 vim presentation.md

It's just temporary and it'll be set back to your own language once the command returns ;)

@alaindanet
Copy link
Contributor Author

Sorry, I could not find the pattern for this bug. But it has disappeared! Thank you so much for your help!

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

No branches or pull requests

2 participants