Contents

• General information

• For Windows

  • Scoop installation
  • Micro installation
  • fzf installation
  • fd installation
  • bat installation
  • PowerShell setup
  • PowerShell 7 installation

• For Linux

• Micro

• Tools

• Web browser

• Windows terminal settings

General information

For working with Python, a tool environment will be prepared to facilitate work using the keyboard:

• scoop: a program manager supporting open source
• micro: a console text editor
• setting environment variables, aliases and functions

Clone this repository to your computer:

• start terminal
• go (create) to the folder where you want to put the repository
• git clone https://github.com/python-edu/01terminal_help.git - clone the repository

For Windows

Scoop installation

From Scoop:

• a command-line installer for Windows.
• Open a PowerShell terminal (version 5.1 or later) and from the PS C:> prompt, run:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Invoke-RestMethod -Uri https://get.scoop.sh | Invoke-Expression

Micro installation

From micro web or github:

a modern and intuitive terminal-based text editor

In the PowerShell terminal, type:

scoop install micro

or with winget:

winget install zyedidia.micro

If you really don't want to learn micro you can use any other text editor e.g. Nnotepad++.

fzf installation

From fzf github:

• Warp, the intelligent terminal for developers
• Available for MacOS, Linux, & Windows
• fzf is a general-purpose command-line fuzzy finder

In the PowerShell terminal, type:

scoop install fzf

fd installation

From df github:

fd is a program to find entries in your filesystem. It is a simple, fast and user-friendly alternative to find.

scoop install fd

bat installation

From bat:

A cat(1) clone with syntax highlighting and Git integration.

scoop install bat

PowerShell setup

The solutions in this section are intended for Windows users with a PowerShell terminal. Commands are executed in the terminal or saved to a special configuration file, the location of which is set in the $PROFILE environment variable.

1. PROFILE $PROFILE: A PowerShell system variable that stores the path to the user's profile file. This is a script that is automatically executed when PowerShell starts. In the PowerShell terminal:

• echo $PROFILE: this will show you the location of the PowerShell configuration file eg.: C:\Users\test1\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
• dir Documents: this will show if there is a folder WindowsPowerShell in the Documents directory. If the WindowsPowerShell directory does not exist it should be created: mkdir .\Documents\WindowsPowerShell
• to make PowerShell configuration easier you can use the profile.ps1 file from this repository and copy it to the path specified by $PROFILE. Assuming you have cloned the repository to your disk as in the image below:

• now you can copy the file using the command:

cp profile.ps1 $PROFILE

• restart PowerShell to load the new configuration.

2. Editor In the $PROFILE file, a variable is set that configures the editor that will be used in the terminal. The default one is micro. To set a different editor:

• open the file for editing: micro $PROFILE
• go to the line $env:EDITOR = "micro" # "micro", "vim", "code", ... and type your editor (if installed)

3. Functions Two functions are defined in the configuration file:

• mcc: searches for files, displays the contents of text files and opens the selected file for reading
• cdd: searches for directories, displays the contents of the selected directory and goes to the selected directory

PowerShell 7 installation

Your Windows system probably does not have the latest version of Powershell installed. Usually the version available on your system is much older (series 5) than the current one (series 7). If you want to use the latest version, you will need to install it. There are more than one way to install it and they are described in the documentation learn.microsoft.com.

Example installation using winget:

1. Check available powershell versions: when using winget for the first time a message will appear - confirm it (YES).

   winget search Microsoft.PowerShell

2. Install PowerShell:

winget install --id Microsoft.PowerShell --source winget

3. Launch terminal - Win keyboard, type terminal. You may get an error like:

• open settings
• in settings click (in the left panel) PowerShell, next click Command line
• delete the existing entry and type pwsh
• save settings, close the terminal and restart it

Different versions of PowerShell use different configuration files stored in different directories - as you can see in the image below.

1. Open two separate windows:

• PowerShell version 5 - Win key, type powershell
• PowerShell version 7 - Win key, type terminal

2. Run the commands shown in the images below:

• check if the directory with $PROFILE exists, if not - create it
• copy the file profile.ps1 to $PROFILE
• restore the terminal - it should be ready to work

---

For Linux

1. Installation of dependencies In distributions based on the Debian system, programs such as fzf and micro should be available in official repositories - this is the case, for example, for Debian 12. If necessary, use the information contained on the websites of these programs.

Example of installation:

sudo apt update
sudo apt install fzf micro bat

2. Configuration

• copy the bash_func.sh file (downloaded from the repository) to the directory in which you store your own scripts (let's assume that this is the .scripts catalog)
• use the chmod command to make the script executable

cp bash_func.sh ~/.scripts/fzf_func.sh
chmod +x ~/.scripts/fzf_func.sh

• open the .bashrc file eg.: micro .bashrc
• add at the end of the file: path to the directory with your scripts (eg. ~/.scripts) to $PATH
• add at the end of the file: source path_to_script.sh

export PATH="$HOME/.scripts:$PATH"
source $HOME/.scripts/fzf_linux_func.sh

---

Micro

Micro settings

1. Configuring the micro editor involves placing entries in the settings.json file. File location:

   • Windows:

     # PowerShell
     $env:APPDATA\micro\settings.json
     
     # CMD.exe
     %APPDATA%\micro\settings.json
     
     # example: C:\Users\<YourName>\AppData\Roaming\micro\settings.json

   • Linux:

     ~/.config/micro/settings.json

   • macOs:

     ~/Library/Application Support/micro/settings.json

2. Minimal settings (Python-friendly):

   {
     "autoindent": true,
     "tabstospaces": true,
     "tabsize": 4,
   
     "detectindent": false,
     "rmtrailingws": true,
   
     "colorcolumn": 80
   }

3. settings_micro.json

   The settings shown above are available in the repository in the settings_micro.json file. Copy the file to the appropriate location and rename it to settings.json

Micro help

1. Link to Default Keys
2. In the opened editor, enter:

• <ctr> + e: open a command prompt for running commands
• Tab: In command prompt, it will autocomplete if possible.
• In command prompt: help defa + Tab --> help defaultkeys - will display help on defined keyboard shortcuts

3. Basic shortcuts:

• <ctr> + q: close current file (quits micro if this is the last file open)
• <ctr> + o: open a file (prompts for filename)
• <ctr> + s: save current file.

Tools

If the software installation and configuration have been made, the following tools for work in the terminal should be available:

• mc: launches the user-defined editor - probably micro
• fzf: interactive file search in the current working directory
• mcc: file search in the user's home directory with content preview (only text files) and opening to the edition of the selected file
• cdd: search for catalogs with a preview of their content and transition to the selected directory

In the entered patterns you can use:

• $ - means that the pattern ends the line, e.g. TXT $ will search for all files or catalogs ending with txt
• | logical or e.g.txt $ | csv
• ' ' (space) logical and eg: txt$ csv

Web browser

To view rendered markdown files, you may find useful browser extensions:

1. Google Chrome: Markdown Viewer
2. Mozilla Firefox: Markdown Viewer
3. Microsoft Edge: Markdown Preview
4. Safari: QLMarkdown

Windows terminal settings

Creating a new account in Windows 11 requires each time settings according to the user's preferences. The settings.json file contains the settings for the terminal in Windows 11. Example settings:

• window size
• font size
• color scheme

Paste this file in a specific location on the disk allows you to easily transfer settings between accounts.

1. Determining the location of the settings.json file:

• open powershell
• run the cdd function
• type: microsoft terminal state
• go to the directory containing the settings.json file

2. For safety, make a copy of the original file:

cp settings.json settings-copy.json

3. Copy the settings.json file (downloaded from gidhub):