1. 18 Mar, 2021 1 commit
  2. 17 Mar, 2021 1 commit
  3. 13 Mar, 2021 1 commit
  4. 12 Mar, 2021 1 commit
  5. 02 Feb, 2021 1 commit
  6. 01 Feb, 2021 1 commit
  7. 18 Sep, 2020 2 commits
  8. 17 Aug, 2020 2 commits
  9. 03 Aug, 2020 1 commit
  10. 27 Jul, 2020 1 commit
  11. 14 Jun, 2020 2 commits
  12. 05 Jun, 2020 1 commit
    • Bruno Sutic's avatar
      Don't be too smart when restoring vim session · bd671b83
      Bruno Sutic authored
      A user may decide to use custom session file. Eg vim -S Session1.vim
      With the previous approach we were preventing that as we only checked
      for the existence of the default Session.vim file.
      bd671b83
  13. 21 Mar, 2020 1 commit
  14. 17 Dec, 2019 3 commits
  15. 06 Dec, 2019 1 commit
  16. 27 Nov, 2019 1 commit
  17. 21 Oct, 2019 1 commit
  18. 27 Aug, 2019 1 commit
  19. 19 Apr, 2019 1 commit
  20. 01 Mar, 2019 2 commits
  21. 07 Jan, 2019 2 commits
  22. 29 Dec, 2018 2 commits
  23. 28 Dec, 2018 2 commits
  24. 10 Dec, 2018 1 commit
    • Lars Wilke's avatar
      Fix #94 start default-shell as login shell. · 9187f8b3
      Lars Wilke authored
      If pane content is restored and no default-command is set, restore.sh
      falls back to default-shell, which tmux sets automatically and calls as
      a login shell.
      
      In pane_creation_command() we need to make sure to call default-shell as a login shell.
      As tmux does. But take care not to call default-command as a login shell.
      9187f8b3
  25. 30 Nov, 2018 1 commit
  26. 08 Oct, 2018 1 commit
  27. 11 Sep, 2018 2 commits
  28. 10 Sep, 2018 1 commit
  29. 20 Aug, 2018 2 commits