Archey3

Archey3 is a simple Python script that prints basic system information and ASCII art of the Arch Linux logo.

Installation

Starting

Archey3 can be run by typing:

$ archey3

This should produce an output similar to below.

               +                OS: Arch Linux x86_64
               #                Hostname: Archie
              ###               Kernel Release: 4.9.11-1-ARCH
             #####              Uptime: 0:32
             ######             WM: None
            ; #####;            DE: GNOME
           +##.#####            Packages: 1034
          +##########           RAM: 1687 MB / 16045 MB
         #############;         Processor Type: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
        ###############+        $EDITOR: nano
       #######   #######        Root: 16G / 20G (80%) (ext4)
     .######;     ;###;`".      
    .#######;     ;#####.       
    #########.   .########`     
   ######'           '######    
  ;####                 ####;   
  ##'                     '##   
 #'                         `#

It can also be started automatically with each new shell session. To do this, append archey3 to a new line in your configuration file, including any options.

Configuration

Archey3's configuration file is stored at ~/.archey3.cfg by default. However this can be adjusted using this command where CONFIG represents the file to use:

$ archey3 --config=CONFIG

Colors

Archey3 can display colors other than the default blue. To change colors, append the -c foo flag, where "foo" represents the desired color. Supported colors are: black, red, green, yellow, blue, magenta, cyan, and white. For example, to display archey3 in red, type:

$ archey3 -c red

Editing the configuration file

A sample configuration file, with comments showing all of the possible options for configuration, is available in the examples page.

gollark: Those can be edited via the string metatable.

gollark: The sandbox's path resolution relies on a few string operations.

gollark: Anyway. The string metatable is global, and can be set inside the sandbox, yes?

gollark: ```luaif (f1 == p1 and f2 == p2) or (f2 == p1 and f1 == p2) then term.clear() term.setCursorPos(1, 1) print "Accepted. Moving potatOS files. This computer will now boot to CraftOS." for _, filename in pairs(files) do local newpath = ".potatOS-old-" .. filename pcall(fs.delete, newpath) pcall(fs.move, filename, newpath) end print "Press any key to continue." os.pullEvent "key" os.reboot() else```

gollark: It TOTALLY DOESN'T, okay?