From Newsgroup: comp.lang.forth

I'm running the Gforth 0.7.9_20251001 app on Android 16 smartphone.

A few months ago, Bernd helped me here to get around Android's golden
caging by creating a directory under /storage/emulated/0/Download for
copying files in and out of the Gforth app, and adding that directory to
fpath.

That worked well at that time, but yesterday I copied a new file into
that shared directory (/storage/emulated/0/Download/gforth on my phone)
and Gforth cannot find the file with either include or 'sh ls', even
though files I copied into the directory months ago still show up as
expected.

Permissions on all the files in the directory, old and new, is 660
(read+wrote for owner and group). I tried changing perms to 666 (add
world read+write), but it had no effect, and permissions were reset to
660 after I restarted the phone.

Any idea what's going on with the new file?
--
David Meyer
Takarazuka, Japan
papa@sdf.org
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

On Sat, 30 May 2026 10:57:36 +0900
David Meyer <papa@sdf.org> wrote:

I'm running the Gforth 0.7.9_20251001 app on Android 16 smartphone.

A few months ago, Bernd helped me here to get around Android's golden
caging by creating a directory under /storage/emulated/0/Download for
copying files in and out of the Gforth app, and adding that directory
to fpath.

That worked well at that time, but yesterday I copied a new file into
that shared directory (/storage/emulated/0/Download/gforth on my
phone) and Gforth cannot find the file with either include or 'sh
ls', even though files I copied into the directory months ago still
show up as expected.

Permissions on all the files in the directory, old and new, is 660 (read+wrote for owner and group). I tried changing perms to 666 (add
world read+write), but it had no effect, and permissions were reset to
660 after I restarted the phone.

Any idea what's going on with the new file?

Dying SD-cards silently go read-only all by themselves. Possibly all
types of flash memory do this too. Maybe that's it?

Android/Linux, I seem to remember, silently re-mounts the disk
read-only.
--
Regards,

Martin Nicholas.

E-mail: reply-202605@mgn.org.uk (Address will be valid throughout May).

Free Usenet posting accounts are available through: https://www.eternal-september.org/

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Martin Nicholas <reply-2026@mgn.org.uk> writes:

On Sat, 30 May 2026 10:57:36 +0900
David Meyer <papa@sdf.org> wrote:

[...]

Android/Linux, I seem to remember, silently re-mounts the disk
read-only.

This last sentence is very confusing for anyone.

Does "Android/Linux" mean both the operating systems "Android" and "GNU"
(which is also -- wrongly -- called "Linux") ? Or does "Android/Linux"
simply mean one operating system, the "Android" ?

Maybe skip adding the kernel to the name of the operating system, maybe
unless is an operating system that can support different kernel-types,
such as the PC operating system "GNU" (with, or "Hurd", or "Linux").

I you meant to say the kernel "Linux" instead, then just say, or
"Linux", or "the kernel Linux". People who can /not/ call the proper
names to things made this confusion exist, to begin with...

Don't take me wrong, I think it is worth this intervention of mine.

Cheers,

=2D-=20
The pioneers of a warless world are the youth that
refuse military service. ~ Albert Einstein

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJmBAEBCgBQFiEEOVeKaEm0xBhCsMmYlk/BEMQK1XUFAmoa3UgbFIAAAAAABAAO bWFudTIsMi41KzEuMTEsMiwyFhxkYW4ubGlzdEBsaXNwY2x1Yi5jb20ACgkQlk/B EMQK1XWqvxAAmawFhPVpLmiA3BphCjAKPUgCab5JyyD1+XPwSCI5bHzbQmgxwvwB z+HK0JeJDz2QbdO9xP6/tauMp8CH00HmOPuIUfz47vW2kr8QU1PdpMOZb7hvGi3d +ZzsmKehxI57927cTY3apzoK4znlR1CJe3IHJyER9pDFIr4a0TC7lFSWmN06q+1i wwy8t1Bb0XG6aB6zLiqW5WHfDy9pj/guyOw8sZwGK+74z06488PxxymaCdIAtkiM PhtHgfsnKiptbs+0TEKvHQNTN4NTq3fYfuuK3A6pxhKb4oMBSO4XsIQSh6tEYke+ 5U6RS6b6mMTJQ1k+CLBTVpU76/ATdJSkBKwlLoEsVB8Nf5wynRPLL4J6KyxZMTYD 3kOfKRvhGmgiEBqvNHl36DHr+iKy6qTsmQb4JeLpPpo52XWYUaj7bB78PPps+bup vDXCVtRmAxR6+mbafDysDyXYH/A1j7NXs8p69WAGABI6pJVW4uuUd4/CgusWuRRO 1BnaSKgxnqUadhhBt/M/LaLd4CMwinOnsjdpT+z/RjYkvOUTHcz8rPg7UIstKT5Y IPoCgT5ZcKpGZcvxGsSBzJBSR8kVkgecas8d2XbiqAxgXIV8snVColY9yMYmH2U8 3TtrvrT+6KjIHu3YZ8YAgAzCch+Z6qIz8ZfEy5NNfURXg8llilOirSY=
=u73L
-----END PGP SIGNATURE-----
--=-=-=--
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

I tried reinstalling the Gforth app. Now Gforth can see none of the
files in .../Download/gforth, new nor old. :(

Are my choices to either rooting the phone or running Gforth inside
Termux?
--
David Meyer
Takarazuka, Japan
papa@sdf.org
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

Am Sat, 30 May 2026 10:57:36 +0900 schrieb David Meyer:

Any idea what's going on with the new file?

I recently updated Android, too, and can reproduce this. I suppose Google tightened the screws again.

What still works is using the one single privileged file browser (the one
that comes with the device) to copy such a file into /storage/emulated/0/ Android/data/gnu.gforth/gforth/home and load it from there.

IMHO the best way to spend my time on this enshittification of Android is
to get net2o's DVCS working good enough that you can edit your files on a
PC, and then sync them over to Android with tools all embedded within the Gforth app.
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ*
https://bernd-paysan.de/
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

Am Sun, 31 May 2026 07:45:51 -0000 (UTC) schrieb Bernd Paysan:

Am Sat, 30 May 2026 10:57:36 +0900 schrieb David Meyer:

Any idea what's going on with the new file?

I recently updated Android, too, and can reproduce this. I suppose
Google tightened the screws again.

Checking for possible workarounds: If Gforth creates the file, it can see
and read it even when the file manager edited it. So you might want to
define a "touch" command that allows you to quickly create files there,
and then overwrite/edit them with the file browser.
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ*
https://bernd-paysan.de/
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

Bernd Paysan <bernd@net2o.de> writes:

Checking for possible workarounds: If Gforth creates the file, it can see and read it even when the file manager edited it. So you might want to define a "touch" command that allows you to quickly create files there,
and then overwrite/edit them with the file browser.

That works, though only if you edit the file created by
Gforth. Overwriting the file from another app makes it inaccessible from Gforth.

At least the Gforth app is now useful, until Google decides to make
further "improvements" to Android.
--
David Meyer
Takarazuka, Japan
papa@sdf.org
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

Based on Bernd's guidance, I've written a couple of utilities to make it
easier to share files between Gforth and an editor app on Android and summarized what I've learned. Comments are welcome.

https://papa.sdf.org/cave/forth/gforth-android-edit.html
--
David Meyer
Takarazuka, Japan
papa@sdf.org
--- Synchronet 3.22a-Linux NewsLink 1.2