neulab/tldr huggingface dataset:
Create or update a file called ajosey; the resulting file has both the last data modification and last data access timestamps set to November 12, 2007 at 10:15:30 UTC with a fractional second timestamp of .002 seconds:
touch -d "2007-11-12 10:15:30.002Z" ajosey
Create or update a file called cathy; the resulting file has both the last data modification and last data access timestamps set to November 12, 2007 at 10:15:00 local time:
touch -t 200711121015 cathy
Create or update a file called drepper; the resulting file has both the last data modification and last data access timestamps set to November 12, 2007 at 10:15:30 local time:
touch -t 200711121015.30 drepper
Create or update a file called ebb9; the resulting file has both the last data modification and last data access timestamps set to November 12, 2007 at 10:15:30 local time:
touch -t 0711121015.30 ebb9
Create or update a file called eggert; the resulting file has the last data access timestamp set to the corresponding time of the file named mark instead of the current time. If the file exists, the last data modification time is not changed:
touch -a -r mark eggert
The functionality of touch is described almost entirely through references to functions in the System Interfaces volume of POSIX.1‐2017. In this way, there is no duplication of effort required for describing such side-effects as the relationship of user IDs to the user database, permissions, and so on.
There are some significant differences between the touch utility in this volume of POSIX.1‐2017 and those in System V and BSD systems. They are upwards-compatible for historical applications from both implementations:
1. In System V, an ambiguity exists when a pathname that is a decimal number leads the operands; it is treated as a time value. In BSD, no time value is allowed; files may only be touched to the current time. The -t time construct solves these problems for future conforming applications (note that the -t option is not historical practice).
2. The inclusion of the century digits, CC, is also new. Note that a ten-digit time value is treated as if YY, and not CC, were specified. The caveat about the range of dates following the Epoch was included as recognition that some implementations are not able to represent dates beyond 18 January 2038 because they use signed int as a time holder.
The -r option was added because several comments requested this capability.  This option was named -f in an early proposal, but was changed because the -f option is used in the BSD version of touch with a different meaning.
At least one historical implementation of touch incremented the exit code if -c was specified and the file did not exist. This volume of POSIX.1‐2017 requires exit status zero if no errors occur.
In previous version of the standard, if at least two operands are specified, and the first operand is an eight or ten-digit decimal integer, the first operand was assumed to be a date_time operand. This usage was removed in this version of the standard since it had been marked obsolescent previously.
The -d date_time format is an ISO 8601:2004 standard complete representation of date and time extended format with an optional decimal point or <comma> followed by a string of digits following the seconds portion to specify fractions of a second. It is not necessary to recognize "[+/-]hh:mm" and "[+/-]hh" to specify timezones other than local time and UTC. The T time designator in the ISO 8601:2004 standard extended format may be replaced by <space>.
The Base Definitions volume of POSIX.1‐2017, Section 4.16, Seconds Since the Epoch, Chapter 8, Environment Variables, Section 12.2, Utility Syntax Guidelines, <sys_stat.h>
The System Interfaces volume of POSIX.1‐2017, creat(), futimens(), time(), utime()
MKTEMP(1)                         User Commands                        MKTEMP(1)
mktemp - create a temporary file or directory
mktemp [OPTION]... [TEMPLATE]
Create a temporary file or directory, safely, and print its name. TEMPLATE must contain at least 3 consecutive 'X's in last component.  If TEMPLATE is not specified, use tmp.XXXXXXXXXX, and --tmpdir is implied. Files are created u+rw, and directories u+rwx, minus umask restrictions.
-d, --directory create a directory, not a file
-u, --dry-run do not create anything; merely print a name (unsafe)
-q, --quiet suppress diagnostics about file/dir-creation failure
--suffix=SUFF append SUFF to TEMPLATE; SUFF must not contain a slash.  This option is implied if TEMPLATE does not end in X
-p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp.  With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component
-t     interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated]
Written by Jim Meyering and Eric Blake.
mkstemp(3), mkdtemp(3), mktemp(3)
Full documentation <https://www.gnu.org/software/coreutils/mktemp> or available locally via: info '(coreutils) mktemp invocation'
calc(1)                      General Commands Manual                     calc(1)
calc - arbitrary precision calculator
calc [-c] [-C] [-d] [-D calc_debug[:resource_debug[:user_debug]]] [-e] [-f filename] [-h] [-i] [-m mode] [-O] [-p] [-q] [-s] [-u] [-v] [[--] calc_cmd ...]
#!/usr/bin/calc [optional_other_flags ...] -f
-c     Continue reading command lines even after a scan/parse error has caused the abandonment of a line.  Note that this option only deals with scanning and parsing of the calc language.  It does not deal with execution or run-time errors.
calc read many_errors.cal
will cause calc to abort on the first syntax error, whereas:
calc -c read many_errors.cal
will cause calc to try to process each line being read despite the scan/parse errors that it encounters.
By default, calc startup resource files are silently ignored if not found.  This flag will report missing startup resource files unless -d is also given.
-C     Permit the execution of custom builtin functions.  Without this flag, calling the custom() builtin function will simply generate an error.
Use of this flag may cause calc to execute functions that are non- standard and that are not portable.  Custom builtin functions are disabled by default for this reason.
-d     Disable the printing of the opening title.  The printing of resource file debug and informational messages is also disabled as if config("resource_debug", 0) had been executed.
calc "read qtime; qtime(2)"
will output something like:
qtime(utc_hr_offset) defined It's nearly ten past six.
whereas:
calc -d "read qtime; qtime(2)"
will just print:
It's nearly ten past six.
This flag disables the reporting of missing calc startup resource files.
This flag also disables the printing the leading tilde. For example:
calc 2/3
will print:
~0.66666666666666666667
calc -d 2/3
0.66666666666666666667
-D calc_debug[:resource_debug[:user_debug]] Force the initial value of config("calc_debug"), config("resource_debug") and config("user_debug").
The : separated strings are interpreted as signed 32 bit integers. After an optional leading sign a leading zero indicates octal conversion, and a leading ``0x'' or ``0X'' hexadecimal conversion. Otherwise, decimal conversion is assumed.
By default, calc_debug is 0, resource_debug is 3 and user_debug is 0.
For more information use the following calc command:
help config
-e     Ignore any environment variables on startup.  The getenv() builtin will still return values, however.
-f filename This flag is normally only with calc shell scripts.
This flag is required when using calc in shell script mode.  It must be at the end of the initial #!  line of the script, as in:
the rest of the file will be processed in shell script mode.
A common flag to use, prior to the -f on the #! line is the -q flag.  For example:
#!/usr/bin/calc -q -f
This allows the script to run independely of startup scripts.
See SHELL SCRIPT MODE section of this man page below for details.
While the actual form of this flag is:
-f filename
for systems that treat an executable that begins with #!  as a script, the path of the executable is appended by the kernel as the final argument to the exec() system call.  This is why the -f flag at the very end of the #!  line.
It is possible use -f filename on the command line:
calc [optional_other_flags ...] -f filename
This will cause calc to process lines in filename in shell script mode.
The use of -f filename implies the -s flag.
-h     Print a help message.  This option implies -q.  This is equivalent to the calc command help help.  The help facility is disabled unless the mode is 5 or 7.  See -m.
-i     Become interactive if possible.  This flag will cause calc to drop into interactive mode after the calc_cmd arguments on the command line are evaluated.  Without this flag, calc will exit after they are evaluated.
calc 2+5
will print the value 7 and exit whereas:
calc -i 2+5
will print the value 7 and prompt the user for more calc commands.
-m mode This flag sets the permission mode of calc.  It controls the ability for calc to open files and execute programs.  Mode may be a number from 0 to 7.
The mode value is interpreted in a way similar to that of the chmod(1) octal mode:
0  do not open any file, do not execute progs 1  do not open any file 2  do not open files for reading, do not execute progs 3  do not open files for reading 4  do not open files for writing, do not execute progs 5  do not open files for writing 6  do not execute any program 7  allow everything (default mode)
If one wished to run calc from a privileged user, one might want to use -m 0 in an effort to make calc somewhat more secure.
Mode bits for reading and writing apply only on an open.  Files already open are not effected.  Thus if one wanted to use the -m 0 in an effort to make calc somewhat more secure, but still wanted to read and write a specific file, one might want to do in sh(1), ksh(1), bash(1)-like shells:
calc -m 0 3<a.file
Files presented to calc in this way are opened in an unknown mode. Calc will attempt to read or write them if directed.
If the mode disables opening of files for reading, then the startup resource files are disabled as if -q was given.  The reading of key bindings is also disabled when the mode disables opening of files for reading.
-O     Use the old classic defaults instead of the default configuration. This flag as the same effect as executing config("all", "oldcfg") at startup time.
NOTE: Older versions of calc used -n to setup a modified form of the default calc configuration.  The -n flag currently does nothing.  Use of the -n flag is now deprecated and may be used for something else in the future.
-p     Pipe processing is enabled by use of -p.  For example:
calc -p "2^21701-1" | fizzbin
In pipe mode, calc does not prompt, does not print leading tabs and does not print the initial header.  The -p flag overrides -i.
-q     Disable the reading of the startup scripts.
-s     By default, all calc_cmd args are evaluated and executed.  This flag will disable their evaluation and instead make them available as strings for the argv() builtin function.
-u     Disable buffering of stdin and stdout.
-v     Print the calc version number and exit.
--     The double dash indicates to calc that no more option follow. Thus calc will ignore a later argument on the command line even if it starts with a dash.  This is useful when entering negative values on the command line as in:
calc -p -- -1 - -7
With no calc_cmd arguments, calc operates interactively.  If one or more arguments are given on the command line and -s is NOT given, then calc will read and execute them and either attempt to go interactive according as the -i flag was present or absent.
If -s is given, calc will not evaluate any calc_cmd arguments but instead make them available as strings to the argv() builtin function.
Sufficiently simple commands with no no characters like parentheses, brackets, semicolons, '*', which have special interpretations in UNIX shells may be entered, possibly with spaces, until the terminating newline.  For example:
calc 23 + 47
will print 70.  However, command lines will have problems:
calc 23 * 47
calc -23 + 47
The first example above fails because the shell interprets the '*' as a file glob.  The second example fails because '-23' is viewed as a calc option (which it is not) and do calc objects to that it thinks of as an unknown option.  These cases can usually be made to work as expected by enclosing the command between quotes:
calc '23 * 47'
calc "print sqrt(2), exp(1)"
or in parentheses and quotes to avoid leading -'s as in:
calc '(-23 + 47)'
One may also use a double dash to denote that calc options have ended as in:
calc -- -23 + 47
calc -q -- -23 + 47
If '!' is to be used to indicate the factorial function, for shells like csh(1) for which '!' followed by a non-space character is used for history substitution, it may be necessary to include a space or use a backslash to escape the special meaning of '!'.  For example, the command:
print 27!^2
may have to be replaced by:
print 27! ^2   or   print 27^2
Reading from standard input when calc is part of a pipe works as long as the -p flag is given to calc.  For example, this will print chongo was here:
echo chongo was here | calc -p 'print fgetline(files(0));'
while this does not:
echo chongo was here | calc 'print fgetline(files(0));'
nor will this print chongo was here:
echo chongo was here | calc -i 'print fgetline(files(0));'
This is because without -p, the interactive parser, in an effort to parse interactive commands, flushes data on standard input.
Normally on startup, if the environment variable $CALCRC is undefined and calc is invoked without the -q flag, or if $CALCRC is defined and calc is invoked with -e, calc looks for a file "startup" in the calc resource directory .calcrc in the user's home directory, and .calcinit in the current directory.  If one or more of these are found, they are read in succession as calc scripts and their commands executed.  When defined, $CALCRC is to contain a ':' separated list of names of files, and if calc is then invoked without either the -q or -e flags, these files are read in succession and their commands executed.  No error condition is produced if a listed file is not found.
If the mode specified by -m disables opening of files for reading, then the reading of startup files is also disabled as if -q was given.
If the environment variable $CALCPATH is undefined, or if it is defined and calc is invoked with the -e flag, when a file name not beginning with /, ~ or ./, is specified as in:
calc read myfile
calc searches in succession:
./myfile ./myfile.cal /usr/lib/myfile /usr/lib/myfile.cal /usr/share/calc/custom/myfile /usr/share/calc/custom/myfile.cal
If the file is found, the search stops and the commands in the file are executed.  It is an error if no readable file with the specified name is found.  An alternative search path can be specified by defining $CALCPATH in the same way as PATH is defined, as a ':' separated list of directories, and then invoking calc without the -e flag.
Calc treats all open files, other than stdin, stdout and stderr as files available for reading and writing.  One may present calc with an already open file using sh(1), ksh(1), bash(1)-like shells is to:
calc 3<open_file 4<open_file2
For more information use the following calc commands:
help help help overview help usage help environment help config
If the first line of an executable file begins #!  followed by the absolute pathname of the calc program and the first line ends with the flag -f as in:
the rest of the file will be processed in shell script mode.  Note that -s -f must at the end of the initial ``#!'' line.  Any other optional optional_other_flags must come before the -f flag.
In shell script mode the contents of the file are read and executed as if they were in a file being processed by a read command, except that a "command" beginning with '#' followed by whitespace and ending at the next newline is treated as a comment.  Any optional optional_other_flags will be parsed first followed by the later lines within the script itself.
In shell script mode, -s is always assumed.  In addition, -d and -p are automatically set if -i is not given.
For example, if the file /tmp/mersenne:
/* setup */ argc = argv(); program = argv(0); stderr = files(2);
/* parse args */ if (argc != 2) { fprintf(stderr, "usage: %s exp0, program); abort "must give one exponent arg"; } exp = eval(argv(1)); if (!isint(exp) || exp < 0) { fprintf(stderr, "%s: exp must be non-negative integer0, program); abort "must give one exponent arg"; }
/* print the mersenne number */ print "2^": exp : "-1 =", 2^exp-1;
is made an executable file by:
chmod +x /tmp/mersenne
/tmp/mersenne 127
2^127-1 = 170141183460469231731687303715884105727
Note that because -s is required in shell script mode non-dashed args are made available as strings via the argv() builtin function.  Therefore:
2^eval(argv(1))-1
will print the decimal value of 2^n-1 whereas
2^argv(1)-1
will not.
Fundamental builtin data types include integers, real numbers, rational numbers, complex numbers and strings.
By use of an object, one may define an arbitrarily complex data types. One may define how such objects behave a wide range of operations such as addition, subtraction, multiplication, division, negation, squaring, modulus, rounding, exponentiation, equality, comparison, printing and so on.
help types help obj show objfuncs
Variables in calc are typeless.  In other words, the fundamental type of a variable is determined by its content.  Before a variable is assigned a value it has the value of zero.
The scope of a variable may be global, local to a file, or local to a procedure.  Values may be grouped together in a matrix, or into a a list that permits stack and queue style operations.
help variable help mat help list show globals
INPUT/OUTPUT A leading ``0x'' implies a hexadecimal value, a leading ``0b'' implies a binary value, and a ``0'' followed by a digit implies an octal value. Complex numbers are indicated by a trailing ``i'' such as in ``3+4i''. Strings may be delimited by either a pair of single or double quotes.  By default, calc prints values as if they were floating point numbers.  One may change the default to print values in a number of modes including fractions, integers and exponentials.
A number of stdio-like file I/O operations are provided.  One may open, read, write, seek and close files.  Filenames are subject to `` '' expansion to home directories in a way similar to that of the Korn or C- Shell.
~/.calcrc ~chongo/lib/fft_multiply.cal
The calc language is a C-like language.  The language includes commands such as variable declarations, expressions, tests, labels, loops, file operations, function calls.  These commands are very similar to their counterparts in C.
The language also include a number of commands particular to calc itself. These include commands such as function definition, help, reading in resource files, dump files to a file, error notification, configuration control and status.
help command help statement help expression help operator help config
/usr/bin/calc calc binary
/usr/bin/cscript/* calc shell scripts
/usr/lib/*.cal calc standard resource files
/usr/lib/help/* help files
/usr/lib/bindings non-GNU-readline command line editor bindings
/usr/include/calc/*.h include files for C interface use
/usr/lib/libcalc.a calc binary link library
/usr/lib/libcustcalc.a custom binary link library
/usr/share/calc/custom/*.cal custom resource files
/usr/share/calc/custhelp/* custom help files
CALCPATH A :-separated list of directories used to search for calc resource filenames that do not begin with /, ./ or ~.
Default value: .:./cal:~/.cal:/usr/share/calc:/usr/share/calc/custom
CALCRC On startup (unless -h or -q was given on the command line), calc searches for files along this :-separated environment variable.
Default value: ./.calcinit:~/.calcrc:/usr/share/calc/startup
CALCBINDINGS On startup (unless -h or -q was given on the command line, or -m disallows opening files for reading), calc reads key bindings from the filename specified by this environment variable.  The key binding file is searched for along the $CALCPATH list of directories.
Default value: binding
This variable is not used if calc was compiled with GNU-readline support.  In that case, the standard readline mechanisms (see readline(3)) are used.
CALCHISTFILE Location of the calc history file.
Default value: ~/.calc_history
This variable is not used if calc was compiled with GNU-readline support.
CALCHELP Location of the calc help directory.
Default value: /usr/share/calc/help
CALCCUSTOMHELP Location of the calc custom help directory.
Default value: /usr/share/calc/custhelp
The main chunk of calc was written by David I. Bell.
The calc primary mirror, and calc bug report processing is performed by Landon Curt Noll.
Landon Curt Noll maintains the master reference source, performs release control functions as well as other calc maintenance functions.
Thanks for suggestions and encouragement from Peter Miller, Neil Justusson, and Landon Noll.
Thanks to Stephen Rothwell for writing the original version of hist.c which is used to do the command line editing.
Thanks to Ernest W. Bowen for supplying many improvements in accuracy and generality for some numeric functions.  Much of this was in terms of actual code which I gratefully accepted.  Ernest also supplied the original text for many of the help files.
Portions of this program are derived from an earlier set of public domain arbitrarily precision routines which was posted to the net around 1984. By now, there is almost no recognizable code left from that original source.
COPYING / CALC GNU LESSER GENERAL PUBLIC LICENSE Calc is open software, and is covered under version 2.1 of the GNU Lesser General Public License.  You are welcome to change it and/or distribute copies of it under certain conditions.  The calc commands:
help copyright help copying help copying-lgpl
should display the contents of the COPYING and COPYING-LGPL files.  Those files contain information about the calc's GNU Lesser General Public License, and in particular the conditions under which you are allowed to change it and/or distribute copies of it.
You should have received a copy of the version 2.1 of the GNU Lesser General Public License.  If you do not have these files, write to:
Free Software Foundation, Inc. 51 Franklin Street Fifth Floor Boston, MA  02110-1301 USA
Calc is copyrighted in several different ways.  These ways include:
Copyright (C) year  David I. Bell Copyright (C) year  David I. Bell and Landon Curt Noll Copyright (C) year  David I. Bell and Ernest Bowen Copyright (C) year  David I. Bell, Landon Curt Noll and Ernest Bowen Copyright (C) year  Landon Curt Noll Copyright (C) year  Ernest Bowen and Landon Curt Noll Copyright (C) year  Ernest Bowen
This man page is:
Copyright (C) 1999-2021  Landon Curt Noll
and is covered under version 2.1 GNU Lesser General Public License.
If you have a simple general question about calc, send Email to:
calc-quest-mail at asthe dot com
NOTE: Remove spaces and replace 'at' with @, and 'dot' with .
NOTE: Yes, the Email address uses 'asthe', while the web site uses 'isthe'.
PLEASE put following the SPECIAL PHRASE somewhere in your Email Subject line:
calc question
You may add additional words to your subject line.
IMPORTANT: If your Email doesn't contain the above phrase, then we WILL NOT SEE your Email.
PLEASE BE SURE you have that SPECIAL PHRASE somewhere in the subject line!
Suggestion:
From time to time, the Email address and Subject SPECIAL PHRASE may change so verify you have the current info by visiting:
http://www.isthe.com/chongo/tech/comp/calc/calc-question.html
Please limit your questions to general questions about calc.  We cannot go into great detail in our answers, nor can we do your homework, nor can we do much more than answer short general questions about calc.
Please be patient as we cannot always respond to Email messages quickly.
BUG REPORTS / BUG FIXES Send bug reports and bug fixes to:
calc-bugrept at asthe dot com
NOTE: Remove spaces and replace 'at' with @, 'dot' with .
You MUST use following SPECIAL PHRASE in your Email Subject line:
calc bug report
http://www.isthe.com/chongo/tech/comp/calc/calc-bugrept.html
See the BUGS source file or use the calc command:
help bugs
for more information about bug reporting.
Calc is open source.  Contributions of code are welcome.
We welcome and encourage you to send us:
* calc resource files (cal/*.cal) * calc shell scripts (cscript/*.calc) * builtin functions that you have modified or written, i.e.: assocfunc.c comfunc.c func.c func.h listfunc.c matfunc.c qfunc.c zfunc.c * custom functions that you have modified or written (custom/*) * help files modified or written (help/*) * brief description of you added, fixed, improved in CHANGES * regression test cases (cal/regress.cal) * Makefile improvements (Makefile, */Makefile) * other source code modifications (*.c, *.h) * etc. (* */* :) )
If you add functionality to calc, please be sure to modify/patch/add Makefiles, help files, cal/regress.cal test code as well.  Regression test cases are vital to maintaining calc's level of correctness and helps us avoid code bug regression.
In order to consider integrating your code, we need:
* calc version you are working with (please try use the latest version) * new help files or help file patches, if applicable (documentation) * proposed text for the CHANGES file (brief description of what it does) * regress.cal test patch as needed * your source code and/or source code changes (:-))
The best way to send us new code, if your changes are small, is via a patch (diff -c from the latest alpha code to your code).  If your change is large, you should send entire files (either as a diff -c /dev/null your-file patch, or as a uuencoded and gziped (or compressed) tar file).
Please try to generate a patch against the most recent version of calc, and if you use GitHub, the top of the master branch:
https://github.com/lcn2/calc
The best way contribute to calc bug is to generate calc GitHub pull request:
https://github.com/lcn2/calc/pulls
Your code needs to be contributed under either the 2.1 of the GNU Lesser General Public License (LGPL 2.1) or be in the public domain.
If you do not want to use calc GitHub, then send EMail to:
calc-contrib at asthe dot com
calc contribution
http://www.isthe.com/chongo/tech/comp/calc/calc-contrib.html
Landon Noll maintains the calc web site is located at:
www.isthe.com/chongo/tech/comp/calc/
Share and Enjoy! :-)
MIX(1)                     BSD General Commands Manual                    MIX(1)
mix â€” The software project management tool
mix [TASK] [project_name] elixir [OPTIONS] -S mix [TASK] [project_name]
mix is intended for both organizing code into projects and their maintenance. For the latter the tool offers some advanced features like dependency management, packaging, preparing documentation, testing and so on.
Have a look at the SYNOPSIS section and the second way of running mix it offers. The point is that the tool is none other than the Elixir script, therefore it can be invoked via elixir(1) in the same way as any other script. It's useful when you want to run mix with particular options.
All the mix functionality is represented by a set of tasks. A task is a piece of code written in Elixir and intended for solving a particular problem. Like programs, many tasks accept input parameters and/or support options which slightly modify their behaviour, but others do not. There are two types of tasks: those that are available after installation this or that archive (local tasks) and those that are offered by mix (built-in tasks).  The run task will be executed by default if none other has been specified.
In spite of the fact that the greater part of mix is tasks, the man page doesn't contain the help information related to each of them because mix is self-descriptive. Thus, using the help task, you can get both the full list of local/built-in tasks and the information related to a particular task.
An archive, in terms of Erlang/OTP, is the ZIP file with the .ez extension which contains a precompiled OTP application with all its dependencies[1].
An application is an entity that helps to combine sets of components into a single unit to simplify their reusing in other systems[2].
MIX_ARCHIVES Allows specifying the directory into which the archives should be installed (see mix help archive.install).  The ~/.mix/archives directory is used for this purpose by default.
MIX_DEBUG When set, outputs debug information about each task before running it.
MIX_ENV Allows specifying which environment should be used. The dev environment is used by default if none other has been specified.
Sometimes you have to use a particular set of configuration parameter values or perform particular steps when you compile or run a project (or in some other cases).  The mix environments allow grouping values of configuration parameters and steps to switch between them by specifying the necessary environment via MIX_ENV.
MIX_TARGET Allows specifying which target should be used. The host target is used by default if none other has been specified.
MIX_EXS Allows changing the full path to the mix.exs file (see FILES section).  The most obvious use case is to have more than one copy of mix.exs in a project, but it's worth noting that MIX_EXS should be used only if the mix environments (see above) are not enough to solve the problem.
MIX_HOME path to Mix's home directory, stores configuration files and scripts used by Mix
MIX_INSTALL_DIR Specifies directory where Mix.install/2 keeps installs cache
MIX_PATH Allows expanding the code path. If the MIX_PATH environment variable has a value which consists of multiple paths, they must be colon-separated (for Unix-like operating systems) or semicolon- separated (for Windows).
As mentioned above, there are two types of tasks: local and built- in. These tasks are always visible for mix because the directories, in which they are located, are a part of code path. If a task belongs to neither the one type nor the other, MIX_PATH helps you say to mix where it should search the task.
MIX_QUIET When set, does not print information messages to the terminal.
mix.exs Contains the most significant information related to the project, such as its name, version, list of dependencies and so on. As a rule, the file is named mix.exs and located at the top of the project's source tree, but you can change the full path to it using the MIX_EXS environment variable (see the ENVIRONMENT section).
mix.lock Allows locking down the project dependencies with a proper version range before performing any updates. It is useful when you know that your project is incompatible with newer versions of certain dependencies. The file is located at the top of the project's source tree as well as mix.exs (see above).
[1] https://erlang.org/doc/man/code.html#id103620
[2] https://erlang.org/doc/design_principles/applications.html
elixir(1), elixirc(1), iex(1)
UNISON(1)                    General Commands Manual                   UNISON(1)
unison - a file-synchronization tool for Unix and Windows
unison [options] unison root1 root2 [options] unison profilename [options] unison-gtk [options]
This manual page briefly documents Unison, and was written for the Debian GNU/Linux distribution because the original program does not have a manual page. For a full description, please refer to the inbuilt documentation or the manuals in /usr/share/doc/unison/. The unison-gtk binary has similar command-line options, but allows the user to select and create profiles and configure options from within the program.
Unison is a file-synchronization tool for Unix and Windows. It allows two replicas of a collection of files and directories to be stored on different hosts (or different disks on the same host), modified separately, and then brought up to date by propagating the changes in each replica to the other.
Unison offers several advantages over various synchronization methods such as CVS, Coda, rsync, Intellisync, etc. Unison can run on and synchronize between Windows and many UNIX platforms. Unison requires no root privileges, system access or kernel changes to function. Unison can synchronize changes to files and directories in both directions, on the same machine, or across a network using ssh or a direct socket connection.
Transfers are optimised using a version of the rsync protocol, making it ideal for slower links. Unison has a clear and precise specification, and is resilient to failure due to its careful handling of the replicas and its private structures.
All Unison options are long, starting with one dash (`-') only.  A summary of options is included here. For a complete description, see the inbuilt documentation or the manuals in /usr/share/doc/unison/.
-addprefsto specify a file to add new preferences to in interactive mode
-addversionno add version number to name of unison executable on server
-auto  automatically accept default actions
-backup xxx add a regexp to the backup list
-backups keep backup copies of files (deprecated: use 'backup')
-batch batch mode: ask no questions at all
-contactquietly suppress the 'contacting server' message during startup
-debug xxx debug module xxx ('all' -> everything, 'verbose' -> more)
-doc xxx show documentation ('-doc topics' lists topics)
-dumbtty do not try to change terminal settings in text UI
-editor xxx command for displaying the output of the -merge program
-fastcheck do fast (and slightly unsafe) update detection on windows
-follow xxx add a regexp to the follow list
-force xxx force changes from this replica to the other
-group synchronize group
-height n height (in lines) of main window in graphical interface
-ignore xxx add a regexp to the ignore list
-ignorecase ignore upper/lowercase spelling of filenames
-ignorenot xxx add a regexp to the ignorenot list
-killserver kill server when done (even when using sockets)
-log   record actions in file specified by logfile preference
-logfile xxx log file name
-maxbackups n number of backed up versions of a file to keep
-merge xxx command for merging conflicting files
-merge2 xxx command for merging files (when no common version exists)
-numericids don't map uid/gid values by user/group names
-owner synchronize owner
-path xxx path to synchronize
-perms n part of the permissions which is synchronized
-prefer xxx choose this replica's version in case of conflict
-root xxx root of a replica
-rootalias xxx register alias for canonical root names
-rshargs xxx other arguments (if any) for remote shell command
-rshcmd xxx path to the rsh executable
-servercmd xxx name of unison executable on remote server
-silent print nothing (except error messages)
-socket xxx act as a server on a socket
-sortbysize list changed files by size, not name
-sortfirst xxx add a regexp to the sortfirst list
-sortlast xxx add a regexp to the sortlast list
-sortnewfirst list new before changed files
-sshcmd xxx path to the ssh executable
-statusdepth n status display depth for local files
-terse suppress status messages
-testserver exit immediately after the connection to the server
-times synchronize modification times
-ui xxx select user interface ('text' or 'graphic')
-version print version and exit
Some preferences are just boolean flags. Others take numeric or string arguments, indicated in the preferences list by n or xxx. Most of the string preferences can be given several times; the arguments are accumulated into a list internally.
The program is documented fully in the in-built documentation and the manual, available as HTML, PostScript and text in /usr/share/doc/unison/.
This manual page was written by Robert McQueen <robot101@debian.org>, for the Debian GNU/Linux system (but may be used by others).
UNCLUTTER(1X)                                                      UNCLUTTER(1X)
unclutter - remove idle cursor image from screen
unclutter [-display|-d display] [-idle seconds] [-keystroke] [-jitter pixels] [-grab] [-noevents] [-reset] [-root] [-onescreen] [-not] name ...
unclutter removes the cursor image from the screen so that it does not obstruct the area you are looking at after it has not moved for a given time.  It does not do this if the cursor is in the root window or a button is down.  It tries to ignore jitter (small movements due to noise) if you have a mouse that twitches.
-display is followed by the display to open.
-idle  is followed by the number of seconds between polls for idleness. The default is 5.
-keystroke tells unclutter not to use a timeout to determine when to remove the cursor, but to instead wait until a key has been pressed (released, really).
-jitter is followed by the amount of movement of the pointer that is to be ignored and considered as random noise.  The default is 0.
-grab  means use the original method of grabbing the pointer in order to remove the cursor.  This often doesn't interoperate too well with some window managers.
-noevents stops unclutter sending a pseudo EnterNotify event to the X client whose cursor has been stolen.  Sending the event helps programs like emacs think that they have not lost the pointer focus.  This option is provided for backwards compatibility in case some clients get upset.
-reset resets the timeout for idleness after the cursor is restored for some reason (such as a window being pushed or popped) even though the x y coordinates of the cursor have not changed.  Normally, the cursor would immediately be removed again.
-root  means remove the cursor even if it is on the root background, where in principle it should not be obscuring anything useful.
-onescreen restricts unclutter to the single screen specified as display, or the default screen for the display.  Normally, unclutter will unclutter all the screens on a display.
-not   is followed by a list of window names where the cursor should not be removed.  The first few characters of the WM_NAME property on the window need to match one the listed names.  This argument must be the last on the command line.
The -keystroke option may not work (that is, the cursor will not disappear) with clients that request KeyRelease events.  Games and Xt applications using KeyUp in their translation tables are most likely to suffer from this problem.  The most feasible solution is to extend unclutter to use the XTest extension to get all keyboard and mouse events, though this of course requires XTest to be in the server too.
The -keystroke option does not distinguish modifier keys from keys which actually generate characters.  If desired this could be implemented in a simple way by using XLookupString to see if any characters are returned.
someone created a sub-window to my sub-window!
means that unclutter thinks a second unclutter is running, and tried to steal the cursor by creating a sub-window to the sub-window already used to steal the cursor.  This situation quickly deteriorates into a fight no one can win, so it is detected when possible and the program gives up.
Mark M Martin. cetia 7feb1994. mmm@cetia.fr
GIT-SUMMARY(1)                     Git Extras                     GIT-SUMMARY(1)
git-summary - Show repository summary
git-summary [--line] [<commitish>]
Shows a summary of the repository.
<commitish>
Summarize only the range of commits included in the <commitish>.
--line
Summarize with lines other than commits. This actually just results in a call to git-line-summary(1). Any <commitish> is ignored when --line is specified. See git-line-summary(1) for more info.
Outputs a repo summary:
$ git summary
project  : express repo age : 10 months ago commits  : 1893 active   : 93 days files    : 111 authors  : 1285 visionmedia 478 Tj Holowaychuk 48 Aaron Heckmann 34 csausdev 26 ciaranj 6 Guillermo Rauch 3 Nick Poulden 2 Brian McKinney 2 Benny Wong 1 Justin Lilly 1 James Herdman 1 Adam Sanderson 1 Viktor Kelemen 1 Gregory Ritter 1 Greg Ritter 1 ewoudj 1 isaacs 1 Matt Colyer
This command can also take a commitish, and will print a summary for the range of commits included in the commitish:
$ git summary v42..
FROM(1)                    BSD General Commands Manual                   FROM(1)
from â€” print names of those who have sent mail
from [-c] [-s sender] [-f file] [user]
The from utility prints out the mail header lines from the invoker's mailbox.
-c      Just print a count of messages and exit.
-f file The supplied file is examined instead of the invoker's mailbox.  If the -f option is used, the user argument should not be used.  Read from standard input if file name - is given.
-s sender Only mail from addresses containing the supplied string are printed.
If user is given, the user's mailbox is examined instead of the invoker's own mailbox.  (Privileges are required.)
MAIL        If set, the location of the invoker's mailbox.  Otherwise, the default in /var/mail is used.
/var/mail/*
biff(1), mail(1)
The from command appeared in 3.0BSD.
RPCCLIENT(1)                      User Commands                     RPCCLIENT(1)
rpcclient - tool for executing client side MS-RPC functions
rpcclient [-c|--command=COMMANDS] [-I|--dest-ip=IP] [-p|--port=PORT] [-?|--help] [--usage] [-d|--debuglevel=DEBUGLEVEL] [--debug-stdout] [--configfile=CONFIGFILE] [--option=name=value] [-l|--log-basename=LOGFILEBASE] [--leak-report] [--leak-report-full] [-R|--name-resolve=NAME-RESOLVE-ORDER] [-O|--socket-options=SOCKETOPTIONS] [-m|--max-protocol=MAXPROTOCOL] [-n|--netbiosname=NETBIOSNAME] [--netbios-scope=SCOPE] [-W|--workgroup=WORKGROUP] [--realm=REALM] [-U|--user=[DOMAIN/]USERNAME[%PASSWORD]] [-N|--no-pass] [--password=STRING] [--pw-nt-hash] [-A|--authentication-file=FILE] [-P|--machine-pass] [--simple-bind-dn=DN] [--use-kerberos=desired|required|off] [--use-krb5-ccache=CCACHE] [--use-winbind-ccache] [--client-protection=sign|encrypt|off] [-V|--version] {BINDING-STRING|HOST}
rpcclient is a utility initially developed to test MS-RPC functionality in Samba itself. It has undergone several stages of development and stability. Many system administrators have now written scripts around it to manage Windows NT clients from their UNIX workstation.
BINDING-STRING|HOST When connecting to a dcerpc service you need to specify a binding string.
The format is:
TRANSPORT:host[options]
where TRANSPORT is either ncacn_np (named pipes) for SMB or ncacn_ip_tcp for DCERPC over TCP/IP.
"host" is an IP or hostname or netbios name. If the binding string identifies the server side of an endpoint, "host" may be an empty string. See below for more details.
"options" can include a SMB pipe name if using the ncacn_np transport or a TCP port number if using the ncacn_ip_tcp transport, otherwise they will be auto-determined.
•   ncacn_ip_tcp:samba.example.com[1024]
•   ncacn_ip_tcp:samba.example.com[sign,seal,krb5]
•   ncacn_ip_tcp:samba.example.com[sign,spnego]
•   ncacn_np:samba.example.com
•   ncacn_np:samba.example.com[samr]
•   ncacn_np:samba.example.com[samr,sign,print]
•   ncalrpc:/path/to/unix/socket
•   //SAMBA
The supported transports are:
•   ncacn_np - Connect using named pipes
•   ncacn_ip_tcp - Connect over TCP/IP
•   ncalrpc - Connect over local RPC (unix sockets)
The supported options are:
•   sign - Use RPC integrity authentication level
•   seal - Enable RPC privacy (encryption) authentication level
•   connect - Use RPC connect level authentication (auth, but no sign or seal)
•   packet - Use RPC packet authentication level
•   spnego - Use SPNEGO instead of NTLMSSP authentication
•   ntlm - Use plain NTLM instead of SPNEGO or NTLMSSP
•   krb5 - Use Kerberos instead of NTLMSSP authentication
•   schannel - Create a schannel connection
•   smb1 - Use SMB1 for named pipes
•   smb2 - Use SMB2/3 for named pipes
•   validate - Enable the NDR validator
•   print - Enable debug output of packets
•   padcheck - Check reply data for non-zero pad bytes
•   bigendian - Use big endian for RPC
•   ndr64 - Use NDR64 for RPC
-c|--command=<command string> Execute semicolon separated commands (listed below)
-I|--dest-ip IP-address IP address is the address of the server to connect to. It should be specified in standard "a.b.c.d" notation.
Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution mechanism described above in the name resolve order parameter above. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being connected to will be ignored.
There is no default for this parameter. If not supplied, it will be determined automatically by the client as described above.
-p|--port port This number is the TCP port number that will be used when making connections to the server. The standard (well-known) TCP port number for an SMB/CIFS server is 139, which is the default.
-?|--help Print a summary of command line options.
-d|--debuglevel=DEBUGLEVEL level is an integer from 0 to 10. The default value if this parameter is not specified is 1 for client applications.
The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day-to-day running - it generates a small amount of information about operations carried out.
Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.
Note that specifying this parameter here will override the log level parameter in the smb.conf file.
--debug-stdout This will redirect debug output to STDOUT. By default all clients are logging to STDERR.
--configfile=<configuration file> The file specified contains the configuration details required by the client. The information in this file can be general for client and server or only provide client specific like options such as client smb encrypt. See smb.conf for more information. The default configuration file name is determined at compile time.
--option=<name>=<value> Set the smb.conf(5) option "<name>" to value "<value>" from the command line. This overrides compiled-in defaults and options read from the configuration file. If a name or a value includes a space, wrap whole --option=name=value into quotes.
-l|--log-basename=logdirectory Base directory name for log/debug files. The extension ".progname" will be appended (e.g. log.smbclient, log.smbd, etc...). The log file is never removed by the client.
--leak-report Enable talloc leak reporting on exit.
--leak-report-full Enable full talloc leak reporting on exit.
-V|--version Prints the program version number.
-R|--name-resolve=NAME-RESOLVE-ORDER This option is used to determine what naming services and in what order to resolve host names to IP addresses. The option takes a space-separated string of different name resolution options. The best ist to wrap the whole --name-resolve=NAME-RESOLVE-ORDER into quotes.
The options are: "lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows:
•   lmhosts: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see the lmhosts(5) for details) then any name type matches for lookup.
•   host: Do a standard host name to IP address resolution, using the system /etc/hosts, NIS, or DNS lookups. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the /etc/nsswitch.conf file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored.
•   wins: Query a name with the IP address listed in the wins server parameter. If no WINS server has been specified this method will be ignored.
•   bcast: Do a broadcast on each of the known local interfaces listed in the interfaces parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet.
If this parameter is not set then the name resolve order defined in the smb.conf file parameter (name resolve order) will be used.
The default order is lmhosts, host, wins, bcast. Without this parameter or any entry in the name resolve order parameter of the smb.conf file, the name resolution methods will be attempted in this order.
-O|--socket-options=SOCKETOPTIONS TCP socket options to set on the client socket. See the socket options parameter in the smb.conf manual page for the list of valid options.