{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 混吃等死 的问题《undefined environmental variable expansion in cmd》','https://www.manongdao.com/q-873047.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
On Windows command prompt:
D:\> echo %undef%
%undef%
D:\> type undef.bat
echo %undef%
D:\> undef
D:\> echo
ECHO is on.
My question is why on command line undefined environment variables like %undef% are expanded to %undef% but in BAT files are expanded to empty string?