I had some oddball issues today; it was my own fault, but it got me thinking.
The PB editor saves "extra info" to the end of the file (yes, I know it can be configured to save it to a different file, but the suggestion remains the same...).
It would be nice to be able to define either a list of files TO do that for, or a list of extensions to NOT do that for.
For instance, I had a text file that I edited in PB; this text file was input for a number crunching program. The extra data at the end screwed up the formatted input (read it as invalid data) -- this extra info isn't needed for "non source code files".
Personally, I use pb, pbi, pbh, pbm as purebasic source files; so I can see either way define a list of exceptions or define a list for the extra info... (Like .txt, .dat, etc)
Definable extension list for the editor & purebasic extras
-
- Always Here
- Posts: 6426
- Joined: Fri Oct 23, 2009 2:33 am
- Location: Wales, UK
- Contact:
Re: Definable extension list for the editor & purebasic extr
IdeasVacuum
If it sounds simple, you have not grasped the complexity.
If it sounds simple, you have not grasped the complexity.
Re: Definable extension list for the editor & purebasic extr
jassing wrote:I had a text file that I edited in PB
Source: http://www.purebasic.fr/english/viewtop ... xt#p425648PureBasic Team wrote:The PB IDE is a tool for editing PB files, not a general purpose text editor
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
"PureBasic won't be object oriented, period" - Fred.
Re: Definable extension list for the editor & purebasic extr
i see, so no suggestion on changing anything... noted,recorded, and understood.
thanks
thanks