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

Wrong autocompletion in multi-select mode #6

Open
lorenmt opened this issue May 8, 2015 · 3 comments
Open

Wrong autocompletion in multi-select mode #6

lorenmt opened this issue May 8, 2015 · 3 comments
Labels

Comments

@lorenmt
Copy link

lorenmt commented May 8, 2015

Using the multiselction mode, the autocompletion with the "begin-end" section will become a little bit weird.
Example code:
\begin{align*
\end{align_}}
\begin{align_
\end{align*}}

I guess the main problem is the code does not auto complete the brackets in the multi-selection mode.
Everything else is pretty good!

@Focus
Copy link
Owner

Focus commented May 12, 2015

Hi, thanks for submitting the report. Could you please clarify which bits are the bits that you are typing and which parts does the program autocomplete?

@lorenmt
Copy link
Author

lorenmt commented May 12, 2015

Typing:
\begin{align_} [I usually typed the brackets first, then the environment name, in multiselection mode]
\begin{align_}

Autocomplete[should've] :
\begin{align_}
\end{align_}
\begin{align_}
\end{align_}

After Autocomplete[in reality]:
\begin{align*
\end{align_}}
\begin{align_
\end{align*}}

Problem would not occur if typing directly like { align } rather than {} <- align*

Also: Autocomplete in environment name will not occur if I click enter twice (fast).
For example: [should've]
\begin{align*}

\end{align*}

In reality:
\begin{align*}
[enter]
[enter]

Hope I clarify your confusion. :D

@Focus
Copy link
Owner

Focus commented May 13, 2015

Thanks. I can confirm the bug. This happens because the program checks the line above for a unmatched environment. I didn't really think about multiselection mode.

@Focus Focus added the bug label May 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants