| Age | Commit message (Collapse) | Author |
|---|
|
be able to find out from where the request was comming.
Add the same logging for PermitListen violations which where not
logged at all.
Pointed out by Robert Kisteleki (robert AT ripe.net)
input markus
OK deraadt
|
|
|
|
display-menu shows a menu (bound to the mouse on status line by default)
and a couple of extra formats for the default menus.
|
|
|
|
|
|
|
|
|
|
ok krw@, jsg@
|
|
|
|
users.
OK deraadt@, sashan@
|
|
otherwise. ok tb@ tedu@
|
|
|
|
|
|
|
|
Use the standard functions mbtowc(3), wcwidth(3), iscntrl(3) instead
of bad functions like get_wchar(), utf_len(), is_wide_char(),
is_composing_char(), is_combining_char(), control_char().
If only half of a double-width character is shifted off screen, do not
inspect anything following it because that clearly remains on-screen.
Improve and add comments.
OK millert@
|
|
so it works like swap-pane.
|
|
|
|
ok beck deraadt
|
|
functions.
ok deraadt@
|
|
|
|
|
|
and pane.
|
|
|
|
|
|
generic and hide the display-panes specific bits into
cmd-display-panes.c.
|
|
history-bottom as for cursor-up and cursor-down. GitHub issue 1723.
|
|
Employ the usual form of an mbtowc(3) loop, eliminating two calls
to the bad function step_char() and reducing the number of nested
loops by one. This also removes the last caller of the bad function
binary_char(), which is consequently deleted.
While here, count ASCII C0 non-whitespace control characters as
binary (except backspace and, with -R only, escape).
OK millert@
|
|
Use the standard function mbrtowc(3) to distinguish valid, incomplete,
and invalid multibyte characters, getting rid of five calls to functions
and macros that we want to phase out, and of one goto. Add comments.
OK millert@.
|
|
manual page section and create a new ENVIRONMENT with the expected
content. Move some information that was misplaced below the -u
flag into that new section.
Feedback and OK nicm@ jmc@ tb@
|
|
immediately rather than queuing them (the command can block the queue
which means they were not being seen until it finished which was too
late). Reported by denis@ and solene@, ok solene@.
|
|
work in newer libevent.
|
|
with the current formatting.
OK benno@ naddy@
The original suggestion to delete it rather than fix it came from deraadt@:
we do not want to encourage use of --rsync-path because it is important
that the openrsync client smoothly works with the Samba rsync server.
If it doesn't, we should fix it and not fragment the ecosystem.
|
|
|
|
split-window or display-message -I.
|
|
|
|
into the mouse event that later code uses, it has been adjusted and they
should use the original position. GitHub issue 1710.
|
|
|
|
users of man(1) about running makewhatis(8), which won't help.
Seeing the content of the broken .so request might even help
users to figure out how to access the manual page they want.
Fixing the last issue reported by Lorenzo Beretta <loreb at github>
as part of https://github.com/void-linux/void-packages/issues/9868 .
|
|
|
|
ok schwarze@
|
|
Some mildly broken real-world packages on some operating systems
contain dangling symlinks in manual page directories: pestering the
user to run makewhatis(8) makes no sense because that won't help.
On the other hand, missing read permissions deserve ugly error messages
and are unlikely to occur in practice anyway.
Fixing an issue reported by Lorenzo Beretta <loreb at github>
as part of https://github.com/void-linux/void-packages/issues/9868 .
|
|
|
|
try harder to find the best match.
Use this order of preference:
1. The section in both the directory name and the file name matches exactly.
2. The section in the file name matches exactly.
3. The section in the directory name matches exactly.
4. Neither of them matches exactly.
The latter can happen when mansearch() finds substring matches
or when the second .Dt argument mismatches the dir and file names.
Lorenzo Beretta <loreb at github> reported that this caused real
problems on Void Linux, like "man 3 readline" showing readline(3m).
See https://github.com/void-linux/void-packages/issues/9868 for details.
|
|
|
|
command queue so they are ordered correctly with the commands that they
execute.
|
|
|
|
optionally followed by a letter, and at least one more argument
follows, interpret the first argument as a section name even when
additional characters follow after the digit and letter.
This is needed because many operating systems have section names
consisting of a digit followed by more than one letter - for example
Illumos, Solaris, Linux, even NetBSD.
There is very little risk of regressions: in the whole corpus of
manual pages on man.openbsd.org, there isn't a single manual page
name starting with a digit. And even if programs like "0ad" or
"4channels" had manual pages, "man 0ad" and "man -a cat 0ad" would
still work, only "man -a 0ad cat" will fail with "man: No entry for
cat in section 0ad of the manual."
Fixing one of the issues reported by Lorenzo Beretta <loreb at github>
as part of https://github.com/void-linux/void-packages/issues/9868 .
|
|
in snmprintf. bz#3002, patch from velemas at gmail.com, ok markus@.
|
|
ok deraadt
|
|
|
