This is not a bug, as GNOME Do is not an implementation of Bash. I
suggest writing a plugin to support this, or write a blueprint in the
do-plugins project.
On Aug 14, 2008, at 5:02 PM, holotone <email address hidden> wrote:
> Public bug reported:
>
> I cannot run my bash aliases using Gnome-Do as it does not provide a
> "Run" option for them.
>
> ** Affects: do
> Importance: Undecided
> Status: New
>
> --
> Gnome-do doesn't respect bash aliases
> https://bugs.launchpad.net/bugs/258019
> You received this bug notification because you are a member of GNOME
> Do
> Core Team, which is subscribed to GNOME Do.
I was sent here to file this bug by the folks at #gnome-do; They seemed to think it was a bug as "Run" or "Run in Terminal" should already encompass this functionality.
I use zsh, and others use many different shells. Pretty soon we'll
have the same situation of supporting many different terminal
configurations in the same plugin. Then, someone will write a Konsole
plugin and they'll want support for all different shells so they'll
duplicate the code because shell support wasn't decoupled when it
could have been, like every other component of Do.
David
Sent from my latest-and-greatest, proprietary, DRM-enabled, crypto-
locked gadget.
On Aug 15, 2008, at 10:18 AM, conundrum <email address hidden> wrote:
> Alex and I both think Do should respect bash aliases for run/run in
> terminal. It makes sense to me.
>
> --
> Gnome-do doesn't respect bash aliases
> https://bugs.launchpad.net/bugs/258019
> You received this bug notification because you are a member of GNOME
> Do
> Core Team, which is subscribed to GNOME Do.
Actually, shell support should be provided by the terminal
application. Either the Do terminal plugin is conslfigured improverly,
or GNOME Terminal has a bug. Sending a command line to the terminal
app should cause that line to be run in your preffered shell. If this
happens, we get support for all shells for free.
David
Sent from my latest-and-greatest, proprietary, DRM-enabled, crypto-
locked gadget.
On Aug 15, 2008, at 11:11 AM, David Siegel <email address hidden> wrote:
> "2 vs 1" is not an argument.
>
> I use zsh, and others use many different shells. Pretty soon we'll
> have the same situation of supporting many different terminal
> configurations in the same plugin. Then, someone will write a
> Konsole plugin and they'll want support for all different shells so
> they'll duplicate the code because shell support wasn't decoupled
> when it could have been, like every other component of Do.
>
> David
>
> Sent from my latest-and-greatest, proprietary, DRM-enabled, crypto-
> locked gadget.
>
> On Aug 15, 2008, at 10:18 AM, conundrum <email address hidden> wrote:
>
>> Alex and I both think Do should respect bash aliases for run/run in
>> terminal. It makes sense to me.
>>
>> --
>> Gnome-do doesn't respect bash aliases
>> https://bugs.launchpad.net/bugs/258019
>> You received this bug notification because you are a member of
>> GNOME Do
>> Core Team, which is subscribed to GNOME Do.
Dave, but we need to recognize it as a valid command before we'll allow it to be passed to the terminal, we check $PATH and see if it's on it, otherwise we don't even give Run or Run In Terminal as an available Action.
We are not hardcoding Bash support into Do, but a plugin solution would be nice. We could create a BashEnvironmentService that might take care of this...
This is not a bug, as GNOME Do is not an implementation of Bash. I
suggest writing a plugin to support this, or write a blueprint in the
do-plugins project.
On Aug 14, 2008, at 5:02 PM, holotone <email address hidden> wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 258019
>
> I cannot run my bash aliases using Gnome-Do as it does not provide a
> "Run" option for them.
>
> ** Affects: do
> Importance: Undecided
> Status: New
>
> --
> Gnome-do doesn't respect bash aliases
> https:/
> You received this bug notification because you are a member of GNOME
> Do
> Core Team, which is subscribed to GNOME Do.