0298a32e37
i3bar: makefile: prefix messages with [i3bar]
2011-10-21 19:03:54 +01:00
bc679b0168
change default config to use 'bar' blocks (Thanks mxf)
2011-10-21 19:01:02 +01:00
cf67966fa0
i3bar: document -b in --help (Thanks mxf)
2011-10-21 18:59:59 +01:00
2647f47ec5
bar config: make dock mode the default
2011-10-20 23:38:55 +01:00
0f3d31124d
docs/userguide: document the bar configuration
2011-10-20 23:38:34 +01:00
d970b19b59
i3bar: update manpage
2011-10-20 22:55:24 +01:00
caee0a0fda
cfgparse: eliminate absolute states, use yy_push_state/yy_pop_state
...
This fixes a problem with workspace assignments.
I tested i3 -C with three user configs (Thanks SardemFF7, julien, xeen)
and did not notice any problems.
2011-10-20 22:38:46 +01:00
12d866e4f6
Don’t start i3-nagbar when using -C to validate the config
2011-10-20 22:25:59 +01:00
bf408c9a08
tests: depend on AnyEvent::I3 0.09 (for get_bar_config)
2011-10-20 20:31:44 +01:00
093507fc38
ipc: document the GET_BAR_CONFIG request/reply
2011-10-20 20:16:07 +01:00
2bda05d1b8
docs/ipc: fix example end
2011-10-20 19:51:01 +01:00
a33c720ce8
docs/ipc: document i3 --get-socketpath
2011-10-20 19:46:57 +01:00
c5caa9682c
i3bar: don’t reconnect, but exit(0) on EOF
...
Since i3 starts i3bar instances as necessary, EOF is considered a signal to
either shutdown because i3 exited or because it is restarting.
2011-10-20 19:08:41 +01:00
230b238870
Actually start i3bar instances for each configured bar
2011-10-20 19:03:40 +01:00
ab2d96ba48
tests: modify $PATH so that it prefers the compiled versions of everything in ../
2011-10-20 19:02:08 +01:00
ad0f13a0a9
Clean bars before reloading the config (+test)
...
While the configuration gets updated in i3, the i3bar processes will not pick
up these changes. We have to think about a good way to do that.
2011-10-20 18:47:09 +01:00
a5be27cb79
Make i3bar get its config from i3 via IPC
...
In order to not duplicate configuration options and make stuff confusing, we
dropped the commandline flags (except for socket_path and bar_id). This means
that you *have to* specify bar_id when starting i3bar. The best way is to let
i3 start i3bar, which it will do automatically for every bar {} configuration
block it finds.
2011-10-19 22:58:19 +01:00
15bface10d
Create different IDs for each bar (+test)
2011-10-19 19:57:39 +01:00
063b124e35
Implement parsing bar {} config blocks
2011-10-18 22:16:04 +01:00
d9f3a31cb7
tests: add a test to check that bar configs are parsed correctly
2011-10-18 22:15:48 +01:00
149b05aacf
ipc: when requesting the bar config without a payload, return an array of available bar IDs
2011-10-18 22:12:46 +01:00
e3cbdea1fc
Bugfix: Correctly close the colors map in the IPC bar config reply
2011-10-18 22:11:44 +01:00
c2c6ca25d5
Make the barconfig list a TAILQ
2011-10-18 22:11:27 +01:00
24ede1c834
add an IPC request to get the bar configuration (by ID)
2011-10-18 19:05:49 +01:00
4898f78e5e
add a data structure for 'bar' configuration
2011-10-18 19:05:49 +01:00
f26a344dfa
reformat include/config.h
2011-10-18 19:05:49 +01:00
9d67ae2202
Focus new window only if it is on a visible workspace on the current focused output.
2011-10-18 18:56:39 +01:00
a506e59b3c
Bugfix: Fix segfault when starting i3 (Thanks pnutzh4x0r)
2011-10-18 18:47:07 +01:00
f09d9a4c37
log: use localtime_r instead of localtime
...
localtime_r does not have the side-effect of behaving like it called tzset(),
in particular it will save one stat(/etc/localtime) syscall. This is not a big
deal, but it makes the strace output cleaner and thus more useful :).
2011-10-18 18:32:47 +01:00
744def377a
Merge branch 'workspace_baf' into next
2011-10-17 23:35:19 +01:00
82ec0169cb
tests: add t/176-workspace-baf for the workspace back_and_forth feature
2011-10-17 23:34:29 +01:00
178be03fa6
Implement 'workspace back_and_forth' (Patch by Michael Walle)
2011-10-17 23:17:56 +01:00
c3a18104cd
docs/Makefile: use $(ASCIIDOC), add asciidoc 'latest git docs' config
2011-10-15 23:32:04 +01:00
88f147ebe4
debian: use debian/i3-wm.manpages instead of manuall installing manpages
2011-10-15 22:36:03 +01:00
914ca6cfe7
Bugfix: Use _exit in forking to avoid calling the libev cleanup handler (Thanks xeen)
2011-10-15 16:56:47 +01:00
32b97745ec
Don’t call ev_destroy_loop with ev < 4 in atexit (Thanks xeen)
2011-10-15 16:56:32 +01:00
fce422d99e
i3test.pm: use strict; use warnings; and fix related bugs
2011-10-12 22:21:57 +01:00
27dadb4ad9
testcases/makefile: add modeline, add testsuite-* and latest to 'clean' target
2011-10-10 21:56:43 +01:00
71a3da1ef3
t/175-startup-notification: don’t wait for i3 mapping the window
...
It is on a different workspace and will therefore not get mapped.
Syncing is enough.
2011-10-10 16:00:34 +01:00
819980ce2b
Merge branch 'startup-notification' into next
2011-10-10 15:54:23 +01:00
5f52c78aa0
Change the root window cursor to 'watch' during startups
2011-10-10 15:54:18 +01:00
ad9ffcc917
debian: update debian/control with new build-dep libstartup-notification0-dev
2011-10-10 15:54:18 +01:00
a09d2eee74
add libstartup-notification to DEPENDS
2011-10-10 15:54:18 +01:00
2ad4fbb34a
startup: delete the startup sequence upon completion, make the timeout complete it
2011-10-10 15:54:18 +01:00
ae7dec2774
Move the includes after the include guard, no need to include these files more than once
2011-10-10 15:54:17 +01:00
997a539a8a
Implement timeouts for startup notifications
2011-10-10 15:54:17 +01:00
6ac098a45e
support _NET_STARTUP_ID on the client leader window
...
(necessary for GIMP, geeqie, …)
2011-10-10 15:54:17 +01:00
4204b8e2b0
Get the _NET_STARTUP_ID in manage_window, get the corresponding workspace
2011-10-10 15:54:17 +01:00
7750382b89
test: set the _NET_STARTUP_ID before mapping the window
2011-10-10 15:54:17 +01:00
499d89bdb0
Keep track of startup notifications in a TAILQ, save workspace
2011-10-10 15:54:17 +01:00
Michael Stapelberg