[Git-commits] [grml/grml-scripts] b38256: grml-resolution: Quick 'n dirty xrandr output pars...

Michael Prokop noreply at github.com
Mon Nov 28 08:34:35 CET 2022


  Branch: refs/heads/master
  Home:   https://github.com/grml/grml-scripts
  Commit: b3825665c6b20c495e6964bc1fa1a23aa0b30ed9
      https://github.com/grml/grml-scripts/commit/b3825665c6b20c495e6964bc1fa1a23aa0b30ed9
  Author: Darshaka Pathirana <dpat at syn-net.org>
  Date:   2022-11-27 (Sun, 27 Nov 2022)

  Changed paths:
    M usr_bin/grml-resolution

  Log Message:
  -----------
  grml-resolution: Quick 'n dirty xrandr output parser fix

The xrandr output parser of grml-resolution seems to be broken since at
least Grml 2014.11: grml-resolution does not list possible resolutions
but its corresponding refresh rates.

It seems like once upon a time xrandr had a 'size-index' in front of
each resolution. This is not the case anymore and there does not seem to
be an option to add that behaviour back to xrandr.
So, CURRENT_NUM did not receive the 'size-index' of the current
resolution, therefor I dropped that variable which was used to detect if
the user had chosen the current resolution (nothing bad happens if
xrandr sets the current resolution).

We now list the possible resolutions and refresh rates, separated by an
underscore because `dialog` does not like spaces.
xrandr -s works fine with the chosen 'index' from dialog.

Closes: grml/grml-scripts#14


  Commit: 3c7dcfd47d7ed6c7b6029fb0952fd73695da7e89
      https://github.com/grml/grml-scripts/commit/3c7dcfd47d7ed6c7b6029fb0952fd73695da7e89
  Author: Michael Prokop <mika at grml.org>
  Date:   2022-11-28 (Mon, 28 Nov 2022)

  Changed paths:
    M usr_bin/grml-resolution

  Log Message:
  -----------
  Merge remote-tracking branch 'origin/github/pr/16'


Compare: https://github.com/grml/grml-scripts/compare/168953e791d6...3c7dcfd47d7e


More information about the Git-commits mailing list