Bug 168334

Summary:	Kile alows non-"tex" file extensions for source files
Product:	[Applications] kile	Reporter:	kadlecf
Component:	user interface	Assignee:	Michel Ludwig <michel.ludwig>
Status:	RESOLVED FIXED
Severity:	normal	CC:	reescf
Priority:	NOR
Version First Reported In:	2.0.1
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description kadlecf 2008-08-04 14:43:17 UTC

Version:           2.0.1 (using 3.5.9 "release 49.1" , openSUSE 11.0)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.25.11-0.1-pae

Kile will allow to save the source (e.g., LaTeX) file with an extension other than .tex. This may lead to confusing behavior. If, by mistake (e.g. mouse hovering over the file dialog), the source file has an extension which is used in the compilation process (.ps, .pdf, .dvi etc.) then building the appropriate file format will overwrite the original tex code. Upon returning from the viewer (Kdvi, Kdvipart, Kpdf, etc.) to the editor, a prompt appears warning that the file is now binary. Anyway, the latest edited changes will be lost.

Comment 1 reescf 2015-07-02 22:37:04 UTC

Surely this is the intended behaviour? Not all source files have the extension .tex. .cls, .sty, .dtx, .ins, .cfg, .def, .dat, .bib, .lbx, .cbx, .bst, .mp, .code.tex (TikZ libraries)... and new packages may introduce new extensions as required (as Biblatex and TikZ etc. make clear).

I realise this is probably obvious but since this has been left open, I wondered why it had not be closed as 'won't fix' which seems the only possible response!

Comment 2 Justin Zobel 2021-03-09 06:59:11 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 3 kadlecf 2021-03-09 14:53:40 UTC

In the current version, the bug no longer exists.