We are explicitly decoding the first occurrence of a hash in a URL, although I’m not sure why (even though I approved the change).
The history of why we did it is at https://github.com/quicksilver/Quicksilver/pull/1114 which I’m hoping might help either of the other two developers who helped make those changes (Rob, Etienne) remember why it was done! It may well need revisiting, as this looks like a bug On 17 Medi 2014, at 14:42, Tim <[email protected]> wrote: > I set up a new web search for beta.jisho.org. I need quicksilver to send this: > > http://beta.jisho.org/search/他%20%23kanji > > I set up the url like so: > > http://beta.jisho.org/search/***%20%23kanji > > But it ends up sending this: > > http://beta.jisho.org/search/他%20#kanji > > Quicksilver decodes the octothorp entity prior to submitting the request, so > it ends up not working quite the way I want. Just wondering if this is a bug, > or if is it necessary for some reason internal to quicksilver? I've tried a > number of workarounds, but nothing I came up with yet has worked to produce > the desired results. Any ideas? > > Thanks, > > Tim > > -- > You received this message because you are subscribed to the Google Groups > "Quicksilver" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/blacktree-quicksilver. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/d/optout.
