or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
nu-cmd crate topology proposal
what should the name be ?
nu-cmd-xxx as the base crate for command traits
it would not have lots of dependencies but be a core command type of crate similar to nu-protocol
amtoine and I are starting to bust out and design some more crates from nu-command to nu-cmd-extra
we are starting to think about a crate topology similar to the beautiful crate topology design of arrow
I don't want to make nu-util be that dumping ground of core traits that nu-commands need moving forward
nu-util is for ansi stuff and color stuff and we need a base nu-command crate and I don't want nu-util to be that crate…
I would like to have another base crate for commands and I would like to come up with a nu-cmd crate topology longer term.
Does this strategy make sense ?
We would like to have a hierarchy of nu-command crates that make sense similar to the
Arrow Crate Topology.
They started out with one large crate and came up with a very logical design of smaller
crates. We don't need something quite like this yet.
But it would be great if we could at least have one base crate and thus nu-cmd-xxx
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →References