UHHHHHH, that worked for only the one xterm I ran it in. What If I want it run on all xterms? Run it in .xinitrc ?
On Thu, Dec 12, 2024 at 8:00 AM Todd Gruhn <tgru...@gmail.com> wrote: > > Thanks -- gives me something to do... > > On Thu, Dec 12, 2024 at 7:13 AM <ignat...@cs.uni-bonn.de> wrote: > > > > On Thu, Dec 12, 2024 at 10:23:27AM +0100, ignat...@cs.uni-bonn.de wrote: > > > On Thu, Dec 12, 2024 at 08:47:22AM +0100, Martin Husemann wrote: > > > > On Thu, Dec 12, 2024 at 08:09:46AM +0100, Ignatios Souvatzis wrote: > > > > > No, but you can do that with a small script from the terminal - > > > > > there's an escape character sequence. I'll post my script later when > > > > > I have access to it. > > > > > > > > Something like: > > > > > > > > printf "\x1b]2;you are: ${USER} and here: ${cwd} \x07" > > > > > > > > where \x1b is ESC and \x07 is ^G aka BEL > > > > > > > > or: > > > > > > > > printf "\x1b]2;Hi ${USER} it is %s\x07" "$(date)" > > > > > > Yes , only my script useds \033 and \007, not that newfangled hex stuff > > > ;-) > > > > > > Be careful not to send that to wscons terminals, only xterms and > > > similar, though! The ANSI standard ESC ] introduces much longer > > > sequences ("Operating System Control") that end in a different > > > delimiter! > > > > Wait - we disarmed this trap in 2021, so any supported NetBSD releases > > are safe. > > > > -is