Hi, Micko.
Thanks for the heads-up. I like the look of iguleder's script, I must say. Very neat.....
and simple. As all the best ideas usually are.
peebee will probably be able to incorporate some of that into the Chromium launcher script. Chrome, being a wee bit more proprietary, employs a very different 'wrapper-script' to start things.....but anything's possible.
01micko wrote:I'm not fussed by the error.. chrome/chromium is noisy.. I'm posting from it now (google-chrome 56.0.2924.87 (64-bit)) downloaded with Ruari's gist.
Tell me about it. I've never seen owt quite like the Chromium-based browsers for generating crap in the terminal. For all that, they
still run...
-----------------------------------------------------------------------------------------
I'll have a look at iguleder's script when I get in later on. It might be just as easy to incorporate that into my Chrome builds, and let it run through before it actually starts; d'you suppose he would mind my 'borrowing' it?
Perhaps start the exec-line with that, stick a 'sleep 3 (or 5)' statement in, then let the normal google-chrome exec statement run.
Something like:-
Code: Select all
/usr/bin/puppy-chrome
sleep 5
exec -a "$0" /opt/google/chrome/chrome --user-data-dir=/root/.config/google-chrome --disable-infobars "$@"
What d'you think? Sound feasible? Or am I approaching this from the wrong angle? (Remember, I'm still feeling my way with all this scripting stuff...)
I'll have a look at that download script, too, when I get the time.
Cheers.
Mike.