kumihimo for VS Code 0.10.2

Patch Changes

• Updated dependencies [a33bb38]
  • @love-rox/kumihimo-core@0.12.1

入れ方 / Install

code --install-extension kumihimo-vscode-0.10.2.vsix

拡張パネル右上の「…」→ Install from VSIX… でも同じです。

同梱物のライセンスは THIRD-PARTY-NOTICES.txt にあります。elkjs は EPL-2.0 です。

@love-rox/kumihimo-vue@0.12.1

Patch Changes

• Updated dependencies [a33bb38]
  • @love-rox/kumihimo-core@0.12.1

@love-rox/kumihimo-rehype@0.12.1

Patch Changes

• Updated dependencies [a33bb38]
  • @love-rox/kumihimo-core@0.12.1

@love-rox/kumihimo-react@0.12.1

Patch Changes

• Updated dependencies [a33bb38]
  • @love-rox/kumihimo-core@0.12.1

@love-rox/kumihimo-editor@0.12.1

Patch Changes

• Updated dependencies [a33bb38]
  • @love-rox/kumihimo-core@0.12.1
  • @love-rox/kumihimo-react@0.12.1

@love-rox/kumihimo-core@0.12.1

Patch Changes

• a33bb38: The duplicate-connection message names both ends again.

  It was built by taking the key the two port ids are stored under and swapping the separator
  for an arrow — except the separator was a NUL byte that had been typed into the source rather
  than written as an escape. The swap looked for a space, found none, and the sentence reached
  the reader as a.OUT, a control character, b.IN.

  Everywhere the message goes: the command line, the VS Code problems panel, the diagnostics
  under a diagram in a note.

  The key still separates the two ids with a NUL, now written as an escape; the sentence is
  built from the ids instead of from the key. A key is a key and a sentence is a sentence, and
  the two stopped being the same string the moment the separator did.

  The stray byte also made packages/core/src/build.ts read as binary to grep and file,
  which is how it stayed invisible.

@love-rox/kumihimo-cli@0.12.1

Patch Changes

• Updated dependencies [a33bb38]
  • @love-rox/kumihimo-core@0.12.1

@love-rox/kumihimo-astro@0.12.1

Patch Changes

• Updated dependencies [a33bb38]
  • @love-rox/kumihimo-core@0.12.1
  • @love-rox/kumihimo-rehype@0.12.1

kumihimo for VS Code 0.9.4

Patch Changes

• Updated dependencies [8c11552]
  • @love-rox/kumihimo-core@0.11.1

入れ方 / Install

code --install-extension kumihimo-vscode-0.9.4.vsix

拡張パネル右上の「…」→ Install from VSIX… でも同じです。

同梱物のライセンスは THIRD-PARTY-NOTICES.txt にあります。elkjs は EPL-2.0 です。

kumihimo for VS Code 0.9.3

Patch Changes

• 497aa86: A diagram in a Markdown Preview Enhanced note, and --quiet to make it possible.

  MPE is not VS Code's Markdown preview: it reads none of the extension's contributions, so a
  ```kumihimo block stays a code block there and says nothing about why. It offers one door
  to everybody — a code chunk that runs a command — and now that door works.

  ```kumihimo {cmd="kumihimo" args=["-", "--stdout", "--quiet"] stdin=true output="html"}
  
  ```

  --quiet is not decoration. MPE concatenates standard error into the output, so a clean
  run's ✓ 問題は見つかりませんでした would land in the page beside the drawing. Read out of
  MPE's own bundle rather than guessed, along with how the block reaches the command:
  stdin=true writes it to standard input, $input_file in args is replaced with a
  temporary path, and neither appends the path as the last argument.

  stdin=true is the one documented, because MPE runs the command in the document's own
  directory — so a use of a file beside the note resolves the way it reads, where a temporary
  file would not.

  A smoke test drives the command exactly as MPE drives it, including concatenating both
  streams, and asserts the output is an SVG and nothing else. One of its five checks asserts
  that without --quiet the report does come along, so the flag cannot quietly stop being
  needed without somebody noticing.

  • @love-rox/kumihimo-core@0.11.0

入れ方 / Install

code --install-extension kumihimo-vscode-0.9.3.vsix

拡張パネル右上の「…」→ Install from VSIX… でも同じです。

同梱物のライセンスは THIRD-PARTY-NOTICES.txt にあります。elkjs は EPL-2.0 です。