screen TERM environment problem after upgradation

Dear list, I have the following setting in .screenrc from the beginning `` shell -$SHELL # for locale charset setenv LC_CTYPE en_US.UTF-8 setenv TERM xterm hardstatus alwayslastline hardstatus string '%{= kW}%-Lw%{= Gk}%50>%n%f* %t%{= kW}%+Lw%< %{= Gk}%-=%D %d %M %Y %c:%s%{-}' # de

Re: at-command and NEED_DISPLAY

On Tue, 2 Feb 2010, Sadrul Habib Chowdhury wrote: * Peder Stray had this to say on [02 Feb 2010, 19:25:29 +0100]: Why does then 'at' command need a display? It doesn't anymore! See: http://git.savannah.gnu.org/gitweb/?p=screen.git;a=commit;h=4b778782ce398747f080b7b7ffd8a2e26c3b0a88 Goodie

Re: at-command and NEED_DISPLAY

* Peder Stray had this to say on [02 Feb 2010, 19:25:29 +0100]: > > Why does then 'at' command need a display? It doesn't anymore! See: http://git.savannah.gnu.org/gitweb/?p=screen.git;a=commit;h=4b778782ce398747f080b7b7ffd8a2e26c3b0a88 Cheers, Sadrul _

at-command and NEED_DISPLAY

Why does then 'at' command need a display? I have a screen I sometimes start with -d -m. In the config file it uses there are a few 'at'-commands that doesn't run when stated in that way. I know the at command may need a display in som invocations, but not when the first parameter is a num