farvardin

sure. As a workaround, you can modify /usr/local/share/gforth/xx_version_xx/gforthrc.fs and put at the end: ``' noop is bootmessage`` actually, gforth should recognise a ~/.config/gforthrc but on gforth 0.7.9_20221117 after setting export...

altering ``/usr/local/share/gforth/xx_version_xx/gforthrc.fs`` is not ideal, because the bootmessage word is calling the gforth and not the actual bootmessage, and there is also a process for loading the status bar and...

@WraithGlade I've looked again at this problem. I still don't understand why the history isn't working when we have ``' noop is bootmessage`` to the ~/.config/gforthrc0 because it seems this...

@forthy42 that's a very interesting feature! I couldn't find it in the online doc, and it didn't even work in my gforth-0.7.9 from 2022-01-27, so I've discovered it was a...

> I'd suggest to provide some setup information (aka. complete the issue template) For example, this might be needed at minimum: I've tried again, with the config in ~/.config/redshift.conf and...

well, I've never bothered with AppArmor, I didn't even know it was used outside some servers' scope. I suppose redshift has made some adjustement to skip AppArmor stuff, because none...

I was going to open a similar issue until I've found this one. It seems to be more complicated than I thought. I suppose disabling the JS alert and making...

> i think the best advice for now is to find a pixel doubling X server. I don't know which one will do that but perhaps someone will ? that...

> You might try the SDL version, which has a scaling option on all devices. thank you, it's working! I've built maiko using the sdl backend: ``./makeright sdl`` then I've...

thank you @iyzsong it helped to patch espforthstation: https://github.com/uho/ESP32forthStation/issues/1