obestwalter / i3configger Goto Github PK

SOLUTION: just don't resolve them.

Might be a stupid idea. Would be a solution for transient states:
https://www.reddit.com/r/i3wm/comments/6f8znm/does_i3_support_transient_states/digobgi/

generate unused keys

It's tedious, but worthwhile, to define unused keys as "nop" inside a mode. This avoids typos "falling through" into the file you're editing for example.

• Convention for mode: mode-.conf
• add unused keys

This will make context merging even simpler.

... as part of arch pkgbuild.

pandoc can convert md to man easily for example.

Those bars should only be integrated if the display is present

Use http://python-xlib.sourceforge.net/doc/html/python-xlib_16.html to read display infos?

Decide best way, polling? i3subscribe?
4711 ODER 4712

• https://unix.stackexchange.com/a/60110/60516
• https://stackoverflow.com/questions/10400236/how-to-observe-changes-in-connected-monitors-via-xlib
• https://faq.i3wm.org/question/6039/is-there-a-way-to-keybind-display-changes/index.html%3Fanswer=6045.html
• https://faq.i3wm.org/question/5721/how-do-i-subscribe-to-i3-events-using-bash-easily.1.html

e.g.

$i3configger_bin -> path to own binary (or just i3configger if bin is in path)

More an intergration question/thought ...

If i3configger is started/run once before i3 is started the config can be build depending on settings and environments. e.g in xinitrc before i3wm is started.

tox -e i3configger

tox -e i3configger -- --daemon

e.g. which displays are connected and how should the workspaces and bars be configured according to that.

This doesn't work if you don't use i3status. I use polybar instead so I have no i3status process running, which causes this error when running your tool:

i3status: no process found
Traceback (most recent call last):
  File "/usr/bin/i3configger", line 11, in <module>
    load_entry_point('i3configger==0.4.3', 'console_scripts', 'i3configger')()
  File "/usr/lib/python3.6/site-packages/i3configger/main.py", line 46, in main
    ipc.StatusBar.refresh()
  File "/usr/lib/python3.6/site-packages/i3configger/ipc.py", line 74, in refresh
    subprocess.check_call(['killall', '-SIGUSR1', 'i3status'])
  File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['killall', '-SIGUSR1', 'i3status']' returned non-zero exit status 1.

Review is done: https://bbs.archlinux.org/viewtopic.php?id=227106

pkgbuild is here: https://github.com/obestwalter/i3configger-pkgbuild

only have to publish it ... use https://github.com/eli-schwartz/aurpublish?

atm the daemon can be started more than once. Prevent this with a pidfile or something.

changes in message handling lead to message not being processed now in watch mode ...