New document can't be saved with extension .tcl (not allowed).
The options offered are .null and .tcl.null
It may be a OSX security problem, since .tex files are saved normally.
Perhaps the system is afraid of .tcl files...?
Tcl files are scary... But I can't reproduce this: I just saved successfully a new window as foo.tcl. Which version of the system is running on your machine ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tcl files are scary... But I can't reproduce this: I just saved
successfully a new window as foo.tcl. Which version of the system is
running on your machine ?
10.11.1
J.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been able to reproduce the problem on a machine with 10.11.2, then 10.11.5. I tried to save my new file as foobar.tcl and got the message you mention. I finally chose the proposed .tcl.null extension and the file was saved in fact as foobar.tcl (not foobar.tcl.null).
Now I can't reproduce the bug anymore, but meanwhile I have been playing around with some keys in the Info.plist file, declaring a new export type for Tcl files. It seems that at some point my experiment has fixed the bug or has taught the System about the .tcl file extension, so that I can't provoke this bug anymore.
Could you see what happens if you choose to save your file with .tcl.null extension and tell me if the bug persists or vanishes?
Last edit: Bernard Desgraupes 2016-07-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have generalized the previous experiment and introduced custom Alpha UTIs for each mode. They are declared via the UTExportedTypeDeclarations key in the plc file (which is used to generate the Info.plist). This needs more testing on OS X El Capitan.
Changes committed to svn (rev. 1087). The core needs to be rebuilt in order to regenerate the file Info.plist.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tcl files are scary... But I can't reproduce this: I just saved successfully a new window as foo.tcl. Which version of the system is running on your machine ?
On 07/06/16 21:52, Bernard Desgraupes wrote:
10.11.1
J.
I have no problems in saving tcl files.
I am running 10.11.5
Do you still observe this problem with the recently released version 9.0a4 ?
Yes, still the same problem in 9.0a4 (OSX 10.11.1).
I have been able to reproduce the problem on a machine with 10.11.2, then 10.11.5. I tried to save my new file as foobar.tcl and got the message you mention. I finally chose the proposed .tcl.null extension and the file was saved in fact as foobar.tcl (not foobar.tcl.null).
Now I can't reproduce the bug anymore, but meanwhile I have been playing around with some keys in the Info.plist file, declaring a new export type for Tcl files. It seems that at some point my experiment has fixed the bug or has taught the System about the .tcl file extension, so that I can't provoke this bug anymore.
Could you see what happens if you choose to save your file with .tcl.null extension and tell me if the bug persists or vanishes?
Last edit: Bernard Desgraupes 2016-07-05
I have generalized the previous experiment and introduced custom Alpha UTIs for each mode. They are declared via the UTExportedTypeDeclarations key in the plc file (which is used to generate the Info.plist). This needs more testing on OS X El Capitan.
Changes committed to svn (rev. 1087). The core needs to be rebuilt in order to regenerate the file Info.plist.