[GH-ISSUE #165] Improved config file parsing, trimming spaces #121

New issue

Closed

opened 2026-03-03 01:19:58 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 01:19:58 +03:00

Owner

Originally created by @d99kris on GitHub (Jul 13, 2024).
Original GitHub issue: https://github.com/d99kris/nmail/issues/165

Originally assigned to: @d99kris on GitHub.

Discussed in https://github.com/d99kris/nmail/discussions/164

... the warning messages in the log.txt provided indicates that your ui.conf contains some fields that nmail cannot parse - more specifically instead of KEY_SPACE (no trailing space) the ui.conf file contains KEY_SPACE (many trailing spaces). Same with - usage.

Unfortunately the config file parsing is not so flexible currently, so nmail fails to parse these values. I will see if I can make the parsing a bit more flexible (trimming spaces, etc) ...

Originally created by @d99kris on GitHub (Jul 13, 2024). Original GitHub issue: https://github.com/d99kris/nmail/issues/165 Originally assigned to: @d99kris on GitHub. ### Discussed in https://github.com/d99kris/nmail/discussions/164 <div type='discussions-op-text'> > ... the warning messages in the log.txt provided indicates that your ui.conf contains some fields that nmail cannot parse - more specifically instead of `KEY_SPACE` (no trailing space) the ui.conf file contains `KEY_SPACE ` (many trailing spaces). Same with `-` usage. > Unfortunately the config file parsing is not so flexible currently, so nmail fails to parse these values. I will see if I can make the parsing a bit more flexible (trimming spaces, etc) ...