1. 17 Oct, 2018 2 commits
  2. 14 Oct, 2018 1 commit
  3. 05 Oct, 2018 1 commit
  4. 13 Sep, 2018 1 commit
  5. 05 Sep, 2018 2 commits
  6. 02 Sep, 2018 6 commits
  7. 01 Sep, 2018 1 commit
  8. 30 Aug, 2018 1 commit
    • Charlène's avatar
      Multiple fixes, OpenBSD related · e07f545c
      Charlène authored
      - get_wm: Fixes non-EWMH WM detection on OpenBSD by introducing a
        ps_flags array the same way we do for disks. Tested successfully on
        Debian GNU/Linux (this change impacts all OSes).
      
      - get_wm: Adds fvwm support
      
      - get_model: Adds vmm(4) (OpenBSD's KVM counterpart) support
      
      - get_disk: On OpenBSD you can't use df against a /dev/... unless being
      root or in the 'operator' group. A separate disks array creation using
      awk has been introduced only for this OS.
      e07f545c
  9. 29 Aug, 2018 1 commit
  10. 25 Aug, 2018 2 commits
  11. 24 Aug, 2018 4 commits
  12. 16 Aug, 2018 6 commits
  13. 15 Aug, 2018 2 commits
  14. 31 Jul, 2018 1 commit
  15. 27 Jul, 2018 3 commits
  16. 26 Jul, 2018 1 commit
  17. 24 Jul, 2018 1 commit
  18. 17 Jul, 2018 1 commit
    • Ain's avatar
      Fix borked version display for mksh · f960594c
      Ain authored
      `"$SHELL" -c "printf %s \$KSH_VERSION"` as part of the shell version
      detection for ksh and mksh was expanding to `printf %s $KSH_VERSION`
      inside of shell. This resulted in `$KSH_VERSION` being substituted as
      multiple arguments to printf. While (afaik) unspecified, mksh, bash
      and zsh resort to repeating the format strings. This resulted in all
      spaces missing from `$shell`, which in turn caused the string cleanup
      to fail: `Shell: mksh @MIRBSDKSHR562017/08/29`
      
      Quoting `$KSH_VERSION` causes it to be given to printf as a single
      argument, which preserves its spaces. The output after this change
      looks like follows: `Shell: mksh R56 2017/08/29`
      f960594c
  19. 16 Jul, 2018 2 commits
  20. 29 Jun, 2018 1 commit