You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this must be due to the commit 65c1742, since this is the last change that happened in the terminal plugin, and it looks like the kind of change that could make a bug like this happen.
Also, I was wondering while looking at that commit, wouldn't a change like this, that makes cosmic-terminal the default be unnecesary?
I mean, the plugin already uses x-terminal-emulator from debian alternatives already, wouldnt it be better to just change that default there?
The text was updated successfully, but these errors were encountered:
Sorry about the delay, I was very busy and I forgot about the issue.
My point was just that, right now, in Pop_os, if i change the x-terminal-emulator option, the Meta+T option changes to the new one, but if cosmic-terminal is installed then the launcher shortcut t: will always use cosmic-terminal as a hardcoded option.
Wouldn't it be better to put the x-terminal-emulator option with a higher priority, so that people using pop_os with a diferent default terminal won't have any issues even if they have installed cosmic-terminal. Or at least give the option to change t: in a config file diferent from the debian alternatives system.
In any case, since the title of the issue was about it using xterm instead of any other terminal, I tried just now uninstalling cosmic-term, to check if under that situation the issue I originally had happened again, but it just used gnome-terminal, so that issue doesn't happen anymore. In any case, I still think it isn't great that it prefers use of cosmic-term in that hardcoded manner
I believe this must be due to the commit 65c1742, since this is the last change that happened in the terminal plugin, and it looks like the kind of change that could make a bug like this happen.
Also, I was wondering while looking at that commit, wouldn't a change like this, that makes
cosmic-terminal
the default be unnecesary?I mean, the plugin already uses
x-terminal-emulator
from debian alternatives already, wouldnt it be better to just change that default there?The text was updated successfully, but these errors were encountered: