desktop-packages team mailing list archive

[Ash <flubba86@xxxxxxxxx>]

Is there any chance of this being looked at? I use XFCE4 and this bug
affects me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/778801

Title:
  TERM unconditionally set to "xterm", regardless of config

Status in Gnome Virtual Terminal Emulator:
  Invalid
Status in XFCE4 Terminal Emulator:
  Unknown
Status in “vte” package in Ubuntu:
  Triaged
Status in “xfce4-terminal” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xfce4-terminal

  Xubuntu 11.04 Natty Narwhal

  xfce4-terminal 0.4.7-0ubuntu1
  libvte9 0.27.90

  I wish to enable 256-color support in apps running under
  xfce4-terminal; but even though I've set TERM to this value in the
  config (and verified it in .config/Terminal/terminalrc), the TERM
  variable winds up having the value "xterm".

  Upon digging a little further, xfce4-terminal correctly sets the TERM
  variable in the environment vector that it then passes through to vte
  via vte_terminal_command_full (this takes place within the
  terminal_screen_launch_child function found in terminal/terminal-
  screen.c). However, vte_terminal_fork_command_full copies everything
  from that vector _except_ the TERM variable, unconditionally replacing
  that with a value that should be set by calling vte_pty_set_term (this
  happens in src/pty.c:__vte_pty_merge_environ(), which is called by
  (and gets the TERM value from) src/pty.c:__vte_pty_spawn, which in
  turn is called by src/vte.c:vte_terminal_fork_command_full() ).
  xfce4-terminal doesn't appear to ever call that function anywhere, and
  thus vte defaults to "xterm". So the appropriate fix would seem to be
  to make xfce4-terminal call that function to register the correct TERM
  value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/vte/+bug/778801/+subscriptions