goatfiles / nu_scripts Goto Github PK

i would like to add a vm clone subcommand to clone VMs, just as can be done in managers such as virtualbox 👍

from amtoine/dotfiles#31

i would like to add the following kind of script to the nushell config:

# rm trough pipe
#
# Example
# ls *.txt | first 5 | pipe rm
export def "pipe rm" [] {
  if not ($in | is-empty) {
    get name 
    | ansi strip
    | par-each {|file| 
        rm -rf $file
      } 
    | flatten
  }
}

I would like to add a module, e.g. called tomb, mainly a tomb manage function, to easily interact with tombs 💀

until now, all the scripts assume the environment variables they use are set, either in env.nu or in the current interactive shell with a manual let-env VAR = val.

however, this is error prone when used on another config than man which sets all the variables, 'cause i use them

i want to use default values to make sure all the environment variables are set at runtime 👍

an example

• let vm_directory = ($env.QUICKEMU_HOME | path join $os) in vm.nu#L54 would become

let vm_directory = (
  $env | get -i QUICKEMU_HOME | default "~/.local/share/quickemu" | path expand
  | path join $os
)

• let path = ($env.GHQ_ROOT | path join $repo) in repo.nu#L100 would become

let path = (
  $env | get -i GHQ_ROOT | default "~/.local/share/ghq" | path expand
  | path join $repo
)

from amtoine/dotfiles#32

there are a lot of TODOs in the nushell modules...
namely i left the documentation undone intentionnally until... well now 👀

i would like to complete all the documentation of the nushell modules and get rid of all the TODOs 👍

that is a proposition, e.g. instead of having

Error:
  × User choose to exit...
    ╭─[scripts/prompt.nu:27:1]
 27 │     if ($choice | is-empty) {
 28 │         error make (context user_choose_to_exit)
    ·         ─────┬────
    ·              ╰── User choose to exit...
 29 │     }
    ╰────

when pressing <C-c> inside the selection of repo goto we could have a simpler

User choose to exit...

when i cd to /tmp/, even /tmp/foo/, i get

Error: nu::shell::eval_block_with_input (link)

  × Eval block failed with pipeline input
    ╭─[scripts/shell_prompt.nu:12:1]
 12 │     $"!/($env.PWD)" |
 13 │       str replace $"!/($home)" ~ -s |
    ·       ─────┬─────
    ·            ╰── source value
 14 │       split row $sep
    ╰────

Error: nu::shell::access_beyond_end (link)

  × Row number too large (empty content).
    ╭─[scripts/shell_prompt.nu:24:1]
 24 │       $el
 25 │     } else if ($spwd_src.0 == ".") {
    ·                          ┬
    ·                          ╰── index too large (empty content)
 26 │       $".($spwd_src.1)"
    ╰────

We discussed this here nushell/nushell#8583 (comment). Excerpt below.

https://github.com/goatfiles/nu_scripts/blob/bleeding/scripts/plugin.nu

@amtoine I noticed that this script isn't cross platform. It doesn't really matter for you, but if someone on Windows wants to use this, they need to change this line:

| str replace '^register (.*) \s+{' '{"binary": "$1",'

to something more like this

| str replace '^register (.*) \s+{' `{"binary": '$1',`

notice the difference is "$1" vs '$1'. Double quotes means to interpret escapes, which is fine for *nix, but on Windows where paths are like C:\some\path, all that mess is now escaped because of double quotes.

i would like to refactor the scripts a bit, mainly

• fix some indentation and typos
• use the | pipe symbol at the beginning of the lines instead of the end
  this is both
  • easier to read because one can see the pipe directly when starting a line
  • easier to work with because all the lines of a pipe, except the first obviously, have the same structure and can thus be removed or shuffles without breaking the pipeline

for instance, to change

start-of-pipe |
command-1 |
command-2 |
end-of-pipe

one would have to make sure the | is added to the last command and removed from others when shuffling

with

start-of-pipe
| command-1
| command-2
| end-of-pipe

one can shuffle and remove any of the last three commands without ever breaking the pipeline itself 👍

I would like to add a module, e.g. called trash, to interact with the freedesktop trash functionnality activated by the $env.config.rm.always_trash option.