Bug 278610 - net-im/gomuks: backspace erases entire words
Summary: net-im/gomuks: backspace erases entire words
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Emanuel Haupt
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-27 13:20 UTC by tr
Modified: 2024-04-29 08:18 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (ehaupt)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tr 2024-04-27 13:20:55 UTC 
When composing a message, if backspace is pressed, the entire last word is erased (up until the closest whitespace)

If Ctrl+Backspace is pressed, only one character is erased, this should be the default behavior?
Comment 1 Emanuel Haupt freebsd_committer freebsd_triage 2024-04-27 18:56:49 UTC 
Could you please open an issue at https://github.com/tulir/gomuks/issues with the upstream project?
Comment 2 tr 2024-04-28 09:45:32 UTC 
Done.
Comment 3 Emanuel Haupt freebsd_committer freebsd_triage 2024-04-28 12:31:07 UTC 
Thank you.

For reference:
https://github.com/tulir/gomuks/issues/322
https://github.com/tulir/gomuks/issues/457
Comment 4 Emanuel Haupt freebsd_committer freebsd_triage 2024-04-28 17:09:22 UTC 
I've tested the "implied" solution in https://github.com/tulir/gomuks/issues/322.

Setting backspace1_removes_word to false in ~/.config/gomuks/config.yaml changes the behavior for me. Does that work for you?
Comment 5 tr 2024-04-29 07:55:05 UTC 
(In reply to Emanuel Haupt from comment #4)

This fixed it. I feel silly not looking into the config file before, but the documentation didn't mention this anywhere.

Many thanks.
Comment 6 Emanuel Haupt freebsd_committer freebsd_triage 2024-04-29 08:18:30 UTC 
To be fair, I probably wouldn't expect there to be a config option for such behavior. Defaulting backspace to deleting entire words by default seems a bit unorthodox to me. Thank you for reporting back.