Re: I need further understanding of wine or bash

On Sat, Apr 26, 2008 at 12:40:39AM +1200, Chris Bannister wrote: > You've gotta be careful with #!/bin/sh it may not be linked to bash, > i.e: > > ls -al /bin/sh > lrwxrwxrwx 1 root root 9 2008-01-22 04:04 /bin/sh -> /bin/dash I did check for bashism in the script before posting it. I tend to a

Re: I need further understanding of wine or bash

On Mon, Apr 21, 2008 at 08:43:53PM +, Tzafrir Cohen wrote: > On Mon, Apr 21, 2008 at 02:05:23PM -0400, Dylan Garrett wrote: > > > One issue that I see that you should fix (though it won't affect your > > results): > > #bin/bash! > > Should be: > > #!/usr/bin/bash > > /usr/bin/bash? where? /bi

Re: I need further understanding of wine or bash

Rich Healey wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Damon L. Chesser wrote: Dylan Garrett wrote: On Mon, Apr 21, 2008 at 4:43 PM, Tzafrir Cohen <[EMAIL PROTECTED] > wrote: On Mon, Apr 21, 2008 at 02:05:23PM -0400, Dylan Garrett wrote: >

Re: I need further understanding of wine or bash

Dylan Garrett wrote: On Mon, Apr 21, 2008 at 4:43 PM, Tzafrir Cohen <[EMAIL PROTECTED] > wrote: On Mon, Apr 21, 2008 at 02:05:23PM -0400, Dylan Garrett wrote: > One issue that I see that you should fix (though it won't affect your > results): > #

Re: I need further understanding of wine or bash

On Mon, Apr 21, 2008 at 4:43 PM, Tzafrir Cohen <[EMAIL PROTECTED]> wrote: > On Mon, Apr 21, 2008 at 02:05:23PM -0400, Dylan Garrett wrote: > > > One issue that I see that you should fix (though it won't affect your > > results): > > #bin/bash! > > Should be: > > #!/usr/bin/bash > > /usr/bin/bash?

Re: I need further understanding of wine or bash

On Mon, Apr 21, 2008 at 02:05:23PM -0400, Dylan Garrett wrote: > One issue that I see that you should fix (though it won't affect your > results): > #bin/bash! > Should be: > #!/usr/bin/bash /usr/bin/bash? where? /bin/bash > Or better yet: > #!/usr/bin/env bash Or simpler: #!/bin/sh -- Tzafr

Re: I need further understanding of wine or bash

Dylan Garrett wrote: On 4/21/08, *Damon L. Chesser* <[EMAIL PROTECTED] > wrote: Brian McKee wrote: On 21-Apr-08, at 11:08 AM, Damon L. Chesser wrote: if I use a term and cd into the games dir and type " wine Sins\ of\ a\ Solar\

Re: I need further understanding of wine or bash

On 4/21/08, Damon L. Chesser <[EMAIL PROTECTED]> wrote: > > Brian McKee wrote: > > > > > On 21-Apr-08, at 11:08 AM, Damon L. Chesser wrote: > > > > if I use a term and cd into the games dir and type " wine Sins\ of\ a\ > > > Solar\ Empire.exe " it works > > > > > > > Why not try adding a 'cd into t

Re: I need further understanding of wine or bash

Brian McKee wrote: On 21-Apr-08, at 11:08 AM, Damon L. Chesser wrote: if I use a term and cd into the games dir and type " wine Sins\ of\ a\ Solar\ Empire.exe " it works Why not try adding a 'cd into the games dir' before the wine line? Brian Brian, That worked: #bin/bash! cd /home/damo

Re: I need further understanding of wine or bash

On Monday 21 Apr 2008, Damon L. Chesser wrote: > #bin/bash! > wine /home/damon/C_drive/'Program Files'/'Stardock Games'/'Sins of a > Solar Empire'/'Sins of a Solar Empire.exe' I must confess I haven't read your email in full, but why not just a desktop shortcut to: env WINEPREFIX="/home/damon/.w

I need further understanding of wine or bash

I have a game (only one :) ) that runs in win. I find I can use thunar or nautilus to tunnel down to the executable and right click, choose "open with wine", game runs fine. This is tedious. So, using my superior knowledge of scripting, I thought I would just make a quick bash script and exe