IDE option to not save empty project settings to a file

[Mistrel]

Sometimes I will enable certain project settings in the IDE. I don't like to append these to the end of a source file as it causes a lot of false edits with version control systems. I like the alternative options to save to a file but the frustration I have with this is that empty settings files are being generated when there are no settings to be written.

For example (project.cfg):

Code: Select all

[SomeFile.pb]
  IDE Options = PureBasic 5.61 (Windows - x64)

The same is true for the alternative (SomeFile.pb.cfg):

Code: Select all

IDE Options = PureBasic 5.61 (Windows - x64)

I have a lot of files where I want changes to be saved and others where I don't as they're only meant to be included and never run or compiled by themselves. Obviously I would only ever need to have these settings saved if I chose to enable them. Otherwise the settings files already do nothing.

Some people may be happy with the current behavior but I don't think it would be too much to ask for this to be added as a checkbox somewhere.

[Trond]

I would be happy if everything that affected the behaviour of the program (compiler options such as threadsafe) were stored in the file, and extra information such as cursor position was stored somewhere else (maybe a common file for each directory). The cursor position creates noise with version control systems, but storing a separate file for each source file is noisy, also I like the "same source, same output" model, meaning compiler options has to be in the source file.

[skywalk]

Version control is often overlooked and compiler options must be tracked.
I see no real benefit tracking cursor positions, markers, or folding when these change at the whim of the last coder touching a shared file.
Still, I absolutely suffer the noise of these 3 lines:

Code: Select all

; CursorPosition = 138
; FirstLine = 105
; Folding = 0--
; Markers = 9

To get critical parameters affecting the compiled code:

Code: Select all

; EnableThread
; EnableXP
; UseIcon = ..\myapp\myicon.ico
; Executable = ..\..\myapp\myapp.exe
; CompileSourceDirectory
; IncludeVersionInfo
; VersionField0 = %yy,%mm,%dd,0
; VersionField1 = %yy,%mm,%dd,0
; VersionField2 = MeCo
; VersionField3 = MyApp
; VersionField4 = %yy.%mm.%dd
; VersionField5 = %yy.%mm.%dd
; VersionField6 = Do stuff
; VersionField7 = MyApp
; VersionField8 = MyApp
; VersionField9 = MeCo
; VersionField10 = MeCo
; VersionField13 = me@MyCo.com
; VersionField14 = www.MyCo.com

[Mistrel]

Version control is often overlooked and compiler options must be tracked.
I see no real benefit tracking cursor positions, markers, or folding when these change at the whim of the last coder touching a shared file.
Still, I absolutely suffer the noise of these 3 lines:

Code: Select all

; CursorPosition = 138
; FirstLine = 105
; Folding = 0--
; Markers = 9

You can disable cursor positions and marker positions being saved but even without any folding I will still sometimes get something like "; Folding = -". I don't know how to trigger it but I still see it occasionally. I've ended up deciding that this kind of information should be transient anyways. I can't think of a time where I would actually want to resume that kind of state after having decided to close the source.

I don't know what "FirstLine" does.

[skywalk]

FirstLine = line at top of editor.
I guess the IDE needs a "No Noise" option in the Preference Settings.