Skip to content

Commit ec5c5b4

Browse files
committed
Added changes to release notes for version 0.99.0 due to nushell/#14020
1 parent 5a6b8cb commit ec5c5b4

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

blog/2024-10-15-nushell_0_99_0.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,7 @@ As part of this release, we also publish a set of optional plugins you can insta
2727
- [_Highlights and themes of this release_](#highlights-and-themes-of-this-release-toc)
2828
- [_Changes_](#changes-toc)
2929
- [_Additions_](#additions-toc)
30+
- [_`enhanced keybinding configuration`_](#enhanced-keybinding-configuration-toc)
3031
- [_Breaking changes_](#breaking-changes-toc)
3132
- [_Deprecations_](#deprecations-toc)
3233
- [_Removals_](#removals-toc)
@@ -70,6 +71,32 @@ As part of this release, we also publish a set of optional plugins you can insta
7071

7172
## Additions [[toc](#table-of-content)]
7273

74+
### `enhanced keybinding configuration` [[toc](#table-of-content)]
75+
76+
**Support for Unicode Code Points in Keycodes.**
77+
78+
Starting from [#14020](https://github.com/nushell/nushell/pull/14020), users can now specify characters in the keycode field using their Unicode code points, such as `char_u003B` for the semicolon (`;`). This provides greater flexibility when configuring keybindings in Nushell.
79+
80+
Previously, it was possible to specify characters by enclosing them in quotes, like keycode: "char_;". However, this approach was inconsistent for all Unicode characters, particularly when distinguishing between uppercase and lowercase Latin letters, although it worked for non-Latin characters. The new feature allows for a more straightforward and universally applicable way to define keybindings using Unicode code points.
81+
82+
**Key Feature:**
83+
84+
The current implementation does not restrict the number of leading zeroes when specifying Unicode code points. For example, the character `A` can be represented as `char_u41,` `char_u0041`, or even `char_u000041`. However, it is recommended to use four hexadecimal digits (e.g., `char_u0041`) to improve readability and maintain a consistent format across different configurations. This recommendation follows the standard Unicode representation and helps prevent ambiguity.
85+
86+
**Example usage:**
87+
88+
```nushell
89+
{
90+
name: <command_name>, # name of the command
91+
modifier: none, # key modifier
92+
keycode: char_u003B, # Unicode code for the semicolon (';')
93+
mode: vi_normal, # mode in which this binding should work
94+
event: {
95+
send: <action> # action to be performed
96+
}
97+
}
98+
```
99+
73100
## Breaking changes [[toc](#table-of-content)]
74101

75102
### Standard Library

0 commit comments

Comments
 (0)