Custom command > Run in Terminal doesn't run the command about workspaces HOT 6 CLOSED

So, after some evaluation and debugging with @DevAlien , we noticed that x-terminal-emulator -x my-alias and x-terminal-emulator -e "my-alias" weren't working with aliases, because non-interactive commands do not have access to aliases defined in .bashrc.

On my local tests, running x-terminal-emulator -e 'bash -i -c "my-alias"' worked. It basically the -i flag means the terminal will be interactive, which makes the aliases load. It fixed my use case, and didn't break anything apparently.

from workspaces.

That's fine. As soon as the change that changes -c to -e comes out, I can add bash -i -c "my-alias" part myself on the command.

from workspaces.

Maybe flatpak-spawn needs some flags to run in terminal. I'm investigating

from workspaces.

For the record, I'm having a similar issue with a non-Flatpak version (I installed from AppCenter).

But I can actually get some commands to work. For example, I run "mongod" to start the MongoDB service and it works. Same for "htop". However, I can't run some aliases (for example "graphics" in my screencast below), and more complex commands that start with "cd ~/Pictures" for example, that throw out Failed to execute child process “cd” (No such file or directory).

If you think this might be a different problem, I can open a different issue.

from workspaces.

@matfantinel Sorry I missed this. We made a fix for this, would be great if you could give it a go. It is in the develop branch.

from workspaces.

If someone wants something special like that should do it on its own for the moment, not everybody uses bash etc. BUt commands should run better now. The issue with aliases stays there though. This is ready for 3.1 #32

from workspaces.