nu_scripts/sourced/cool-oneliners
Mel Massadian c47ccd42b8
refactor: (#418)
* refactor:  move in one commit

Eveything in modules should probably be changed to `exported` defs.
The idea is to move everything first to keep proper history.

* refactor: 📝 add modules readme (wip)

* refactor:  small move

* refactor: 📝 changed nestring, updated modules readme

* refactor: 📝 to document or not to document

* fix: 🐛 themes

replaced the template to use `main` and regenerated them
from lemnos themes.

* Revert "fix: 🐛 themes"

This reverts commit 4918d3633c.

* refactor:  introduce sourced

- Created a source `root` in which sourcable demos are stored.
  Some might get converted to modules later on.
- Moved some files to bin too.

* fix: 🐛 fehbg.nu

* fix: 🐛 modules/after.nu

* moved some other stuff around

---------

Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-04-25 17:56:25 -05:00
..
cargo_search.nu refactor: (#418) 2023-04-25 17:56:25 -05:00
clear_screen_buf.nu refactor: (#418) 2023-04-25 17:56:25 -05:00
dict.nu refactor: (#418) 2023-04-25 17:56:25 -05:00
file_cat.nu refactor: (#418) 2023-04-25 17:56:25 -05:00
file_convert_naming_case.nu refactor: (#418) 2023-04-25 17:56:25 -05:00
git_gone.nu refactor: (#418) 2023-04-25 17:56:25 -05:00
parse_fish_command_history.nu refactor: (#418) 2023-04-25 17:56:25 -05:00
pwd-short.nu refactor: (#418) 2023-04-25 17:56:25 -05:00
README.md refactor: (#418) 2023-04-25 17:56:25 -05:00

cool oneliners

Capturing oneliners to and from the nushell Discourse channel #cool-oneliners.

Consider these a living library. Or an ongoing story of how people actually use nu.

Naming and script requirements

  • the filename should be an abbreviation of the general topic of the script For example:

    git_batch_extract.nu
    
  • the script should have two lines

    • the first line should be a comment describing the script's purpose
    • the second line should be the cool oneliner