You are not logged in.
Everythings faster and better as well as cleaner for me.. cept i cant get firefox to work.. :-/ is this a common problem ? i install it via pacman.. but i cant launch it.. :-/
I use the pacman version, too, albeit with a different startup script:
cat /usr/bin/mozilla-firefox
#!/bin/bash
# Firefox executable
FIREFOX="/opt/mozilla/bin/firefox"
# Check if Firefox is running. (Ugly hack, remote options doesn't work)
FFNUM=`ps -A | grep -c firefox-bin`;
if [ -z $1 ]; then
# No url: open new window with home page.
URL="";
else
# Load the url given on the command line.
URL=$1;
fi
if [ $FFNUM -eq 0 ]; then
# No running Firefox instance: fire up a new copy of the browser.
$FIREFOX $URL &
else
# Open the url from the command line argument in a new tab in an
# already running Firefox instance.
$FIREFOX -a firefox -remote "openURL($URL,new-tab)" &
# To open a new window instead of a new tab, use:
#$FIREFOX -a firefox -remote "openURL($URL,new-window)" &
fi
Offline
awesome.. that worked like a charm.. why is the pacman installer so fudged up ?? and not fixed ??
sn0n.com - rob douglas
sig v0.0.2
Offline
awesome.. that worked like a charm.. why is the pacman installer so fudged up ?? and not fixed ??
Well, is it? I've used that script for a while, now, because I wanted clicked links to open new tabs rather than a new Firefox window, hence I have no idea ...
If it IS broken, please file a bug report on flyspray.
93,
-Sascha.rb
Offline
awesome.. that worked like a charm.. why is the pacman installer so fudged up ?? and not fixed ??
It never fails to amaze me that people tend to jump immediately to the conclusion that if something doesn't work as expected for them, it's broken and someone else has neglected to fix it.
The truth is, in most cases, the problem is somewhere on the user's local system that is "fudged up" and not the fault of someone else who has "not fixed" it.
A wise man once noted that '97% of all computer errors occur between the chair and the keyboard.'
--Theoden :shock:
"If builders built buildings the way programmers write programs,
the first woodpecker that came along would destroy civilization."
Offline
Guys, because my GNOME is a bit f**ked up with gconf errors keys etc etc, how can I be sure that I will have virgin GNOME 2.10?
rm ~/.gnome2/ ~/.gconf/ -rf
doesn't seem to help that much
I also have gnomemeeting [which gives me gconf errors]
Offline