Bug 187120

Summary:	New line not working in Kopete with Qt-4.5
Product:	[Applications] kopete	Reporter:	Alberto Gonzalez <luis6674>
Component:	Chat Window	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	doochik, kde_bugzilla_2, martin.batora
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:

Description Alberto Gonzalez 2009-03-14 10:44:49 UTC

Version:           4.2.1 (using KDE 4.2.1)
Compiler:          GCC-4.3.3 
OS:                Linux
Installed from:    Unspecified Linux

After upgrading to Qt-4.5, I cannot start a new line in Kopete's message window. It used to work with Ctrl+return, but now it stopped working.

I don't know if it's a Kopete bug or a Qt one, or just some configuration change. If you think I should report it to Qt please let me know.

Comment 1 Rasto Stanik 2009-03-26 10:20:00 UTC

A new line can be entered in chat window by pressing the Enter key on the numeric keypad. However I would also prefer to have Ctrl+Enter available.

Comment 2 Matt Rogers 2009-03-29 20:25:44 UTC

oh, that is annoying.

Comment 3 martin batora 2009-04-10 14:36:46 UTC

hi!
shift + enter works for me

Comment 4 Alberto Gonzalez 2009-04-10 14:58:40 UTC

Aha, shift + enter does work here too. So it seems it was a configuration change in QT and not a bug? Go figure why they changed it, but anyway thanks for the tip. Maybe the bug can be closed, but it would be nice to document the change somewhere, no?

Comment 5 Stephan Sokolow 2009-05-03 08:51:10 UTC

Keep the bug open. If necessary, add an explicit "Insert newline" entry in the shortcuts dialog which I can set to Ctrl+Enter, but I don't consider Shift+Enter to be a solution worthy of RESO.

If I was OK with all my apps having unconfigurable, potentially mutually-incompatible keybindings, I'd use GNOME as my desktop, emacs as my code editor, Firefox as my main browser, and I'd give up on ever enjoying the efficiency that muscle memory can bring.

Comment 6 Justin Zobel 2021-03-09 22:40:50 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 7 Alberto Gonzalez 2021-03-09 22:48:12 UTC

After 12 years I guess it can certainly be closed.