Cannot write [ in spyder

Cannot write [, only ] bracket, therefore cannot make subsets [ ]. The [ bracket can be written in any other editor (Notepad, Word, …) or consoles (Win Command Prompt, Anaconda Prompt, …) While typing “ALT Gr + F” (which I have to type to get [ symbol ) nothing shows up. Sometimes it seems that Spyder reacts something (hidden) because the software window ‘blinks’ once, but this is not reproducible. In general nothing happens.

Checked Spyder Preferences / Keyboard shortcuts, but could not find such keyboard combination as “ALT Gr + F”.

This error persists since last Anaconda + Spyder update in 2022 January.

Spyder ver 5.1.5 (Python 3.8.8. 64 bit, Qt 5.9.7, PyQt5 5.9.2, Windows 10)

• Reproduced the issue after updating with conda update spyder (Admin mode)
• Reproducable both in the editor and in the console
• Restarted Spyder, several times (after updating, as well)
  • Nothing was modified in preferences, no reset was made… but then I made it accoridng to Basic Troubleshoot guide… not fixed the issue (just have to start setting up my environment again 😦 )
  • Tried the other applicable steps from the Troubleshooting Guide
• Completed the Problem Description, Steps to Reproduce and Version sections below

Paste Traceback/Error Below (if applicable)

### Dependencies

# Mandatory:
atomicwrites >=1.2.0          :  1.4.0 (OK)
chardet >=2.0.0               :  4.0.0 (OK)
cloudpickle >=0.5.0           :  2.0.0 (OK)
cookiecutter >=1.6.0          :  1.7.2 (OK)
diff_match_patch >=20181111   :  20200713 (OK)
intervaltree >=3.0.2          :  3.1.0 (OK)
IPython >=7.6.0               :  7.31.1 (OK)
jedi >=0.17.2;<0.19.0         :  0.18.1 (OK)
jsonschema >=3.2.0            :  3.2.0 (OK)
keyring >=17.0.0              :  23.4.0 (OK)
nbconvert >=4.0               :  6.1.0 (OK)
numpydoc >=0.6.0              :  1.2 (OK)
paramiko >=2.4.0              :  2.8.1 (OK)
parso >=0.7.0;<0.9.0          :  0.8.3 (OK)
pexpect >=4.4.0               :  4.8.0 (OK)
pickleshare >=0.4             :  0.7.5 (OK)
psutil >=5.3                  :  5.8.0 (OK)
pygments >=2.0                :  2.11.2 (OK)
pylint >=2.5.0;<2.10.0        :  2.9.6 (OK)
pyls_spyder >=0.4.0           :  0.4.0 (OK)
pylsp >=1.2.2;<1.3.0          :  1.2.4 (OK)
pylsp_black >=1.0.0           :  None (OK)
qdarkstyle =3.0.2             :  3.0.2 (OK)
qstylizer >=0.1.10            :  0.1.10 (OK)
qtawesome >=1.0.2             :  1.0.3 (OK)
qtconsole >=5.1.0             :  5.2.2 (OK)
qtpy >=1.5.0                  :  1.11.2 (OK)
rtree >=0.9.7                 :  0.9.7 (OK)
setuptools >=49.6.0           :  58.0.4 (OK)
sphinx >=0.6.6                :  4.4.0 (OK)
spyder_kernels >=2.1.1;<2.2.0 :  2.1.3 (OK)
textdistance >=4.2.0          :  4.2.1 (OK)
three_merge >=0.1.1           :  0.1.1 (OK)
watchdog >=0.10.3             :  2.1.6 (OK)
zmq >=17                      :  22.3.0 (OK)

# Optional:
cython >=0.21                 :  0.29.25 (OK)
matplotlib >=2.0.0            :  3.5.0 (OK)
numpy >=1.7                   :  1.20.3 (OK)
pandas >=1.1.1                :  1.3.5 (OK)
scipy >=0.17.0                :  1.7.3 (OK)
sympy >=0.7.3                 :  1.9 (OK)

[jablka]

ah, now I understand. Yes, you are right, the @ sign was there too. Ok, I will open up a new issue. Thanks

[dalthviz]

Checking a little bit I think the problem is that we have Ctrl+Alt+P (which is equivalent to pressing AltGr+P) as a shortcut for the Symbol finder by default (which is the File Switcher instance with the @ command prefiled when launched), so that default shortcut will need to be changed to prevent the issue (probably in general we will need to do a review for Ctrl + Alt shortcuts to prevent it to collide with typing characters).

Anyhow, could you please open a new issue so we can continue the discussion there, please?