Skip to content

Commit 19fbf8e

Browse files
committedOct 22, 2023
Add docs comparing engine-mode with webjump
1 parent 4b5ab45 commit 19fbf8e

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed
 

‎README.org

+22
Original file line numberDiff line numberDiff line change
@@ -177,6 +177,28 @@ import them into Emacs.
177177

178178
[[https://github.com/sshaw][@sshaw]] has written a script to [[https://gist.github.com/sshaw/9b635eabde582ebec442][import from Chrome on OS X]]. Thanks for that!
179179

180+
** Comparison with =webjump=
181+
182+
Emacs has a perfectly lovely built-in =webjump= package which allows the user to
183+
define a set of URLs, interpolate search terms into them, and visit them in the
184+
browser.
185+
186+
Why might you use =engine-mode= instead of =webjump=?
187+
188+
- You want to bind specific searches to keybindings. Because =engine-mode= defines
189+
a function for each engine, keybindings in =engine-mode= can be associated
190+
directly with specific searches.
191+
- You'd like to associate browser functions with engines on a case-by-case
192+
basis. For example, if you want to perform some searches in Firefox, and other
193+
searches in =eww=, that's trivial in =engine-mode=.
194+
- You like some of =engine-mode='s minor UI conveniences. If you've got a region
195+
selected, for example, =engine-mode= will use that as the search query, while
196+
=webjump= will ignore it and offer an empty prompt.
197+
198+
If you're not interested in these features, =webjump= is a great choice! Honestly,
199+
the author of =engine-mode= probably wouldn't have bothered writing it if they'd
200+
known =webjump= existed at the time. :sweat_smile:
201+
180202
** Engine examples
181203

182204
#+begin_src emacs-lisp

0 commit comments

Comments
 (0)
Please sign in to comment.