swift-sh VS z

Yes, swift CLI will compile and run your swift file.

But many people also want to use libraries. For Python, they use the system libraries or work within an environment with installed libraries (i.e., the library-install process happens at environment-configuration time).

In Swift, the easiest way to consume libraries is using packages, but that requires a Package.swift declaring the project scope for the script file (which must comply with top-level and main-entrypoint code requirements).

The easiest way to do that when scripting is a swift tool that manages the process of gathering your library dependencies, auto-generating a project, building the tool, and caching it all so there's no overhead the next time.

The best available tool now is https://github.com/mxcl/swift-sh. It reads dependency information off import comments.

It can also generate the project for you, if/when you want to build in XCode (e.g., move into a more complex application, perhaps requiring sandbox declarations).

Working scripts are not always updated, so any script-build tool has to maintain backwards compatibility, but the swift package manager has changed a lot in recent versions. swift-sh seems to err on the side of backwards compatibility, and does not support e.g., the most recent dependency versioning styles.

Swift-forum discussions about better support for scripting haven't resulted in any official tooling.

Note that this has nothing to do with the Raspberry Pi. You'll have the same issue running on the command-line. If you wish to test your programs on your computer where you have more tools and horse-power, I find swift-sh gives a good command-line experience and is a great alternative to Playgrounds especially for small tests.

- Visidata

- z (https://github.com/rupa/z)

- fzf

- vim

- Fastmail

- WireGuard

- draw.io

- PowerShell (it’s difficult to overstate how much PS has improved Windows system administration)

- Microsoft PowerToys

- WSL (alternating joy and extreme frustration)

- Home Assistant

- Airfoil

For even more power use z

https://github.com/rupa/z

- quickly jump to recent directory: https://github.com/rupa/z - however I find it kinda annoying it seems to forget/ignore(?) directories, anyone know of a better version of this?

- quickly opening my personal wiki: https://github.com/francium/dotfiles/blob/master/bin/.local/...

- re-run a script when a file changes: https://github.com/francium/dotfiles/blob/master/bin/.local/...

For `while-watchdo` you, you run it like `while-watchdo "echo hi"`, then in my editor, I have a custom shortcut that does `touch .watchfile` causing the command, in this case `echo hi` to run. I prefer this to tools that retrigger commands as soon as you save _any_ file. Also works in docker containers, edit a file on host, command runs in a container.

2) Well friend, this is where you can have the best of both of worlds. You can just open the file explorer via the CLI. Typically you'll have the xdg-open command that opens the directory in your default file browser. I have that aliased to xdgo. So you can navigate quickly to where you need to be, and then open it visually with xdgo . . There's also other really convenient navigation tools like z (https://github.com/rupa/z) that I can't imagine going without anymore.

I would like to know how you use the terminal and nvim in your daily workflow. Here is mine: I have a shortcut (with raycast) to open alacritty full screen from anywhere. I open alacritty and start the tmux (create work and personal sessions). Then using z navigate to the desired project. Next, I have a bash script pde that opens nvim, and 2 terminal splits below. Nvim opens with alpha-nvim (startify theme). For file explorer I use lir.nvim. Fuzzy finding using fzf-lua. I have harpoon but don't use it very often, instead, I manage buffers with fzf-lua and vim-bbye. When working on multiple files I usually have 2-4 vsplits. I do git stuff mostly using vim-fugitive (gv.vim, resetting hunks with gitsigns.nvim), occasionally git commands from another tmux window. I use auto-save.nvim. My most used command is :F (lsp.bug.format). For movements I use Ctrl+D/U/O/I/, sometimes relative line jumping. Other often movements [q,]q (quickfix jumps), [d,]d (diagnostics jumps), [c,]c (Gitsigns hunks). Alacritty + Neovim view

For general filesystem navigation in my terminal, I'm using z command. But for finer control, I am using the following commands.

z

Do you know about the program z? https://github.com/rupa/z

https://github.com/rupa/z is an awesome command to teleport to your most used directories. It's really handy to jump from a project to another.