Skip to content

Revise nested match examples in basics.md#125

Open
drkvetta wants to merge 1 commit intoespanso:mainfrom
drkvetta:patch-1
Open

Revise nested match examples in basics.md#125
drkvetta wants to merge 1 commit intoespanso:mainfrom
drkvetta:patch-1

Conversation

@drkvetta
Copy link

Updated nested match examples better explain and demonstrate the feature. The current example works but undersells the feature: the sub-match is only used once, so there is no apparent reason to nest rather than just write the word directly. The following example nests the same sub-match in two parent matches, making the core benefit clear: define content once, reuse it everywhere, and update it in one place.

Updated nested match examples better explain and demonstrate the feature. The current example works but undersells the feature: the sub-match is only used once, so there is no apparent reason to nest rather than just write the word directly. The following example nests the same sub-match in two parent matches, making the core benefit clear: define content once, reuse it everywhere, and update it in one place.
@drkvetta drkvetta requested a review from smeech as a code owner March 15, 2026 18:23
@vercel
Copy link

vercel bot commented Mar 15, 2026

@drkvetta is attempting to deploy a commit to the Federico Terzi's projects Team on Vercel.

A member of the Team first needs to authorize it.

@drkvetta
Copy link
Author

I am new to both espanso and github. Recently started using espanso. I worked through the documentation I thought this section could be improved. So consider this or something similar to better explain this feature. Thanks

Copy link
Collaborator

@smeech smeech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution.

I agree the nested matches section is brief, and perhaps undersells the feature, although it's a minor, and little-used option that in most cases would be replaced by a global variable anyway. I don't think the section is misleading, however, is it? I try to avoid the documentation becoming more verbose than necessary.

We could simply replace "…another one." in the text with "…one or more others." or something like that?

@drkvetta
Copy link
Author

Thank you. No, nothing misleading. Yes, your substitute wording would improve it.

@smeech smeech mentioned this pull request Mar 15, 2026
49 tasks
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