>Synopsis: cwm can't window-vtile after window-htile and vice versa
>Category: user
>Environment:
System : OpenBSD 7.0
Details : OpenBSD 7.0 (GENERIC.MP) #232: Thu Sep 30 14:25:29 MDT
2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/am
>Synopsis: can't `ZZZ`, `zzz`, `apm -a` etc.
>Category: system
>Environment:
System : OpenBSD 7.0
Details : OpenBSD 7.0 (GENERIC.MP) #3: Wed Dec 15 13:14:26 MST 2021
r...@syspatch-70-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENER
Firstly, the `ps auxw | grep apm` output got automatically distorted.
Here is a manually word wrapped version, for clarity:
root 53666 0.0 0.0 196 328 ?? IU Wed09PM0:00.33 \
/usr/sbin/apmd -A -t 60 -z 15
root 40604 0.0 0.0 1004 916 ?? Ip 7:42PM0:00.01 \
/b
My observation is that putting `apm -a` or `apm -b`
into `/etc/apm/powerup` breaks `apm`.
My actions, with `-av` for clarity:
0. Try `apm -av` to see it works.
1. Make `/etc/apm/powerup` like this:
#! /bin/sh
apm -av >> /tmp/apm_powerup 2>&1
2. Check it works:
/bin/sh /etc/apm/powerup
3. Foll
> apmd runs the script, and does nothing until the script is
> finished.
>
> The script runs apm.
>
> apm talks to apmd.
>
> apmd is not listening, it is busy waiting for the script to
> finish.
>
>
> Once you understand the mechanism you'll realize it will never work.
Thanks for the clarifi
> > May I ask you devs to put a note on it into
> > http://man.openbsd.org/apmd.8
> > as there is currently no description of `apmd`
> > waiting for `/etc/apm/*` executables to finish
> > without processing new calls in the meantime.
>
> I don't see what to add, because it is obvious.
It's good
> Well, the nice thing about open source is that you get the source code,
> so you can try to impliment recursion and propose a diff.
As I wrote earlier in this thread, I can't involve in coding
(`c`-programming is not my domain)
> You are trying to run apm in apmd-operated scripts. You figured
>Synopsis: `cwm`: custom `bind-key` for `command term` don't work
>Category: user
>Environment:
System : OpenBSD 7.1
Details : OpenBSD 7.1 (GENERIC) #1: Tue May 3 08:27:33 MDT 2022
r...@syspatch-71-i386.openbsd.org:/usr/src/sys/arch/i386
> > There are 2 special `command`s: `term` and `lock`.
>
> No, there are two special commands: 'terminal' and 'lock'.
>
> You probably want:
>
> bind-key M-Return terminal
I see, so there are https://man.openbsd.org/cwmrc#command
command term ...
command lock ...
but https://man.openbsd.or
Here I opine from my user-perspective, treat is as such.
> Maybe just allowing 'term' in bindings is enough without documenting
If a user reads http://man.openbsd.org/cwmrc#command first, like I did,
then they might wonder
See video
https://streamable.com/djd02e
on the left there is vertical tint2 panel,
out of 4 windows in group "four", window-cycle-ingroup cycles between 2
xterms, one of which is screen recording with ffmpeg and the other one
is switching windows with xdotool, but 2 windows: pcmanfm and iridium
ne
With cwm, /usr/X11R6/bin/X and conky reaching 100%
Workaround, thank you, rvp @ unitedbsd.com
https://www.unitedbsd.com/d/1241-conky-high-cpu/3
Looks like some bad interaction between cwm and conky. (It
works fine with evilwm and twm.)
For cwm, put this in your ~/
12 matches
Mail list logo
