Da tempo ero alla ricerca di una soluzione software semplice, veloce e minimale per poter prendere, gestire e rileggere appunti di testo tramite terminale durante la mie attività al computer. Su piattaforma GNU/Linux ci sono alcune soluzioni libere realizzate con queste premesse ma nessuno dei software che ho trovato, nonostante la qualità, soddisfaceva le mie esigenze. In particolare, quello che cercavo e avevo in mente, non era niente più che una semplice interfaccia di gestione che mi permettesse di controllare da riga di comando tutto il processo di scrittura e lettura di appunti appoggiandomi ad un editor presistente, nel mio caso nano.

può esserci sicuramente utile questo software, dall’utilizzo semplice, che permette di inviare mails utilizzando come relay Gmail (o qualsiasi altro SMTP) tramite le nostre credenziali (user/pwd)...

Using the GCC compiler Automating builds with make The preceding post, “Programming Environments and Interfaces,” provided a high-level view of Linux programming, focusing on the overall development environment and introducing the idioms that give programming on a Linux system its distinctive character. This chapter goes into greater detail and describes some of the tools and toys found on a typical Linux development system. Examining library utilities Exploring source code control The goal of this chapter is not to turn you into a developer in 30 pages or less, but simply to explore some of the variety of tools developers use so you will at least know what they are and what they do. You’ll also learn how to use some of the programs and utilities. Debugging with GDB

If you are using Linux over a network or from a dumb terminal (a monitor that allows only text input with no GUI support), your shell may be all that you have. You may be used to a windowing environment where you have a lot of programs active at the same time so that you can switch among them as needed. This shell thing can seem pretty limited. Although the bash shell doesn’t include a GUI for running many programs, it does let you move active programs between the background and foreground. In this way, you can have a lot of stuff running, while selectively choosing the one you want to deal with at the moment. There are several ways to place an active program in the background. One mentioned earlier is to add an ampersand (&) to the end of a command line. Another way is to use the at command to run commands in a way in which they are not connected to the shell.

Linux File Systems Versus Windows-Based File Systems Although similar in many ways, the Linux file system has some striking differences from file systems used in MS-DOS and Windows operating systems. There are a few: In MS-DOS and Windows file systems, drive letters represent different storage devices (for example, A: is a floppy drive and C: is a hard disk). In Linux, all storage devices are fit into the file system hierarchy. So, the fact that all of /usr may be on a separate hard disk or that /mnt/rem1 is a file system from another computer is invisible to the user.

Command-Line Recall After you type a command line, that entire command line is saved in your shell’s history list. The list is stored in a history file, from which any command can be recalled to run again. After it is recalled, you can modify the command line, as described earlier. To view your histor y list, use the history command. Type the command without options or followed by a number to list that many of the most recent commands

Although similar in many ways, the Linux file system has some striking differences from file systems used in MS-DOS and Windows operating systems. Here are a few: In MS-DOS and Windows file systems, drive letters represent different storage devices (for example, A: is a floppy drive and C: is a hard disk). In Linux, all storage devices are fit into the file system hierarchy. So, the fact that all of /usr may be on a separate hard disk or that /mnt/rem1 is a file system from another computer is invisible to the user.

Bash Configuration Files File Description /etc/profile Sets up user environment information for every user. It is executed when you first log in. This file provides values for your path, as well as setting environment variables for such things as the location of your mailbox and the size of your history files. Finally, /etc/profile gathers shell settings from configuration files in the /etc/profile.d directory. /etc/bashrc Executes for every user who runs the bash shell, each time a bash shell is opened. It sets the default prompt and may add one or more aliases. Values in this file can be overridden by information in each user’s ~/.bashrc file.