Skip to content

Implement improved, interactive error handling #65

@attilaoroszdev

Description

@attilaoroszdev
  • Error messages shoudl go in their own file, and be read from there.
  • One liners must fir on the minimum terminal size, startup messages and shutdown messages can be any lenght.
  • All exit statuses higher than 0, and startup notifications must go on this file, but only the text
  • The error handler function must be notified for requirements like "coloured", and where to print the error (bottom row(s) or start/exit screen.
  • On startup errors, the user must decide whether they want to start things as they are, or if they prefer to fix the errors
    • For width related issues, this will open the menu-entries.la` file with the user's preferred editor (or asks them to define it) This is now handled differently
    • For height related issues, it will open the user-defaults.la. This is now handled differently
    • In both cases, there will be suggestions what to change This is now handled differently
    • This requires error codes, to be able to identify the issue

Metadata

Metadata

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions