Skip to content

Remove angle brackets (>) notation, use blank-line grouping#85

Closed
maxim-uvarov-ai-assistant wants to merge 14 commits into
nushell-prophet:mainfrom
maxim-uvarov-ai-assistant:feat/remove-angle-brackets-notation
Closed

Remove angle brackets (>) notation, use blank-line grouping#85
maxim-uvarov-ai-assistant wants to merge 14 commits into
nushell-prophet:mainfrom
maxim-uvarov-ai-assistant:feat/remove-angle-brackets-notation

Conversation

@maxim-uvarov-ai-assistant
Copy link
Copy Markdown

Summary

  • Removes the > REPL-style notation for command grouping
  • Introduces blank-line separation to group commands within code blocks
  • Each group separated by blank lines is executed independently
  • Preserves blank lines between command groups in output

Test plan

  • All example files updated and regenerated
  • Integration tests pass with expected diffs (only timestamp-dependent content)
  • README updated with new format documentation

maxim and others added 14 commits December 10, 2025 22:43
Updated todo file to define clear implementation goals for removing the `>` notation from numd code block execution. The new approach will parse entire blocks, group commands by double newlines, and output results in `# =>` comment lines.
- Rewrite execute-block-lines to split by blank lines instead of > prefix
- Add split-by-blank-lines helper function
- Remove > stripping from remove-comments-plus
- Update clear-outputs to not preserve > lines
- Update capture start to use inline # => output format
- Add separate-block fence option for separate output blocks
- Change create-execution-code to use separate-block option
- Update code block parsing explanation (6-point list)
- Remove > notation from all code examples
- Update help output examples
- Remove reference to deleted types_of_data example
- Remove > notation from all example files
- Update to blank-line grouping format
- Regenerate # => output lines
- Update all _intermed.nu files with new execution format
- Update stripped markdown .nu files
This example had persistent formatting issues with the new
blank-line grouping format and is removed for now.
Update Example 2 to demonstrate the separate-block fence option
which outputs results in a separate code block instead of inline.
When a command produces no output (like variable assignments), the blank
line delimiter between command groups was being lost. This adds an
explicit `print ''` after each command group execution to ensure visual
separation is maintained in the output.
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.

3 participants