summaryrefslogtreecommitdiffstats
path: root/usr.bin/tmux/server.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Add pane_dead_status for exit status of dead panes.nicm2014-12-091-1/+2
|
* Move cfg_causes local into cfg.c and remove struct causelist.nicm2014-10-271-14/+7
|
* Wake up any clients waiting with the wait-for command when the servernicm2014-09-011-2/+18
| | | | exits.
* lockf is entirely useless and it was a mistake to change to it, go backnicm2014-07-211-1/+2
| | | | | to using flock which actually works sensibly. Also always retry the lock to fix a potential race, and add some extra logging.
* Now that cmdlists are reference counted, there is no need for two-stepnicm2014-05-141-2/+1
| | | | deletion via the dead_key_bindings tree. From Keith Amling.
* There is no longer a need for a paste_stack struct or for global_buffersnicm2014-04-241-4/+1
| | | | to be global. Move to paste.c.
* Some more long lines.nicm2014-04-171-2/+2
|
* Do not run any command line command from the client which starts thenicm2013-10-201-1/+4
| | | | | | server until after the configuration file completes. This prevents it racing against run-shell or if-shell in .tmux.conf that run in the background.
* Rename global configuration define.nicm2013-04-241-5/+5
|
* Add a command queue to standardize and simplify commands that call othernicm2013-03-241-19/+25
| | | | | | | | | | | | | | | | | | | | | | commands and allow a command to block execution of subsequent commands. This allows run-shell and if-shell to be synchronous which has been much requested. Each client has a default command queue and commands are consumed one at a time from it. A command may suspend execution from the queue by returning CMD_RETURN_WAIT and then resume it by calling cmd_continue() - for example run-shell does this from the callback that is fired after the job is freed. When the command queue becomes empty, command clients are automatically exited (unless attaching). A callback is also fired - this is used for nested commands in, for example, if-shell which can block execution of the client's cmdq until a new cmdq becomes empty. Also merge all the old error/info/print functions together and lose the old curclient/cmdclient distinction - a cmdq is bound to one client (or none if in the configuration file), this is a command client if c->session is NULL otherwise an attached client.
* No more lint means no more ARGSUSED.nicm2013-03-221-4/+1
|
* Fix argument order in a log statement.nicm2012-12-061-2/+2
|
* Use a utility function for common code to show errors in config file,nicm2012-11-191-17/+6
| | | | from Thomas Adam.
* xfree is not particularly helpful, remove it. From Thomas Adam.nicm2012-07-101-6/+6
|
* Stop accepting new clients for 1 second on EMFILE/ENFILE. Based onnicm2012-04-111-7/+32
| | | | ongoing fixes to other daemons by Theo.
* Use a lock file and flock() to serialize server start, avoids problemsnicm2012-03-091-2/+6
| | | | | when running a bunch of tmux from cron at the same time. Based on a diff from Tim Ruehsen.
* Give each pane created in a tmux server a unique id (starting from 0),nicm2011-03-271-1/+2
| | | | | put it in the TMUX_PANE environment variable and accept it as a target. Suggested by and with testing and tweaks from Ben Boeckel.
* Use LIST_* not SLIST_*.nicm2011-01-261-2/+2
|
* Move all calls to fcntl(...O_NONBLOCK) into a function and clear thenicm2011-01-081-7/+3
| | | | | flag on the stdio file descriptors before closing them (fixes things like "tmux ls && cat").
* Don't reset the activity timer for unattached sessions every second,nicm2011-01-011-11/+3
| | | | | | | this screws up the choice of most-recently-used. Instead, break the time update into a little function and do it when the session is attached. Pointed out by joshe@.
* Change from a per-session stack of buffers to one global stack which isnicm2010-12-301-1/+4
| | | | | | | much more convenient and also simplifies lot of code. This renders copy-buffer useless and makes buffer-limit now a server option. By Tiago Cunha.
* Store sessions in an RB tree by name rather than a list, this is tidiernicm2010-12-211-34/+27
| | | | | | | | | and allows them to easily be shown sorted in various lists (list-sessions/choose-sessions). Keep a session index which is used in a couple of places internally but make it an ever-increasing number rather than filling in gaps with new sessions.
* Merge the before and after attach client code into one in client.cnicm2010-10-181-8/+4
| | | | (instead of two in tmux.c and client.c).
* Trying to set FD_CLOEXEC on every fd is a lost cause, just usenicm2010-10-161-3/+1
| | | | closefrom() before exec.
* Two new options:nicm2010-09-261-5/+7
| | | | | | | | | | | | - server option "exit-unattached" makes the server exit when no clients are attached, even if sessions are present; - session option "destroy-unattached" destroys a session once no clients are attached to it. These are useful for preventing tmux remaining in the background where it is undesirable and when using tmux as a login shell to keep a limit on new sessions.
* Modify the permissions on the socket when adding or removing +x to shownicm2010-09-261-6/+17
| | | | attached sessions, rather than replacing them.
* Do not call event_del() for signals after fork(), just use sigaction()nicm2010-08-191-2/+2
| | | | | directly instead - calling libevent functions after fork() w/o event_reinit() is a bad idea, even if in this case it was harmless.
* switch back to kqueue for now, since (a) kqueue has been fixed to dealderaadt2010-08-041-4/+1
| | | | | | with strange devices and (b) since there appears to be a bull in the poll code in libevent as well... requested by nicm who is away
* kqueue(2) is currently broken when used with /dev/null and a few othernicm2010-07-241-1/+4
| | | | | | | | devices. An upcoming fix for some problems with the client stdout/stderr handling relies on it working, so make tmux force libevent to use poll(2) via EVENT_NOKQUEUE, until we have fixed kqueue.
* Give tmux sockets (but not the containing folder) groupnicm2010-06-211-4/+4
| | | | | permissions. This allows hardlinks to the sockets to be used more easily.
* Put this back in with the initialisation in the right order.nicm2010-05-041-62/+7
|
* Revert last change, it appears to be broken somehow.nicm2010-05-041-8/+62
|
* Make signal handler setup/teardown two common functions instead of six,nicm2010-05-031-62/+8
| | | | | and reset SIGCHLD after fork to fix problems with some shells. From Romain Francois.
* Merge copy mode and output mode, dropping the latter. Idea and code fromnicm2010-04-061-3/+4
| | | | Micah Cowan.
* Nuke unused variable.nicm2010-03-221-3/+2
|
* Use the array.h code for the causes list.nicm2010-02-061-12/+12
|
* Instead of bailing out on the first configuration file error, carry on,nicm2010-02-061-27/+30
| | | | | collecting all the errors, then start with the active window in more mode displaying them.
* Ignore SIGHUP as well.nicm2010-01-301-1/+5
|
* Massive spaces->tabs and trailing whitespace cleanup, hopefully for the lastnicm2009-12-031-4/+4
| | | | | time now I've configured emacs to make them displayed in really annoying colours...
* Close the pane if the process died due to a signal, not just if it exitednicm2009-12-021-2/+2
| | | | normally.
* Remove a couple of unused arguments where possible, and add /* ARGSUSED */ tonicm2009-11-261-1/+4
| | | | the rest to reduce lint output.
* Destroy panes immediately rather than checking them all every loop.nicm2009-11-131-5/+3
|
* Free the pane bufferevent when the fd is closed (the signal could come beforenicm2009-11-111-1/+2
| | | | the error callback).
* Only need to chmod +x or -x the socket when a client is created, lost ornicm2009-11-111-7/+4
| | | | attached, rather than every event loop.
* EVLOOP_ONCE takes care of the wakeup, so no need to call event_loopexit(NULL).nicm2009-11-051-2/+1
|
* Now all timers are events, there is no longer any need to wake up every 50 ms -nicm2009-11-051-7/+2
| | | | only wake up when an event happens.
* Move status timer check into the global once-per-second timer, this could maybenicm2009-11-041-1/+3
| | | | be done better but one every second is better than once every 50 ms.
* Don't reenlist the client imsg event every loop, instead have a small functionnicm2009-11-041-5/+3
| | | | to it and call it after the event triggers or after a imsg is added.
* Tell the client to exit on configuration file error.nicm2009-11-041-1/+2
|
* Convert the window pane (pty master side) fd over to use a bufferevent.nicm2009-11-041-2/+1
| | | | | The evbuffer API is very similar to the existing tmux buffer API so this was remarkably painless. Not many possible ways to do it, I suppose.
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.