Skip to content
Commits on May 30, 2016
  1. @npostavs

    Clarify release notes regarding auto revert

    Specifically, about `magit-auto-revert-mode' replacing
    `magit-revert-buffers'.
    
    Close #2665.
    npostavs committed May 30, 2016
  2. @npostavs
Commits on May 29, 2016
  1. @kyleam
  2. @npostavs
Commits on May 28, 2016
  1. @npostavs

    magit-insert-revision-message: remove trailing CRs

    The default format of `git show' removes them as well.
    
    As of May 2016, creating a commit message from Github's web interface
    inserts carriage returns at the end of each line (except the last) in
    the commit message body.  This commit is an example.  
    
    Fixes #2666.
    npostavs committed May 28, 2016
  2. @tarsius

    magit-message: new function

    Add new function `magit-message' as a substitute for `message' to be
    used when the usefulness of a particular message is being disputed.  Add
    new option `magit-no-message' to allow users to configure which messages
    should not be displayed by `magit-message'.
    
    Re #2662.
    tarsius committed May 28, 2016
Commits on May 27, 2016
  1. @npostavs

    magit-insert-worktrees: use string-width

    When we're checking how wide the filenames are, it's more correct to use
    `string-width' than `length'.
    npostavs committed May 27, 2016
  2. @npostavs

    magit-*-copy-*: check use-region-p

    The commands `magit-blame-copy-hash', `magit-copy-section-value',
    `magit-copy-buffer-revision', call `kill-ring-save' when the region is
    active.  The function `use-region-p' should be used to check this rather
    than `region-active-p' so that an empty active region won't
    count (unless the user has set `use-empty-active-region').
    npostavs committed May 27, 2016
  3. @npostavs
  4. @npostavs

    magit-branch-rename: use magit-revision-history

    This makes the name of the branch being renamed available via `M-p',
    similar to Emacs' builtin `rename-file' command.
    npostavs committed May 23, 2016
  5. @npostavs

    magit-branch-read-args: don't default to existing

    Setting magit-branch-read-upstream-first to non-nil is useful when
    creating a local branch of an existing remote topic branch, because it
    gives the remote name as the initial-input.  When creating a new topic
    branch from origin/master this suggests "master" which is invalid since
    that branch (probably) already exists.
    
    Therefore, avoid giving an initial-input when that would be an existing
    branch.
    npostavs committed May 23, 2016
Commits on May 26, 2016
  1. @kyleam

    add magit-display-buffer-fullframe-status-topleft-v1

    This function is an alternative to
    magit-display-buffer-fullframe-status-v1 that makes Magit buffers pop up
    on the same side as they would with magit-display-buffer-traditional.
    
    Do this by calling display-buffer-pop-up-window call and then swapping
    the windows.  This will work best with magit-bury-buffer-function set to
    its default value of magit-restore-window-configuration, but a few
    window parameters are adjusted so that magit-mode-quit-window and
    quit-window behave sensibly.
    
    Another approach would be to make a variant of
    display-buffer-pop-up-window that pops up on the desired side.  However,
    doing this would require either relying on several internal window.el
    functions or re-implementing these functions.  A third approach would be
    to define a display-buffer-above-selected analog of
    display-buffer-below-selected, but this has the same problem as the
    second approach and also deviates from
    magit-display-buffer-traditional's behavior in that it hardcodes a
    horizontal split rather than respecting split-window-preferred-function.
    
    Re: #2656
    kyleam committed May 24, 2016
  2. @kyleam

    magit--display-buffer-fullframe: prefer same window

    Using the current window for the status buffer allows
    magit-mode-quit-window to return to the buffer the was selected when
    magit-status was called.
    kyleam committed May 25, 2016
Commits on May 25, 2016
  1. @kyleam
Commits on May 24, 2016
  1. @npostavs
  2. @npostavs

    magit-insert-worktrees: use short aligned paths

    - Use relative or abbreviated absolute names, whichever is shorter.
    - Align the filename column
    - Drop the "(detached)" case, since it was never hit.  A detached
      worktree is identified by having a commit instead of a branch.
    
    Close #2658
    npostavs committed May 22, 2016
  3. @kyleam

    add more magit-display-buffer-function options

    As mentioned in #2541, there are a lot of possible behaviors for
    display-buffer functions.  Provide a few more options that users can try
    before resorting to writing their own functions.
    
    magit-display-buffer-same-window-except-diff-v1 and
    magit-display-buffer-fullcolumn-most-v1 are modified from variants
    proposed in #2541.  magit-display-buffer-fullframe-status-v1 provides
    the full-frame status behavior that seems to be popular (#1953).
    
    The names of these functions are versioned, as suggested in #2541.
    
    The helper function magit--display-buffer-fullframe is modified from a
    function that Sebastian Wiesner shared in #1953.
    kyleam committed May 21, 2016
  4. @kyleam

    2.7.0.txt: fix typo

    kyleam committed May 23, 2016
Commits on May 22, 2016
  1. @tarsius
Commits on May 21, 2016
  1. @npostavs
  2. @npostavs

    magit-popup-describe-function: use correct window

    If we let `display-buffer' (called by `describe-function') decide where
    to put the *Help* window, it may (if the frame is wide enough) decide to
    split horizontally instead of using the window we were creating earlier
    with `split-window-below'.  This results in 3 windows, 2 of which are
    the popup buffer, and is generally not very helpful.
    
    To avoid this, let-bind `display-buffer-alist' to tell `display-buffer'
    that it should reuse the window we made.
    npostavs committed May 21, 2016
Commits on May 20, 2016
  1. @tarsius

    2.7.0.txt: fix typos

    tarsius committed May 20, 2016
  2. @npostavs

    magit-diff-show-or-scroll: fix stash scrolling

    Since switching to magit-stash-show from magit-diff-stash in [1], the
    stash buffer's mode and refresh args are `magit-stash-mode' and
    stash@{N}, respectively.
    
    Fixes #2654.
    
    [1]: "magit-stash-show: new command" 2014-10-05
    bbb08e2
    npostavs committed May 19, 2016
Commits on May 19, 2016
  1. @tarsius

    add v2.7.1 release notes stub

    tarsius committed May 19, 2016
  2. @tarsius

    reset Package-Requires for Melpa

    tarsius committed May 19, 2016
  3. @tarsius

    release version 2.7.0

    tarsius committed May 19, 2016
  4. @tarsius
Commits on May 17, 2016
  1. @tarsius
  2. @tarsius

    replace setenv with push on process-environment

    Let-binding process-environment does not nessarily protect from changes
    made by setenv, because setenv may destructively modify the list object.
    tarsius committed May 17, 2016
Commits on May 14, 2016
  1. @npostavs

    magit-branch-popup-show-variables: do check it

    magit-branch-popup-setup should only add the config variables if the
    option is non-nil.
    npostavs committed May 14, 2016
  2. @npostavs

    magit-clone: restore dropped code

    The code for setting remote.pushDefault and unsetting origin/HEAD was
    accidentally dropped in [1].
    
    [1]: "magit-clone: run asynchronously"
    cf479b9.
    npostavs committed May 14, 2016
Commits on May 13, 2016
  1. @kyleam

    2.7.0.txt: fix typo

    kyleam committed May 13, 2016
  2. @npostavs

    magit-clone: run asynchronously

    This allows intercepting password prompts, and is also nicer if the
    clone happens to take a long time.
    npostavs committed May 11, 2016
  3. @npostavs

    magit-process-finish: error DATA must be a list

    Also remove text properties from message, to avoid seeing the string
    representation of a magit section showing up in the error message.
    npostavs committed May 13, 2016
Commits on May 12, 2016
  1. @tarsius
Something went wrong with that request. Please try again.