| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
3rd (variadic) mode_t parameter is irrelevant. Many developers in the past
have passed mode_t (0, 044, 0644, or such), which might lead future people
to copy this broken idiom, and perhaps even believe this parameter has some
meaning or implication or application. Delete them all.
This comes out of a conversation where tb@ noticed that a strange (but
intentional) pledge behaviour is to always knock-out high-bits from
mode_t on a number of system calls as a safety factor, and his bewilderment
that this appeared to be happening against valid modes (at least visually),
but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef.
ok millert
|
|
|
|
| |
GitHub issue 2924.
|
| |
|
| |
|
|
|
|
|
|
| |
(which does not have many practical uses) and only support running a
program in the popup. display-popup is now simpler and can accept
multiple arguments to avoid escaping problems (like the other commands).
|
|
|
|
| |
compilers, GitHub issue 2573.
|
| |
|
|
|
|
|
| |
above the normal layout. These work similarly to menus and are created
with the display-popup command.
|
|
|
|
| |
anything yet.
|
|
|
|
|
|
| |
value < 0. errno is only updated in this case. Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
|
|
|
|
| |
return NULL. GitHub issue 1547.
|
| |
|
|
|
|
| |
always starting in home, GitHub issue 1488.
|
| |
|
| |
|
|
|
|
|
| |
not exit until jobs started from run-shell/if-shell have finished (add a
job flags member and a flag to indicate other jobs). GitHub issue 1245.
|
|
|
|
|
| |
correctly, so set it explicitly back to default (and the others for good
measure).
|
|
|
|
|
|
| |
event_reinit) - if the child gets a signal and fires the libevent signal
handler during this period it could write a signal into the parent's
signal pipe. GitHub issue 1001 from Aaron van Geffen.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
must be a full line). Don't let it redraw the status line more than once
a second.
Requested by someone about 10 years ago...
|
|
|
|
| |
into it.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
around, we can't use file descriptors for the working directory because
we will be unable to pass it to a privileged process to tell it where to
read or write files or spawn children. So move tmux back to using
strings for the current working directory. We try to check it exists
with access() when it is set but ultimately fall back to ~ if it fails
at time of use (or / if that fails too).
|
| |
|
|
|
|
|
|
|
| |
socketpair and setting it to -1 to mark when the other side is
closed. This avoids closing it while the libevent bufferevent still has
it (it could try to add it to the polled set which some mechanisms don't
like). Fixes part a problem reported by Bruno Sutic.
|
| |
|
| |
|
|
|
|
| |
Kezes.
|
| |
|
| |
|
| |
|
|
|
|
| |
popen, from Chris Johnsen.
|
| |
|
| |
|
|
|
|
|
| |
or bugs in $EventMechanism on $OtherOS makes libevent get it's knickers
in a twist. From Dylan Alex Simon.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fire-and-forget.
Status jobs now managed with two trees of output (new and old), rather
than storing the output in the jobs themselves. When the status line is
processed any jobs which don't appear in the new tree are started and
the output from the old tree displayed. When a job finishes it updates
the new tree with its output and that is used for any subsequent
redraws. When the status interval expires, the new tree is moved to the
old so that all jobs are run again.
This fixes the "#(echo %H:%M:%S)" problem which would lead to thousands
of identical persistent jobs and high memory use (this can still be
achieved by adding "sleep 30" but that is much less likely to happen by
accident).
|
| |
|
| |
|
|
|
|
|
| |
flag on the stdio file descriptors before closing them (fixes things
like "tmux ls && cat").
|
|
|
|
| |
closefrom() before exec.
|
|
|
|
|
| |
directly instead - calling libevent functions after fork() w/o
event_reinit() is a bad idea, even if in this case it was harmless.
|
| |
|
| |
|
|
|
|
|
| |
and reset SIGCHLD after fork to fix problems with some shells. From
Romain Francois.
|
|
|
|
|
| |
modified with setenv -g) rather than with the environment tmux started
with.
|