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

Aggressive Autocomplete, Specific Example #3021

Closed
alecloudenback opened this issue Sep 12, 2024 · 3 comments · Fixed by #3055
Closed

Aggressive Autocomplete, Specific Example #3021

alecloudenback opened this issue Sep 12, 2024 · 3 comments · Fixed by #3055
Labels

Comments

@alecloudenback
Copy link

ref #3008, opening a new issue as requested

I have also found the autocomplete to be very aggressive.

Example: I am trying to define a new function called foo and I type foo( and upon hitting ( the input autocompletes to floor(

Screen.Recording.2024-09-12.at.1.48.59.PM.mov

Pluto 0.19.46

Julia Version 1.11.0-rc3
Commit 616e45539db (2024-08-26 15:46 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: macOS (arm64-apple-darwin22.4.0)
  CPU: 8 × Apple M3
  WORD_SIZE: 64
  LLVM: libLLVM-16.0.6 (ORCJIT, apple-m3)
Threads: 4 default, 0 interactive, 2 GC (on 4 virtual cores)
Environment:
  JULIA_NUM_THREADS = auto
  JULIA_REVISE_WORKER_ONLY = 1
@Pangoraw Pangoraw added the autocomplete <TAB> label Sep 12, 2024
@christiangnrd
Copy link
Contributor

I am also experiencing this quite frustrating issue.

@lukeburns
Copy link

lukeburns commented Oct 1, 2024

Hard to use. If I type f(x) = x, Pluto autocompletes to factorial(x) = x. ( should not be a trigger for autocompletion.

@fonsp
Copy link
Owner

fonsp commented Oct 14, 2024

Thanks for the feedback! I disabled the ( autocomplete commit character in #3055

@fonsp fonsp closed this as completed Oct 14, 2024
@fonsp fonsp linked a pull request Oct 14, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants