error messages in status window should be more explicit

[KaiMartin]

If gschem encounters a line in a config file it does not understand, the message sent to the status window lacks the keywords "error" or "warning". Subsequently, gschem quits parsing the resource file at the offending line and resumes the start-up procedure. This may result in unexpected behavior.

Suggestion:
The message might read: "gschem encountered a problem while reading <filename>, line <line number>. The rest of the file remains unread."
This message should go to stdout, too.

---<(kaimartin)>---

[Peter TB Brett (peter-b)]

I'm currently working on enhancements to libgeda to support this.

[KaiMartin (kmk-familieknaak)]

Nice!
This will certainly improve user experience.
---<)kaimartin(>---

[Peter TB Brett (peter-b)]

Hi KaiMartin,

I've just committed some changes to unstable which:

- Modify all libgeda-using apps other than gschem to print errors on stderr and exit with non-zero status if they encounter errors while loading initial configuration files.
- Modify gschem to show error dialogs for any errors loading initial configuration files.

Please test them, and give me feedback. Note that there will still not be exit errors/error dialogs for per directory configuration file errors found while loading schematics, as those unfortunately use a rather different codepath which is going to be quite difficult to refactor in a "nice" way.

I'm going to move onto other issues for now; this bug should be revisited sometime in the future, at which time local configuration should be factored out of f_open_flags() and applications updated as necessary. Lowering importance to medium, since most serious aspects of bug have been fixed.

[Peter TB Brett (peter-b)]

It will not be possible to improve on this issue without major changes that aren't feasible to fit into 1.8.0, sorry.