Re: Help-bash Digest, Vol 146, Issue 2

[Budi]

Excellent

One thing is sure that this Wine+.exec launching has a tiny error at the
time just about to perform displaying GUI
as it's echoed in terminal when launched manually on it, the only way
separating Bash/terminal with ... &exit will work

So the point then is this error is ignorable, harmless when done manually
so, but does affect when trying to be automated as a script leading to fail
to separate Bash/terminal with the executables

Any further knowledge of it?

On Tue, Dec 12, 2023 at 12:02 AM <help-bash-request@gnu.org> wrote:

> Send Help-bash mailing list submissions to
>         help-bash@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.gnu.org/mailman/listinfo/help-bash
> or, via email, send a message with subject or body 'help' to
>         help-bash-request@gnu.org
>
> You can reach the person managing the list at
>         help-bash-owner@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Help-bash digest..."
>
>
> Today's Topics:
>
>    1. Have this CLI / one-liner works as exactly well as in a
>       launcher (Budi)
>    2. Re: Have this CLI / one-liner works as exactly well as in a
>       launcher (bill-auger)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 11 Dec 2023 07:26:57 +0700
> From: Budi <budikusasi@gmail.com>
> To: help-bash@gnu.org
> Subject: Have this CLI / one-liner works as exactly well as in a
>         launcher
> Message-ID:
>         <
> CAH0GyZCzo6RMdKBfjnx4MgptPuhN1D8hUeoAU-ths5SZg1FXGw@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> *WINEARCH=win64; cd /home/budi/.wine/drive_c/shamela4; LC_ALL=ar_SA.UTF-8
> wine64 app/win/64/bin/shamela.exe & exit *
>
> How to have the above functional CLI / one-liner works as exactly well as
> in a Linux Xfce desktop launcher:
> Aim is:
> To have the app/executable after being launched 100% work, it must get
> separated of Bash (and terminal) and Bash (and terminal) must then be
> closed/killed completely
>
> it'll execute the .exe binary upon wine binary successfully than back to
> bash environment and exiting it automatically closing the whatever terminal
> hosting it
>
> been trying more than 25 tries for 3 days with no avail (!)
> differs only USER=foo due to a reason, eg. tries:
> 1.
> usr/bin/env WINEARCH=win64 LC_ALL=ar_SA.UTF-8 wine64
> app/win/64/bin/shamela.exe
> & exit
>
> 2.
> same above with launcher "Working Directory field" ia set to
> /home/foo/.wine/drive_c/shamela4
>
> 3.
> xfce4-terminal --execute bash -c 'export WINEARCH=win64; cd
> /home/foo/.wine/drive_c/shamela4; LC_ALL=ar_SA.UTF-8 wine64
> app/win/64/bin/shamela.exe
> ;exec bash & exit'
>
> 4.
> xfce4-terminal --execute bash --rcfile ini.sh
> whle ini.sh
>
> export WINEARCH=win64
> cd /home/foo/.wine/drive_c/shamela4
> LC_ALL=ar_SA.UTF-8 wine64 app/win/64/bin/shamela.exe & exit
>
> 5
> same above with the end is changed:
>
> &{ sleep 9; exit ;}
>
> 6
> same above with the end is changed:
>
> &{ disown; exit ;}
>
> ...
>
> all such combination much more so on.
>
>
> either it won't get launched or later on both exit ( the sleep try),  or
> launched while both keep together alive on PID
> PLEASE SINCERELY HELP !
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 11 Dec 2023 09:26:03 -0500
> From: bill-auger <bill-auger@peers.community>
> To: Budi <budikusasi@gmail.com>
> Cc: help-bash@gnu.org
> Subject: Re: Have this CLI / one-liner works as exactly well as in a
>         launcher
> Message-ID: <20231211092603.704f3a36@parabola.localdomain>
> Content-Type: text/plain; charset=US-ASCII
>
> this is not really a BASH question - any of this would apply to any shell
> - i
> suspect that your troubles are much more likely to be related to wine and
> the
> wine environment
>
> but another thing to note, is that launcher scripts are not the norm in
> the *nix
> world - if you are running an XDG-compliant desktop such as XFCE, the
> standard
> way to create launchers for GUI applications is XDG .desktop files (look
> under
> /usr/share/applications/ for examples), which automatically makes the
> launcher
> available in the desktop application menus - see if you can find a .desktop
> file which launches a wine application and customize it - you can put your
> own
> under $HOME/.local/share/applications - the "one-liner" would be quite
> similar
> otherwise - that would be the Exec= line in the .desktop file
>
> note that you should not make assumptions about the environment $PATH in
> scripts which may be run by any user, but always use absolute paths (not
> simply
> 'wine64') - that alone could be the problem with your current approach
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Help-bash mailing list
> Help-bash@gnu.org
> https://lists.gnu.org/mailman/listinfo/help-bash
>
>
> ------------------------------
>
> End of Help-bash Digest, Vol 146, Issue 2
> *****************************************
>