Hi Honza,
In the bottom of each email from this list there is this link:
http://rubyforge.org/mailman/listinfo/mechanize-users
>From there, you will find the option to unsubscribe at the bottom of the
page. Not the most intuitive interface I agree, but it will probably help
you accomplish what you need way faster and easier.
Getting yourself banned (hence not being able to send new messages) but
keeping the subscription alive (therefore still getting these messages)
would be somewhat counter-productive :)
On Sunday, May 5, 2013, Skurt wrote:
> Hey,
> for a couple of years I wasn''t able to manage to unsubscribe from
this
> mailing list.
> So hopefully you could ban me for inapropriate language.
> FUCK
>
> With my best regards
> Honza
>
>
> 2013/5/6 Godfrey Chan <godfreykfc at gmail.com <javascript:_e({},
''cvml'',
> ''godfreykfc at gmail.com'');>>
>
>> I''m looking into GitHub #307 reported by Jason. The gist of
the problem
>> boils down to:
>>
>> agent = Mechanize.new
>>
>> agent.post some_url, [
>> [''key1, ''value1''],
>> [''key2'', ''value2''],
>> ...
>> ]
>>
>> ...sometimes results in unexpected order.
>>
>> I believe the problem is that we are trying to sort the form fields
here<https://github.com/sparklemotion/mechanize/blob/master/lib/mechanize/form.rb#L259>when
building the query string. This works just fine when the form is
>> parsed from the DOM, in which case we always sort them by the order
they
>> are defined in the DOM. However when using Agent#post, there is no DOM
>> nodes to refer to, so we simply give up and sort the fields
randomly<https://github.com/sparklemotion/mechanize/blob/master/lib/mechanize/form/field.rb#L41>
(I
>> am pretty sure this is not a valid implementation of <=>, because
when
>> comparing two non-DOM fields, they will simultaneously be greater than
each
>> other).
>>
>> The simple fix would be to leave out the non-DOM fields before we sort
>> them, and prepend or append them to the sorted (DOM-)fields array in
the
>> order they were added. But the way <=> is implemented right now
feels like
>> a bit of a hack so it would be nice to get that fixed as well (not too
sure
>> how though).
>>
>> Alternatively, because mechanize is primarily a "browser"
implementation
>> rather than a generic http library, we can just not support this and
update
>> the docs.
>>
>> Just want to get some opinions on this before I start working on it.
>>
>> Godfrey
>>
>> _______________________________________________
>> Mechanize-users mailing list
>> Mechanize-users at rubyforge.org <javascript:_e({},
''cvml'',
>> ''Mechanize-users at rubyforge.org'');>
>> http://rubyforge.org/mailman/listinfo/mechanize-users
>>
>
>
>
> --
> S p??n?m p?kn?ho dne
> Jan Kadera
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/mechanize-users/attachments/20130506/cb4f7098/attachment.html>