Skip to content

Conversation

bar-g
Copy link
Collaborator

@bar-g bar-g commented Jun 19, 2025

This applies the helpful info from the old PR "word_parse.py: parse_backslash (errors + hinting questions)" #1824 to the new error-catalog instead.

@bar-g bar-g marked this pull request as ready for review June 19, 2025 18:27
@bar-g
Copy link
Collaborator Author

bar-g commented Aug 26, 2025

bump

@andychu
Copy link
Contributor

andychu commented Aug 29, 2025

I looked over this - I think the existing wording is clearer

This seems to "assault" the reader with a lot of information that doesn't necessarily help solve the problem

@bar-g
Copy link
Collaborator Author

bar-g commented Sep 1, 2025

Your sparse stuff/style is unfortunately very much incomplete, and not systematic.
A larger problem is that as such, it doesn't scale to bring more comprehensive help to the user.

Instead, it actually even brings more puzzles after facing an error.

Did you mean \\z?

what?

Therefore I rather started listing involved options, facts, and then real example alternatives for the user.

Maybe, the facts could be shortened, or their inlined examples be moved to their ends, but I don't think your response is appropriate.
(Besides that the current infos hadn't helped me to understand things I added.)

@bar-g
Copy link
Collaborator Author

bar-g commented Sep 1, 2025

from the old PR:

#1824 (comment)
this belongs in a new file doc/error-catalog.md

@bar-g
Copy link
Collaborator Author

bar-g commented Sep 1, 2025

done fixing typos, small improvements and missing bits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants