16 Commits (991d5a9c74f658225cc82e0b08d168c092eefdbe)

Author	SHA1	Message	Date
Nicholas Marriott	991d5a9c74	Add compat for getdtablesize, GitHub issue 2406.	2020-10-07 09:39:43 +01:00
Nicholas Marriott	aebb17dc75	Sync imsg from OpenBSD.	2018-04-23 15:40:15 +01:00
Nicholas Marriott	d720a1487b	Update imsg*.c from OpenBSD.	2017-04-11 11:51:25 +01:00
Nicholas Marriott	2e5664d2df	Update imsg*.[ch] from OpenBSD, add some compat bits it needs and remove some ... bits it doesn't.	2017-03-24 10:05:53 +00:00
Nicholas Marriott	3e495b4001	compat/* should not include tmux.h.	2017-01-25 13:49:01 +00:00
Nicholas Marriott	235e0bd65a	Update imsg*.[ch] from OpenBSD, including bzero->memset.	2015-07-12 19:46:58 +01:00
Nicholas Marriott	63b7a031a5	queue.h should come from compat.h.	2015-05-07 11:43:52 +01:00
Nicholas Marriott	747cab4281	No need for $Id$ now.	2014-11-08 12:27:43 +00:00
Thomas Adam	0e23ab4cce	Sync libutil from OpenBSD (imsg) ... Changes in the imsg API need to be reflected here as tmux wasn't creating any clients because of it.	2014-08-09 20:32:01 +01:00
Nicholas Marriott	1099442c0a	+strings.h in compat/.	2013-06-25 09:57:49 +01:00
Tiago Cunha	391f1f08c0	Expand the Id keyword.	2011-07-09 09:42:33 +00:00
Tiago Cunha	bebfd7c2c8	Sync OpenBSD patchset 706: ... Rename some imsg bits to make namespace collisions less likely buf to ibuf, buf_read to ibuf_read, READ_BUF_SIZE to IBUF_READ_SIZE.	2010-06-06 00:08:28 +00:00
Tiago Cunha	150fba5ecd	Sync OpenBSD patchset 329: ... Enclose repeated buffer draining code in a new msgbuf_drain() function, which is additionally exported for use by others. From nicm@, who reminded me that tmux is now using buffer.c, too.	2009-09-15 23:59:40 +00:00
Nicholas Marriott	dd9dd142c9	Add $Id$, nuke queue.h.	2009-08-20 12:54:08 +00:00
Tiago Cunha	b402cef338	Adjust imsg changes to the portable version due to OpenBSD patchset 243.	2009-08-14 21:13:48 +00:00
Tiago Cunha	a9b6bfdddd	Sync OpenBSD patchset 243: ... Switch tmux to use imsg. This is the last major change to make the client-server protocol more resilient and make the protocol versioning work properly. In future, the only things requiring a protocol version bump will be changes in the message structs, and (when both client and server have this change) mixing different versions should nicely report an error message. As a side effect this also makes the code tidier, fixes a problem with the way errors reported during server startup were handled, and supports fd passing (which will be used in future). Looked over by eric@, thanks. Please note that mixing a client with this change with an older server or vice versa may cause tmux to crash or hang - tmux should be completely exited before upgrading.	2009-08-14 21:04:04 +00:00