| Age | Commit message (Collapse) | Author |
|---|
|
As of Git 2.11, the default abbreviation size is no longer hardcoded
as 7 but instead scales with the repository size.
To determine the default abbreviation size in a way that works under
the old and new system, use the length of "git rev-parse --short HEAD".
Unless core.abbrev is set, this will always be at least as large as
the auto-sized value. In the cases where HEAD needs to be lengthened
for an unambiguous id, the size will be larger than the auto-sized
value, but these situations should be rare and harmless.
Closes #2880.
|
|
|
|
This reverts commit f9fba53ae8120fd4977fa86f4cf142a93830ad57.
|
|
This new behavior is consistent with magit-read-range.
Closes #2878.
|
|
|
|
For each major-mode in whose buffers the log margin is supported add
an option `magit-*-margin', which can be customized independently of
the respective options of other modes. `magit-log-margin-spec' used
to control some aspects of how the margin looks for all modes.
Remove the options, adding options/variable:
`magit-duration-spec' -> `magit--age-spec'
`magit-log-margin-spec' ~> (all of the below:)
`magit-log-show-margin' -> `magit-log-margin'
`magit-reflog-show-margin' -> `magit-reflog-margin'
-> `magit-stashes-margin'
-> `magit-log-select-margin'
-> `magit-status-margin'
`magit-refs-show-margin' -> `magit-refs-margin'
For each of the supported major-mode it is now possible to control:
- whether the margin is shown initially,
- whether the committer name is shown,
(though in some modes that would currently just waste space)
- and how the time is presented.
Beside showing the age of a commit, it is now also possible to show
its actual author date.
Previously the margin ended with a pseudo-fringe, but only in log
buffers, because that looked worse in other buffers. Now no such
pseudo-fringe is used anywhere now, because it is not possible to
draw it in the area of the window past the end of the buffer.
|
|
|
|
When magit-find-file and magit-find-file-other-window were introduced,
the value for the default-directory of the buffer corresponded to the
default-directory of the buffer from which the magit-find-file*
command was called. As of e4ee279 (magit-find-{index,file}-noselect:
unify, 2016-06-22), default-directory is instead set to the file's
directory. The new behavior has the advantage that the
default-directory is consistent for a file and doesn't depend on the
arbitrary detail of where the magit-find-file* command was called.
Also, subsequent commands that are sensitive to default-directory will
behave the same way for both a buffer visiting a revision and a buffer
visiting a file in the working tree.
It does, however, lead to problems if that directory doesn't exist in
the working tree, as many commands reasonably assume that
default-directory exists. For example, calling dired-jump in a
revision file whose directory doesn't exist in the working tree will
signal a file-error. Avoid these issues by using the top-level
directory if the subdirectory doesn't exist.
Re: https://github.com/magit/magit/pull/2704#r68160943
|
|
|
|
|
|
|
|
When we switched from `magit-key-mode.el' to `magit-popup.el' the
meaning of prefix arguments changed and so we forced users to read
the documentation before being able to use prefix arguments again.
That was three years ago - we no longer need that safety net.
|
|
I recently saw some Magit screencasts and noticed that even some users
who enjoy Magit enough to create a screencast about it do not hide the
section with common commands. Because I also think that this section
is a distraction I have decided to no longer show it by default.
This increases the odds that some users will never become aware of the
common commands. To counter that the usage instructions displayed in
the echo area now also mention the key that can be used to show those
common commands.
|
|
Previously the default was t to avoid changing key bindings. However
I recently saw a screencast about Magit and noticed how confusing that
essential popup must be to new users who aren't used to Magit's popups
at all yet, and decided that a good first impression is more important
in this case than to preserve the old key bindings.
|
|
Add the command git-rebase-show-or-scroll-down to provide the
scroll-down functionality described in the git-rebase-mode section of
the manual. Extend git-rebase--show-commit rather than calling
magit-diff-show-or-scroll-down directly for the same reasons described
in 7da77ee (git-rebase: disable save check when showing commits,
2016-09-14).
|
|
|
|
|
|
|
|
|
|
This iteration does not suffer from the infinite hang of the
previous version, but the lines it draws are sometimes to short.
There is nothing we can do about it. For more information see
https://github.com/magit/magit/issues/2758 ff.
|
|
|
|
|
|
|
|
|
|
Thanks to Noam, who came up with most of this.
|
|
|
|
|
|
|
|
|
|
|
|
This follows core Emacs behavior. For example M-x shell, term and epa
all export similar env vars. This will enable functionality such as the
pinentry package distributed with Emacs 25.1 being used for the
passphrase for git commit signing with gpg.
|
|
|
|
Fixes #2758#247479656.
|
|
Fixes #2765.
|
|
|
|
|
|
|
|
All output will be nil in a freshly initialized repository.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #2705.
|
|
Changing the buffer changes the value of `default-directory' even though
it is let-bound, because for buffer-local variables such bindings are
buffer-local too.
In [1] we ensured that the desired binding stayed in effect for indirect
buffers, now we extend this to blog buffers. To make it more obvious
what is going on explicitly let-bind `default-directory' twice, but
avoid calculating the value twice.
Fixes #2731.
|
|
Closes #2686.
|
|
|
|
|
|
An element can now be a cons-cell whose cdr is the depth. For elements
that are strings the value of `magit-repository-directories-depth' is
still used.
|
