Bug 384449 - New documents (without storage url) have mimetype guessed without respecting selected mode/highlighting
Summary: New documents (without storage url) have mimetype guessed without respecting ...
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-ktexteditor
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks: 384971 384972 384973
  Show dependency treegraph
 
Reported: 2017-09-06 21:50 UTC by Friedrich W. H. Kossebau
Modified: 2022-12-10 05:14 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 Friedrich W. H. Kossebau 2017-09-06 21:50:57 UTC
When creating a new text document in Kate (or KDevelop), estimation of the mimetype of the document in KTextEditor::DocumentPrivate::mimeType() is only done based on content, which in many cases will fail due to missing intelligence by the mime database (e.g. Markdown content).
The user though has the chance to manually select a filetype mode (from Tools/Mode menu) in case the detection fails (and I surely are not the only one to do that). And usually they select a matching mode.
So in the case that there is only one mimetype covered by a filetype mode, it would be helpful to have the mimetype of the document being overruled by the filetype mode setting. And in other cases some further control by the user of the mimetype is needed.
Comment 1 Justin Zobel 2022-11-10 08:52:12 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 2 Bug Janitor Service 2022-11-25 05:17:28 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 3 Bug Janitor Service 2022-12-10 05:14:36 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!