1. 27 Aug, 2021 2 commits
    • A Farzat's avatar
      Fix even more bugs in before last commit · 1b63a940
      A Farzat authored
      First, increment the relevant indices in the awk statements regarding
      windows, as now the window_name entry exists.
      
      Second, remove the window_name entry from the dump_pane_contents and
      dump_shell_history functions as it no longer exists in the format.
      1b63a940
    • A Farzat's avatar
      Fix some of the errors in the last commit · 02a7f1f9
      A Farzat authored
      First, make sure to include the ":" placeholder in the window_name
      format.
      
      Second, decrement the indices in relevant awk commands to make sure they
      point to the right items.
      02a7f1f9
  2. 26 Aug, 2021 1 commit
    • A Farzat's avatar
      Leave window name handling to windows · 6c9322aa
      A Farzat authored
      Previously, window names were set when creating panes and were therefore
      saved with pane data. However, saving the names with window data is more
      intuitive and easier to manage. In addition, one can set the name and
      automatic-rename options in the same function, so one can make sure that
      renaming the windows will not overwrite the automatic-rename option.
      6c9322aa
  3. 23 Aug, 2021 1 commit
    • A Farzat's avatar
      Maintain the value of automatic-rename · 80adb917
      A Farzat authored
      When the session is restored, the windows are renamed to their original
      names switching off automatic-rename, which can be undesirable.
      Therefore the value of automatic-rename is now saved for each window and
      restored after the renaming.
      
      If the value is set, that value is saved and then applied. Otherwise, a
      placeholder of ':' is placed instead, in which case the local option is
      unset for that window (as it originally was).
      80adb917
  4. 05 Jul, 2021 1 commit
  5. 18 Mar, 2021 1 commit
  6. 17 Mar, 2021 1 commit
  7. 13 Mar, 2021 1 commit
  8. 12 Mar, 2021 1 commit
  9. 02 Feb, 2021 1 commit
  10. 01 Feb, 2021 1 commit
  11. 18 Sep, 2020 2 commits
  12. 17 Aug, 2020 2 commits
  13. 03 Aug, 2020 1 commit
  14. 27 Jul, 2020 1 commit
  15. 14 Jun, 2020 2 commits
  16. 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
  17. 21 Mar, 2020 1 commit
  18. 17 Dec, 2019 3 commits
  19. 06 Dec, 2019 1 commit
  20. 27 Nov, 2019 1 commit
  21. 21 Oct, 2019 1 commit
  22. 27 Aug, 2019 1 commit
  23. 19 Apr, 2019 1 commit
  24. 01 Mar, 2019 2 commits
  25. 07 Jan, 2019 2 commits
  26. 29 Dec, 2018 2 commits
  27. 28 Dec, 2018 2 commits
  28. 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
  29. 30 Nov, 2018 1 commit
  30. 08 Oct, 2018 1 commit