Re: [Geany-Devel] [Geany-devel] Separating session file lists from config (again)
Am 18.11.2013 11:03, schrieb Lex Trotman: On 18 November 2013 20:49, Thomas Martitz thomas.mart...@student.htw-berlin.de mailto:thomas.mart...@student.htw-berlin.de wrote: Am 18.11.2013 10:22, schrieb Thomas Young: How about $project.geany.d? ;) On 18/11/2013 10:12, Lex Trotman wrote: 2. various names were suggested, but no clear winner emerged, suggestions included $project.geany, geany.$project and $project.conf.d. Objections included $project.geany is the existing name and may be confused or overwritten by an old version of geany and $project.conf.d is ugly. Making it a define was suggested, which is fine during development, but a permanent solution must be selected prior to merging the change. I thought we $project.geany as the new directory name was accepted. I posted the summary because I was sure there were places where we were agreeing on different things :) My only problem with this name is, what will an old Geany do with it since it matches the current naming convention? I guess we'll find an accceptable name until it's ready for merging. But I do think the string geany should be there to avoid potential clashes with other IDEs. I totally agree with that, just not as the extension since thats the existing convention. Also, remember that $project.geany can also be foobar.geany, it must not be called after the project. I am not sure what you mean here, yes it can actually be any name, .geany extension is only a convention, but why can't it be named after the project? And it must not be within the project's root directory (see Matthew's case for ~/.Projects/*.geany). This should be maintained. Why can't it be in the projects root directory? Currently it can be anywhere, in ~/projects, in ~/.Projects, in the root of the tree, why does that need to change just because the config becomes a directory not a file? I meant to say that we should keep the ability to use non-project related names for the directory and to place it outside the project's root directory, in the same way that's possible with the current geany. Yes, it can be called after the project and it can be within the directory. Sorry, I misused must not, not a native speaker. Should have been does not have to be. Best regards. ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] [Geany-devel] Separating session file lists from config (again)
[...] 1. Project and user session file formats should match to allow the same code to store both. The fact that the storing the current project in the project session file is not needed doesn't matter. It looks like a good idea, I agree, but we need to keep on allowing to save user-wide settings when a project is open. I mean, we shouldn't save all settings changes to the project settings just because one is open, the user might want to change a general setting. I think this was discussed one day already, and I think it should be a separate thread. I said **session** file format, not the config files, as you say ATM the only change to config should be to remove the session info. All further changes are indeed another topic. [...] Old Geany couldn't read it since it's a directory, and I don't think you can possibly overwrite a directory with a file, even accidentally. You'd need to delete the directory first. I agree, I don't think this should be an issue. Older Geany would not be able to load the project, but that should be all. And if the config part starts with the same format as old $project.geany, a user could workaround that by loading $project.geany/project.conf manually. I'm happy for it to be the same so long as someone can assure me that geany saving a file can't overwrite a directory on the most common file system arrangements which includes windows and includes windows file systems on a NAS mounted via Samba (a sadly increasing situation with cheep NAS boxes). Note that config saving will use g_file_set_contents() if the option is set, which writes to a temp file, and renames it over the old file. I agree that on Linux it can't rename a file over a directory, but on what it thinks is a windows file system it deletes the old file first and then renames the temp to it. Are we sure that won't allow it to overwrite directories? But it may be confusing to the users, indeed. Well, I don't think it's more confusing that having the name change, and it would keep on working exactly the same: `geany $project.geany` If my concerns above are allayed then yes its an advantage for operation to remain the same. Cheers Lex Regards, Colomban ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
Re: [Geany-Devel] [Geany-devel] Separating session file lists from config (again)
Le 19/11/2013 00:14, Lex Trotman a écrit : [...] 1. Project and user session file formats should match to allow the same code to store both. The fact that the storing the current project in the project session file is not needed doesn't matter. It looks like a good idea, I agree, but we need to keep on allowing to save user-wide settings when a project is open. I mean, we shouldn't save all settings changes to the project settings just because one is open, the user might want to change a general setting. I think this was discussed one day already, and I think it should be a separate thread. I said **session** file format, not the config files, as you say ATM the only change to config should be to remove the session info. All further changes are indeed another topic. Oops, misread you :) ___ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
