-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
keyval completion starts from wrong letter if on new line #3966
Comments
can't reproduce on linux |
Could it be a line ending issue in the keyval completion code? I know windows and linux/mac do line endings differently |
can't confirm on win11 (4.8.6rc1) |
Hmm then it's probably related to my specific settings. This has been an annoyance for me for a long time so I'd really like to figure it out. Unfortunately changing my completion settings to the defaults shown in https://texstudio-org.github.io/configuration.html#configuring-the-autocompletion did not fix the issue. |
I checked with completion (all) instead of completion (typical), but no difference |
Same. I've tried changing a bunch of settings but nothing seems to fix it. Not sure where to go from here. If nothing can be done, I guess the issue can be closed. |
@octaeder Thanks for confirming.
What do you mean by this? |
Ah and sorry, I forgot this is a Windows 10 computer I'm on. I will change the issue description. |
I thought I never used the package so it should not be installed by MikTeX. But it says I installed it last November. I think there was another issue with this package and it seems that I made a build of the pdf. Anyway, I wasn't sure if this might make a difference. |
I just tried on a Windows 11 machine and the issue is still there. |
@octaeder I think that needs a new issue. But interestingly it doesn't happen with keyvals that have more than one letter, e.g. typing \documentclass{article}
\usepackage{tikz}
\begin{document}
\begin{tikzpicture}[xshift]
content...
\end{tikzpicture}
\end{document} |
space or tab is the point ... |
side effect of 7ec5dd8 |
Environment
Related: #3962
Expected behavior
When autocompleting keyvals, it should match the entire typed string.
Actual behavior
If the keyval is on a new line, it does not. It starts from the immediately preceding letter.
Here I've typed only the letter
i
, hit Ctrl+Space, and the completion list is as expected.But after typing
in
and hitting Ctrl+Space, the completion list matches keyvals starting withn
, notin
as expected.The expected behavior does occur if the keyval is on the same line as the command.
How to reproduce
Place cursor after
in
and hit Ctrl+Space.I've confirmed the issue on both Windows 10 and 11 machines.
The text was updated successfully, but these errors were encountered: