49bc20c934
Fix incorrect comment
2013-06-23 22:34:04 +02:00
684a77442e
Make default shmlog_size a const int
2013-06-12 23:24:07 +02:00
271189444d
bump copyright years to 2013
2013-03-17 01:01:04 +01:00
3365b52384
Allow servers which do not support the XKB extension.
...
If we can open the X display but the XKB extension is not available,
continue without it.
2013-01-23 20:27:27 +01:00
dcb8ac84f8
ipc_recv_message: store message_type, don’t compare. add distinct EOF retval
...
Also use ELOG, which requires i3-msg to provide logging functions.
2013-01-23 18:51:39 +01:00
d8e27dd5aa
ignore MotionNotify events generated while warping the pointer
2012-12-27 17:04:13 +01:00
b304e6ad34
remove old cfgparse.{l,y}
2012-12-24 15:46:57 +01:00
625401d162
Bugfix: handle MapRequests sent between i3 registering as a wm and handling events
...
This fixes the problem where i3-nagbar does not come up because its
MapRequest is ignored.
fixes #892
2012-12-24 14:49:19 +01:00
20c0fa7cfb
use the new parser by default
...
you can force the old parser with the command line flag
--force-old-config-parser-v4.4-only (which will be present in v4.4 only,
as the name suggests)
2012-10-08 13:26:42 +02:00
1cbf665581
remove async-unsafe functions from signal handler
2012-09-27 12:37:27 +02:00
9c01bdeef7
Revert "Use ev_signal to avoid async-unsafe functions (Thanks Markus)"
...
This makes our signal handler useless and leads to infinite SIGSEGV
loops because the ev callback handler gets called only from within the
event loop, and control doesn’t necessary get to the event loop…
This reverts commit 514265b529
2012-09-27 12:34:09 +02:00
e582e19ffd
Clicking the root window should try to focus the relevant workspace.
2012-09-23 16:39:35 +02:00
514265b529
Use ev_signal to avoid async-unsafe functions (Thanks Markus)
...
Functions such as fprintf() might be unsafe to use in a signal handler,
see http://stackoverflow.com/questions/3941271/#answer-3941563
By using ev_signal, libev will use a tiny signal handler which just
passes on the information and then calls (outside of the signal handler)
our callback function which can use fprintf() and other unsafe
functions.
fixes #803
2012-09-21 16:35:25 +02:00
99e91c8049
--help: note that nVidia’s driver supports RandR from 302.17 on
2012-09-19 17:52:56 +02:00
73d5dcbbaf
x: grab server and process pending events before managing existing windows
...
fixes #782
2012-09-04 18:02:37 +02:00
4eff386439
remove obsolete branch reference "(tree)" from starting line
2012-08-13 01:57:23 +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
884627ef20
use I3__FILE__ for DLOG, leave __FILE__ as is
...
See also commit 0e752070ac
2012-08-12 12:19:47 +02:00
70ec3867fe
clean up zero-byte logfile on immediate exit
...
Otherwise, a zero-byte log file stays behind after every call to `i3
--get-socketpath`. Also, replace "return" calls with more explicit "exit"
calls.
Before:
$ ls -ld /tmp/i3* | wc -l; \
repeat 10 i3 --get-socketpath >/dev/null; \
ls -ld /tmp/i3* | wc -l
1
11
Now:
$ ls -ld /tmp/i3* | wc -l; \
repeat 10 i3 --get-socketpath >/dev/null; \
ls -ld /tmp/i3* | wc -l
1
1
Signed-off-by: Julius Plenz <julius@plenz.com>
2012-08-11 02:23:03 +02:00
6ba0944430
scratchpad: fix moving scratchpad window
...
From the source:
When starting i3 initially (and after each change to the connected
outputs), this function fixes the resolution of the __i3
pseudo-output. When that resolution is not set to a function which
shares a common divisor with every active output’s resolution,
floating point calculation errors will lead to the scratchpad window
moving when shown repeatedly.
fixes #632
2012-08-08 18:45:40 +02:00
0e752070ac
explicitly set filenames to $(basename __FILE__)
...
This makes the debug log a bit more readable, especially since commit
48f1e383ca
2012-08-07 09:55:52 +02:00
1b2d222449
Properly report errors in 'focus parent' (Thanks eeemsi)
...
Also, make X11 errors debug log level only. They are harmless usually.
fixes #762
2012-08-05 20:57:20 +02:00
8a1c8115ca
fix a few warnings/places where the clang static analyzer complains
2012-08-05 16:34:38 +02:00
bdc078914b
i3: Replace loglevels by a global debug logging
...
File-limited were not used nor really useful
Besides, they are painful to maintain in Makefile rules compared to the
benefit
2012-07-22 18:41:12 +02:00
6146f39b8a
when using i3 -C, don’t send remaining arguments via IPC (Thanks Somelauw)
2012-06-25 21:43:41 +02:00
62d3329906
remove dead code
...
This was a left-over of commit 9d68d780e2
2012-05-09 20:00:46 +02:00
eeb6ff9237
Move is_debug_build() to libi3/
2012-05-09 19:12:20 +02:00
cc9f0ab353
bump copyright in --version (Thanks joepd)
2012-04-22 13:04:24 +02:00
0f10ccdf12
Implement fake-outputs option (cmdline, cfg) for multi-monitor testing
...
This kills the dependency on xdmx and makes the testsuite simpler
and more flexible (in the output sizes / configurations).
2012-04-09 14:28:36 +02:00
206b96202c
Use (void) instead of () for functions without args (Thanks fernandotcl)
...
See also:
http://article.gmane.org/gmane.linux.kernel/1268792
The C compiler will handle (void) as "no arguments" and () as "variadic
function" (equivalent to (...)) which might lead to subtle errors, such
as the one which was fixed with commit 0ea64ae4
2012-03-31 10:53:04 +02:00
9d68d780e2
Use 32bit visual only when needed. Thus we could drop the --enable-32bit-visual option.
2012-03-26 16:50:44 +02:00
4172e43c9c
debugging trick: keep a symbol pointing to I3_VERSION around
...
This way, gdb will include the i3 version in backtraces.
2012-03-21 20:48:00 +01:00
58ecd14900
Implement support for chosing a 32 bit visual (necessary for pseudo-transparency) (Thanks darkraven)
...
You need to specify the --enable-32bit-visual flag when starting i3. This is
done because everything feels sluggish on my system when using a 32 bit visual
instead of a 24 bit visual. Fast > fancy.
2012-02-15 18:56:07 +00:00
318d4fdeef
make in-place restarts use socket activation, too (for faster/less flaky tests)
2012-01-21 23:03:09 +00:00
759ed0b6e3
Merge branch 'master' into next
2012-01-20 18:10:52 +00:00
4f26d6f2a1
Bugfix: Setup the _NET_SUPPORTING_WM_CHECK atom in a standards-compliant way
...
This makes chrome (and probably other apps, too) receive changes of the
_NET_ACTIVE_WINDOW and thus show its bookmark dialog properly.
Fixes : #544
2012-01-20 18:09:53 +00:00
dee7c07ad2
shmlog: store meta information in the buffer itself, store path as X11 atom
...
This makes i3-dump-log completely independent of a running i3 instance.
2012-01-06 23:40:07 +00:00
f7a73f4a68
fix the SHM log size
2011-12-10 11:15:57 +00:00
aa82adb5c0
Introduce --shmlog-size flag, unlink SHM log when exiting
2011-12-10 10:51:55 +00:00
f23d675de9
Implement new "i3bar_command" option for bar.
...
This allows you to specify an alternate path to the i3bar binary.
The userguide docu is included.
2011-11-27 21:40:57 +00:00
b6e859787e
clarify comments about socket activation (Thanks mxf)
2011-11-16 23:14:57 +00:00
6bdd12a584
Bugfix: Correctly fill the buffer with zeros
2011-11-09 22:23:33 +00:00
332dbfe9c1
Enable (unlimited) core dumps when running i3 development versions
...
Also prints out useful stuff:
CORE DUMPS: You are running a development version of i3, so coredumps were
automatically enabled (ulimit -c unlimited).
CORE DUMPS: Your current working directory is "/home/michael/i3".
CORE DUMPS: Your core_pattern is: /tmp/%e.core.%p
i3 (tree) version 4.0.2-479-g26ab2ac (2011-11-08, branch "next") starting
This does not affect child processes of i3.
The intention of this change is to make debugging easier – it’s one less thing
users of the development version have to worry about when trying to help with
debugging.
2011-11-08 22:49:25 +00:00
bbfbd28dfa
Add a --no-startup-id flag for exec (command), exec (config), exec_always (config)
2011-10-25 22:18:17 +01:00
91134f75c0
Move get_mod_mask to libi3, use it in i3 and i3-config-wizard
...
Also, the API changed a bit. There are two functions now, both assume you
already got the keysyms (which is the case for i3 and i3-config-wizard),
one gets the modifier mapping for you (aio_get_mod_mask_for) while the other
assumes you also got that. No roundtrips are required for the latter.
2011-10-23 21:26:15 +01:00
a512b99a51
Introduce --get_socketpath and --force_xinerama as synonyms for --get-socketpath and --force-xinerama
2011-10-23 19:41:40 +01:00
9d15a00ba8
introduce sasprintf() in libi3, use it everywhere
2011-10-23 13:16:56 +01:00
42d355f2b7
normalize modelines/headers across src/*.c
2011-10-22 23:40:02 +01:00
12d866e4f6
Don’t start i3-nagbar when using -C to validate the config
2011-10-20 22:25:59 +01:00
230b238870
Actually start i3bar instances for each configured bar
2011-10-20 19:03:40 +01:00
Alexander Berntsen