A set of Web Extensions that adds ArchLinux (bug tracker, forum, packages, wiki, AUR, man pages) as a search engine to the Firefox browser (using the chrome_settings_overrides manifest key). Submits the query via GET request for compatibility with Multi-Account Containers.
Available search engines:
| name | shortcut | Install |
|---|---|---|
| ArchLinux Packages Search | alpkgs |
AMO |
| ArchLinux Wiki Search | alwiki |
AMO |
| ArchLinux User Repository (AUR) Search | alaur |
AMO |
| ArchLinux Bugtracker (by FS) Search | albugsfs |
AMO |
| ArchLinux Bugtracker (by text) Search | albugst |
AMO |
| ArchLinux Forum (by author) Search | alforuma |
AMO |
| ArchLinux Forum (by keywords) Search | alforumk |
AMO |
| ArchLinux manual pages | alman |
AMO |
- On ArchLinux:
pikaur -S firefox-extension-arch-search - On any other OS: install the extensions manually via AMO (Addons MOzilla) following the links above
- Clone the repo
- Install tools:
- Install dependencies:
npm i
- Lint (check for manifest syntax errors)
npm run lint -- -s web-extensions/v3/<ext-name>
- Run add-on in isolated Firefox instance using web-ext (open the Browser Toolbox for console logging):
npm run run -- -s web-extensions/v3/<ext-name>
- Package for distribution:
- One extension:
npm run build -- -s web-extensions/v3/<ext-name> - All extensions:
npm run buildAll
- One extension:
- Why is there one extension per search engine?
- After the installation, I still don't see the new search enines. Where are there?
- Disable/Enable the extensions, this will reload them and they'll appear.
- It's possible to add the search engines by clicking the plus button on the search bar, so why an extension?
- It's way quicker to install the extension rather than manually adding the search engines. An extension also allows automation.
- The bug tracker & the forum use advanced search with several parameters so it's not possible to add them manually via the search bar, an extension is mandatory.
