Bug 153676 - Parts of the filename not selected because of incorrect extension guessing
Summary: Parts of the filename not selected because of incorrect extension guessing
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-08 13:49 UTC by Jorge Salamero Sanz
Modified: 2023-01-06 05:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jorge Salamero Sanz 2007-12-08 13:49:14 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Debian testing/unstable Packages

verbatim copy from bugs.debian.org/405481:

"When I select to save a message to a file on disk (by clicking on the floppy disk icon on the task-bar) the subject of the message is the default file name.  The subject line up to the first '.' (full-stop) character is selected but the rest isn't.

When I save a spam message to disk I want to replace the entire subject with my own file name, so ideally the entire subject would be selected so I only need to start typing the new name.

I can't think of any benefit in the current mode of operation.  Why have part of the name selected but not all?"
Comment 1 Thomas McGuire 2007-12-09 14:52:59 UTC
This seems to be a problem in kdelibs. KMail just calls:

>static KUrl subjectToUrl( const QString &subject ) {
>
>  return KFileDialog::getSaveUrl( KUrl::fromPath( subject.trimmed()
>                                  .replace( QDir::separator(), '_' ) ),
>                                  "*.mbox" );
>}

I don't see anything wrong with that.
So it seems KFileDialog thinks the rest after the dot is the extension, and therefore selects everything before the dot.
I think KFileDialog should check if the extension is really a known extension, by looking at the mime database and see if the extension is known there.
Comment 2 Andrew Crouthamel 2018-11-02 04:20:50 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-16 02:41:22 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-07 00:23:43 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-22 05:19:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-06 05:23:03 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!