This option controls whether some Magit commands are automatically bound in the global keymap even before Magit is used for the first time in the current session.
If this variable is non-nil, which it is by default, then the following bindings may be added to the global keymap.
These bindings may be added when
after-init-hook is run.
Each binding is added if and only if at that time no other key
is bound to the same command and no other command is bound to
the same key. In other words we try to avoid adding bindings
that are unnecessary, as well as bindings that conflict with
Adding the above bindings is delayed until
is called to allow users to set the variable anywhere in their
init file (without having to make sure to do so before
is loaded or autoloaded) and to increase the likelihood that
all the potentially conflicting user bindings have already
To set this variable use either
setq or the Custom interface.
Do not use the function
customize-set-variable because doing
that would cause Magit to be loaded immediately when that form
is evaluated (this differs from
doesn’t load the libraries that define the customized variables).
Setting this variable to nil has no effect if that is done after the key bindings have already been added.
We recommend that you bind
C-c g instead of
C-c M-g to
magit-file-dispatch. The former is a much better binding
C-c <letter> namespace is strictly reserved for
users; preventing Magit from using it by default.
(global-set-key (kbd "C-c g") 'magit-file-dispatch)