You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues (including closed ones) and believe that this is not a duplicate.
I have searched the documentation and believe that my question is not covered.
I am willing to lend a hand to help implement this feature.
Feature Request
The default logging format introduces aggressive line wraps. For example:
[11:03:07] ERROR Could not process generators.py:871
pages/xxxxx/xxxxxxxxxxx/xxxxxxxxxxx.rst
/home/cpitclaudel/git/xxxxxxx/xxx/xxx/page
s/xxxxx/xxxxxxxxxxx/xxxxxxxxxxx.rst:74:
(ERROR/2) …
Unfortunately, my editor is not smart enough to undo the line breaks, so it offers to open s/xxxxx/xxxxxxxxxxx/xxxxxxxxxxx.rst:74 instead.
I would love an option to just print the error using a less-fancy log handler. The default format is pretty OK:
Could not process pages/xxxxx/xxxxxxxxxxx/xxxxxxxxxxx.rst
/home/cpitclaudel/git/xxxxxxx/xxx/xxx/pages/pages/xxxxx/xxxxxxxxxxx/xxxxxxxxxxx.rst:74: (WARNING/2) …
The text was updated successfully, but these errors were encountered:
* pelican/__init__.py (parse_arguments): Declare new --logs-handler argument.
Uses a string instead of a `type=` argument to get better error messages when
passed an incorrect choice.
(main): Pass `args.logs_handler` to `init_logging`
* pelican/log.py: Expose default log handler as `DEFAULT_LOG_HANDLER`.
(init): Pass handler to `logging.basicConfig`.
ClosesgetpelicanGH-3292.
* pelican/__init__.py (parse_arguments): Declare new --logs-handler argument.
Uses a string instead of a `type=` argument to get better error messages when
passed an incorrect choice.
(main): Pass `args.logs_handler` to `init_logging`
* pelican/log.py: Expose default log handler as `DEFAULT_LOG_HANDLER`.
(init): Pass handler to `logging.basicConfig`.
ClosesgetpelicanGH-3292.
Feature Request
The default logging format introduces aggressive line wraps. For example:
Unfortunately, my editor is not smart enough to undo the line breaks, so it offers to open
s/xxxxx/xxxxxxxxxxx/xxxxxxxxxxx.rst:74
instead.I would love an option to just print the error using a less-fancy log handler. The default format is pretty OK:
The text was updated successfully, but these errors were encountered: