c8cfc77b0a
docs/testsuite: mention why using a separate language is great
2012-08-23 20:27:08 +02:00
b9255f51f8
Use (void) instead of () for functions without args
2012-08-23 19:34:37 +02:00
d29b62f24f
Remove dead code in cmd_workspace_number
...
If a ws doesn't exist, maybe_back_and_forth
will never return true for it.
2012-08-22 17:58:08 +02:00
82b73c20c9
testcase for the previous commit
2012-08-22 17:57:58 +02:00
eadf1e306f
Fix 'back and forth' in 'workspace number' for named ws
2012-08-22 17:57:32 +02:00
6e75dc7e0e
testsuite: add hint about missing DUMMY Xorg module
2012-08-22 17:22:20 +02:00
7cadc40846
testcase for the previous commit
2012-08-22 17:16:18 +02:00
bb853660cf
Create ws in "move workspace number n" if not existing
...
fixes #729
2012-08-22 17:08:02 +02:00
4622cde7b7
Merge branch 'master' into next
2012-08-22 16:02:02 +02:00
2ac3b08cf6
Merge branch 'floating-resize-height'
2012-08-22 16:01:57 +02:00
1089b0b201
fix resizing floating windows by height
...
When resizing floating windows, changing the height was not correctly
handled. This commit fixes that and adds testcases for shrinking and
growing the width and height of floating windows.
2012-08-22 16:01:40 +02:00
be6190a516
complete-run: check whether Xdummy dies, add a flag to keep the Xdummy output
2012-08-18 16:27:00 +02:00
ad21037cd2
update DEPENDS, prepare RELEASE-NOTES for 4.3
2012-08-18 15:33:36 +02:00
5257a1268f
Bugfix: don’t change tabbed/stacked cons to splitv/splith layout (Thanks Merovius)
...
To automagically do the right thing when rotating monitors with regards
to splith/splitv layout (depending on width/height of the monitor), we
change the orientation of existing workspaces and the first child.
If that first child happens to be a stacked/tabbed con, we cannot change
the layout unconditionally (previously, the orientation was not in the
layout, so we never noticed this problem).
fixes #768
2012-08-17 01:55:31 +02:00
ba8b5c480d
debian: make 'i3' recommend dunst
2012-08-13 13:44:54 +02:00
1173740a35
debian/control: format build-depends nicely, add pango/cairo
2012-08-13 13:44:36 +02:00
125bf09e70
pango: divide by PANGO_SCALE to get a "normal" font size
2012-08-13 13:39:58 +02:00
d7b11bde28
i3 --moreversion: use readlink /proc/$pid/exe instead of realpath(argv[0])
...
The latter is actually wrong. For example, when running i3
--moreversion, it will print $(pwd)/i3 instead of $(which i3). In my
previous tests, this coincidentally was the same.
2012-08-13 13:38:04 +02:00
ef90ccd1a8
default config: include a short explanation about xft fonts
2012-08-13 13:34:30 +02:00
2896ae8057
logging: make libi3 use verboselog()/errorlog(), provide it in each caller
...
While this is a bit ugly, it makes the log messages end up where they
are supposed to: in the shmlog/stdout in case of i3 and on stdout in
case of utilities such as i3-input
2012-08-13 13:27:16 +02:00
6c9bf84d4e
userguide: Update Fonts section for Pango support
2012-08-13 11:39:31 +02:00
310f542937
libi3/font: Log the used font
2012-08-13 11:39:30 +02:00
9f7247fd9c
libi3: Introduce LOG
2012-08-13 11:39:30 +02:00
6ff3f7abad
libi3: Implement Pango rendering
2012-08-13 11:39:30 +02:00
f06161b58a
common.mk: Check for Pango
2012-08-13 11:39:30 +02:00
ec17a26b0e
libi3: Rework font to support multiple backends
2012-08-13 11:39:29 +02:00
edd9007ebf
i3bar: Rename xcb_screen to root_screen for consistency
2012-08-13 11:37:34 +02:00
5d8ccc5912
libi3: Introduce get_visualtype
2012-08-13 11:37:34 +02:00
210fc6dfed
libi3: Rework predict_text_width
...
predict_text_width now takes an i3String as argument
2012-08-13 11:37:23 +02:00
53365fa887
libi3: Rework draw_text
...
We now have two versions of draw_text
draw_text: Now takes an i3String
draw_text_ascii: Designed for static strings in plain ASCII
2012-08-13 11:37:21 +02:00
284294e9c2
i3-input: Store and use xcb_char2b_t directly
2012-08-13 11:30:08 +02:00
d89cb04c98
i3-input: Port prompt to i3String
2012-08-13 11:30:08 +02:00
bf177da17d
i3/sighandler: Pre-compute i3Strings for text
2012-08-13 11:30:08 +02:00
b6c705a1a4
i3/window: Port window names to i3String
2012-08-13 11:30:08 +02:00
bc5f33878a
i3/log.h: Prepare for libi3.h inclusion
2012-08-13 11:30:08 +02:00
50b7764ae4
i3-nagbar: Port to i3String
2012-08-13 11:30:08 +02:00
bbd1b16043
i3bar: Port to i3String
2012-08-13 11:30:05 +02:00
50d52f8f9b
i3bar/util.h: Prepare for libi3.h inclusion
2012-08-13 11:29:22 +02:00
7f22d4fe32
libi3: Implement i3String
...
New type designed to handle UCS-2/UTF-8 conversion nicely
2012-08-13 11:29:18 +02:00
b01545b131
Makefile: Always link libi3 first
2012-08-13 02:00:01 +02:00
a7569e6a98
implement error messages when moving to another ws fails (Thanks eeemsi)
...
fixes #769
2012-08-13 01:57:39 +02:00
4eff386439
remove obsolete branch reference "(tree)" from starting line
2012-08-13 01:57:23 +02:00
e68a8dd86c
shm-logging: implement i3-dump-log -f (follow)
...
This changes the SHM log format, it doesn’t use 0-bytes to separate
entries anymore. Instead of using lots of printf() calls in i3-dump-log,
we now do precisely one big write().
So, to be clear: i3-dump-log and i3 both need to be upgraded.
Mismatching versions will lead to garbage output (no crashes of i3, just
garbage output).
The -f flag uses an inter-process pthread_cond_t in the shared memory
header to broadcast the arrival of new messages to all i3-dump-log
processes. This internally uses futexes and thus doesn’t even mean a
kernel call in most cases. inter-process pthread_cond_ts require NPTL
(the Native Posix Thread Library, introduce in Linux 2.6).
2012-08-13 01:06:09 +02:00
070a18e598
i3bar: update manpage for the i3bar-protocol
...
fixes #739
2012-08-12 19:26:04 +02:00
f94edd9fc3
i3bar-protocol: add example (illustration-only!) shell script, clarify {"version":1} header
2012-08-12 18:47:24 +02:00
e53405c216
i3bar: be less strict about the {"version":1} JSON header
2012-08-12 18:40:15 +02:00
dbe406641f
use errx() instead of err() for custom error message
2012-08-12 18:34:03 +02:00
68a23b9577
Bugfix: only honor _NET_ACTIVE_WINDOW for visible windows (+test) (Thanks Tucos)
...
fixes #774
2012-08-12 16:08:53 +02:00
1e49f1b08a
Implement i3 --moreversion
...
From the code:
Connects to i3 to find out the currently running version. Useful since it
might be different from the version compiled into this binary (maybe the
user didn’t correctly install i3 or forgot te restart it).
Here is an example output:
$ ./i3 --moreversion
Binary i3 version: 4.2-202-gb8e782c (2012-08-12, branch "next") © 2009-2012 Michael Stapelberg and contributors
Running i3 version: 4.2-202-gb8e782c (2012-08-12, branch "next") (pid 14804)
The i3 binary you just called: /home/michael/i3/i3
RUNNING BINARY DIFFERENT FROM BINARY ON DISK!
The i3 binary you are running: /home/michael/i3/i3
$ i3 restart
2012-08-12 15:05:28 - Additional arguments passed. Sending them as a command to i3.
IPC: received EOF instead of reply
$ ./i3 --moreversion
Binary i3 version: 4.2-202-gb8e782c (2012-08-12, branch "next") © 2009-2012 Michael Stapelberg and contributors
Running i3 version: 4.2-202-gb8e782c (2012-08-12, branch "next") (pid 14804)
The i3 binary you just called: /home/michael/i3/i3
The i3 binary you are running: /home/michael/i3/i3
2012-08-12 15:10:13 +02:00
b8e782c983
root_atom_contents: handle CARDINAL atoms such as I3_PID
2012-08-12 14:30:24 +02:00
Michael Stapelberg