Hi all,

Welcome to the August update for Mepo covering the 0.5 release. You can
follow Mepo's development at http://sr.ht/~mil/mepo and do note that
release notes are also mirrored in the git annotated tags for each
release.

--------------------------------------------------------------------------- 
Contents:

0.5 Release Notes:
- Preference system overhaul & introduction of save/restore state
- Interactive debugging via STDIN
- Async shellpipe, user location script, and pin editing script

Hi Bobby,
Thanks for sending! So 2 pieces of feedback:

1) Generally with git-send-email and patch based workflows the idea is
to keep the commit message as concise as possible. E.g. rather then the
full email with hello and signature etc. being in the commit message,
maybe the commit message could be just:
```
place global amixer scontrol variables inside function main()

Currently, the three variables that determine what amixer scontrol
identifiers the script uses are placed inside the devicepine64pinephone()
function, which makes sense from a device compatability perspective.
```

On Sat, Aug 6, 2022, at 5:02 PM, Lucca Pellegrini wrote:
> The printf statement in prompt() must be redirected to prevent forming a
> broken Nominatim query. Additionally, the grep command fails to output
> the selected option and is thus replaced.
> ---
>  scripts/mepo_dl.sh | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/mepo_dl.sh b/scripts/mepo_dl.sh
> index e7363c7..fbddaf3 100755
> --- a/scripts/mepo_dl.sh
> +++ b/scripts/mepo_dl.sh
> @@ -24,7 +24,7 @@ sep() {
> 

Hi Bobby,

Finally was able to cut out some time to look into this. I tested on
Alpine once upgraded to latest version of oil (0.11) and it seems the
same issue with strict_errexit existed there too. I believe that the oil
developer changed the base set of options set for strict:all to include
strict_errexit.. which was not previously the case, as these scripts
used to work OOTB with strict:all in earlier versions of oil/osh.

We use osh & strict:all with f_scripts as a good set of defaults which
are backwards compatible with shell; however for now I've decided to
make the default for all scripts to additionally unset strict_errexit
to fix this regression. The eventual plan is to upgrade to oil proper so
these will be systematically reworked in anycase. I've tagged f_scripts

Hi Bobby,

Thanks for sticking with this and sorry about the delay on my end,
been a bit tied up with other things. Happy to help you work on these
remaining issues.

1) As for the oil 'shopt -s strict:all' issue, can we work out a minimal
test case that works on Alpine's version of oil but doesn't work on Arch?
Can you tell me if the following works on Arch?

#!/usr/bin/env oil
shopt -s strict:all
R=$(echo foo)
echo "$R"

On Wed, May 11, 2022, at 12:06 AM, Bobby Hamblin wrote:
> Good evening Miles,
>
>> Just tagged 0.5 for fbp which builds against Zig 0.9.1 which should
>> be default for Arch.
>
> Thanks! I tested and updated my pr to fbp 0.5 and it works as
> expected as long as Zig 0.9.1 is installed beforehand.
>
> I figured out systemd stuff enough to make a post-install script that
> enabled the fbp systemd service on boot, and fbp now behaves exactly
> like it does on pmOS to my knowledge. It automatically starts on boot
> with no extra tinkering needed, just run makepkg. I've updated the top
> comment on my pr to reflect the current state of things.

Hi all,

Welcome to the March monthly update for Mepo; covering the 0.4 release.
You can follow Mepo's development at http://sr.ht/~mil/mepo and do note
that release notes are also mirrored in the git annotated tags for each
release. Also note, the 0.4 release also has an associated demo video
of Mepo running on a postmarketOS/Phosh phone which can be seen at:
https://media.lrdu.org/mepo_demos/mepo_demo_0.4.webm

--------------------------------------------------------------------------- 
Contents:

0.4 Release Notes:
- GPU-based rendering & HiDPI support

On Sun, Mar 13, 2022, at 11:57 AM, Miles Alan wrote:
> On Sat, Mar 12, 2022, at 1:43 PM, Bobby Hamblin wrote:
>> I've gotten fbp to build on Arch using the pkgbuild in the pr below, 
>> but am having trouble figuring out how to autostart fbp on boot. 
>> Looking at the post install script in the pmOS repo, it seems like it 
>> just adds the fbp services to OpenRC's list of services to start at 
>> boot. Looking through the list of systemd services on my Pinephone, i 
>> don't see a service listed for fbp. Am i missing something? Or do I 
>> need to create a systemd service so that I can start that on boot? 
>> Thanks.
>> Pull request (in progress) - 
>> https://github.com/dreemurrs-embedded/Pine64-Arch/pull/344
>> 	-Bobby
>

On Mon, Mar 14, 2022, at 9:21 PM, m@milesalan.com wrote:
> From: Miles Alan <m@milesalan.com>
>
> In certain instances trans may be set to a window that doesn't actually
> map to a client via wintoclient; in this case it doesn't make sense
> to set isfloating/oldstate since trans is essentially invalid in that
> case / correlates to the above condition check where trans is set /
> XGetTransientForHint is called.
> ---
>  dwm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dwm.c b/dwm.c
> index 1473b7e..77911d7 100644

From: Miles Alan <m@milesalan.com>

In certain instances trans may be set to a window that doesn't actually
map to a client via wintoclient; in this case it doesn't make sense
to set isfloating/oldstate since trans is essentially invalid in that
case / correlates to the above condition check where trans is set /
XGetTransientForHint is called.
---
 dwm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dwm.c b/dwm.c
index 1473b7e..77911d7 100644
--- a/dwm.c
[message trimmed]