PG-15 - Format problems after jump migration from 9-4 to 15

Hi all,
it's a long time I did not submit any query as I was happily working with
a database created many years ago with Postgresql-9.4 under Linx/Debian.
As my old PC is falling into pieces I migrated old PG-9.4 clusters to a
brand new PG-15 under Debian-12 on a Beelink Mini Pro 12.

While testing if all was in order I received an unusual warning on one of
the tables, containing instruction like those reported hereunder that I'm
unable to solve.
Could you please give me some hints to overcome the problem?

Thanks in advance for your help.
Kind regards,
emmio

-------------------------
§§--> This is one of the code lines in my script, just to give you
§§--> an idea:

usr(at)deby:~$ minc="`psql mydb -tc "select cast(date_part('month',current_date) as integer);"`"
usr(at)deby:~$ echo $minc
Target width is 150. Output format is wrapped. 1

§§--> And this is what appears on the screen when I enter 'mydb':

usr(at)deby:~$ psql mydb
Target width is 150.
Output format is wrapped.
psql (15.10 (Debian 15.10-0+deb12u1))
Type "help" for help.

(§§-> Nothing happens after setting PAGER)

mydb=> \setenv PAGER less
mydb=> \q

usr(at)deby:~$ minc="`psql mydb -tc "select cast(date_part('month',current_date) as integer);"`"
usr(at)deby:~$ echo $minc
Target width is 150. Output format is wrapped. 1
usr(at)deby:~$

--
[Perché usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?//
Fà qualche cosa di cui non sei capace!" (diceva Henry Miller) (°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that. .)=(.
Do something you aren't good at!" (as Henry Miller used to say)] /_____\