neulab/tldr huggingface dataset:
NOTIFY-SEND(1)                    User Commands                   NOTIFY-SEND(1)
notify-send - a program to send desktop notifications
notify-send [OPTIONS] {summary} [body]
With notify-send you can send desktop notifications to the user via a notification daemon from the command line. These notifications can be used to inform the user about an event or display some form of information without getting in the userâ€™s way.
-?, --help Show help and exit.
-u, --urgency=LEVEL Specifies the urgency level (low, normal, critical).
-t, --expire-time=TIME The duration, in milliseconds, for the notification to appear on screen.
(Ubuntu's Notify OSD and GNOME Shell both ignore this parameter.)
-i, --icon=ICON[,ICON...] Specifies an icon filename or stock icon to display.
-c, --category=TYPE[,TYPE...] Specifies the notification category.
-h, --hint=TYPE:NAME:VALUE Specifies basic extra data to pass. Valid types are INT, DOUBLE, STRING and BYTE.
The Desktop Notification Spec on http://www.galago-project.org/specs/notification/.
Andre Filipe de Assuncao e Brito <decko@noisemakers.org> Original author
Paul van Tilburg <paulvt@debian.org> Original author
Riccardo Setti <giskard@debian.org> Original author
NICE(1P)                    POSIX Programmer's Manual                   NICE(1P)
This manual page is part of the POSIX Programmer's Manual.  The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.
nice — invoke a utility with an altered nice value
nice [-n increment] utility [argument...]
The nice utility shall invoke a utility, requesting that it be run with a different nice value (see the Base Definitions volume of POSIX.1‐2017, Section 3.244, Nice Value).  With no options, the executed utility shall be run with a nice value that is some implementation-defined quantity greater than or equal to the nice value of the current process. If the user lacks appropriate privileges to affect the nice value in the requested manner, the nice utility shall not affect the nice value; in this case, a warning message may be written to standard error, but this shall not prevent the invocation of utility or affect the exit status.
The nice utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
The following option is supported:
-n increment A positive or negative decimal integer which shall have the same effect on the execution of the utility as if the utility had called the nice() function with the numeric value of the increment option-argument.
The following operands shall be supported:
utility   The name of a utility that is to be invoked. If the utility operand names any of the special built-in utilities in Section 2.14, Special Built-In Utilities, the results are undefined.
argument  Any string to be supplied as an argument when invoking the utility named by the utility operand.
The following environment variables shall affect the execution of nice:
LANG      Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
LC_ALL    If set to a non-empty string value, override the values of all the other internationalization variables.
LC_CTYPE  Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments).
LC_MESSAGES Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
NLSPATH   Determine the location of message catalogs for the processing of LC_MESSAGES.
PATH      Determine the search path used to locate the utility to be invoked.  See the Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables.
The standard error shall be used only for diagnostic messages.
If utility is invoked, the exit status of nice shall be the exit status of utility; otherwise, the nice utility shall exit with one of the following values:
1‐125   An error occurred in the nice utility.
126   The utility specified by utility was found but could not be invoked.
127   The utility specified by utility could not be found.
The following sections are informative.
The only guaranteed portable uses of this utility are:
nice utility Run utility with the default higher or equal nice value.
nice -n <positive integer> utility Run utility with a higher nice value.
On some implementations they have no discernible effect on the invoked utility and on some others they are exactly equivalent.
Historical systems have frequently supported the <positive integer> up to 20. Since there is no error penalty associated with guessing a number that is too high, users without access to the system conformance document (to see what limits are actually in place) could use the historical 1 to 20 range or attempt to use very large numbers if the job should be truly low priority.
The nice value of a process can be displayed using the command:
ps -o nice
The command, env, nice, nohup, time, and xargs utilities have been specified to use exit code 127 if an error occurs so that applications can distinguish ``failure to find a utility'' from ``invoked utility exited with an error indication''. The value 127 was chosen because it is not commonly used for other meanings; most utilities use small values for ``normal error conditions'' and the values above 128 can be confused with termination due to receipt of a signal. The value 126 was chosen in a similar manner to indicate that the utility could be found, but not invoked. Some scripts produce meaningful error messages differentiating the 126 and 127 cases. The distinction between exit codes 126 and 127 is based on KornShell practice that uses 127 when all attempts to exec the utility fail with [ENOENT], and uses 126 when any attempt to exec the utility fails for any other reason.
The 4.3 BSD version of nice does not check whether increment is a valid decimal integer. The command nice -x utility, for example, would be treated the same as the command nice --1 utility.  If the user does not have appropriate privileges, this results in a ``permission denied'' error.  This is considered a bug.
When a user without appropriate privileges gives a negative increment, System V treats it like the command nice -0 utility, while 4.3 BSD writes a ``permission denied'' message and does not run the utility. The standard specifies the System V behavior together with an optional BSD- style ``permission denied'' message.
The C shell has a built-in version of nice that has a different interface from the one described in this volume of POSIX.1‐2017.
The term ``utility'' is used, rather than ``command'', to highlight the fact that shell compound commands, pipelines, and so on, cannot be used. Special built-ins also cannot be used.  However, ``utility'' includes user application programs and shell scripts, not just utilities defined in this volume of POSIX.1‐2017.
Historical implementations of nice provide a nice value range of 40 or 41 discrete steps, with the default nice value being the midpoint of that range. By default, they raise the nice value of the executed utility by 10.
Some historical documentation states that the increment value must be within a fixed range. This is misleading; the valid increment values on any invocation are determined by the current process nice value, which is not always the default.
The definition of nice value is not intended to suggest that all processes in a system have priorities that are comparable. Scheduling policy extensions such as the realtime priorities in the System Interfaces volume of POSIX.1‐2017 make the notion of a single underlying priority for all scheduling policies problematic. Some implementations may implement the nice-related features to affect all processes on the system, others to affect just the general time-sharing activities implied by this volume of POSIX.1‐2017, and others may have no effect at all. Because of the use of ``implementation-defined'' in nice and renice, a wide range of implementation strategies are possible.
Earlier versions of this standard allowed a -increment option. This form is no longer specified by POSIX.1‐2008 but may be present in some implementations.
Chapter 2, Shell Command Language, renice
The Base Definitions volume of POSIX.1‐2017, Section 3.244, Nice Value, Chapter 8, Environment Variables, Section 12.2, Utility Syntax Guidelines
The System Interfaces volume of POSIX.1‐2017, nice()
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group.  In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .
GIT-COLA(1)                         git-cola                         GIT-COLA(1)
git-cola - The highly caffeinated Git GUI
git cola [options] [sub-command]
git cola is a sleek and powerful Git GUI.
–amend Start git cola in amend mode.
–prompt Prompt for a Git repository.  Defaults to the current directory.
-r, –repo <path> Open the Git repository at <path>.  Defaults to the current directory.
-s, –status-filter <filter> Apply the path filter to the status widget.
–version Print the git cola version and exit.
-h, –help Show usage and optional arguments.
–help-commands Show available sub-commands.
SUB-COMMANDS am Apply patches.
archive Export tarballs from Git.
branch Create branches.
browse Browse tracked files.
config Configure settings.
dag Start the git dag Git history browser.
diff Diff changed files.
fetch Fetch history from remote repositories.
grep Use git grep to search for content.
merge Merge branches.
pull Fetch and merge remote branches.
push Push branches to remotes.
rebase Start an interactive rebase.
remote Create and edit remotes.
search Search for commits.
stash Stash uncommitted modifications.
tag Create tags.
version Print the git cola version.
The editor used by Ctrl-e is configured from the Preferences screen.  The environment variable $VISUAL is consulted when no editor has been configured.
ProTip: Configuring your editor to gvim -f -p will open multiple tabs when editing files.  gvim -f -o uses splits.
git cola is {vim, emacs, textpad, notepad++}-aware.  When you select a line in the grep screen and press any of Enter, Ctrl-e, or the Edit button, you are taken to that exact line.
The editor preference is saved in the gui.editor variable using git config.
git cola has many useful keyboard shortcuts.
You can see the available shortcuts by pressing the ? key, choosing Help -> Keyboard shortcuts from the main menu, or by consulting the git cola keyboard shortcuts reference.
The git cola interface is composed of various cooperating tools. Double-clicking a tool opens it in its own subwindow.  Dragging it around moves and places it within the window.
Tools can be hidden and rearranged however you like.  git cola carefully remembers your window layout and restores it the next time it is launched.
The Control-{1, 2, 3, …} hotkey gives focus to a specific tool.  A hidden tool can be re-opened using the Tools menu or the Shift+Control-{1, 2, 3, …} shortcut keys.
The Diff editor can be focused with Ctrl-j.  the Status tool can be focused with Ctrl-k.  the Commit tool can be focused with Ctrl-l.
The Status tool provides a visual analog to the git status command.
Status displays files that are modified relative to the staging area, staged for the next commit, unmerged files from an in-progress merge, and files that are untracked to git.
These are the same categories one sees when running git status on the command line.
You can navigate through the list of files using keyboard arrows as well as the ergonomical and vim-like j and k shortcut keys.
There are several convenient ways to interact with files in the Status tool.
Selecting a file displays its diff in the DIFF viewer.  Double-clicking a file stages its contents, as does the the Ctrl-s shortcut key.
Ctrl-e opens selected files in the conifgured editor, and Ctrl-d opens selected files using git difftool
Additional actions can be performed using the right-click context menu.
Actions Clicking the Staged folder shows a diffstat for the index.
Clicking the Modified folder shows a diffstat for the worktree.
Clicking individual files sends diffs to the Diff Display.
Double-clicking individual files adds and removes their content from the index.
Various actions are available through the right-click context menu. Different actions are available depending a file’s status.
Stage Selected Add to the staging area using git add Marks unmerged files as resolved.
Launch Editor Launches the configured visual text editor
Launch Difftool Visualize changes using git difftool.
Revert Unstaged Edits Reverts unstaged content by checking out selected paths from the index/staging area
Revert Uncommitted Edits Throws away uncommitted edits
Unstage Selected Remove from the index/staging area with git reset
Launch Merge Tool Resolve conflicts using git mergetool.
Delete File(s) Delete untracked files from the filesystem.
Add to .gitignore Adds untracked files to to the .gitignore file.
The diff viewer/editor displays diffs for selected files.  Additions are shown in green and removals are displayed in light red.  Extraneous whitespace is shown with a pure-red background.
Right-clicking in the diff provides access to additional actions that use either the cursor location or text selection.
Staging content for commit The @@ patterns denote a new diff hunk.  Selecting lines of diff and using the Stage Selected Lines command will stage just the selected lines.  Clicking within a diff hunk and selecting Stage Diff Hunk stages the entire patch diff hunk.
The corresponding opposite commands can be performed on staged files as well, e.g. staged content can be selectively removed from the index when we are viewing diffs for staged content.
The commit message editor is a simple text widget for entering commit messages.
You can navigate between the Subject and Extended description… fields using the keyboard arrow keys.
Pressing enter when inside the Subject field jumps down to the extended description field.
The Options button menu to the left of the subject field provides access to the additional actions.
The Ctrl+i keyboard shortcut adds a standard “Signed-off-by: ” line, and Ctrl+Enter creates a new commit using the commit message and staged content.
Sign Off The Sign Off button adds a standard:
Signed-off-by: A. U. Thor <a.u.thor@example.com>
line to the bottom of the commit message.
Invoking this action is equivalent to passing the -s option to git commit.
Commit The commit button runs git commit.  The contents of the commit message editor is provided as the commit message.
Only staged files are included in the commit – this is the same behavior as running git commit on the command-line.
Line and Column Display The current line and column number is displayed by the editor.  E.g. a 5,0 display means that the cursor is located at line five, column zero.
The display changes colors when lines get too long.  Yellow indicates the safe boundary for sending patches to a mailing list while keeping space for inline reply markers.
Orange indicates that the line is starting to run a bit long and should break soon.
Red indicates that the line is running up against the standard 80-column limit for commit messages.
Keeping commit messages less than 76-characters wide is encouraged.  git log is a great tool but long lines mess up its formatting for everyone else, so please be mindful when writing commit messages.
Amend Last Commit Clicking on Amend Last Commit makes git cola amend the previous commit instead of creating a new one.  git cola loads the previous commit message into the commit message editor when this option is selected.
The Status tool will display all of the changes for the amended commit.
Create Signed Commit Tell git commit and git merge to sign commits using GPG.
Using this option is equivalent to passing the --gpg-sign option to git commit and git merge.
This option’s default value can be configured using the cola.signcommits configuration variable.
Prepare Commit Message The Commit -> Prepare Commit Message action or Ctrl-Shift-Return keyboard shortcut runs the cola-prepare-commit-msg hook if it is available in .git/hooks/.  This is a git cola-specific hook that takes the same parameters as Git’s prepare-commit-msg hook
The hook is passed the path to .git/GIT_COLA_MSG as the first argument and the hook is expected to write an updated commit message to specified path.  After running this action, the commit message editor is updated with the new commit message.
To override the default path to this hook set the cola.prepareCommitMessageHook git config variable to the path to the hook script.  This is useful if you would like to use a common hook across all repositories.
The Branches tool provides a visual tree to navigate through the branches.  The tree has three main nodes Local Branch, Remote Branch and Tags.  Branches are grouped by their name divided by the character ‘/’.Ex:
branch/feature/foo branch/feature/bar branch/doe
Will produce:
branch - doe + feature - bar - foo
Current branch will display a star icon. If current branch has commits ahead/behind it will display an up/down arrow with its number.
Actions Various actions are available through the right-click context menu. Different actions are available depending of selected branch status.
Checkout The checkout action runs git checkout [<branchname>].
Merge in current branch The merge action runs git merge –no-commit [<branchname>].
Pull The pull action runs git pull –no-ff [<remote>] [<branchname>].
Push The push action runs git push [<remote>] [<branchname>].
Rename Branch The rename branch action runs git branch -M [<branchname>].
Delete Branch The delete branch branch action runs git branch -D [<branchname>].
Delete Remote Branch The remote branch action runs git push –delete [<remote>] [<branchname>].
Use the File -> Apply Patches menu item to begin applying patches.
Dragging and dropping patches onto the git cola interface adds the patches to the list of patches to apply using git am.
You can drag either a set of patches or a directory containing patches. Patches can be sorted using in the interface and are applied in the same order as is listed in the list.
When a directory is dropped git cola walks the directory tree in search of patches.  git cola sorts the list of patches after they have all been found.  This allows you to control the order in which patchs are applied by placing patchsets into alphanumerically-sorted directories.
git cola remembers modifications to the layout and arrangement of tools within the git cola interface.  Changes are saved and restored at application shutdown/startup.
git cola can be configured to not save custom layouts by unsetting the Save Window Settings option in the git cola preferences.
These variables can be set using git config or from the settings.
cola.blameviewer The command used to blame files.  Defaults to git gui blame.
cola.browserdockable Whether to create a dock widget with the Browser tool.  Defaults to false to speedup startup time.
cola.checkconflicts Inspect unmerged files for conflict markers before staging them.  This feature helps prevent accidental staging of unresolved merge conflicts. Defaults to true.
cola.defaultrepo git cola, when run outside of a Git repository, prompts the user for a repository.  Set cola.defaultrepo to the path of a Git repository to make git cola attempt to use that repository before falling back to prompting the user for a repository.
cola.dictionary Specifies an additional dictionary for git cola to use in its spell checker.  This should be configured to the path of a newline-separated list of words.
cola.expandtab Expand tabs into spaces in the commit message editor.  When set to true, git cola will insert a configurable number of spaces when tab is pressed. The number of spaces is determined by cola.tabwidth.  Defaults to false.
cola.fileattributes Enables per-file gitattributes encoding support when set to true.  This tells git cola to honor the configured encoding when displaying and applying diffs.
cola.fontdiff Specifies the font to use for git cola’s diff display.
cola.icontheme Specifies the icon themes to use throughout git cola. The theme specified must be the name of the subdirectory containing the icons, which in turn must be placed in the inside the main “icons” directory in git cola’s installation prefix.
If unset, or set either “light” or “default”, then the default style will be used.  If set to “dark” then the built-in “dark” icon theme, which is suitable for a dark window manager theme, will be used.
If set to an absolute directory path then icons in that directory will be used.  This value can be set to multiple values using, git config –add cola.icontheme $theme.
This setting can be overridden by the GIT_COLA_ICON_THEME environment variable, which can specify multiple themes using a colon-separated value.
The icon theme can also be specified by passing –icon-theme=<theme> on the command line, once for each icon theme, in the order that they should be searched.  This can be used to override a subset of the icons, and fallback to the built-in icons for the remainder.
cola.inotify Set to false to disable file system change monitoring.  Defaults to true, but also requires either Linux with inotify support or Windows with pywin32 installed for file system change monitoring to actually function.
cola.refreshonfocus Set to true to automatically refresh when git cola gains focus.  Defaults to false because this can cause a pause whenever switching to git cola from another application.
cola.linebreak Whether to automatically break long lines while editing commit messages. Defaults to true.  This setting is configured using the Preferences dialog, but it can be toggled for one-off usage using the commit message editor’s options sub-menu.
cola.maxrecent git cola caps the number of recent repositories to avoid cluttering the start and recent repositories menu.  The maximum number of repositories to remember is controlled by cola.maxrecent and defaults to 8.
cola.dragencoding git cola encodes paths dragged from its widgets into utf-16 when adding them to the drag-and-drop mime data (specifically, the text/x-moz-url entry).  utf-16 is used to make gnome-terminal see the right paths, but other terminals may expect a different encoding.  If you are using a terminal that expects a modern encoding, e.g. terminator, then set this value to utf-8.
cola.readsize git cola avoids reading large binary untracked files.  The maximum size to read is controlled by cola.readsize and defaults to 2048.
cola.safemode The “Stage” button in the git cola Actions panel stages all files when it is activated and no files are selected.  This can be problematic if it is accidentally triggered after carefully preparing the index with staged changes.  “Safe Mode” is enabled by setting cola.safemode to true.  When enabled, git cola will do nothing when “Stage” is activated without a selection.  Defaults to false.
cola.savewindowsettings git cola will remember its window settings when set to true.  Window settings and X11 sessions are saved in $HOME/.config/git-cola.
cola.showpath git cola displays the absolute path of the repository in the window title.  This can be disabled by setting cola.showpath to false.  Defaults to true.
cola.signcommits git cola will sign commits by default when set true. Defaults to false. See the section below on setting up GPG for more details.
cola.tabwidth The number of columns occupied by a tab character.  Defaults to 8.
cola.terminal The command to use when launching commands within a graphical terminal.
cola.terminal defaults to xterm -e when unset.  e.g. when opening a shell, git cola will run xterm -e $SHELL.
If either gnome-terminal, xfce4-terminal, or konsole are installed then they will be preferred over xterm when cola.terminal is unset.
cola.textwidth The number of columns used for line wrapping.  Tabs are counted according to cola.tabwidth.
cola.turbo Set to true to enables “turbo” mode.  “Turbo” mode disables some features that can slow things down when operating on huge repositories.  “Turbo” mode will skip loading Git commit messages, author details, status information, and commit date details in the File Browser tool.  Defaults to false.
cola.color.text The default diff text color, in hexadecimal #RRGGBB notation.  Defaults to “#030303”:
git config cola.color.text '#030303'
cola.color.add The default diff “add” background color, in hexadecimal #RRGGBB notation. Defaults to “#d2ffe4”:
git config cola.color.add '#d2ffe4'
cola.color.remove The default diff “remove” background color, in hexadecimal #RRGGBB notation.  Defaults to “#fee0e4”:
git config cola.color.remove '#fee0e4'
cola.color.header The default diff header text color, in hexadecimal #RRGGBB notation. Defaults to “#bbbbbb”:
git config cola.color.header '#bbbbbb'
gui.diffcontext The number of diff context lines to display.
gui.displayuntracked git cola avoids showing untracked files when set to false.
gui.editor The default text editor to use is defined in gui.editor.  The config variable overrides the VISUAL environment variable.  e.g. gvim -f -p.
gui.historybrowser The history browser to use when visualizing history.  Defaults to gitk.
diff.tool The default diff tool to use.
merge.tool The default merge tool to use.
user.email Your email address to be recorded in any newly created commits.  Can be overridden by the ‘GIT_AUTHOR_EMAIL’, ‘GIT_COMMITTER_EMAIL’, and ‘EMAIL’ environment variables.
user.name Your full name to be recorded in any newly created commits.  Can be overridden by the ‘GIT_AUTHOR_NAME’ and ‘GIT_COMMITTER_NAME’ environment variables.
GIT_COLA_ICON_THEME When set in the environment, GIT_COLA_ICON_THEME overrides the theme specified in the cola.icontheme configuration.  Read the section on cola.icontheme above for more details.
GIT_COLA_SCALE IMPORTANT: GIT_COLA_SCALE should not be used with newer versions of Qt.
Set QT_AUTO_SCREEN_SCALE_FACTOR to 1 and Qt will automatically scale the interface to the correct size based on the display DPI.
See the Qt High DPI documentation for more details.
git cola can be made to scale its interface for HiDPI displays.  When defined, git cola will scale icons, radioboxes, and checkboxes according to the scale factor.  The default value is 1.  A good value is 2 for high-resolution displays.
Fonts are not scaled, as their size can already be set in the settings.
GIT_COLA_TRACE When defined, git cola logs git commands to stdout.  When set to full, git cola also logs the exit status and output.  When set to trace, git cola logs to the Console widget.
VISUAL Specifies the default editor to use.  This is ignored when the gui.editor configuration variable is defined.
git cola automatically detects your language and presents some translations when available.  This may not be desired, or you may want git cola to use a specific language.
You can make git cola use an alternative language by creating a ~/.config/git-cola/language file containing the standard two-letter gettext language code, e.g. “en”, “de”, “ja”, “zh”, etc.:
mkdir -p ~/.config/git-cola && echo en >~/.config/git-cola/language
Alternatively you may also use LANGUAGE environmental variable to temporarily change git cola’s language just like any other gettext-based program.  For example to temporarily change git cola’s language to English:
LANGUAGE=en git cola
To make git cola use the zh_TW translation with zh_HK, zh, and en as a fallback.:
LANGUAGE=zh_TW:zh_HK:zh:en git cola
git cola allows you to define custom GUI actions by setting git config variables.  The “name” of the command appears in the “Actions” menu.
guitool.<name>.cmd Specifies the shell command line to execute when the corresponding item of the Tools menu is invoked. This option is mandatory for every tool. The command is executed from the root of the working directory, and in the environment it receives the name of the tool as GIT_GUITOOL, the name of the currently selected file as FILENAME, and the name of the current branch as CUR_BRANCH (if the head is detached, CUR_BRANCH is empty).
guitool.<name>.background Run the command in the background (similar to editing and difftool actions).  This avoids blocking the GUI.  Setting background to true implies noconsole and norescan.
guitool.<name>.needsfile Run the tool only if a diff is selected in the GUI. It guarantees that FILENAME is not empty.
guitool.<name>.noconsole Run the command silently, without creating a window to display its output.
guitool.<name>.norescan Don’t rescan the working directory for changes after the tool finishes execution.
guitool.<name>.confirm Show a confirmation dialog before actually running the tool.
guitool.<name>.argprompt Request a string argument from the user, and pass it to the tool through the ARGS environment variable. Since requesting an argument implies confirmation, the confirm option has no effect if this is enabled. If the option is set to true, yes, or 1, the dialog uses a built-in generic prompt; otherwise the exact value of the variable is used.
guitool.<name>.revprompt Request a single valid revision from the user, and set the REVISION environment variable. In other aspects this option is similar to argprompt, and can be used together with it.
guitool.<name>.revunmerged Show only unmerged branches in the revprompt subdialog. This is useful for tools similar to merge or rebase, but not for things like checkout or reset.
guitool.<name>.title Specifies the title to use for the prompt dialog.  Defaults to the tool name.
guitool.<name>.prompt Specifies the general prompt string to display at the top of the dialog, before subsections for argprompt and revprompt.  The default value includes the actual command.
guitool.<name>.shortcut Specifies a keyboard shortcut for the custom tool.
The value must be a valid string understood by the QAction::setShortcut() API.  See http://qt-project.org/doc/qt-4.8/qkeysequence.html#QKeySequence-2 for more details about the supported values.
Avoid creating shortcuts that conflict with existing built-in git cola shortcuts.  Creating a conflict will result in no action when the shortcut is used.
When creating signed commits gpg will attempt to read your password from the terminal from which git cola was launched.  The way to make this work smoothly is to use a GPG agent so that you can avoid needing to re-enter your password every time you commit.
This also gets you a graphical passphrase prompt instead of getting prompted for your password in the terminal.
Install gpg-agent and friends On Mac OS X, you may need to brew install gpg-agent and install the Mac GPG Suite.
On Linux use your package manager to install gnupg2, gnupg-agent and pinentry-qt, e.g.:
sudo apt-get install gnupg2 gnupg-agent pinentry-qt
On Linux, you should also configure Git so that it uses gpg2 (gnupg2), otherwise you will get errors mentioning, “unable to open /dev/tty”.  Set Git’s gpg.program to gpg2:
git config --global gpg.program gpg2
Configure gpg-agent and a pin-entry program On Mac OS X, edit ~/.gnupg/gpg.conf to include the line,:
use-agent
This is typically not needed on Linux, where gpg2 is used, as this is the default value when using gpg2.
Next, edit ~/.gnupg/gpg-agent.conf to contain a pinentry-program line pointing to the pinentry program for your platform.
The following example ~/.gnupg/gpg-agent.conf shows how to use pinentry-gtk-2 on Linux:
pinentry-program /usr/bin/pinentry-gtk-2 default-cache-ttl 3600
This following example .gnupg/gpg-agent.conf shows how to use MacGPG2’s pinentry app on On Mac OS X:
pinentry-program /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac default-cache-ttl 3600 enable-ssh-support use-standard-socket
Once this has been setup then you will need to reload your gpg-agent config.:
echo RELOADAGENT | gpg-connect-agent
If you see the following output:
Then the daemon is already running, and you do not need to start it yourself.
If it is not running, eval the output of gpg-agent –daemon in your shell prior to launching git cola.:
eval $(gpg-agent --daemon) git cola
Git Installation If Git is installed in a custom location, e.g. not installed in C:/Git or Program Files, then the path to Git must be configured by creating a file in your home directory ~/.config/git-cola/git-bindir that points to your git installation.  e.g.:
C:/Tools/Git/bin
Git Cola’s Git Repository https://github.com/git-cola/git-cola/
Git Cola Homepage https://git-cola.github.io/
Mailing List https://groups.google.com/group/git-cola
David Aguilar and contributors
2007-2019, David Aguilar and contributors
MSMTP(1)                     General Commands Manual                    MSMTP(1)
msmtp - An SMTP client
Sendmail mode (default): msmtp [option...] [--] recipient... msmtp [option...] -t [--] [recipient...]
Configuration mode: msmtp --configure <mailaddress>
Server information mode: msmtp [option...] --serverinfo
Remote Message Queue Starting mode: msmtp [option...] --rmqs=host|@domain|#queue
In the default sendmail mode, msmtp reads a mail from standard input and sends it to an SMTP server for delivery. In server information mode, msmtp prints information about an SMTP server. In Remote Message Queue Starting mode, msmtp sends a Remote Message Queue Starting request for a host, domain, or queue to an SMTP server.
The standard sendmail exit status codes are used, as defined in sysexits.h.
Options override configuration file settings. They are compatible with sendmail where appropriate.
General options
--version Print version information, including information about the libraries used.
--help Print help.
-P, --pretend Print the configuration settings that would be used, but do not take further action.  An asterisk (`*') will be printed instead of your password.
-v, -d, --debug Print lots of debugging information, including the whole conversation with the SMTP server. Be careful with this option: the (potentially dangerous) output will not be sanitized, and your password may get printed in an easily decodable format!
Changing the mode of operation
--configure=mailaddress Generate a configuration for the given mail address and print it. This can be modified or copied unchanged to the configuration file.  Note that this only works for mail domains that publish appropriate SRV records; see RFC 8314.
-S, --serverinfo Print information about the SMTP server and exit. This includes information about supported features (mail size limit, authentication, TLS, DSN, ...) and about the TLS certificate (if TLS is active).
--rmqs=(host|@domain|#queue) Send a Remote Message Queue Starting request for the given host, domain, or queue to the SMTP server and exit.
-C, --file=filename Use the given file instead of ~/.msmtprc or $XDG_CONFIG_HOME/msmtp/config as the user configuration file.
-a, --account=account_name Use the given account instead of the account named "default". The settings of this account may be changed with command line options. This option cannot be used together with the --host option.
--host=hostname Use this SMTP server with settings from the command line; do not use any configuration file data. This option cannot be used together with the --account option.
--port=number Set the port number to connect to. See the port command.
--source-ip=[IP] Set or unset an IP address to bind the socket to. See the source_ip command.
--proxy-host=[IP|hostname] Set or unset a SOCKS proxy to use. See the proxy_host command.
--proxy-port=[number] Set or unset a port number for the proxy host. See the proxy_port command.
--socket=[socketname] Set or unset a local unix domain socket name to connect to. See the socket command.
--timeout=(off|seconds) Set or unset a network timeout, in seconds. See the timeout command.
--protocol=(smtp|lmtp) Set the protocol. See the protocol command.
--domain=[string] Set the argument of the SMTP EHLO (or LMTP LHLO) command. See the domain command.
--auth[=(on|off|method)] Enable or disable authentication and optionally choose the method.  See the auth command.
--user=[username] Set or unset the user name for authentication. See the user command.
--passwordeval=[eval] Evaluate password for authentication. See the passwordeval command.
--tls[=(on|off)] Enable or disable TLS/SSL. See the tls command.
--tls-starttls[=(on|off)] Enable or disable STARTTLS for TLS. See the tls_starttls command.
--tls-trust-file=[file] Set or unset a trust file for TLS. See the tls_trust_file command.
--tls-crl-file=[file] Deprecated. Set or unset a certificate revocation list (CRL) file for TLS. See the tls_crl_file command.
--tls-fingerprint=[fingerprint] Set or unset the fingerprint of a trusted TLS certificate. See the tls_fingerprint command.
--tls-key-file=[file] Set or unset a key file for TLS. See the tls_key_file command.
--tls-cert-file=[file] Set or unset a cert file for TLS. See the tls_cert_file command.
--tls-certcheck[=(on|off)] Enable or disable server certificate checks for TLS. See the tls_certcheck command.
--tls-priorities=[priorities] Set or unset TLS priorities. See the tls_priorities command.
--tls-host-override=[host] Set or unset override for TLS host verification. See the tls_host_override command.
--tls-min-dh-prime-bits=[bits] Deprecated, use --tls-priorities instead.  Set or unset minimum bit size of the Diffie-Hellman (DH) prime. See the tls_min_dh_prime_bits command.
Options specific to sendmail mode
-f, --from=address Set the envelope-from address. If no account was chosen yet (with --account or --host), this option will choose the first account that has the given envelope-from address (set with the from command). If no such account is found, "default" is used. See the from command for substitution patterns supported in address.
-N, --dsn-notify=(off|cond) Set or unset DSN notification conditions. See the dsn_notify command.
-R, --dsn-return=(off|ret) Set or unset the DSN notification amount. See the dsn_return command.  Note that hdrs is accepted as an alias for headers to be compatible with sendmail.
--set-from-header[=(auto|on|off)] Set From header handling. See the set_from_header command.
--set-date-header[=(auto|off)] Set Date header handling. See the set_date_header command.
--remove-bcc-headers[=(on|off)] Enable or disable the removal of Bcc headers. See the remove_bcc_headers command.
--undisclosed-recipients[=(on|off)] Enable or disable the replacement of To/Cc/Bcc with "To: undisclosed-recipients:;".  See the undisclosed_recipients command.
-X, --logfile=[file] Set or unset the log file. See the logfile command.
--logfile-time-format=[fmt] Set or unset the log file time format. See the logfile_time_format command.
--syslog[=(on|off|facility)] Enable or disable syslog logging. See the syslog command.
-t, --read-recipients Read recipient addresses from the To, Cc, and Bcc headers of the mail in addition to the recipients given on the command line.  If any Resent- headers are present, then the addresses from any Resent-To, Resent-Cc, and Resent-Bcc headers in the first block of Resent- headers are used instead.
--read-envelope-from Read the envelope from address from the From header of the mail.
--aliases=[file] Set or unset an aliases file. See the aliases command.
-Fname Msmtp adds a From header to mails that lack it, using the envelope from address. This option allows one to set a full name to be used in that header.
--auto-from[=(on|off)] Obsolete. See the auto_from command.
--maildomain=[domain] Obsolete. See the maildomain command.
--     This marks the end of options. All following arguments will be treated as recipient addresses, even if they start with a `-'.
The following options are accepted but ignored for sendmail compatibility: -Btype, -bm, -G, -hN, -i, -L tag, -m, -n, -O option=value, -ox value
A suggestion for a suitable configuration file can be generated using the --configure option.  Normally, a system wide configuration file and/or a user configuration file contain information about which SMTP server to use and how to use it, but all settings can also be configured on the command line. The information about SMTP servers is organized in accounts. Each account describes one SMTP server: host name, authentication settings, TLS settings, and so on. Each configuration file can define multiple accounts.
The user can choose which account to use in one of three ways:
--account=id Use the given account. Command line settings override configuration file settings.
--host=hostname Use only the settings from the command line; do not use any configuration file data.
--from=address or --read-envelope-from Choose the first account from the system or user configuration file that has a matching envelope-from address as specified by a from command. This works only when neither --account nor --host is used. Subadresses are supported. For example, the envelope from address user+detail@example.com will match the account for user@example.com. Furthermore, the envelope-from address of the account may be a wildcard pattern.  See the from command.
If none of the above options is used (or if no account has a matching from command), then the account "default" is used.
Msmtp transmits mails unaltered to the SMTP server, with the following exceptions: - The Bcc header(s) will be removed. This behavior can be changed with the remove_bcc_headers command and --remove-bcc-headers option. - A From header will be added if the mail does not have one. This can be changed with the set_from_header command and --set-from-header option. The header will use the envelope from address and optionally a full name set with the -F option. - A Date header will be added if the mail does not have one. This can be changed with the set_date_header command and --set-date-header option. - When undisclosed_recipients is set, the original To, Cc, and Bcc headers are removed and replaced with "To: undisclosed-recipients:;".
Skip to the EXAMPLES section for a quick start.
If it exists and is readable, a system wide configuration file SYSCONFDIR/msmtprc will be loaded, where SYSCONFDIR depends on your platform.  Use --version to find out which directory is used. If it exists and is readable, a user configuration file will be loaded (~/.msmtprc will be tried first followed by $XDG_CONFIG_HOME/msmtp/config by default, but see --version). Accounts defined in the user configuration file override accounts from the system configuration file. Configuration data from either file can be changed by command line options.
A configuration file is a simple text file.  Empty lines and comment lines (whose first non-blank character is `#') are ignored. Every other line must contain a command and may contain an argument to that command. The argument may be enclosed in double quotes ("), for example if its first or last character is a blank. If a file name starts with the tilde (~), this tilde will be replaced by $HOME.  If a command accepts the argument on, it also accepts an empty argument and treats that as if it was on. Commands are organized in accounts. Each account starts with the account command and defines the settings for one SMTP account.
Commands are as follows:
defaults Set defaults. The following configuration commands will set default values for all following account definitions in the current configuration file.
account name [:account[,...]] Start a new account definition with the given name. The current default values are filled in. If a colon and a list of previously defined accounts is given after the account name, the new account, with the filled in default values, will inherit all settings from the accounts in the list.
host hostname The SMTP server to send the mail to.  The argument may be a host name or a network address.  Every account definition must contain this command.
port number The port that the SMTP server listens on.  The default is 25 ("smtp"), unless TLS without STARTTLS is used, in which case it is 465 ("smtps").
source_ip [IP] Set a source IP address to bind the outgoing connection to. Useful only in special cases on multi-home systems. An empty argument disables this.
proxy_host [IP|hostname] Use a SOCKS proxy. All network traffic will go through this proxy host, including DNS queries, except for a DNS query that might be necessary to resolve the proxy host name itself (this can be avoided by using an IP address as proxy host name). An empty hostname argument disables proxy usage.  The supported SOCKS protocol version is 5. If you want to use this with Tor, see also "Using msmtp with Tor" below.
proxy_port [number] Set the port number for the proxy host. An empty number argument resets this to the default port.
socket socketname Set the file name of a unix domain socket to connect to. This overrides both host/port and proxy_host/proxy_port.
timeout (off|seconds) Set or unset a network timeout, in seconds. The argument off means that no timeout will be set, which means that the operating system default will be used.
protocol (smtp|lmtp) Set the protocol to use. Currently only SMTP and LMTP are supported. SMTP is the default. See the port command above for default ports.
domain argument Use this command to set the argument of the SMTP EHLO (or LMTP LHLO) command.  The default is localhost, which is stupid but usually works. Try to change the default if mails get rejected due to anti-SPAM measures. Possible choices are the domain part of your mail address (provider.example for joe@provider.example) or the fully qualified domain name of your host (if available). The following substitution patterns are supported: %H will be replaced by $HOSTNAME, or if that fails by the host name of the system. %C will be replaced by the canonical name of %H. %M will be replaced by the contents of /etc/mailname (potentially a different directory is used depending on the build configuration; see the output of msmtp --version and look for the location of the system configuration file).
user login Set the user name for authentication. An empty argument unsets the user name.
password secret Set the password for authentication. An empty argument unsets the password.  Consider using the passwordeval command or a key ring instead of this command, to avoid storing cleartext passwords in the configuration file.
passwordeval [eval] Set the password for authentication to the output (stdout) of the command eval.  This can be used e.g. to decrypt password files on the fly or to query key rings, and thus to avoid storing cleartext passwords. Note that the eval command must not mess with standard input (stdin) because that is where msmtp reads the mail from. If in doubt, append </dev/null to eval.
ntlmdomain [domain] Set a domain for the ntlm authentication method. This is obsolete.
tls_starttls [(on|off)] Choose the TLS variant: start TLS from within the session (on, default), or tunnel the session through TLS (off).
tls_trust_file file Activate server certificate verification using a list of trusted Certification Authorities (CAs). The default is the special value "system", which selects the system default. An empty argument disables trust in CAs.  If you select a file, it must be in PEM format, and you should also use tls_crl_file.
tls_crl_file [file] Deprecated. This sets a certificate revocation list (CRL) file for TLS, to check for revoked certificates (an empty argument, which is the default, disables this).  Nowadays automatic OCSP checks replace CRL file checks.
tls_fingerprint [fingerprint] Set the fingerprint of a single certificate to accept for TLS. This certificate will be trusted regardless of its contents (this overrides tls_trust_file).  The fingerprint should be of type SHA256, but can for backwards compatibility also be of type SHA1 or MD5 (please avoid this).  The format should be 01:23:45:67:.... Use --serverinfo --tls --tls-certcheck=off --tls-fingerprint= to get the server certificate fingerprint.