Very small editor "window"

[Christoph Pleger]

Hello,

>>> The editor is joe, a very small and simple editor suitable for
>>> beginners. It is a non-GUI editor and in my special case, is running
>>> on a text console (tty1).
>>
>> Why don't you use the standard CLI editor "nano"? Maybe that one works
>> better.
>
> It does.

I still have the problem that, when the editor is called at boot time, it
does not show up before some keys have been pressed; with nano, that is
even worse than with joe. Or more exact: I found out now - it is very
difficult to see, because the screen gets filled so fast - that the editor
is shown, but after that, so many warnings from setupcon about wide
characters appear on the screen, that the editor is not visible any more.
I wonder why this is happening, because console-setup.service - where
setupcon is called - is wanted by sysinit.target, which is followed by
basic.target and multi-user.target before my additional systemd service
starts. This is the unit file for my service:

[Unit]
Description=LINF2 Rescue Service
Requires=multi-user.target
Before=getty at tty1.service
After=multi-user.target

[Service]
Type=oneshot
ExecStart=/usr/local/sbin/linf2-rescue
StandardInput=tty
StandardOutput=tty
TTYPath=/dev/tty1
TTYReset=yes
TTYHangup=yes
TTYVTDisallocate=yes


I took the last three lines from getty at .service, because my own service
starts nearly at the same time when normally the tty logins are shown.

I wonder why the screen is garbaged by setupcon output. As the file above
shows, my service starts after multi-user.target has been reached,
multi-user.target is after basic.target and basic.target after
sysinit.target. sysinit.target wants console-setup.service, which calls
setupcon. Any idea why output of setupcon appears on the screen after the
editor has been started, though setupcon output should have appeared much
earlier?

Regards
  Christoph