[twitter-dev] Re: URL encode problem

2010-12-26 Thread epomqo
Both of the solutions work! Seems the link was broken by the "&" before... Thanks very much for all of your kind help even on these holidays! :-) Best, epomqo On Dec 26, 4:48 pm, Matt Harris wrote: > It looks like you're running curl from the command line. Try wrapping the > entire URL in quot

Re: [twitter-dev] Re: URL encode problem

2010-12-26 Thread Matt Harris
It looks like you're running curl from the command line. Try wrapping the entire URL in quotes - this would make your request: curl "http://search.twitter.com/search.json?geocode=37.781157,-122.398720,15km&lang=en&rpp=100"; > file.txt Alternatively leave out the quotes and escape the &. e.g

Re: [twitter-dev] Re: URL encode problem

2010-12-26 Thread Adam Green
I have never used cURL directed to a file in this way. I always call it from PHP. Doing it that way I have always gotten results with the rpp and page parameter used together with keywords. On Sun, Dec 26, 2010 at 5:57 AM, epomqo wrote: > Thanks Adam. I will carefully look at the results from th

[twitter-dev] Re: URL encode problem

2010-12-26 Thread epomqo
Thanks Adam. I will carefully look at the results from the "lang" parameter. >From the screen display above: [1] Donecurl http://search.twitter.com/search.json?geocode=37.781157,-122.398720,15km [2]- Donelang=en [3]+ Donerpp=100 It

Re: [twitter-dev] Re: URL encode problem

2010-12-26 Thread Adam Green
On Sun, Dec 26, 2010 at 5:11 AM, epomqo wrote: > > And apparently the "lang" parameter sometimes doesn't work: I still > get tweets in other languages. > >From my experience the lang parameter, is not a language detection algorithm. It just pays attention to the language the user has set in thei

[twitter-dev] Re: URL encode problem

2010-12-26 Thread epomqo
Thanks for the reply David, happy holidays too! I tried with your suggestion, however the following cURL command in shell script still cannot export search result to a .txt file: curl http://search.twitter.com/search.json?geocode=37.781157,-122.398720,15km&lang=en&rpp=100&page=1 >> searchrecord.

[twitter-dev] Re: URL encode problem

2010-12-25 Thread David
You don't want to url encode the ampersands in this case since you want to use as part of their reserved function for separating parameters. This URL should work: http://search.twitter.com/search.json?geocode=37.781157,-122.398720,15km&lang=en&rpp=100&page=1 If you wanted to specify an ampersan

[twitter-dev] Re: URL encode problem

2010-12-25 Thread epomqo
Sorry the links seem to be truncated: this works: curl ... search.json?geocode=37.781157%2C-122.398720%2C15km > test.txt this didn't work: curl ... search.json?geocode=37.781157%2C-122.398720%2C15km%26lang=en %26rpp=100%26page=1 > test.txt On Dec 25, 5:08 pm, epomqo wrote: > Dear all, > > Merry