You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a question and proposal as implied by the question:
Why doesn't the site use the Query String to store and refer
queries?
I mean, that you can't refer to search results
on package.elm-lang.org, like this would do:
https://package.elm-lang.org?q=list
So, I propose to change this, because it would
help in remote work, when choosing a library to use
or when trying to incorporate package.elm-lang.org
in your page or search engine, like if you would like to
incorporate it in DuckDuckGo's !Bangs.
The text was updated successfully, but these errors were encountered:
I wish I could search package.elm-lang.org using my launcher, LaunchBar, but doing this would require URL-based query support in the site. I use this for many other package sites, like NPM, RubyGems, and Sublime Text Package Control:
Support for this would let me, from any application on my Mac, type ⌘space, “elm”, space, to bring up packages matching that query without my hands ever leaving the keyboard.
I would be happy to attempt to write a PR with this functionality if at any stage that would be helpful.
It would be better to get this merged at some point, but until then, you can use this feature today by using the unofficial forked frontend provided at https://elm.dmy.fr (or https://dark.elm.dmy.fr). It just loads a different .js and .css file, but the backend is still the official one (so it is always up to date).
This is a question and proposal as implied by the question:
I mean, that you can't refer to search results
on package.elm-lang.org, like this would do:
So, I propose to change this, because it would
help in remote work, when choosing a library to use
or when trying to incorporate package.elm-lang.org
in your page or search engine, like if you would like to
incorporate it in DuckDuckGo's !Bangs.
The text was updated successfully, but these errors were encountered: