I expect vim to honour my choice of not modifying the terminal title.
9.2.0524
Operating system: Debian testing
Terminal: xterm + screen
Value of $TERM: screen.xterm-256color
Version of screen: 5.0.1
Shell: zsh
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
cannot reproduce
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
What do you mean by "vim still sets the terminal title"?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
What do you mean by "vim still sets the terminal title"? What does the terminal title change to?
It changes to [Aucun nom]. Or with LANG=C it changes to [No Name].
But I noticed it only happens within screen, not directly in xterm.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
Just curious, could it be that Vim is querying the termcap for the t_ts value on startup and this effectively overwrites the --cmd argument because it happens later? In that case: vim -u NONE -N -c 'set notitle' should fix it
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
@chrisbra don't waste more time on this, this guys a troll.
podman run --rm -it debian:testing /bin/sh -c 'apt update && apt install -y vim && vim -Esu NONE +"call writefile([execute(\"set title?\")], \"/dev/stdout\")|qall!"' # notitle podman run --rm -it debian:testing /bin/sh -c 'apt update && apt install -y vim-gtk3 && vim -Esu NONE +"call writefile([execute(\"set title?\")], \"/dev/stdout\")|qall!"' # notitle
20:41 <Celelibi> Found it, it's related to X11. When I empty DISPLAY envvar, the title is no longer set.
20:42 <Celelibi> I think help 'title' mentions some special behavior about a behavior change when X11 is available.
20:43 <Celelibi> !unscrable_words :p
20:50 <dza> Celelibi: u didn't mention x11 in your issue and neither did your command.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
Looks like X11 is required to show the issue, but is not enough. Here is the minimum number of environment variables I could get to reproduce the issue in screen:
env -i DISPLAY=:0 TERM=screen.xterm-256color WINDOWID=41943054 vim -u NONE -N -c 'set notitle'
However, adding the option -X does make the issue go away. I'll try to reproduce this bug from a container, but the issue being related to X11, it still won't be completely self-contained.
Not verifying the command return proven via container, moving the goalpost from a terminal, screen vim issue to x11 and giving hints at trolling.
Dude, the goalpost never moved one inch and has always been stated clearly in the title of this issue. The fact that I don't know right away everything required to reproduce it only makes it hard to reproduce, it doesn't make me a troll. If you don't wanna help, don't, there's no obligation.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
Dude, the goalpost never moved one inch and has always been stated clearly in the title of this issue. The fact that I don't know right away everything required to reproduce it only makes it hard to reproduce, it doesn't make me a troll. If you don't wanna help, don't, there's no obligation.
I'm above avg patience, I have a severe case of ADD - so I also give others extra patience and I do take pride in helping others generally with patience.
My bullshit meter went off when you dropped that mocking note with your long-waited x11 reveal from help you never included here or in chat. When you don't verify a copy-pasteable command (claim the impossible), leave out details and keep changing it (everytime I disprove it), that feels like a truly intentional waste of time, mocking those trying to help you.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
@dezza You're just being paranoid. Please save everyone's time and stop posting in this issue. You're detrimental to solving it.
For anyone else interested:
Here's a docker command to run in a fresh xterm that reproduces the issue. At least for me.
docker run --rm -it --env DISPLAY=:0 --env TERM=xterm --env WINDOWID=41943054 --net host -v /tmp/.X11-unix:/tmp/.X11-unix -v ./.Xauthority:/root/.Xauthority debian:testing /bin/sh -c 'apt-get update && apt-get install -y vim-gtk3 screen && screen -T screen.xterm-256color vim -u NONE -N -c "set notitle"'
Some of the env variables (especially the WINDOWID) and path of mounted volumes might need adjustment on your system.
Checking xterm logs, it receives an escape sequence that begins with \e]2; that sets the title. On the other hand, strace show vim sends the would-be title with \e]1;. Looks like screen performs a translation there.
Some google results suggest that \e]1; is the prefix for setting the icon. And indeed, set noicon prevent vim from changing the the terminal title.
May I suggest documenting the behavior that some terminal emulators might treat the icon as a title?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
I expect people to not lie to my face, as I know others do. If you can't understand that, maybe irc or github isn't for you. God bless those who spend time with you.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
has anyone reproduced this issue besides @Celelibi ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()