| Summary: | kmail external editor behaviour | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | colm |
| Component: | composer | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bjoern, gtwilliams, kollix, rjvbertin, roman.cheplyaka, tonyp |
| Priority: | NOR | ||
| Version: | 4.9 pre | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kdepim/c4ffca8a53bade9ada0652c48978c5b295411112 | Version Fixed In: | 4.10.3 |
| Sentry Crash Report: | |||
|
Description
mepk
2001-05-15 12:20:55 UTC
*** Bug 24865 has been marked as a duplicate of this bug. *** I would like to add my 2 cents worth here. I setup kmail to use the external editor, and tryed to send a new message. To me it appeared that the external editor function didn't work. I wasn't until I found this bug that I realized I had to type in the composer window to get my exteral editor to come up. This is VERY wierd behavior and should be fixed. Replaced mepk@c64.org with colm@tuatha.org due to bounces by reporter Comment #2 is absolutely right. I thought it was broken until I looked it up in the documentation. Really weird behaviour. You're all right, the current behavior is weird. For me the most bugging thing is that the external editor is _always_ launched, even if you don't need it. So I propose a solution in Bug/Wish #127817. Feel free to vote. Argh, solution is in Bug #127817. (The "/Wish" prevented bugzilla from automatically creating the link.) First, make it configureable, "Always use external editor" or "Use external editor only when told" or something like that Secondly, make sure that there is a hot key or short-cut key for starting the external editor. (Make that configurable as well.) That way if someone is in "Only when told" mode and they are editing a message they thought would be quick, and later decide to use the external editor, they just hit a hot key and the editor starts up. (With the already edited message.) Don't force the use of a menu. (Although that should be there as well.) That's my vote. I consider having to click in the composer window a bug. A bug that is still valid. Report still valid in kmail2, KDE 4.9RC1 Git commit c4ffca8a53bade9ada0652c48978c5b295411112 by Montel Laurent. Committed on 17/04/2013 at 09:10. Pushed by mlaurent into branch 'KDE/4.10'. Fix Bug 25755 - kmail external editor behaviour FIXED-IN: 4.10.3 (waou bug reported in 2001...) M +1 -2 kmail/kmcomposewin.cpp M +7 -0 messagecomposer/kmeditor.cpp M +2 -0 messagecomposer/kmeditor.h http://commits.kde.org/kdepim/c4ffca8a53bade9ada0652c48978c5b295411112 (In reply to mepk from comment #0) > Whenever I want use the external editor in kmail (emacs %f) the > composer starts and I have to click inside the text area _and_ > _then_ type 1 character first before kmail finally starts the > external editor. > > Sorry but THIS SUCKS! Well, the behavior was fine for me for years. My work flow is now broken (http://xkcd.com/1172/). Open a new message window (ctrl-N); type in recipient(s); tab to subject and type in subject; tab to message area and tab. Now focus is in the editor. Edit message. The behavior you requested and got is fine for replying to a message since you want to start editing the reply immediately. But it's wrong to immediately open the editor and have it steal focus when starting a new message. I wish this "fix" never happened. I think Anthony described how to make the "fix" complete and probably acceptable for everyone: https://bugs.kde.org/show_bug.cgi?id=25755#c7 ... |