-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Run config editor freezes when WSL bash asks for user input #1680
Comments
I cannot reproduce the problem on Windows with 0.7.1 in CLion. I don't know what the problem could be. What happens if you create a run configuration from context, using ctrl+shift+F10 or the gutter icon next to \begin{document}? As that is the intended way to create run configurations. You can also try a different IDE like IntelliJ, then we know if it's CLion specific or not. |
I also checked with IDEA Ultimate 2020.2.3 and Texify 0.7.0, where I also see the same freeze when creating a new configuration. Additional information: |
Ok, so apparently there is something unusual in your system that TeXiFy can't handle. How did you install TeX Live on Windows? Can you check in the terminal if You could also try installing the latest alpha version, because I think I did make some relevant changes, but I doubt it will help (will need IntelliJ 2020.3 if you also want to try it in IntelliJ). |
Okay, I've narrowed it down. I have keychain in my |
Apparently TeXiFy cannot detect any native LaTeX installation on your system (using [Edit] I do see a timeout being set on |
This works both with powershell and cmd. Edit:
worked fine too, so I suspect that checking if texlive is in WSL is done always, and not only if Texlive is not found on windows PATH? |
Yes we do that in order to show you the available options for LaTeX installations in the run config dropdown. But apparently the timeout is not working correctly, I will try to reproduce that.
[Edit] I can reproduce the problem now, thanks! |
Using 0.7.2-alpha5 I can still reproduce the problem.
great, thanks for your quick replies! |
Can you check if the following build resolves the problem? Opening the run config editor will be a bit slow only the first time. |
Using the zip you provided I observed the following:
So yes, this fixes my issue. Depending on how much effort it is I guess it would be nice if texify would close the wsl session again (buts thats really a minor issue I guess). |
Good point, I did not test it but this should do that: |
I tested the new zip, but the behaviour didn't change compared to the last one. |
Type of JetBrains IDE (IntelliJ, PyCharm, etc.) and version
CLion 2020.3
Build #CL-203.5981.166, built on December 1, 2020
Runtime version: 11.0.9+11-b1145.21 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1987M
Cores: 12
Registry: run.processes.with.pty=TRUE
Non-Bundled Plugins: nl.rubensten.texifyidea, org.toml.lang, org.rust.lang
Operating System
Windows
TeXiFy IDEA version
0.7.1
What I did (steps to reproduce)
3.a Select LaTeX from the list of templates
3.b Click
+
and select LaTeXBoth 3.a and 3.b cause the window to freeze. It can still be resized, but it does not react to any clicks or Alt-F4.
Text/images dissappear if the window is resized to the smallest possible and then resized back to the previous size, i.e. the portions become blank.
Other Templates such as Makeindex do not cause this.
Clion must then be force closed via Task manager since it does not recover.
I haven't used Texify Idea in a while so I can't say for sure if this is a new issue.
The text was updated successfully, but these errors were encountered: