Autocomplete normal words

[proteusGIT]

It would be great if "ctrl+space" would suggest word completions based on all tex-files in the current project (at least the current tex-file).

[PHPirates]

Does this Hippie completion work for you? https://www.jetbrains.com/go/guide/tips/cyclic-expand-word/ (You can rebind to a different key combination)

https://www.jetbrains.com/help/idea/auto-completing-code.html#hippie_completion

[proteusGIT]

This somewhat improves the situation for me.
However, this feature does not list the options in the way "ctrl+space" does.
Also, it requires a different shortcut.
Lastly, I would like to mention that "ctrl+space" just works in java comments.

[PHPirates]

However, this feature does not list the options in the way "ctrl+space" does.

Indeed it doesn't, because it's not smart autocompletion. But this is built into IntelliJ, so you have to submit an issue at https://youtrack.jetbrains.com if you want it changed.

Also, it requires a different shortcut.

You can rebind shortcuts, see Settings > KeyMap.

Lastly, I would like to mention that "ctrl+space" just works in java comments.

No, it also works in Java code. In fact, it works like almost everywhere, just in a lot of cases there are no suggestions.

[proteusGIT]

I meant that I would need a shortcut different from "ctrl+space". Changing the shortcut is not the problem.

With the statement on the completion in java comments, I merely wanted to point out that the desired kind of completion works e.g. in java comments but it also works in e.g. txt files. I was just wondering why this feature seems to be disabled/broken/overridden in texify.

[proteusGIT]

Could there maybe be an option for disabling the TeXiFy specific completion mechanism?
Completion of commands and words as in all other files is ok for me.

[PHPirates]

I think you can disable the default code completion with Settings > Editor > General > Code completion > Show suggestions as you type

[proteusGIT]

Well, I do like the normal intelliJ "Basic Completion" (CTRL+SPACE).
I would just like to ensure that TeXiFy does not tamper with that mechanism as its custom support for LaTeX macros breaks the support for normal words.

[PHPirates]

You can disable Live Templates as well, in Settings > Editor > Live Templates then unselect the LaTeX group

[proteusGIT]

I did this already :)
However, the standard "Basic Completion" still does not work.

[proteusGIT]

If I have a tex-file with the content

FooBar
FooBaz

Foo

and I press CTRL+SPACE after the last Foo, I get no suggestions.
Doing the same in a txt file, I get FooBar and FooBaz as suggestions.

[PHPirates]

If I understand correctly, you do not regard a suggestion by Cyclic expand word as a suggestion, but only a suggestion via Basic Completion using the popup. To be honest, I don't really understand why you think the Cyclic expand work suggestion not good enough: to me it clearly suggests words, and you have to press just as much keys.

I'm not sure it is a good idea to make an opt-in setting for such Basic completion on words, because we would have to be very careful that it does not hurt the performance if not switched on, and I'm not convinced that we should try to re-implement Cyclic expand word. If you think the UI experience of Cyclic expand word can be improved, contact Jetbrains.

[proteusGIT]

I fixed it on my system by removing the following from the plugin.xml

      <lang.parserDefinition language="Latex" implementationClass="nl.hannahsten.texifyidea.LatexParserDefinition"/>

I do not know what the parser is intended for but it (or something else once the parser is established) breaks the completion functionality.

[proteusGIT]

"Cyclic expand word" does not currently provide the functionality of showing suggestions and it also requires that a LaTeX specific key combination is used. I would rather not use IntelliJ oder texify but (as mentioned in the previous post) I have fixed it for me.

[proteusGIT]

Well, too bad that commenting is broken with the change above. :-(