On 2019/12/12 10:47, Marc Espie wrote: > Well, in the sysmerge use-case, you see the first line showing the > $OpenBSD$ prompt usually. That's often when you realize your terminal is > really small, and you will miss the next lines. The $OpenBSD$ line is > reasonably unambiguous, as the rev number is fairly prominent.
I run into similar probably at least half the time when I use sdiff. I don't find it too bad with sysmerge - the merge is usually simple for an individual file, and sysmerge itself reacts when the width is changed between files. (Changing sdiff to fetch the width at startup would have no benefit for the sysmerge case). The problem I have is when running sdiff by hand - I do this fairly often when merging in changes to more complex port config files (postgresql, dovecot, php, etc) - if it isn't apparent that a wider terminal is needed until partway through the file, currently or with "fetch at startup" you'd have to exit and redo the work. On 2019/12/12 03:05, Theo de Raadt wrote: > Rather than writing completely new code from scratch with it's own quirks, > find and copy other utilities which already does it fully, such as > ls, ps, sed, column, w, etc Despite not being full-screen, sdiff is fairly long-running and reacts to user input, from a user's perspective it seems that it should work more like top than ls.
