Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multi-word corrections (regex?) #1018

Open
tobiasdiez opened this issue May 22, 2024 · 2 comments
Open

Allow multi-word corrections (regex?) #1018

tobiasdiez opened this issue May 22, 2024 · 2 comments
Labels
A-dict C-enhancement Category: Raise on the bar on expectations S-waiting-on-decision Status: Waiting on a go/no-go before implementing

Comments

@tobiasdiez
Copy link

tobiasdiez commented May 22, 2024

Sometimes the words in itself are correct, but are not used in the correct (grammatical) sense. Examples include

  • right hand side > right-hand side
  • infinite dimensional > infinite-dimensional
  • former or later > former or latter

It would be nice if such expressions could be captured as well.

Perhaps it's an idea to have a expressions group in the config (similar to words) which then matches using regular expressions. Could be used to implement project-specific rules (e.g. if a command is deprecated or a certain multi-word expression shouldn't be used).

(In the other direction, this would be #795. It's also related to #400.)

@tobiasdiez tobiasdiez changed the title Allow multi-word corrects (regex?) Allow multi-word corrections (regex?) May 22, 2024
@epage
Copy link
Collaborator

epage commented Feb 19, 2025

Could you clarify how this is different than #795? I'm inclined to close this as a duplicate.

@tobiasdiez
Copy link
Author

My understanding of #795 is that it is about allowing spaces as the possible corrections (e.g. abouta -> about a) but not about matching strings that contain spaces as in this ticket. Moreover, I think, some of the challenges discussed in #795 don't apply to this feature request here. For example, there is less ambiguity here with what is the correct correction.

@epage epage added C-enhancement Category: Raise on the bar on expectations S-waiting-on-decision Status: Waiting on a go/no-go before implementing A-dict labels Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-dict C-enhancement Category: Raise on the bar on expectations S-waiting-on-decision Status: Waiting on a go/no-go before implementing
Projects
None yet
Development

No branches or pull requests

2 participants