I want to add black module formatting, on each merge it will format the code and push it on main branch

Instructions:
Actions -> Python Application (scroll down lots)

I have installed Ljinux on my RPI Pico, and I wanted to know if there were any programs/tools for it. If not, how do I create a program for it?

for correct led colors(as in Manual.txt) file neopixel_colors.py have to be changed:
line 6: idle = bytearray([0, 3, 0]) # for idling in terminal
line 7: idletype = bytearray([0, 2, 0]) # alternative idle, to indicate input

line 14: error = bytearray([50, 0, 0]) # when errors occur

The facility to do a WiFi scan is really useful - is there a chance of adding the capability to perform a Bluetooth/BLE scan as well on boards that support it?

Yea, I have no idea about those.

/LjinuxRoot/bin/display/f_draw_circle.py requires attention.

RuntimeError: pystack exausted

Command pinout incorrectly shows pins on the backside of RP2040-Zero board.

When it runs it will start 'black .' and all automation scripts

That way we will be informed before committing

Project "vision":

This project aims to create an all-in-one pseudo-os for circuitpython microcontrollers that is easy-to-use and to tinker with.

That isn't to say it shouldn't be functional.
Ljinux should be able to use as much circuitpython compatible hardware as possible.

It's meant to feel like you are using a GNU/Linux bash shell.

Project roadmap:

• Fix telnet tx buffer.
• iwctl don't use input.
• Make hostname a property of settings.toml.
• Redo rm.

Release 0.3.8

• pinctl
• Sensors get battery.
• Redo detection for .connected-less interfaces.
• Update the manual to reflex the last few version changes.

Release 0.4.0

• run-parts
• Tag builds on installation.

Release 0.4.1

• Implement logind.

Release 0.5.0

• Support for terminals without ansi.
• Make nano a preinstalled removable package.

Release 0.5.1

• ble workflow integration.
• Implement fake filesystem.

Release 0.6.0

• jpkg from host.
• jpt wrapper for jpkg.

Release 0.6.1

Later

• coreutils removable (why?)
• Redo w5500.
• First boot setup menu.
• Implement all doable coreutils.
• Complete all based logic with if.

The triangles lose some pixels.. I gotta fix it at some point

The core utilities list

From POSIX standards and the GNU core utilities here is a list of the commands. This issue can be used to discuss progress, priorities, consistencies and general problems related to those commands in an embedded linux environment like the pico.

• grep :: search a file for a pattern
• cat :: concatenate and print files
• printf :: write formatted output
• tr :: translate characters
• xargs :: construct argument lists and invoke utility
• sort :: sort, merge, or sequence check text files
• test :: evaluate expression
• cd :: change the working directory
• ls :: list directory contents
• mkdir :: make directories
• rmdir :: remove directories
• cp :: copy files
• mv :: move files
• rm :: remove directory entries
• diff :: compare two files
• echo :: write arguments to standard output
• jobs :: display status of jobs in the current session
• chmod :: change the file modes
• chgrp :: change the file group ownership
• chown :: change the file ownership
• alias :: define or display aliases
• unalias :: remove alias definitions
• sed :: stream editor
• awk :: pattern scanning and processing language
• cut :: cut out selected fields of each line of a file
• head :: copy the first part of files
• tail :: copy the last part of a file
• more :: display files on a page-by-page basis
• less :: terminal pager (like more)
• pwd :: return working directory name
• df :: report free disk space
• free :: display amount of free and used memory
• du :: estimate file space usage
• find :: find files
• dirname :: return the directory portion of a pathname
• basename :: return non-directory portion of a pathname
• tee :: duplicate standard input
• uniq :: report or filter out repeated lines in a file
• bc :: arbitrary-precision arithmetic language
• cksum :: write file checksums and sizes
• expr :: evaluate arguments as an expression
• read :: read a line from standard input
• sleep :: suspend execution for an interval
• time :: time a simple command
• true :: return true value
• false :: return false value
• wc :: word, line, and byte or character count
• csplit :: split files based on context
• dd :: convert and copy a file
• patch :: apply changes to files
• expand :: convert tabs to spaces
• file :: determine file type
• iconv :: codeset conversion
• ln :: link files
• mkfifo :: make FIFO special files
• nl :: line numbering filter
• od :: dump files in various formats
• pax :: portable archive interchange
• touch :: change file access and modification times
• date :: write the date and time
• id :: return user identity
• uname :: return system name
• type :: write a description of command type
• who :: display who is on the system
• su :: run a command with substitute user and group ID
• sudo :: execute a command as another user
• locate :: find the files by name
• ping :: send request to network hosts
• wget :: network downloader
• curl :: transfer a URL
• man :: interface to the system reference manuals
• mount && unmount :: mount/unmount a filesystem
• lsblk :: list block devices
• dmesg :: print or control the kernel ring buffer
• vim :: screen-oriented (visual) display editor

More commands, see the implementation of core utils in rust : https://github.com/uutils/coreutils

It would be useful to provide such functionality, in order to be able to print large files (like the Manual for example) from within ljinux

I don't know if it has something to do with my build on an esp32-s2 but when I try to create a file with say cp Manual.txt x.x the following error is displayed:

 Traceback (most recent call last):
         OSError:

Hello,
I discovered your project from the recent article at hackster, I feel this idea of a linux toy for the pico is really fun and could go far as an open source project. I will try to help as I like to play with my rpi400 and pico and it looks like the perfect project to come aboard while I am student in software engineering.
If the project become more popular as it iterate and attract more peoples maybe it would be interesting to give some idea for a long term vision, even if it is a toy for developers to have fun (do you know the SerenityOS ?), it would be good to kind of have milestones.

I believe one milestone could be to achieve Ljinux be fully compatible on a complete rp2040+hardware machine like the PICOmputer or the PicoSystem. That would be the most fun journey ever. :)
Here for ref:

• WORLD’S FIRST RP2040 QWERTY COMPUTER
• PICOmputer
• PicoSystem

Of course, it is an idea for a long term project, there would be many fun steps to reach before to have a fully OS toy for the RP2040.

Cheers

The documentation needs to be tested to be noob-proof.

it's .detect_size

While it is very stupid to deploy Ljinux from a windows machine, I feel like it should be doable.
Using GNU/Make on Windows would certainly be a way, even though, a very weird one.
A powershell script should be able to do it, but WSL may be an easier way.
However I have no bare metal windows installations at the moment to test this stuff.

most of the filled triangle stays empty
It has stayed internal for the time being

This is in preperation for custom input environments. (editor)

The Serial input needs to be able to launch custom functions based on the environment it's in. The functionallity Serial Input shall provide should be defined through arguments.

Perhaps an array of keybinds?

I'm not quite sure.

I don't know if there some connection to my minimal setup for the ESP32-S2 but the ljinux console will not accept the number 0 whether the zero is pressed on the main keyboard or the attached keypad.

Headtail was moved externally into /LjinuxRoot/bin and during the conversion it broke. I don't want to revert it though.