Do you want to open links in a new tab? Shouldn't that be the job of your browser?

I guess you are talking about greasemonkey and `Adding items to the menubar'[1].
I do not specifically write scripts for greasemonkey but you're welcome to make
the necessary changes and upload a new script.

You would have to fiddle around with the regular expressions that I used in the
script. When making a callback from a menuitem you could change some boolean
value to signalize a change in the settings.

[1] Adding items to the menubar - http://diveintogreasemonkey.org/advanced/gm_reg...

What we could do is transform a XML into XHTML by using XSLT. I will look into it.
For now I fixed the script so no exception is thrown when encountering unsupported documents.

That's cool.

An explanation for that could be the script makes changes to the HTML-source directly instead of using DOM (objects). It's faster but there're more things to take care of.

Cheers

Hmm... it's working for me. Are you sure it's this script and not something else? If you can/like try to run this script alone and turn of the others. Maybe changing the order of executing scripts might help!?

Is that the only site or does that happen all the time?

I guess I would need the HTML-source from that site since it could be that you are served with a slightly different HTML-code then me. You can send it to `kimabrandt at gmx dot de'.

I'm sorry I can't be of a better help at the moment.

Cheers

Do you have a link and/or screenshot?

matrixik I added a variable `AUTO_STOP' which when set to `false' will ask to continue the script (no change). You have to set it to `true' by yourself if you don't want the question to pop up.

To do this:
1) right-click on the Greasemonkey icon in the status-bar
2) click on the `Manage User Scripts' menu-item
3) select `Text to Link' from the list-box
4) click on the `Edit' button
4a) evtl. choose the editor to use
5) search for `const AUTO_STOP' in the script
6) change `const AUTO_STOP = false;' to say `const AUTO_STOP = true;'

I added the symbols `?' and `#' to the `removeUnwanted' function and switched arround the fixing/removing symbols and the checking with `unwantedRegExp'. I also added a `?' to the `unwantedRegExp' so that there is taken care of an only-scheme without trailing `:'.

Keep them coming..

Bruno 'ReX' Barbieri, I agree that a IPv4 address *alone* is too common to be linkyfied, so I added it to the `unwantedRegExp'. If you/someone want it to be included the `unwantedRegExp' variable is the place to look.

Thanks

That message should show up after 2 and then after every 5 seconds to allow to stop executing the script. When I was testing the script I met sites (especially large *.txt) which would run for about 10-30 seconds. This is the best I could come up with. If there are other ways to do the same please let me know.

You can also change the maximum-time (run-time after which to ask the question, search for `var maxTime = 2.0'), multiplikator (increase the run-time, search for `const MULTI = 2.5') and the run-time-boundary (run-time after which the max-time will not be increased further, search for `if (maxTime < 5.0)').

bobielawlintine, that's because: see comment-20307.

But because it's interesting lets try the `linkify' approach..

I added some regular expression-stuff and now it can do what you asked for. There are some issues with the likify-way of doing things. We have to tell the script when we would like to transform an non-url. I choosed the cases when the host is an ip or the host has a valid top-level domain. The script may also become a little slower than before.

Another downside of the linkify-approach is that we now have to find all the `false positives' ;)

Cheers