libxo
PSReadLine
| libxo | PSReadLine | |
|---|---|---|
| 17 | 15 | |
| 302 | 3,584 | |
| 0.0% | 1.1% | |
| 9.7 | 7.4 | |
| about 2 months ago | 23 days ago | |
| C | C# | |
| BSD 2-clause "Simplified" License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libxo
-
jc: Converts the output of popular command-line tools to JSON
> In FreeBSD, this problem was solved with libxo[0]:
Libxo happens to be in the base system, but it is generally available:
* https://github.com/Juniper/libxo
* https://libxo.readthedocs.io/en/latest/
- Libxo: The Easy Way to Generate Text, XML, JSON, and HTML Output
-
Getting work done with PowerShell on Linux
Or make it flexible:
> libxo - A Library for Generating Text, XML, JSON, and HTML Output
* https://github.com/Juniper/libxo/
* https://wiki.freebsd.org/LibXo
Want structure? Ask for JSON or XML and parse. Otherwise it's the regular text output.
- Libxo: Generate text/XML/JSON structured output in one code path
-
Jc – JSONifies the output of many CLI tools
Can you trust it? Cli tool output is not exactly stable. I thought that's why libxo exists?
https://github.com/Juniper/libxo
- Libxo: Library for Generating Text, XML, JSON, and HTML Output
-
Curl gets a --json flag
Please consider https://github.com/Juniper/libxo or something even better than that.
-
You shouldn't parse the output of ls(1)
That would look a lot like FreeBSD. Many of the FreeBSD userland tools are set up to use the excellent libxo (https://github.com/Juniper/libxo) to allow the user's choice of how things are output.
- The growth of command line options, 1979-Present
- Tips on Adding JSON Output to Your CLI App
PSReadLine
-
Tools to achieve a 10x developer workflow on Windows
sets up PSReadLine: command autocompletion and many other features.
-
Wierd behaviour with using 'Dir' as an alias for my own function
Sounds like a bug, you should report it to PSReadLine. I believe PSReadLine and not PowerShell is the one that handles tab completion here, it sounds like it's caching the alias target so still thinks it is completing Get-ChildItem.
-
DirectoryPredictor - Plugin module for PSReadLine to actively search the current directory for matching files
I then used PSReadLine's GitHub to understand how they made their own module, shared data with Cmdlets and everything inbetween. Which got me the rest of the day.
-
Keyword search through PSReadline command history with '#' operator?
Highly recommend checking out the team’s sample file: https://github.com/PowerShell/PSReadLine/blob/master/PSReadLine/SamplePSReadLineProfile.ps1
-
Using PowerShell for non system-administration
I have a hotkey that converts aliases on the command line when I hit alt+% That makes it easier to paste into discord or wherever. Why % ? I'm not sure, that's what what PSReadLine used
-
Leveling up Windows Powershell with Oh My Posh
GitHub - PowerShell/PSReadLine: A bash inspired readline implementation for PowerShell
- PSReadline – bash inspired readline implementation for PowerShell
-
Hot Reload with Notepad in .NET 6
Bit late, but it's PSReadLine
-
New PowerShell Version - v7.2.0-preview.6: [7.2.0-preview.6] - 2021-05-27
Just a bit of a heads up. The PSReadLine 2.2.0 beta 1 and beta 2 do not work with this release so either you can downgrade to PSReadLine 2.1.0 or stay on PowerShell 7.2.0 preview 5. The PSReadLine 2.2.0 beta 3 will solve the issue.
-
How to solve "Update-Help: Failed to update Help for the module(s) 'PSReadline, WindowsUpdateProvider' with UI culture(s) {en-US} : One or more errors occurred. (Response status code does not indicate success: 404 (The specified blob does not exist.).)." ?
The PSReadline update-help failing is new and should probably have an issue filed on their github, assuming there isn't one already. The failure on "WindowsUpdateProvider" has been around for years, you're missing help for these cmdlets without it
What are some alternatives?
pdfalto - PDF to XML ALTO file converter
ohmyzsh - 🙃 A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
elvish - Powerful scripting language & Versatile interactive shell
PSScriptAnalyzer - Download ScriptAnalyzer from PowerShellGallery
jtbl - CLI tool to convert JSON and JSON Lines to terminal, CSV, HTTP, and markdown tables
oh-my-posh - The most customisable and low-latency cross platform/shell prompt renderer
oil - Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!
bass - Make Bash utilities usable in Fish shell
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
Windows Terminal - The new Windows Terminal and the original Windows console host, all in the same place!
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
PowerShell - Collection of useful PowerShell functions, scripts, snippets and templates