Page 1 of 1

Editor option settings also saved in CSV-file

Posted: Wed Mar 21, 2012 7:19 pm
by uwekel
Hi,

i have configured my PB IDE to save the editor option settings at the end of the file. Today i edited a CSV-file with PB which works fine, but after saving the changes to file, i noticed that the option settings were also attached to the end of the file. In my case, the data file was partially destroyed. From my point of view it would make sense to save these settings to PB owned files (*.pb) only. What do you think?

Best regards
Uwe

Re: Editor option settings also saved in CSV-file

Posted: Wed Mar 21, 2012 10:07 pm
by skywalk
See: Preferences - Editor - Save Settings to: :wink:

Re: Editor option settings also saved in CSV-file

Posted: Wed Mar 21, 2012 10:15 pm
by uwekel
Yes, i know. I want the settings to be saved to the end of all *.pb files, but not any other. I think it does not make too much sense to store information like

Code: Select all

; IDE Options = PureBasic 4.61 Beta 1 (Linux - x64)
; EnableThread
; EnableXP
in any other file than a *.pb file ;-)

Re: Editor option settings also saved in CSV-file

Posted: Thu Mar 22, 2012 12:23 am
by Little John
The PureBasic IDE is for .pb files, it's not a general purpose text editor.
For CSV files, better use e.g. Notepad++ or another text editor.

Re: Editor option settings also saved in CSV-file

Posted: Thu Mar 22, 2012 12:53 am
by Tenaja
I use Notepad++ also, and sometimes Programmers Notepad depending on the feature I need...

But if PB's IDE had a plain text mode (or better, additional languages that are common to PB users), then other editors could be avoided.

Re: Editor option settings also saved in CSV-file

Posted: Thu Mar 22, 2012 7:21 pm
by uwekel
I do not use another editor. Recently i loaded an XML file into PB's IDE and was really impressed about the very nice synthax highlighting. It's just bad that the file gets attached these additional option lines when saving, so it is not conform anymore with the XML standard.

Re: Editor option settings also saved in CSV-file

Posted: Fri Mar 23, 2012 2:45 pm
by Little John
Tenaja wrote:But if PB's IDE had a plain text mode (or better, additional languages that are common to PB users), then other editors could be avoided.
Not generally. Actually, that would apply only to a small number of people.
People who use some advanced features of e.g. Notepad++ can't "avoid" that program and use the PB IDE instead, until those fatures are implemented in the IDE. The same applies to PSPad, UltraEdit, and and, and ... In other words, a plain text mode in the PB IDE would only serve the needs of people who don't have high demands for a text editor. All other people will need an additional good general purpose editor anyway. Actually, even if you want to search correctly for "whole words only" in PureBasic source code, you need an additional editor, since the PB IDE (e.g. versions 4.50, 4.60) is not capable of doing so. :evil:

Re: Editor option settings also saved in CSV-file

Posted: Fri Mar 23, 2012 3:23 pm
by Tenaja
Little John wrote: Not generally. Actually, that would apply only to a small number of people.
While I am a heavy Notepad++ user, I could avoid it about 60 to 70% of the time if PB's IDE could do plain text (the capitalization ruins a LOT of text), an additional 20-25% if you could view two panes at a time, and a full 95% of the time if you could also add custom language styling. Add selected-word highlight, and I could probably skip npp all together.

On the other hand, I know plain text support could be implemented with very little coding time, and I would greatly appreciate it. However, before they spent a full day implementing new IDE features, I'd much rather they spent that time making the output code more efficient.

Re: Editor option settings also saved in CSV-file

Posted: Fri Mar 23, 2012 3:38 pm
by Little John
Tenaja wrote:While I am a heavy Notepad++ user, I could avoid it about 60 to 70% of the time if PB's IDE could do plain text (the capitalization ruins a LOT of text), an additional 20-25% if you could view two panes at a time, and a full 95% of the time if you could also add custom language styling. Add selected-word highlight, and I could probably skip npp all together.
This is just your personal choice. Other Notepad++ users probably think similarly, but in respect to their most frequently used features of Notepad++. As I wrote, the same applies to PSPad, UltraEdit, and dozens of other editor and their users ... So yes, if all features of all editors were implemented in the PB IDE, all other editors could be "avoided". :)

Re: Editor option settings also saved in CSV-file

Posted: Fri Mar 23, 2012 4:00 pm
by skywalk
NotePad++ and the PB IDE use the Scintilla library. But many of the features of NotePad++ are extended by a plug-in system. If PB IDE enables some sort of automation or plug-in system..., then I would implement the features I need in the IDE.

Re: Editor option settings also saved in CSV-file

Posted: Fri Mar 23, 2012 4:09 pm
by Little John
skywalk wrote:If PB IDE enables some sort of automation or plug-in system...,
AFAIR freak had announced something like that, but did not yet have enough time to implement it.

Re: Editor option settings also saved in CSV-file

Posted: Mon Apr 09, 2012 1:44 pm
by MachineCode
Tenaja wrote:if PB's IDE could do plain text (the capitalization ruins a LOT of text)
PB's IDE can do plain text without capitalization. It's in the Preferences.

Re: Editor option settings also saved in CSV-file

Posted: Mon Apr 09, 2012 7:50 pm
by Tenaja
MachineCode wrote:
Tenaja wrote:if PB's IDE could do plain text (the capitalization ruins a LOT of text)
PB's IDE can do plain text without capitalization. It's in the Preferences.
Sure, but I am not about to change the preferences every time I switch tabs from a .pb file to a .txt file!

Re: Editor option settings also saved in CSV-file

Posted: Sat Jun 23, 2012 8:22 pm
by Zach
I think this really is a no brainer.

Irrelevant of the fact that the IDE is not a general purpose editor, it seems to me to be common for people to open up other file types related to a project they are working on, and the IDE should be respecting the data structure of those other file types regardless.