MozillaZine

about:config - keyword.URL

Discussion about official Mozilla Firefox builds
BlueFyre

User avatar
 
Posts: 1982
Joined: February 11th, 2004, 4:33 pm

Post Posted March 25th, 2004, 9:35 pm

I have my keyword.URL set to http://www.google.com/search?btnI=I%27m ... e=UTF-8&q= (default)

But when I type "test" in the address bar it takes me to http://www.google.com/search?q=test ... eg the "search" option.. is that a glitch?

[Edit] Also I tested my search engine bar thingy.. it has Google default on it... If I type test in that it takes me to http://www.google.com/search?q=test&sou ... 8&oe=utf-8 kinda weird...
If you notice this notice you may notice that this notice is not worth noticing.

Kitefighter

User avatar
 
Posts: 373
Joined: March 10th, 2004, 11:09 pm

Post Posted March 25th, 2004, 10:32 pm

As for the searchengine bar thingy: take a look at the file <Firefox program folder>\searchplugins\google.src. There you can fit the string to your needs.

The keyword.URL is supposed to work like calling the lucky link, just as you assumed. But it seems to conflict with certain extensions or settings. For me the whole thing worked in the beginning but stopped functioning at all at some point. When I type "test" I just get the message "http://test/ - The requested URL could not be retrieved" although my keyword-settings are unchanged.

storm119

User avatar
 
Posts: 742
Joined: October 2nd, 2003, 7:13 am
Location: *Land Below The Wind*

Post Posted March 25th, 2004, 10:51 pm

WFM..using Mozilla Suite (mmoy 040323) ,FX (mmoy 040321) (JTw 040320) its take me to www.test.com. I'm adding this in my user.js :

/* KEYWORD SEARCH */
user_pref("keyword.URL","http://www.google.com/search?btnI=I%27m+Feeling+Lucky&ie=UTF-8&oe=UTF-8&q=");

Kitefighter

User avatar
 
Posts: 373
Joined: March 10th, 2004, 11:09 pm

Post Posted March 25th, 2004, 11:01 pm

That's exactly what BlueFyre wrote and it's the Firefox default anyway.

BTW: Note that /* ... */ is CSS syntax and only applicable to your userChrome.css or userContent.css. In Javascript you should comment like this:
// KEYWORD SEARCH

storm119

User avatar
 
Posts: 742
Joined: October 2nd, 2003, 7:13 am
Location: *Land Below The Wind*

Post Posted March 25th, 2004, 11:33 pm

Kitefighter wrote:That's exactly what BlueFyre wrote and it's the Firefox default anyway.


......and how its go to google search option http://www.google.com/search?q=test ,then ?.

Kitefighter wrote:BTW: Note that /* ... */ is CSS syntax and only applicable to your userChrome.css or userContent.css. In Javascript you should comment like this:
// KEYWORD SEARCH


I dont have any problem adding/comments with "/*...*/" in my user.js :) you also can comments "// or //* in user.js.....imo.

...anyway thanx for your concern.. :wink:

Kitefighter

User avatar
 
Posts: 373
Joined: March 10th, 2004, 11:09 pm

Post Posted March 26th, 2004, 12:36 am

storm119 wrote:......and how its go to google search option http://www.google.com/search?q=test ,then ?.

No idea. If I knew I wouldn't have to cope with the fact that it doesn't work at all with my own settings :)

bcool

User avatar
 
Posts: 638
Joined: December 27th, 2003, 9:01 am
Location: Ozarks

Post Posted March 26th, 2004, 2:15 am

Kitefighter wrote:
BTW: Note that /* ... */ is CSS syntax and only applicable to your userChrome.css or userContent.css. In Javascript you should comment like this:
// KEYWORD SEARCH





Traditionally and in a purest sense I see that "//" is the correct way to comment out in javascript. I always wondered why I see variations of this syntax - as you mentioned for example in .CSS. But now I suppose it's become interchangeable as I notice /* */ in our very own generated pref.js file. Nevertheless, I'd rather follow propriety. Thanks for setting the record straight. :)
Never let them see you sweat

chaosite

User avatar
 
Posts: 113
Joined: March 19th, 2004, 4:25 am

Post Posted March 26th, 2004, 2:32 am

Aren't both of them both based on C syntax?

So that:

// Means comment until newline

so this isn't commented...

/* And this means comment until you get the other sign.
which is this (And this is still commented) */ So this isn't commented.


Or did they only take parts of the commenting syntax from C?

TheOneKEA

User avatar
 
Posts: 4864
Joined: October 16th, 2003, 5:47 am
Location: Somewhere in London, riding the Underground

Post Posted March 26th, 2004, 2:49 am

I think they allow full C/C++ comment syntax.
Proud user of teh Fox of Fire
Registered Linux User #289618

MonkeeSage

User avatar
 
Posts: 1011
Joined: December 20th, 2002, 8:15 pm

Post Posted March 26th, 2004, 5:19 am

Since JS, unlike HTML, allows comments anywhere (in HTML a comment inside of an element tag breaks the parsing :| ), a particularly useful way of using the block comments (/* */) is inside of function calls and such where additional / different parameters might be needed or for debugging. Like, alert('behold the ' /* + 'power of' */ + 'goodness of cheese!')


Shelumi`El
Jordan

S.D.G

Return to Firefox Builds


Who is online

Users browsing this forum: Sukigu, xanathar and 7 guests