1. 07 Nov, 2018 1 commit
  2. 25 Oct, 2018 1 commit
  3. 21 Oct, 2018 2 commits
  4. 09 Oct, 2018 1 commit
  5. 08 Oct, 2018 2 commits
  6. 24 Sep, 2018 2 commits
  7. 21 Sep, 2018 1 commit
  8. 17 Sep, 2018 1 commit
  9. 29 Aug, 2018 1 commit
  10. 31 Jul, 2018 1 commit
  11. 26 Jul, 2018 1 commit
  12. 23 Jul, 2018 1 commit
  13. 18 Jul, 2018 1 commit
  14. 14 Jul, 2018 1 commit
  15. 15 Jun, 2018 5 commits
  16. 09 Jun, 2018 1 commit
  17. 07 Jun, 2018 2 commits
  18. 04 Jun, 2018 1 commit
  19. 01 Jun, 2018 1 commit
  20. 31 May, 2018 1 commit
  21. 12 May, 2018 3 commits
  22. 21 Apr, 2018 1 commit
  23. 07 Apr, 2018 1 commit
  24. 02 Apr, 2018 1 commit
  25. 13 Feb, 2018 1 commit
    • Jonas Bernoulli's avatar
      magit-confirm: Simplify · 7648b2e7
      Jonas Bernoulli authored
      Since we are displaying the list of targets right above
      the prompt now anyway, we might as well do it the easy way.
      7648b2e7
  26. 12 Feb, 2018 2 commits
    • Jonas Bernoulli's avatar
      magit-confirm: List targets at bottom of frame · ad4d0036
      Jonas Bernoulli authored
      Also make it more obvious that the list is "part of the question" by
      not separating the list and the question with a mode-line, but make
      sure that there is at least one empty line between the list and the
      prompt. Technically that line may actually be part of the prompt.
      ad4d0036
    • Jonas Bernoulli's avatar
      whitespace-dont-turn-on-in-magit-mode: and maybe don't raise error · d08f91f0
      Jonas Bernoulli authored
      I though it was obvious that the old message implied "... therefore
      do not enable Whitespace mode in Magit buffers.  Please adjust your
      Whitespace mode configuration to prevent that from happening."  But
      it turned out that is not the case.
      
      Change the advice to silently prevent the activation if the attempt
      is made due to the use of `global-whitespace-mode', but if the user
      attempts to enable the local minor-mode directly, then show an error.
      
      The hope is that this compromise results in the fewest invalid bug
      reports.  (There is no bug - not in Magit at least.)
      
      Closes #3374.
      d08f91f0
  27. 02 Feb, 2018 1 commit
  28. 24 Jan, 2018 1 commit
    • Jonas Bernoulli's avatar
      magit-confirm: Fix regression · 42c22614
      Jonas Bernoulli authored
      Unfortunately doing so means changing the function signature in a way
      that is not backward compatible.
      
      This function relies on being able to tell whether ITEMS is nil
      because that argument was not provided or because an empty list was
      provided as its value.  In the former case the action still has to be
      confirmed in the latter case it does not because there is nothing to
      act on.
      
      So the `(items nil sitems)' argument has to be last but in d6420549
      I added a new argument NOCONFIRM after it.
      
      Fixes #3341.
      42c22614
  29. 18 Jan, 2018 1 commit
    • Jonas Bernoulli's avatar
      magit-confirm: Abort if user doesn't confirm · d6420549
      Jonas Bernoulli authored
      Previously we left that for the callers to do.  Or not do - in
      a few cases we should not abort when the user doesn't confirm
      to allow other things to happen.  Add a new argument NOABORT
      to be used in those cases.
      d6420549