Skip to content

feat: add input abbreviations for heavy angle brackets ❰❱#782

Merged
mhuisi merged 1 commit into
masterfrom
add-heavy-angle-brackets
May 27, 2026
Merged

feat: add input abbreviations for heavy angle brackets ❰❱#782
mhuisi merged 1 commit into
masterfrom
add-heavy-angle-brackets

Conversation

@kim-em
Copy link
Copy Markdown
Contributor

@kim-em kim-em commented May 25, 2026

This PR adds input abbreviations for (U+2770, HEAVY LEFT-POINTING ANGLE BRACKET ORNAMENT) and (U+2771, HEAVY RIGHT-POINTING ANGLE BRACKET ORNAMENT), following the existing pattern for French/single-arrow brackets (f<, f>, f<> for ‹›):

  • \h<
  • \h>
  • \h<>❰$CURSOR❱

The h prefix matches the "HEAVY" in the Unicode names. The paired form lives next to the existing paired brackets at the top of the file; the singletons live next to f< / f> further down.

Motivation

Batteries' proof_wanted and construction_wanted commands (leanprover-community/batteries#1814 and stacked PRs) use ❰foo❱ as a bracket syntax for referencing earlier wanted declarations. Without an input abbreviation, users have to copy-paste the characters or set up their own — these PRs aren't really usable without a way to type the brackets.

🤖 Prepared with Claude Code

`h<` → ❰, `h>` → ❱, `h<>` → ❰$CURSOR❱, following the existing `f<`/`f>`/`f<>` pattern for
French/single-arrow brackets `‹›`. The "h" prefix matches the Unicode names HEAVY LEFT/RIGHT-
POINTING ANGLE BRACKET ORNAMENT (U+2770, U+2771).

These characters are used by batteries' `proof_wanted` and `construction_wanted` commands
(leanprover-community/batteries#1814) as a bracket syntax for
referencing earlier wanted declarations.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mhuisi mhuisi merged commit 7af7fa9 into master May 27, 2026
18 checks passed
@mhuisi mhuisi deleted the add-heavy-angle-brackets branch May 27, 2026 09:40
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