| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
|
| |
The previous commit as taken from upstream introduces a compiler warning
for parse.y:
parse.y:110:42: warning: format ‘%lld’ expects argument of
type ‘long long int’, but argument 3 has type ‘int64_t’
Quelch this warning by using PRId64 from inttypes.h
|
|
|
|
| |
other parse.y's; from Leon Fischer <lfischer@airmail.cc>.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
original from naddy@:
> Don't declare variables as "unsigned char *" that are passed to
> functions that take "char *" arguments. Where such chars are
> assigned to int or passed to ctype functions, explicitly cast them
> to unsigned char.
>
> For OpenBSD's clang, -Wpointer-sign has been disabled by default,
> but when the parse.y code was built elsewhere, the compiler would
> complain.
>
> With help from millert@
> ok benno@ deraadt@
|
|
|
|
|
|
|
|
|
| |
Original file locations in the OpenBSD tree:
- lib/libc/stdlib/reallocarray.c
- lib/libc/stdlib/strtonum.c
- lib/libc/string/strlcat.c
- lib/libc/string/strlcpy.c
- sys/sys/queue.h
|
|
|
|
|
|
|
| |
This reverts commit 603548105b9bf9ffd11eb053e62db99f9433e821.
Using u_char instead of char will generate signedness warnings for
strtonum(), lookup(), and xstrdup().
|
|
|
|
| |
htile/vtile actions. From Uwe Werler, with a few manpage tweaks.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> - odd condition/test in PF lexer
> (and other lexers too)
>
> This commit rectifies earlier change:
>
> in the lex... even inside quotes, a \ followed by space or tab should
> expand to space or tab, and a \ followed by newline should be ignored
> (as a line continuation). compatible with the needs of hoststated
> (which has the most strict quoted string requirements), and ifstated
> (where one commonly does line continuations in strings).
>
> OK deraadt@, OK millert@
|
|
|
|
|
|
| |
revision 1.109 of calmwm.c.
ok okan@
|
| |
|
|
|
|
|
|
|
|
| |
which one may configure (wm <name> <path_and_args>) (and choose) specific
window managers to replace the running one. 'wm cwm cwm' is included by
default.
No objections and seems sensible to sthen.
|
| |
|
|
|
|
|
|
|
|
| |
and pointer.
Replace 'bind' and 'mousebind' options with 'bind-key' and 'bind-mouse',
respectively, replace special 'unmap' keyword with 'unbind-key' and
'unbind-mouse', and additionally allow unbinding all with 'all' keyword.
|
| |
|
|
|
|
| |
well as give 'sticky' groups its own variable.
|
|
|
|
| |
ok okan@ on an older version of this diff
|
|
|
|
|
|
| |
No functional change, but will be used shortly.
ok okan@
|
| |
|
|
|
|
|
|
| |
and HOST_NAME_MAX+1, respectively.
ok doug@
|
|
|
|
|
|
|
|
| |
Don't allow embedded nul characters in strings.
Fixes a pfctl crash with an anchor name containing
an embedded nul found with the afl fuzzer.
pfctl parse.y patch from and ok deraadt@
|
|
|
|
| |
Adapted from src parse.y changes by doug@. OK doug@
|
| |
|
|
|
|
| |
removes limit on name matching.
|
|
|
|
|
|
| |
config parse (and use conf_cmd_add to populate defaults); based on a
discussion with Tiago Cunha. While this looks ugly, there are likely
some other changes here to come.
|
|
|
|
| |
config parse; based on a discussion with Tiago Cunha.
|
| |
|
|
|
|
| |
Tiago Cunha.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- make conf_bind_kbd return error on non-matches to match what
conf_bind_mouse does.
- rename some variables while here for clarity.
- constify bind and cmd.
from Tiago Cunha.
|
|
|
|
|
|
|
| |
ewmh hint; urgencyborder is configurable. The urgency flag will stick,
even while on a client in a non-viewable group, until the client
receives focus (where the border is reset). Initial diff from Thomas
Adam with some changes/enhancements from me.
|
|
|
|
|
|
| |
use u_char for buffers in yylex, for ctype calls, as done in all other
parse.y in the tree
found by millert@, ok okan@
|
| |
|
| |
|
|
|
|
|
| |
quotes. Reinstate this support lost in recent sync diff and add a comment to
show that it's intentional. ok okan@
|
|
|
|
|
|
|
| |
validity during the parse phase and not bother adding it to the queue,
instead of each time a client needs to grab (when it's too late);
furthermore, make this a config error, stop parsing and load the
default config.
|
| |
|
|
|
|
|
|
|
|
|
| |
- merge border/menu color structures/functions since they now both use Xft
- switch xu_xorcolor to operating on XftColor instead of just
XRenderColor (basically adding pixel)
- if color name allocation fails, revert back to default (this, along
with font validation should occur during config parse, but we don't
have screens setup yet - likely to change at some point)
|
|
|
|
| |
configuration errors, so warn and load defaults.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
font/color drawing issues; from Alexander Polakov
|
| |
|
|
|
|
|
|
| |
from me.
ok oga@
|
|
|
|
| |
ok oga@
|
|
|
|
|
|
| |
applies to the user supplied font, so rename.
ok oga@
|
|
|
|
|
|
|
|
| |
with the various scenarios of when to attempt a parse of the config,
load defaults, and when to warn and/or exit. triggered by bogus warning
first noticed by sobrado@.
ok oga@
|
|
|
|
|
|
| |
the way with the cwm specific parts.
ok oga@
|