Re: turn off history
Bernd Paysan <[email protected]> Wed, 27 Jul 2022 22:57:13 +0200
| Newsgroups | gmane.comp.lang.forth.gforth |
|---|---|
| Message-ID | <2312557.NG923GbCHz@liubei> |
Am Mittwoch, 27. Juli 2022, 20:27:45 CEST schrieb Tomas Hlavaty: > I do not understand why setting bootmessage to noop from inside the > script turns the bootmessage off but setting 'cold to noop from inside > the script does not turn the history off. Probably because it is > already too late for the history? Yes, 'cold did already run. I think putting the history initialization into bootmessage instead is the right place. The other thing that is difficult to turn off is the loading of ~/.config/ gforthrc0. This can be controlled with a shell variable, but e.g. if you have your sever script using #! <path to gforth>, you can't turn off this environment variable, because only one extra argument is allowed, so #! /usr/bin/env GFORTH_ENV=off <path to gforth> is not valid. -- 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://net2o.de/
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEERJ1NDqPQRwYnwBjr9y2Uk5MtoGcFAmLhpqkACgkQ9y2Uk5Mt oGcJPxAAmwQIsAEb+lTqzisnfVOhjpGYTft1TozuJQIK5h99QI4P1oIBnCELDesX t0lgKXFLJZ5x1FE7cFU8T53qBroXJECMXEPCebK305Kjf3LXnvuYpW5zfS3KKgVt Ni9bNgwVESxg7zMwkfZ8aGEX4j8uRGaUJPTj0jcPF8plbDzb9lULQhIB1nB2sWnA VoM5G4C5IMDbSHV2glLH6CD58HYzVAuuD5RAj7gpYl6zET0+vM5AqncpT2u+jcOw 7VbO47lElMZc1kFDdsrlUr8waqXa6MtVaPTmgIY+iFg+bVvCxqxcNh178l0zQ/st D9iuzmNABelwqqLBUigffN1GKuuj6yEbGBMScTsdR5XGTVeMV8P3RGeDw4POaJNh 9USzeHe1rySZGIcdq0cwYj/BlrnsKyO+9/FNqrIpEt2f6jbhkcbq3ugBhEMfu6ld yq6G13IIBNNWWTgaxYkXTYD9nrYZhqbSJS4+1snbeQpkLsIeej3kDpWyrmw8YzhC ofJb2XCaWMjs0+k65pWReR3WORVxU4uvaOBcyVo/1Um+ZowGWtg3la1GTRw8diXf C+JWD6VRDSp50QOb9QzGWqs8iBe37HvT+RcS58zXwGvpE4DS1PRouWBK7fcOBKNA FDq76lfsSk30C4JgJOhh6v7b3dP8YoFYHTaGnwcekiP/xcM+vyM= =7LqD -----END PGP SIGNATURE-----