It's totally broken (requires MLINKS which we removed long ago,
relies on the old man.conf(5) format we stopped supporting long ago,
Alfred Morgan reported additional bugs on bugs@, ...),
it reimplements man(1) in a very poor way,
and it lacks many useful features that man(1) in an xterm(1)
readily provides, so fixing it would be a waste of time.
matthieu@ deraadt@ krw@ agree with the direction.
there's a window of time where an expose or enternotify event will get
generated for a lower client; use a hammer and drain events after keyboard
move/resize, until such a time that cwm doesn't warp the pointer. Behavior
noticed by kn.
ok kn@
Link what is described as "applications" here to how they are actually
defined in cwmrc(5).
While here, call the configuration file what it is instead of reusing
the default path (already mentioned in the FILES section).
OK okan
ssh-askpass(1) is computing the size of its indicators relatively to
the screen resolution. When multiple monitors are present, the support
for Xinerama computes the dimensions of the window to be created
relatively to the screen on which it will appear. But the computation
of the indicator size is based on the size of the whole display,
resulting in too small indicators (and too many of them if the screens
hare layed out horizontally).
Fix that by computing the resolution of the whole display before
taking xinerama into account.
ok djm@
that comes bundled with xterm(1).
Issue found and based on a diff from Lauri Tirkkonen <lotheac at iki dot fi>.
The final form of the diff follows a suggestion from tedu@.
OK matthieu@
client thus always falling back to client_current(); while the current client
is problaby right in most cases, use event's subwindow (not window) to find the
client. Bail early if this event came to us from a screen we don't manage.
This is result of us grabing all keybindings off the root window instead of
selectively.
* Add the missing locale, modifyFunctionKeys, precompose, and scrollBar.
* Move backarrowKeyIsErase to conform to alphabetical sorting.
* Add a missing full stop.
Diff found in my tree; i obviously forgot to commit it earlier.
* video -q needs 'stdio rpath wpath video' (needs O_RDWR on the device)
* video -i needs 'stdio rpath' (rpath for X11 error/locale access)
* other modes (ie display frames via X11, or output frames to file with
-o/-O) need 'stdio rpath video' since we open output file/video device
before calling pledge(2).
with help from semarie@, nits from matthieu@
ok deraadt@
via property notify events. Previously only the flags were set but nothing was
in the path to apply said flags and/or bwidth. Required slight of re-orgnaization
of client_init.
> - 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@
containing {P,US}Position requests where they are explicitly set to 'ignore' in
cwmrc(5); clients are unaware that their border will be altered (removed in
this case) when calcuating position and thus end up a factor of their original
border width off once mapped by cwm(1). cwm(1) will essentially shift the
client to the edge if the original request's position and border match.
Window offset noticed by at least Andre Stoebe via bugs@, and others since
(and likely before). Thanks!
output_name is provided we need to unveil(2) this one with rwc. Additionally
depending on the different combinations of if these files are passed via args
or from stdin/to stdout we can also pledge(2) accordingly to the code path.
OK deraadt@
This fixes the issue where xenodm whould stay stuck after kill the
Xserver twice.
While here add some more Debug() calls to help following what's going on
