- RTFM will help you to "Read The... Flippin' Manual" entry for a highlighted language keyword/function by quickly directing your browser to your favourite documentation for that language or syntax. Unique settings for every syntax in Nova and fully customizable to target any (searchable) API-reference library. To get more details, RTFM!
- 23 Installs
RTFM will help you to "Read The... Flippin' Manual" entry for a highlighted language keyword by directing your browser to your favourite resource for that language.
Which website you are taken to is determined by the document's current syntax (at bottom right corner of the editor window) and your preferred resource for that syntax (specified in the preferences). If no text is selected when RTFM is triggered, you will be prompted to enter a search string.
RTFM includes settings for every syntax recognized by Nova, so even if you're working in plain-text you could still do a general web search on any string, or set up a Custom URL to search the API of whatever you might be working on / documenting.
Lastly, if you're (say) working on SQL in a PHP file, you could temporarily switch the document's syntax to SQL so you can target your RTFM queries to the SQL resources instead of PHP.
NOTE: This extension is just a shortcut for performing the searches you might do on these sites or through search engines. If the search results aren't better when you're doing the same search on the site itself, this extension can't improve those results. Not all sites are easily searched.
Here's a 30s Video Demo if you prefer to WTFM.
RTFM can be used either by: - right-clicking on a term and choosing the RTFM command from the pop-up menu, OR - selecting a word and then choosing the menu item Editor → RTFM (or assign a hot-key to it!) OR - Triggering RTFM with no text selected to be prompted for a keyword to search for.
To configure the global preferences, open Extensions → Extension Library... then select RTFM's Preferences tab.
For each syntax, you can specify to which online resource you would like to send your searches. Searches that are done "...via Duck Duck Go redirect" use the "I'm feeling Ducky" option to automatically redirect the search to the first search result. This is usually the page you're looking for, but ymmv.
Custom Language Resources
URLs should start with http or https, and should include the %@ token at the location where the search string should appear. URLs can also include the %$ token where you'd like to specify the document's current syntax (helpful if you'are targetting are website like Mozilla.org where they support many syntaxes).
If the URL you enter works in your browser (except for replacing %@ and %$ tokens) it should work in RTFM.
Precisely how to create a custom search url for a website is outside the scope of this manual so you'll need to RTFM about that somewhere else. :-) But if you want to target a specific website through a search engine like Duck Duck Go, the URL generally looks like the placeholder text:
where %$ is the syntax (if needed) and %@ will be whatever you select in your editor to search for. If you're using Duck Duck Go and want to trigger their "I'm Feeling Ducky" redirect-to-first-result feature, start the query with backslash \ . For Google you must include '&btnI' after the search term.
Why are you using these particular presets?
Tradeoffs. Some websites (php.net) do best when searched directly, some do better when searched through a search engine (HTML5Doctor), and some don't seem to support search at all (Vue).
I've tried to provide a decent set of reference sites without overwhelming the menu with choices for each syntax. (SQL has the most, of course, since SQL isn't just one language.)
The "I'm feeling Ducky" searches through Duck Duck Go are generally great and it's an extremely fast way to get right to the page you need. And sometimes the search engines reveal better content than the site itself.
e.g., HTML5Doctor will show you a simple definition for \<figure> if you search for that term directly on their site, but using Duck Duck Go you get a longer article on why and when you should use \<figure>.
Others (e.g., Perl) seem to do worse using DDG, so while it's an option, it's not the default. And some syntaxes are largely symbolic (e.g., Markdown) and it seemed like if anyone needed resources for these it would be for the content they are writing, not for the syntax of the content.
I am not familiar with every language so the presets chosen may not be ideal. If you find something better, you can create and assign you own custom URLs to any syntax. (There's only 3 because I'm hoping that's enough for most people and I didn't want to clutter up the menus.)
2022-06-23 - Typos. Grrrr.
2022-06-22 Initial release
BSD 3-Clause License
Copyright (c) 2022, Colin Foster All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.