#1694 vte overwriting PROMPT_COMMAND
Closed: Insufficient data 6 years ago Opened 7 years ago by srakitnican.

Dear FESCo,

This is an issue of Gnome component overriding system variables. The issue has been reported a while ago on RHBZ as well on Gnome bugzilla with no sign of any progress for almost 4 years. Meanwhile Fedora gets releases with such a broken behavior.

The user expects for PROMPT_COMMAND to be settable as for numerous online tutorials that make use of it for modifying bash prompt style. There is no way for user to know that in Gnome this variable is not usable and, as in my case, loses quite some time debugging it or in other cases simply accept the fact that it doesn't work and moves on.

In other cases some software may make use of it for its core functionality like it is the case for autojump. Such software in this case does not work, and again user may have no idea of why it is the reason.

Therefore I suggest to modify Fedora version of vte to not replace PROMPT_COMMAND but append its commands.

https://bugzilla.redhat.com/show_bug.cgi?id=1183192
https://bugzilla.gnome.org/show_bug.cgi?id=704960

Best regards,

Samuel Rakitničan


Have you discussed this with the Workstation WG?

No, I did not. I am not sure what this question is supposed to imply, I am not very familiar with the process so forgive me if I've missed something obvious!

No, I did not. I am not sure what this question is supposed to imply, I am not very familiar with the process so forgive me if I've missed something obvious!

With the introduction of Editions (Workstation, Server, Cloud/Atomic) most of the decisions that would be specific to that edition are handled by their respective working groups. I was just wondering if you had brought this up to the Workstation WG yet given the Gnome specific aspect of the issue. It might be worth starting a thread on their mailing list (desktop@lists...) to see if you can get some eyes on it.

CC @rishi, our gnome-terminal maintainer

Any news here? I see a post on the desktop list, but no replies yet.

Metadata Update from @sgallagh:
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

6 years ago

Not trying to reopen, but can you elaborate on what "Insufficient data" means?

It has been five months since we last asked if there was any progress here and anything FESCo should do. I closed the ticket because it's been basically abandoned.

Well I've proposed a simple fix to which I've got no response, not sure what else I can do this is clearly not resolved. Should I start a process of unresponsive maintainer or what?

What can FESCo do, maybe decide if it is all right or not to overwrite this variable. If FESCo agrees that it doesn't matter, then there is nothing much anyone can do. If it is not acceptable, then maybe accept my proposed fix if there is no better one?

Login to comment on this ticket.

Metadata