Search
1000 results for “cli_ar”
-
AdvancedCLI (0.4.0) by Maximiliano Ramirez
➡️ https://github.com/alkonosst/AdvancedCLI
A serial CLI for Arduino: register commands, parse arguments, and receive typed callbacks with zero-heap allocation.
-
AdvancedCLI (0.4.0) by Maximiliano Ramirez
➡️ https://github.com/alkonosst/AdvancedCLI
A serial CLI for Arduino: register commands, parse arguments, and receive typed callbacks with zero-heap allocation.
-
AdvancedCLI (0.4.0) by Maximiliano Ramirez
➡️ https://github.com/alkonosst/AdvancedCLI
A serial CLI for Arduino: register commands, parse arguments, and receive typed callbacks with zero-heap allocation.
-
AdvancedCLI (0.3.1) by Maximiliano Ramirez
➡️ https://github.com/alkonosst/AdvancedCLI
A serial CLI for Arduino: register commands, parse arguments, and receive typed callbacks with zero-heap allocation.
-
AdvancedCLI (0.3.0) by Maximiliano Ramirez
➡️ https://github.com/alkonosst/AdvancedCLI
A serial CLI for Arduino: register commands, parse arguments, and receive typed callbacks with zero-heap allocation.
-
New article: "The command line (mostly Git) abbreviations I rely on"
I'm all about saving keystrokes. Common CLI tasks are an easy target. I use abbreviations (CLI text expansion) but many of these will work as aliases too.
Between the lack of algorithm and my not making money off visits, you can believe me when I say it's worth a click just to see this hero image — "A fat hunchbacked man with two large warts on his nose with hairs growing out, admires his fashionable wig in a hand-mirror; a grinning barber trims his wig in front of a table on which there are various hair-dressing appliances"— unobscured by text.
https://olets.dev/posts/the-command-line-mostly-git-abbreviations-i-rely-on/
#zsh #FishShell #git #CLI #abbreviation #alias #CommandLine #DX
-
ESP Mail Client (3.4.24) for esp8266/esp32/sam/samd/stm32/STM32F1/STM32F4/teensy by Mobizt
➡️ https://github.com/mobizt/ESP-Mail-Client
Arduino E-Mail Client Library to send, read and get incoming email notification for ESP32, ESP8266 and SAMD21 devices.
#Arduino #ArduinoLibs #esp8266 #esp32 #sam #samd #stm32 #STM32F1 #STM32F4 #teensy
-
Dune: What the climate of Arrakis can tell us about the hunt for habitable exoplanets https://phys.org/news/2024-03-dune-climate-arrakis-habitable-exoplanets.html 🪐 #Exoplanet #Exoplanets #AlienWorlds #ScienceFiction #SF #SciFi #WritingSciFi #Dune #Astrobiology #AlienLife
-
Part 8: So I did A LOT yesterday, but worked too late on it to really write it up. So today all that gets written up is switching my Swift effort over to a Package with dual-targets (library and executable CLI) using ArgumentParser. It requires more setup than Part 6, Future Me will be relieved to have `--help` when she comes back to her script and does't remember what she did.
image from `swift run sketchpad -sc 4`
#ArgumentParser #SwiftLang #OpenUSD
https://www.whynotestflight.com/excuses/hello-usd-part-8-multiball-moves-to-a-package/
-
❓ What are good tool to schedule posts on a Fediverse account?
More info:
Scenario: I write a post (possibly including pictures) and instead of publishing immediately it should be stored and published at a later point in time.
Interactive/GUI-based tools are good, but scripts and automatable CLI-programs are also appreciated.Let's assume an instance that implements Mastodon's API.
-
❄️ A recent @CNN article by Laura Paddison features Prof. Dirk Notz from #CLICCS. Arctic temperatures are soaring, up to 20°C above normal, leading to the lowest February sea ice levels recorded. “We can wipe out entire landscapes.”
https://edition.cnn.com/2025/03/12/climate/arctic-sea-ice-heat-downward-spiral/index.html #ClimateChange #Arctic -
Next attempt for a command line interface for #boxesandglue is now available at
https://github.com/boxesandglue/cli
There are binaries for Window, Linux and macOS and some sort of documentation at https://boxesandglue.dev/cli/. Very early stage, but it shows the direction. Great thank to the hackers at https://risor.io for the great language / Go bindings.
-
See you at #SymfonyDay Montreal!
@fabpot presents: "Building TUIs in PHP: The Symfony Terminal Component." Interactive CLI tools are having a renaissance—don't miss the live PR opening!⚡ https://symfony.com/blog/symfonyday-montreal-2026-building-tuis-in-php-the-symfony-terminal-component -
Here's another shot of the #Kaka that were wrecking our unused tv antenna.
The photos look a bit washed-out, because my darktable-cli settings are not tuned properly for this camera.
If anyone is interested, I'm happy to supply the RAW images -
I don't see enough people talk about what a great tool #zpaq is! It's a wonderful and easy-to-use CLI journaling archiver for incremental backups that uses one of the best compression algorithms. It also has support for password/encryption.
-
Last week I flew out to Redmond, yes, that Redmond, to preview GitHub Copilot CLI and talk about funding and a bunch of NDA'd stuff that I probably still can't talk about.
If you know or follow me, you're aware that I've discussed how much better Agentic CLI tools are compared to Agentic IDEs, and Copilot CLI is no exception. It's pretty cool that I can talk about it now and finally git push to my dotfiles repo again.
https://github.blog/changelog/2025-09-25-github-copilot-cli-is-now-in-public-preview/
-
Why am I mentioning this? Well, different parts of me want to do different things.
A new #Psion SIBO SDK is, from the outside, not something all that interesting to those who don't understand what an SDK is. CLI tools are boring. This is not a bad thing - they should be boring! They need to get out of your way. But it's hard to go to a #retrocomputing con/fest and show the work that you've done on recreating a C preprocessor. Compilers (one day, one day...) are only interesting to other developers, and generally only appreciated by those who understand how difficult it is to write one.
Hardware is easier for people to grasp, figuratively and literally. I'd like to show a thing. #PsiDrive is good for this. Physical PCBs that you can show working. I would like to revisit making an SSD with an RP2350 - that would be useful for all sorts of reasons.
There's also all the research on the platform that underpins all of these. Logic analysers attached to pins, the ROM dumps, the photos of the PCBs, the uncovered or recreated documentation. Again, this is hard for people to see.
There is, of course a not-so-subtle subtext in those three paragraphs. There are projects that I think are useful, and there are projects that are more likely to grab people's attention. Those two categories aren't mutually exclusive, but they do vary from project to project. And many clearly have less of the latter.
-
Why am I mentioning this? Well, different parts of me want to do different things.
A new #Psion SIBO SDK is, from the outside, not something all that interesting to those who don't understand what an SDK is. CLI tools are boring. This is not a bad thing - they should be boring! They need to get out of your way. But it's hard to go to a #retrocomputing con/fest and show the work that you've done on recreating a C preprocessor. Compilers (one day, one day...) are only interesting to other developers, and generally only appreciated by those who understand how difficult it is to write one.
Hardware is easier for people to grasp, figuratively and literally. I'd like to show a thing. #PsiDrive is good for this. Physical PCBs that you can show working. I would like to revisit making an SSD with an RP2350 - that would be useful for all sorts of reasons.
There's also all the research on the platform that underpins all of these. Logic analysers attached to pins, the ROM dumps, the photos of the PCBs, the uncovered or recreated documentation. Again, this is hard for people to see.
There is, of course a not-so-subtle subtext in those three paragraphs. There are projects that I think are useful, and there are projects that are more likely to grab people's attention. Those two categories aren't mutually exclusive, but they do vary from project to project. And many clearly have less of the latter.
-
Why am I mentioning this? Well, different parts of me want to do different things.
A new #Psion SIBO SDK is, from the outside, not something all that interesting to those who don't understand what an SDK is. CLI tools are boring. This is not a bad thing - they should be boring! They need to get out of your way. But it's hard to go to a #retrocomputing con/fest and show the work that you've done on recreating a C preprocessor. Compilers (one day, one day...) are only interesting to other developers, and generally only appreciated by those who understand how difficult it is to write one.
Hardware is easier for people to grasp, figuratively and literally. I'd like to show a thing. #PsiDrive is good for this. Physical PCBs that you can show working. I would like to revisit making an SSD with an RP2350 - that would be useful for all sorts of reasons.
There's also all the research on the platform that underpins all of these. Logic analysers attached to pins, the ROM dumps, the photos of the PCBs, the uncovered or recreated documentation. Again, this is hard for people to see.
There is, of course a not-so-subtle subtext in those three paragraphs. There are projects that I think are useful, and there are projects that are more likely to grab people's attention. Those two categories aren't mutually exclusive, but they do vary from project to project. And many clearly have less of the latter.
-
Why am I mentioning this? Well, different parts of me want to do different things.
A new #Psion SIBO SDK is, from the outside, not something all that interesting to those who don't understand what an SDK is. CLI tools are boring. This is not a bad thing - they should be boring! They need to get out of your way. But it's hard to go to a #retrocomputing con/fest and show the work that you've done on recreating a C preprocessor. Compilers (one day, one day...) are only interesting to other developers, and generally only appreciated by those who understand how difficult it is to write one.
Hardware is easier for people to grasp, figuratively and literally. I'd like to show a thing. #PsiDrive is good for this. Physical PCBs that you can show working. I would like to revisit making an SSD with an RP2350 - that would be useful for all sorts of reasons.
There's also all the research on the platform that underpins all of these. Logic analysers attached to pins, the ROM dumps, the photos of the PCBs, the uncovered or recreated documentation. Again, this is hard for people to see.
There is, of course a not-so-subtle subtext in those three paragraphs. There are projects that I think are useful, and there are projects that are more likely to grab people's attention. Those two categories aren't mutually exclusive, but they do vary from project to project. And many clearly have less of the latter.
-
Why am I mentioning this? Well, different parts of me want to do different things.
A new #Psion SIBO SDK is, from the outside, not something all that interesting to those who don't understand what an SDK is. CLI tools are boring. This is not a bad thing - they should be boring! They need to get out of your way. But it's hard to go to a #retrocomputing con/fest and show the work that you've done on recreating a C preprocessor. Compilers (one day, one day...) are only interesting to other developers, and generally only appreciated by those who understand how difficult it is to write one.
Hardware is easier for people to grasp, figuratively and literally. I'd like to show a thing. #PsiDrive is good for this. Physical PCBs that you can show working. I would like to revisit making an SSD with an RP2350 - that would be useful for all sorts of reasons.
There's also all the research on the platform that underpins all of these. Logic analysers attached to pins, the ROM dumps, the photos of the PCBs, the uncovered or recreated documentation. Again, this is hard for people to see.
There is, of course a not-so-subtle subtext in those three paragraphs. There are projects that I think are useful, and there are projects that are more likely to grab people's attention. Those two categories aren't mutually exclusive, but they do vary from project to project. And many clearly have less of the latter.
-
Had a #GitHubActions workflow fail this morning because it couldn't find `terraform`. This would be because ubuntu-latest is being updated to ubuntu-24.04 and the new image doesn't include terraform as per https://github.com/actions/runner-images/issues/10636.
The good news is there is an installer action you can use to ensure the Terraform CLI bits are available for your workflow. https://github.com/marketplace/actions/hashicorp-setup-terraform
This will also impact #AzurePipelines runs on Microsoft-hosted agents as they share the same images as GitHub Actions.
-
@atthenius @mathieu_caron
I think, Mathieu raises the question why hard sci climate researchers don't speak up about the #EconomicSystem that keeps eating away at the #PlanetaryBoundaries of what human activities the planet can sustain and still maintain a global tech civilisation.
#ClimateChange is ofc only one of these boundaries. But the underlying problem to overstepping all of them is the economic system and its concepts that have perverted the cultural norms in G-North so much so that upholding the voluntarianisms, the laissez-faire [for the rich] is more important than keeping a habitable, global civilisation-sustaining environment. G-North is the villain here, bc it has imposed its system and culture everywhere, except North Korea. ^^
Hard-sci cli-sci are the go-to-people for all things climate.
I say, unfortunately, because they generally don't speak up about the systemic reasons for the physical extremes humans are pushing the planet into.Some do. Like the late #WillSteffen
But it'd be the duty for all hard sci scientists to do so. -
I just realized something.. I used to love learning new things, i could get engrossed in something because it was simple to learn and easy to use.
New "tech stack" doesn't seem to be like that anymore. It feels needlessly complex and invents a new 'standard' every time. It makes me angry and I hate learning, cause its no longer fun.
Learning #borland #TurboPascal #pascal was fun and easy in High School. Moving to #C and #Perl in university was great and easy enough as well. Not that I was any kind of competent in C, but I felt I learned enough that it set me up on a trajectory to learn the finer details and gotchas.
Things like #Python are annoying AF. Oh, your python program only works on 3.11 and not 3.12 or 3.13? That shouldn't be at all. From 2->3 sure I expect changes, 3->4, i would expect great changes as well. But not a minor change!
Dabbling in #Go was fine actually, it didn't anger me much, and #Rustlang / #rust I'm still doing rustlings so I can't say much there.
CLI tools are weird today too. Do they want to be a TUI, a true CLI tool or what?
The #Unix philosophy made learning new tools nice and easy, at least I think so. Do one thing, do it well, make it so your output can be used as the input to another program and great!
Things don't seem to follow that idea anymore.
Or am I just old and biased cause my brain lost its elasticity?? I don't want to think i'm so egocentric as to not rule that out.
-
So over to the command line. First, a sudo apt update.
Debian fetches the updates as it should. It says:
"Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it."
Apt list --upgradable mentions: monarx-agent/bookworm 4.2.72-master amd64 [upgradable from: 4.2.62-master]
Okay, so with that done, let's try the three commands YunoHost recommended:
sudo apt install --fix-broken produces the following output:
"Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up yunohost (12.0.16) ...
Regenerating configuration, this might take a while...
Traceback (most recent call last):
File "/usr/bin/yunohost", line 108, in <module>
main()
File "/usr/bin/yunohost", line 97, in main
yunohost.cli(
File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 41, in cli
ret = moulinette.cli(
^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/__init__.py", line 140, in cli
).run(args, output_as=output_as, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py", line 521, in run
ret = self.actionsmap.process(args, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 579, in process
return func(**arguments)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/app.py", line 1755, in app_ssowatconf
local_manifest = _get_manifest_of_app(setting_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/app.py", line 2269, in _get_manifest_of_app
manifest = _convert_v1_manifest_to_v2(manifest)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/app.py", line 2397, in _convert_v1_manifest_to_v2
install_questions = manifest["arguments"]["install"]
~~~~~~~~^^^^^^^^^^^^^
KeyError: 'arguments'
dpkg: error processing package yunohost (--configure):
installed yunohost package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
yunohost
E: Sub-process /usr/bin/dpkg returned an error code (1)"
Typing sudo dpkg --configure -a gives us the following:
Setting up yunohost (12.0.16) ...
Regenerating configuration, this might take a while...
Traceback (most recent call last):
File "/usr/bin/yunohost", line 108, in <module>
main()
File "/usr/bin/yunohost", line 97, in main
yunohost.cli(
File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 41, in cli
ret = moulinette.cli(
^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/__init__.py", line 140, in cli
).run(args, output_as=output_as, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py", line 521, in run
ret = self.actionsmap.process(args, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 579, in process
return func(**arguments)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/app.py", line 1755, in app_ssowatconf
local_manifest = _get_manifest_of_app(setting_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/app.py", line 2269, in _get_manifest_of_app
manifest = _convert_v1_manifest_to_v2(manifest)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/app.py", line 2397, in _convert_v1_manifest_to_v2
install_questions = manifest["arguments"]["install"]
~~~~~~~~^^^^^^^^^^^^^
KeyError: 'arguments'
dpkg: error processing package yunohost (--configure):
installed yunohost package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
yunohost"
And let's try sudo dpkg --audit:
"The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
yunohost manageable and configured self-hosting server"
Okay.
So.
Any idea what's going on here?
What should I try next to fix this?
(3/3)
#YunoHost #GoToSocial #Fediverse #FediHelp #Linux #SelfHost #SelfHosters #SelfHostedSoftware #python #yunohosthelp @yunohost @yunohost -
The #RustLang based nethsm-cli package on #ArchLinux is now properly indexed. 🗂️
This means you can read all of its man pages online as well 📖 🎉
https://man.archlinux.org/listing/extra/nethsm-cli/
#Nitrokey #NetHSM #CLI #cryptography #documentation #HSM #OpenPGP #Signstar #DigitalSignature #encryption #decryption
-
@budu Don't forget about the stuff available in the #RubyLang #TTY Toolkit, and testing #CLI apps with Aruba. There's also a book that covers testing such apps with the Aruba gem and #CucumberBDD. IIRC it's entitled "Build Awesome Command-Line Applications in Ruby" by @davetron5000, but it may be out of print. I couldn't find it for Kindle or on the @pragprog website.
- https://ttytoolkit.org/
- https://github.com/cucumber/aruba -
When two people argue, a third is usually happy. It looks like #Watson will win the race.
-
Wenn zwei sich streiten, freut sich meist ein dritter. So wie es aussieht, wird #Watson das Rennen machen.
-
FYI: Developer Tooling: Michael's MVC App Innovation #shorts: A powerful CLI and console are designed around MVC apps. There's also a great testing suite built in, and browser dev tools are being developed to stay in the environments where testing is needed. He's building things around this ecosystem. #MVC #CLI #DeveloperTools #TestingSuite https://www.youtube.com/shorts/ZO5BBOac6KQ