| Age | Commit message (Collapse) | Author |
|---|
|
Considering that real roff implements next-line scope using input
line traps, that isn't all that surprising.
Issue found in the games/xbattle port.
|
|
Needed by about four dozen ports (thanks to naddy@ for the research).
|
|
case is that we get an empty response instead of a message saying that
there is no multicast support.
ok mpi@
|
|
as the same mistake for RSA/DSA
|
|
return statement.
|
|
unbreak sshd, spotted quickly by naddy@
|
|
do not meet this requirement. ok markus@
|
|
|
|
Blowfish, RC4 and CAST ciphers. ok markus@ deraadt@
|
|
conditional for key bindings.
|
|
|
|
xterm-keys by default, generates \033[1;3A instead of
\033\033[OA. Unfortunately this confuses vi, which doesn't understand
xterm keys and now sees Escape+Up pressed within escape-time as Escape
followed by A.
The issue doesn't happen in xterm itself because it gets the keys from X
and can distinguish between a genuine M-Up and Escape+Up.
Because xterm can, tmux can too: xterm will give us \033[1;3A (that is,
kUP3) for a real M-Up and \033\033OA for Escape+Up - in fact, we can be
sure any \033 preceding an xterm key is a real Escape key press because
Meta would be part of the xterm key instead of a separate \033.
So change tmux to recognise both sequences as M-Up for its own purposes,
but generate the xterm version of M-Up only if it originally received
the xterm version from the terminal.
This means we will return to sending \033\033OA instead of the xterm key
for terminals that do not support xterm keys themselves, but there is no
practical way around this because they do not allow us to distinguish
between Escape+Up and M-Up. xterm style escape sequences are now the de
facto standard for these keys in any case.
Problem reported by jsing@ and subsequently by Cecile Tonglet in GitHub
issue 907.
|
|
This is the first feature made possible by the parser reorganization.
Improves the formatting of the SYNOPSIS in many Xenocara GL manuals.
Also important for ports, as reported by many, including naddy@.
|
|
failed builds with different compilers.
ok jsing@
|
|
now that this actually saves code: -70 LOC.
|
|
|
|
ROCHFORD.
|
|
|
|
|
|
modules to the new roff(7) modules. As a side effect,
mdoc(7) now handles .ft, too. Of course, do not use that.
|
|
used by both the mdoc and man formatters, with the ultimate
goal of reducing code duplication between the two macro formatters.
Made possible by the parser unification.
Add the first formatting function (for the .br request).
|
|
Generate the first node on the roff level: .br
Fix some column numbers in diagnostic messages while here.
|
|
control block. This is documented in fstat(1) and makes it possible
to compare the values from both tools.
OK sthen@
|
|
Problem noticed by Harald Dunkel <harald.dunkel@aixigo.de>
|
|
session:
pane-mode-changed
window-pane-changed
client-session-changed
session-window-changed
From Joshua Brot.
|
|
retain SSH v.1 support in the "delete all keys from agent" path.
|
|
|
|
ok markus@
|
|
|
|
|
|
From Anton Lindqvist. OK tobias@ nicm@
|
|
|
|
instead of relying on other methods, after readpassphrase. Some programs on
this diff won't benefit that much since it happens near the terminal path, but
someone might copy the unsafe idiom to another program and place it where it
may leak sensitive data.
Discussed aeons ago with tb@, OK deraadt@ and beck@
|
|
|
|
so it can work when in -I, suggested by Suraj N Kurapati.
|
|
upstream as well.
|
|
|
|
this should too;
|
|
|
|
|
|
|
|
|
|
|
|
got committed to groff which changed .TP from using .it to using .itc,
such that groff now supports more than one man(7) macro line in the .TP
head if all but the last line in the head end with \c.
Of course, relying on that behaviour is utterly non-portable, but if
authors are reckless enough to use that idiom, let's do what they want.
|
|
|
|
widths of the remaining columns is already wider than the line
length, underflowing size_t and dying from ENOMEM is the wrong plan.
Instead, simply refrain from expanding anything in such a situation,
avoiding a crash that tb@ found with afl.
|
|
|
|
and not have to wait for an update when they change pane, we allow
commands to run more than once a second if the expanded form
changes. Unfortunately this can mean them being run far too often
(pretty much continually) when multiple clients exist, because some
formats (including #D) will always differ between clients.
To avoid this, give each client its own tree of jobs which means that
the same command will be different instances for each client - similar
to how we have the tag to separate commands for different panes.
GitHub issue 889; test case reported by Paul Johnson.
|
|
I use rm -f and everuthing...
pointed out by sobrado@
|
|
|
