| Age | Commit message (Collapse) | Author |
|---|
|
GitHub issue 2935.
|
|
|
|
|
|
variables that are already present (and used nearby) in the code;
no functional change
|
|
A comment in the code claimed that the list of spans would be sorted,
but the sorting did not actually work. The layout "LSSS,LLSL" resulted
in the list "0-3, 1-2", whereas the layout "LLSL,LSSS" resulted
in the list "1-2, 0-3". Since sorting serves no purpose, just leave
the list unsorted.
|
|
protocol for copying. Let's get back to testing the SFTP protocol.
|
|
fixes problem with repeat in copy mode reported by tb@.
|
|
Hildebrandt, GitHub issue 2930.
|
|
position and tty_cursor because it may be at the final invisible cursor
position on automargin terminals. The text to be drawn is confined to
the pane, so use the pane cursor position for the checks instead. Fix
from Anindya Mukherjee, redraw problem reported by naddy@.
|
|
Move the auth retry loop into authuser() and only open /dev/tty once.
Also refactor the password reading into authuser_checkpass().
Bug reported by multi AT in-addr DOT xyz. OK kn@
|
|
A tiny realpath(3) wrapper to make a porter's life easier.
Feedback kettenis deraadt cheloha sthen
OK cheloha martijn deraadt
|
|
in GitHub issue 2927.
|
|
use struct in6_addr + struct in_addr instead of a char buffer.
ok millert
|
|
from Anindya Mukherjee.
|
|
GitHub issue 2924.
|
|
We need to validate all line count option arguments, not just the last
such argument found.
While here, switch to the default strtonum(3) error message format:
<argument-name> is <errstr>: <argument-string>
Thread: https://marc.info/?l=openbsd-tech&m=163383023212104&w=2
ok millert@
|
|
- Switch http to https for upstream URL
- Fix buffer sizes and lesskey parser functions
- Fix integer overflow in bracket match function
- Fix prompt hiding feature (CTRL + P)
ok deraadt, millert
|
|
can be used in a Match block. Patch from eehakkin via github PR#277.
|
|
|
|
Make ":tnew" work, i.e. bring the reader to the definition of the full
"new-window" command aliased as "new" just like ":tnew-window" would.
OK nicm
|
|
|
|
issue 2917.
|
|
problem reported by naddy.
|
|
|
|
|
|
any). GitHub issue 2904.
|
|
DECSCUSR. GitHub issue 2891.
|
|
|
|
that is malloc(3)ed. In addition to being less confusing, the new
code is also shorter by two lines.
|
|
after processing each name given on the command line.
Failure to do so resulted in a memory leak of about 50 kilobytes
per name given on the command line. Since man(1) uses a few
Megabytes of memory anyway and people rarely give hundreds of names
on the command line, this leak did not cause practical problems,
but cleaning up properly is better in any case.
|
|
and resetting the internal state to the initial state.
Call this function from the proper place in term_free().
With the way the module is currently used, this does not imply any
functional change, but doing proper cleanup is more robust, makes
it easier during code review to understand what is going on, and
makes it explicit that there is no memory leak.
|
|
struct together with similar state date rather than in a function-scope
static variable, such that it can be free(3)d in roff_man_free();
no functional change
|
|
a user-defined macro. Calls of standard mdoc(7) and man(7) macros
were unaffected, so the effect on OpenBSD manual pages was small,
about 80 Kilobytes grand total for a full run of "makewhatis
/usr/share/man".
Argument expansion contexts for user-defined macros are stored on
a stack that grows as needed if calls of user-defined macros are
nested or recursive. Individual stack entries contain dynamically
allocated arrays of pointers to arguments; these argument arrays
also grow as needed if user-defined macros take more than eight
arguments. The mistake was that argument arrays of already
initialized expansion contexts were leaked rather than reused on
subsequent macro calls.
I found this issue in a systematic hunt for memory leaks after
Michael <Stapelberg at Debian> reported memory exhaustion problems
on the production server manpages.debian.org. This sub-Megabyte
leak is not the cause of Michael's trouble, though, where Gigabytes
of memory are being wasted. We are still investigating whether the
original problem may be related to his supervisor process, which is
written in Go, rather than to mandoc.
|
|
Saves 1k of static storage and prevents snprintf "possible truncation"
warnings from newer compilers (although in this case it's false positive
since the actual sizes are limited by the output size of the SHA1).
ok djm@
|
|
ok dtucker@
|
|
were processed. Useful to see whether a file or command actually has
keys present
|
|
reported by Michael <Stapelberg at Debian> in the Linux md(4) manual.
The reason the colwidth[] array is needed is not that it stores widths
different from those in tbl->cols[].width, but that only part of the
columns participate in the comparisons, i.e. only those intersecting
at least one span the still requires width distribution.
|
|
Fixes error in portable where GCC>=11 takes notice of the bounds.
ok deraadt@
|
|
|
|
needs to loop over the clients, instead do it after all clients are
cleared. Fixes a crash reported by martijn@ when a session with multiple
clients attached is destroyed, but there are other sessions so tmux does
not entirely exit. ok deraadt
|
|
|
|
|
|
OK dtucker deraadt djm
|
|
Upstream removed history file support for secure mode. The history file
feature is off by default already, disallowing it altogether in secure
mode allows us to drop wpath.
Added a note about it to manual page.
ok benno, deraadt
|
|
ok inoguchi
|
|
again as we go along). ok deraadt
|
|
mistake; spotted by jmc@
|
|
gmail.com via github PR#272, ok deraadt@
|
|
We'll wait a little longer for people to pick up sftp-server(8) that
supports the extension that scp needs for ~user paths to continue
working in SFTP protocol mode. Discussed with deraadt@
|
|
Whatever deraadt@
|
