Author Topic: damaged Linux settings  (Read 8766 times)

Offline rpirpag

  • Single posting newcomer
  • *
  • Posts: 8
damaged Linux settings
« on: December 01, 2021, 02:36:56 pm »
Hello,
I think I have damaged my editor settings.

I can not add / or use Strg-c/v, or delete something in the IDE.

e.g. add a / opens a pop-up with instead of of adding /.

In the past all keys are working.

Please help me.

Thank you,
Reinhard

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1553
Re: damaged Linux settings
« Reply #1 on: December 01, 2021, 07:08:59 pm »
You can try disabling the "Keyboard shortcuts" plugin or renaming the default.conf file (it should be in a hidden folder under your home directory) forcing C::B to create a fresh one.

Offline rpirpag

  • Single posting newcomer
  • *
  • Posts: 8
Re: damaged Linux settings
« Reply #2 on: December 02, 2021, 09:40:55 am »
I tried your suggestion but the problem still exist.

I use here V 16.01
« Last Edit: December 02, 2021, 09:44:04 am by rpirpag »

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1553
Re: damaged Linux settings
« Reply #3 on: December 02, 2021, 04:13:29 pm »
What happens if you press / in a console, text editor or web browser?

Offline rpirpag

  • Single posting newcomer
  • *
  • Posts: 8
Re: damaged Linux settings
« Reply #4 on: December 03, 2021, 09:12:54 am »
Only Codeblocks has the problem, LibreOffice and other are working.

Offline cacb

  • Lives here!
  • ****
  • Posts: 536
Re: damaged Linux settings
« Reply #5 on: December 03, 2021, 01:32:16 pm »
Maybe you can try this (not guaranteed to work):

Exit Code::Blocks

Back up ~/.config/codeblocks/default.cbKeyBinder20.conf  and remove or rename the original

Restart Code::Blocks and see if the shortcuts are working. If not, restore the backed up file and look for other solutions

Offline rpirpag

  • Single posting newcomer
  • *
  • Posts: 8
Re: damaged Linux settings
« Reply #6 on: December 04, 2021, 04:43:24 pm »
Hello,

I found out the problem: The *.cpp file I want to edit was read only. If I set it to writeable it works.
For me is this a very strange behavior of C::B. My Linux is Debian 10.

Can someone explain?
« Last Edit: December 08, 2021, 10:38:44 am by rpirpag »