aboutsummaryrefslogtreecommitdiff
path: root/server-window.c
Commit message (Collapse)AuthorAge
* xfree is not particularly helpful, remove it. From Thomas Adam.Nicholas Marriott2012-07-10
|
* Clear flags across all sessions, from Thomas Adam.Nicholas Marriott2012-07-08
|
* Tidy up bell code, from Thomas Adam.Nicholas Marriott2012-06-18
|
* Only hide flags on the current window when the session is attached, fromNicholas Marriott2012-01-21
| | | | Roland Walker.
* Add a tty_bell wrapper function, from Dylan Alex Simon.Nicholas Marriott2011-08-24
|
* Add an option to trigger the terminal bell when there is an alert, fromNicholas Marriott2011-07-03
| | | | Marco Beck.
* Unused declaration.Nicholas Marriott2011-01-26
|
* Store sessions in an RB tree by name rather than a list, this is tidierNicholas Marriott2010-12-21
| | | | | | | | | 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.
* Add an option to alert (monitor) for silence (lack of activity) in aNicholas Marriott2010-12-06
| | | | window. From Thomas Adam.
* Change the way backoff works. Instead of stopping reading from the ptyNicholas Marriott2010-08-11
| | | | | | | | | | when the client tty backs up too much, just stop updating the tty and only update the internal screen. Then when the tty recovers, force a redraw. This prevents a dodgy client from causing other clients to go into backoff while still allowing tmux to be responsive (locally) when seeing lots of output.
* Don't return if in the current window since we may want to report a bellNicholas Marriott2010-07-19
| | | | | (if bell-action any/current), just clear the flag so the status line doesn't show the bell.
* Having a list of winlinks->alerts for each session is stupid, just storeNicholas Marriott2010-06-21
| | | | the alert flags directly in the winlink itself.
* copy mode uses the real screen as backing and if it is updated while copying,Nicholas Marriott2010-02-19
| | | | strange things can happen. So, freeze reading from the pty while in copy mode.
* Massive spaces->tabs and trailing whitespace cleanup, hopefully for the lastNicholas Marriott2009-12-03
| | | | | time now I've configured emacs to make them displayed in really annoying colours...
* Destroy panes immediately rather than checking them all every loop.Nicholas Marriott2009-11-13
|
* Don't try enable/disable the event if the window pane is dead (fd == -1), asNicholas Marriott2009-11-06
| | | | the event will have been freed.
* Change window name change to use a timer event rather than a gettimeofday()Nicholas Marriott2009-11-04
| | | | check every loop.
* Convert the window pane (pty master side) fd over to use a bufferevent.Nicholas Marriott2009-11-04
| | | | | 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.
* Switch window pane pipe redirect fd over to a bufferevent.Nicholas Marriott2009-11-04
|
* Switch tty fds over to a bufferevent.Nicholas Marriott2009-11-04
|
* A couple of minor cosmetic changes.Nicholas Marriott2009-11-04
|
* Initial changes to move tmux to libevent.Nicholas Marriott2009-11-04
| | | | | | | | | This moves the client-side loops are pretty much fully over to event-based only (tmux.c and client.c) but server-side (server.c and friends) treats libevent as a sort of clever poll, waking up after every event to run various things. Moving the server stuff over to bufferevents and timers and so on will come later.
* Don't backoff based on suspended or deda clients as they are always likely toNicholas Marriott2009-11-04
| | | | have data backed up.
* If any client currently displaying a window pane has more than 1 KB of outputNicholas Marriott2009-10-28
| | | | | | | | | buffered, don't accept any further data from the process running in the pane. This makes tmux much more responsive when flooded with output, although other buffers can still have an impact when running remotely. Prompted by a query from Ranganathan Sankaralingam.
* Move the poll registration functions into the server-*.c files.Nicholas Marriott2009-10-27
|
* Split the server code handling clients, jobs and windows off into separateNicholas Marriott2009-10-22
files from server.c (merging server-msg.c into the client file) and rather than iterating over each set after poll(), allow a callback to be specified when the fd is added and just walk once over the returned pollfds calling each callback where needed. More to come, getting this in so it is tested.