CTRL-S does not save file, if pop-up menu is open

[sphh]

Issue Report Checklist

• Searched the issues page for similar reports
• Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
• Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
• Could not reproduce inside jupyter qtconsole (if console-related)
• Tried basic troubleshooting (if a bug/error)
  • Restarted Spyder
  • Reset preferences with spyder --reset
  • Reinstalled the latest version of Anaconda
  • Tried the other applicable steps from the Troubleshooting Guide
• Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

During the debugging cycle, I sometimes only want to change a tiny detail in a file. When doing this, the command completion menu opens and when I press CTRL-S to save the file, the file is not saved. I first have to dismiss the pop-up menu and then I can save the file.

What steps reproduce the problem?

1. Open a file.
2. Move to a position, where the command completion menu opens and wait for it to pop up.
3. Press CTRL-S to save the file.

What is the expected output? What do you see instead?

I would like the file to be saved immediately when pressing CTRL-S, even if a pop-up menu is open, but the file is not saved.

Versions

• Spyder version: Spyder 4.2.2
• Python version: Python 3.8.5 64-bit
• Qt version: Qt 5.12.9
• PyQt version: PyQt5 5.12.3
• Operating System name/version: Linux 5.10.13-surface

Dependencies

# Mandatory:
atomicwrites >=1.2.0            :  1.4.0 (OK)
chardet >=2.0.0                 :  4.0.0 (OK)
cloudpickle >=0.5.0             :  1.6.0 (OK)
diff_match_patch >=20181111     :  20200713 (OK)
intervaltree >=3.0.2            :  3.1.0 (OK)
IPython >=7.6.0                 :  7.20.0 (OK)
jedi =0.17.2                    :  0.17.2 (OK)
jsonschema >=3.2.0              :  3.2.0 (OK)
keyring >=17.0.0                :  22.0.1 (OK)
nbconvert >=4.0                 :  6.0.7 (OK)
numpydoc >=0.6.0                :  1.1.0 (OK)
parso =0.7.0                    :  0.7.0 (OK)
pexpect >=4.4.0                 :  4.6.0 (OK)
pickleshare >=0.4               :  0.7.5 (OK)
psutil >=5.3                    :  5.5.1 (OK)
pygments >=2.0                  :  2.8.0 (OK)
pylint >=1.0                    :  2.7.0 (OK)
pyls >=0.36.2;<1.0.0            :  0.36.2 (OK)
pyls_black >=0.4.6              :  0.4.6 (OK)
pyls_spyder >=0.3.2             :  0.3.2 (OK)
qdarkstyle >=2.8                :  2.8.1 (OK)
qtawesome >=0.5.7               :  1.0.2 (OK)
qtconsole >=5.0.1               :  5.0.2 (OK)
qtpy >=1.5.0                    :  1.9.0 (OK)
setuptools >=39.0.0             :  53.0.0 (OK)
sphinx >=0.6.6                  :  3.5.0 (OK)
spyder_kernels >=1.10.2;<1.11.0 :  1.10.2 (OK)
textdistance >=4.2.0            :  4.2.1 (OK)
three_merge >=0.1.1             :  0.1.1 (OK)
watchdog >=0.10.3;<2.0.0        :  1.0.2 (OK)
xdg >=0.26                      :  0.26 (OK)
zmq >=17                        :  22.0.3 (OK)

# Optional:
cython >=0.21                   :  None (NOK)
matplotlib >=2.0.0              :  3.3.4 (OK)
numpy >=1.7                     :  1.20.1 (OK)
pandas >=1.1.1                  :  1.2.2 (OK)
scipy >=0.17.0                  :  1.6.1 (OK)
sympy >=0.7.3                   :  1.7.1 (OK)

[steff456]

Hi @sphh,

I could reproduce this issue, we will work towards enhancing this in one of our future releases.

Thanks for reporting!

[ccordoba12]

I've been bitten by this multiple times! So I totally agree we need to fix it and we'll try to do it in 5.0.1 or 5.0.2.

[mhechthz]

It is now 24th of February 2022 and the problem still remains with Spyder 5.2.2 :-(

[mhechthz]

Excellent! :-)

[sphh]

Thanks @dalthviz and @ccordoba12!