how/why: tce-run suppresses firefox msgs in term

[ttz]

my screen is a convoluted mess right now...

info:

Code: [Select]

>alias | grep fire
alias ff='firefox'
alias ffs='firefox --search'
goal: start ff from term backgrounded without msgs (i.e. no tce-run, minimal key-strokes).

first pass

Code: [Select]

>version
5.4

>ffs youtube &
[1] 8166


>
(process:8166): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

(firefox:8166): Gtk-WARNING **: Locale not supported by C library.
        Using the fallback 'C' locale.

>WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts).
pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
...
...

the msgs keep coming - annoying

-------------------------------
second pass

Code: [Select]

>tce-run firefox &
[1] 8298


>/etc/sysconfig/tcedir/optional/firefox.tcz not found!

(process:8298): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

(firefox:8298): Gtk-WARNING **: Locale not supported by C library.
        Using the fallback 'C' locale.

[1]+  Done                    tce-run firefox


>firefox -h
...
...
with second: no msgs now for, like, half an hour. that is what i want except for having to do more than use my aliases - i hope to just type "ffs somesearchparam &" and go on about using the term.

this is not  limited to 5.4 or youtube or tc.

put it another way:

ffs without tce-run; just alias and no msgs?

[nitram]

//  i hope to just type "ffs somesearchparam &" and go on about using the term.
// this is not  limited to 5.4 or youtube or tc.
Firefox always outputs lots when run from terminal regardless of version or Linux distribution.

Your goal is simply to run FF from terminal without interfering output so you can continue using terminal, correct?

If so just start 'firefox google.com &' or whatever, it will spit out a couple messages, just press Enter and you'll get your prompt back.

Otherwise i misunderstand.

[nitram]

firefox &> /dev/null &
... returns no output to terminal, immediate prompt return

http://unix.stackexchange.com/questions/16456/disable-browser-logging-output-to-console

[coreplayer2]

Why make searching so complicated

Simply set Google as your start page in any browser then select the browser icon on the wbar to open an instance with Google search page already open
Then type in your search criteria
So. This is
one mouse click
The only typing required are as letters in the search word
And then hit enter once

Unless you like making things difficult..?


Sent from my iPhone using Tapatalk

[curaga]

I don't think bb ash supports the &> redirect, so the usual 2> should be used instead.

Also, to avoid having to type the & to background, you could make a script instead.

[ttz]

Unless you like making things difficult..?

It is truly very much the opposite.

Example:

Accept that I always have a term and am generally using it. When it is time to shutdown, I just type: night.

In my .bashrc (on two boxes) I have:

Code: [Select]

alias night='sudo poweroff'
Whether it is a good idea to use sudo in an alias is separate question. For now, when I'm done for the day...

Hey, I'm just exploring things! Thanks for your time and reply,
ttz

[ttz]

@nitram

looks like you've found something. give me some time to work thru it (a couple days, maybe?).

Thank you,
ttz

[ttz]

it seems curaga was right:

Also, to avoid having to type the & to background, you could make a script instead.

Big picture:
noob is trying to build and reading docs; wants to check a link in the docs:

http://keplerproject.github.com/luafilesystem/

now, with a mouse hi-light, i:

Code: [Select]

>fs http://keplerproject.github.com/luafilesystem/
the link is inserted with SHIFT+INSERT

what i did:

Code: [Select]

>which fs
/home/tc/.local/bin/fs
fs:

Code: [Select]

>more $(which fs)
#!/bin/bash
firefox $1 &> /dev/null &
exit 0;
resource:

http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO-3.html

from that:

3.6 Sample: stderr and stdout 2 file

This will place every output of a program to a file. This is suitable sometimes for cron entries, if you want a command to pass in absolute silence.

            rm -f $(find / -name core) &> /dev/null

I can't deny the immediate complexity, but expect it will be worth the trouble in the long run.

best wishes from a noob,
ttz