1 \input texinfo @c -*-texinfo-*-
3 @setfilename elpher.info
4 @settitle Elpher Manual v3.0.0
8 * Elpher: (elpher). A gopher and gemini client for Emacs.
12 This manual documents Elpher, a gopher and gemini client for Emacs.
14 Copyright @copyright{} 2019, 2020, 2021 Tim Vaughan@*
15 Copyright @copyright{} 2021 Daniel Semyonov@*
16 Copyright @copyright{} 2021 Alex Schroeder
19 The source and documentation of Elpher is free software. You can
20 redistribute it and/or modify it under the terms of the GNU General
21 Public License as published by the Free Software Foundation; either
22 version 3, or (at your option) any later version.
24 Elpher is distributed in the hope that it will be useful, but WITHOUT
25 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
26 FITNElpher FOR A PARTICULAR PURPOSE. See the GNU General Public License in
27 the file COPYING in the same directory as this file for more details.
32 @title Elpher Gopher and Gemini Client Manual
36 @vskip 0pt plus 1filll
43 @node Top, Introduction, (dir), (dir)
49 * Introduction:: Elpher Overview: what's this all about?
50 * Installation:: Installing Elpher
51 * Quick Start:: Get up and running quickly
52 * Navigation:: Fundamentals of Elpher navigation
53 * Bookmarks:: How to record and visit bookmarks
54 * Gopher character encodings:: How Elpher selects encodings for gopher pages
55 * Encrypted gopher connections:: How and when TLS is enabled for gopher
56 * Gemini support:: Support for the Gemini protocol
57 * Finger support:: Support for the Finger protocol
58 * Customization:: How to customize various aspects of Elpher
60 * News:: Changes introduced by major releases
61 * Acknowledgements:: Contributors to Elpher
64 --- The Detailed Node Listing ---
68 * Within-page navigation:: Moving about within a page
69 * Between-page navigation:: Commands for moving between pages
70 * History and Caching:: Explanation of how Elpher represents history
77 @macro keycmd{key,cmd}
78 @item \key\ (@code{\cmd\})
82 @node Introduction, Installation, Top, Top
85 Elpher aims to be a capable and practical gopher and gemini client for
86 Emacs. Its focus is on easy keyboard-driven navigation based on
87 sensible default bindings (with out-of-the-box support for Evil). It is
88 intended to be robust and behave in non-surprising ways at all times.
89 Additionally, Elpher provides the following bells and whistles:
93 followable web and gopher links in plain text,
96 an easily navigable history, sporting caching of visited pages (both
97 content and cursor position),
100 auto-completing menu item navigation,
103 direct visualization of image files where supported (no writing to
107 basic support for the new ``heavier than gopher, lighter than the web'' Gemini protocol,
110 support for the Finger protocol.
114 Elpher is still under active development. Although we try very hard to
115 ensure that releases are bug-free, this cannot be guaranteed. However,
116 this also means that any usability features that you feel are missing
117 can likely by incorporated quickly, so please get in touch if you
120 @node Installation, Quick Start, Introduction, Top
121 @chapter Installation
123 Elpher is available from the MELPA package repository. If you have
124 never installed packages from this repository before, you'll need
125 to follow the instructions at @url{https://melpa.org/#/getting-started}.
127 @noindent To install Elpher, enter the following:
130 @kbd{M-x package-install @key{RET} elpher @key{RET}}
133 @noindent To uninstall, use
136 @kbd{M-x package-delete @key{RET} elpher @key{RET}}.
139 It is also possible to install Elpher directly by downloading the file
140 @file{elpher.el} from @url{gopher://thelambdalab.xyz/1/projects/elpher}
141 (you'll need to download the ``source archive'' and extract it), adding
142 it to a directory in your @code{load-path}, and then adding
148 @noindent to your Emacs initialization file.
150 @node Quick Start, Navigation, Installation, Top
153 Before diving into the minutiae of the different commands available,
154 we will quickly describe how to get up and running with Elpher.
156 Once installed, you can launch Elpher using
159 @kbd{M-x elpher @key{RET}}
162 @noindent This will switch to the *Elpher* buffer and display a start
163 page, with information on each of the default keyboard bindings.
165 From here you can move point between links (which may be menu items or
166 inline URLs in text files) by using @key{TAB} and @kbd{S-@key{TAB}},
167 as in Info. You can also jump directly to a menu item using @key{m}, or
168 use the standard Emacs or Evil motion and search commands to find your
169 way around. To open a link, press @key{RET}. (Where a mouse is
170 available, Clicking on a link with the mouse cursor has the same
173 To return to the page you just followed the link from, press @key{u}.
175 Elpher caches (for the duration of an Emacs session) both page contents
176 and the position of point on each of the pages (gopher menus, gemini
177 pages, query results, or text pages) you visit, restoring these when you
178 next visit the same page. Thus, pressing @key{u} displays the previous
179 page in exactly the same state as when you left, meaning that you can
180 quickly and visually explore the different documents in a menu without
181 having to wait for anything to reload.
183 Of course, sometimes you'll @emph{want} to reload the current page
184 rather than stick with the cached version. To do this use @key{R}.
185 (This is particularly useful for search query results, where this
186 allows you to perform a different search.)
188 That's more-or-less it. Elpher supports a number of other features,
189 such a support for different coding schemes and TLS encryption, and a
190 variety of customization options, all of which are explained in the
191 rest of this document. However the emphasis is on keeping the basic
192 navigation experience as intuitive and responsive as possible.
194 Note that you can launch multiple Elpher sessions in parallel by using
198 @kbd{C-u M-x elpher @key{RET}}
201 @node Navigation, Bookmarks, Quick Start, Top
203 Throughout this manual, we use the word ``page'' to refer to any
204 visualization of a response from a gopher or gemini server, be it a
205 menu/directory, query result, text file or image.
207 Elpher's navigation interface is inspired by the Emacs Info mode.
208 Movement within a page is essentially the same as moving
209 around any other text file in Emacs, but with special keys
210 for quickly jumping between menu items and URLs in text files.
211 Movement between pages is facilitated by a simple linear history
212 coupled with caching of pages and cursor position.
215 * Within-page navigation:: Moving about within a page
216 * Between-page navigation:: Commands for moving between pages
217 * History and Caching:: Explanation of how Elpher represents history
221 @node Within-page navigation, Between-page navigation, Navigation, Navigation
222 @section Within-page navigation
224 To move about within a page, you should be able use the same keys you usually
225 use to browse files in Emacs. This is even true when Evil mode is
226 enabled. Paragraph hopping, searching etc should work as usual.
228 In addition, the following commands are provided for quickly moving between
229 links and menu items.
232 @keycmd{@key{TAB}, elpher-next-link}
233 Move to the next link or menu item in the file.
235 @item @kbd{Shift-@key{TAB}} or @key{BACKTAB} (@code{elpher-prev-link})
236 @findex elpher-prev-link
237 Move to the previous link or menu item in the file.
239 @keycmd{@key{m}, elpher-jump}
240 Jump directly to a link within a file by specifying its display string
241 or link text. (Unlike the previous two commands, this immediately opens
246 The following commands can be used to retrieve information about the
247 current page, or the address of the link at point:
250 @keycmd{@key{i}, elpher-info-link}
251 Display host, port and selector information for the link at point.
253 @keycmd{@key{I}, elpher-info-current}
254 Display host, port and selector information for the current page.
256 @keycmd{@key{c}, elpher-copy-link-url}
257 Add URL representing address of link at point to the kill-ring and the
258 system clipboard (if available).
260 @keycmd{@key{C}, elpher-copy-current-url}
261 Add URL representing address of the current page to the kill-ring and
262 the system clipboard (if available).
264 @keycmd{@key{d}, elpher-download}
265 Download link at point and save the result as a file. The minibuffer
266 will prompt for the name of the file to write, with the default name being
267 the display string (if available) associated with the link.
269 @keycmd{@key{D}, elpher-download-current}
270 This is similar to @code{elpher-download}, but instead applies to the
271 current page rather than a link.
273 @keycmd{@key{.}, elpher-view-raw}
274 This displays the raw server response for the current page. While not
275 useful for general browsing, it is useful for debugging incorrect rendering
276 or out-of-spec server responses.
279 @node Between-page navigation, History and Caching, Within-page navigation, Navigation
280 @section Between-page navigation
282 Moving to a different page can be accomplished in several ways,
283 described by the following command:
286 @keycmd{@key{RET}\, @kbd{mouse-1}, elpher-follow-link}
287 Follow the menu item or link at point (or selected with the mouse).
289 Exactly what is meant by ``follow'' depends on the kind of item selected:
293 For text or menu type items or links, the current page text is replaced
294 by the text of this item. Unless the customization variable
295 @code{elpher-use-header} (@pxref{Customization}) is
296 @code{nil}, the display string of the link is displayed in the buffer header.
297 Links to images behave similarly on Emacs systems supporting the display of
298 bitmap graphics, however their content is not cached in memory by default.
301 When followed, links to search/query items (type 7) prompt for input in
302 the minibuffer then display the results in the same way as for text and menu
306 Following links to binary files (and image files on unsupported systems)
307 causes Elpher to prompt for a filename in which to save the content.
310 Following links of type `h' with a selector having the `URL:' prefix, or
311 unsuported URLs in text files, will result in Elpher using an external
312 programme to open the URL. This will be either the default system browser
313 or, if the @code{elpher-open-urls-with-eww} customization variable is non-nil,
314 Emacs' own EWW browser. (See @pxref{Customization}.)
318 Once a text, menu or query response page has been displayed, its contents are
319 cached for the duration of the Emacs session.
321 @keycmd{@key{g}, elpher-go}
322 Open a particular page by specifying either its full URL or just
323 entering a gopher host name. (The protocol defaults to gopher, so gemini
324 links must include the @code{gemini://} prefix.
326 If a unsupported protocol is used in the URL the result will be the same
327 as following a URL link of the same type from a link in a page.
329 @keycmd{@key{o}, elpher-go-current}
330 Prompts for a URL similar to @code{elpher-go}, but initialized to the URL
331 of the current page. This allows you to easily try other selectors for the
334 Remember however, that the Gopher RFC 1436 provides @emph{no} guarantees about the
335 structure of selectors.
337 @keycmd{@key{O}, elpher-root-dir}
338 Open the root page (empty selector) on the current host.
340 @keycmd{@key{u}\, @key{-}\, @key{^}\, @kbd{mouse-3}, elpher-back}
341 Return to the previous page, where ``previous'' means the page where the
342 page which was displayed immediately before the current page.
346 @node History and Caching, , Between-page navigation, Navigation
347 @section History and Caching
349 The history and caching strategy in Elpher is extremely simple, but
350 may be confusing without a good mental model of how it works. That
351 is what this section attempts to provide.
353 Essentially, @strong{every} time you navigate to a new page, either
354 by clicking or pressing @key{RET} on a link, using @key{g} to jump
355 to a new page by its address, or using @key{O} to open the root selector,
356 the following two things occur:
360 the cursor position and content for the original page are recorded in an
364 the original page is set as the ``parent'' of the new page.
367 The only way to return to pages in this history is by using @key{u},
368 which returns to the previous of the current page. @footnote{The
369 addition of the new page to the history happens even if the new page is
370 one that has been seen before. This is mostly the desired behaviour.
371 However, opening an explicit ``back'' link provided by a gopher menu or
372 gemini page will also add a new entry to the history. Unless you
373 haven't yet visited that menu, it's therefore better to use @key{u} to
374 go back in this case.}
376 One aspect that may seem peculiar is that Elpher lacks a corresponding ``next'' or
377 ``forward'' command. However, since Elpher caches the position of point,
378 this will be automatically positioned on the link that was most recently followed
379 from a given page. This means that, at least for links followed from menus
380 and text files, the inverse of @key{u} is actually just @key{RET}.
382 Elpher actually maintains two histories, and there are two different
383 commands to access them:
386 @keycmd{@key{s}, elpher-show-history}
387 This shows the history of the current buffer. This shows all the links
388 you would visit if you were to use @key{u} again and again.
390 @keycmd{@key{S}, elpher-show-visited-pages}
391 This shows the entire Elpher browsing history. It includes all the
392 pages you visited in your current Emacs session.
396 @node Bookmarks, Gopher character encodings, Navigation, Top
399 Elpher makes use of standard Emacs bookmarks. @xref{Bookmarks, , ,
400 emacs, The Emacs Editor}. The following commands are perhaps the most
404 @keycmd{@key{a}, elpher-bookmark-link}
405 Add a bookmark for the link at point. The minibuffer will prompt for
406 a name for the bookmark, which defaults to the display string.
408 @keycmd{@key{A}, elpher-bookmark-current}
409 Add a bookmark for the current page. The minibuffer will prompt for
410 a name for the bookmark, defaulting to the display string associated
411 with the link that was followed to reach the current page.
413 @keycmd{@key{B}, elpher-open-bookmarks}
414 Open a page displaying all current bookmarks. This is where you can
415 delete and search bookmarks, for example.
418 On opening the bookmarks page, elpher will offer to import any legacy
419 (2.x) bookmarks files into the new system. Once the import is complete,
420 the original bookmarks file will have ``-legacy'' appended to it, so
421 so that elpher knows not to import it again.
423 If you have any other legacy bookmark files (besides the one in the
424 original location, or specified in the @code{elpher-bookmarks-file}
425 customization variable, which should be automatically detected), you can
426 can import these using
429 @kbd{M-x elpher-bookmark-import @key{RET}}
432 Once this is done, you may delete these legacy bookmarks files.
434 @node Gopher character encodings, Encrypted gopher connections, Bookmarks, Top
435 @chapter Gopher character encodings
437 Responses Elpher retrieves from servers are initially read as pure
438 binary data. When the data is intended to be interpreted as textual (as
439 determined by the type parameter of the gopher menu item or the gopher
440 URL), this data needs to be @emph{decoded} into a sequence of
441 characters. To do this properly requires knowledge of the encoding
442 system used by whoever authored the document.
444 Unfortunately gopher lacks a systematic way of acquiring this necessary
445 information. Thus, the details of the coding system must be either
446 inferred from the binary data, or must be specified by the user.
448 By default, Elpher applies Emacs' built-in character encoding detection
449 system to the full (undecoded) response data and uses this to attempt to
450 convert it into a character string.
451 (See @pxref{Recognize coding, Recognizing coding systems, ,emacs}.) While
452 this approach can be okay, it is important to realize that its inference
453 algorithm is extremely primitive and depends heavily on assumptions based
454 on the language settings of your emacs system.
456 The alternative is to explicitly set the coding system used for decoding
457 using the following command:
460 @keycmd{@key{!},elpher-set-coding-system}
461 Causes a elpher to prompt for a coding system to use for decoding
462 future gopher text. The @key{TAB} key can be used at this prompt to display a
463 list of alternatives (which is extensive) and to auto-complete. An empty
464 response will cause Elpher to return to its default auto-detection
468 Note that changing the coding system only affects newly loaded text.
469 Thus, if text has already been decoded using an incorrect system, you
470 will need to select the correct coding and then reload the text using
474 @node Encrypted gopher connections, Gemini support, Gopher character encodings, Top
475 @chapter Encrypted gopher connections
477 While RFC 1436 does not broach the topic of encryption at all, several
478 modern gopher servers can serve content over encrypted connections,
479 and a common choice for this is TLS.
481 Elpher can retrieve selectors using Emacs' built-in TLS support which
482 uses the GnuTLS library. (It is possible to build emacs without
483 GnuTLS, in which case encryption is not supported.)
485 To retrieve documents using TLS, Elpher's TLS mode must be enabled.
486 This can be directly toggled using @key{T}, but note that just as with
487 the character encoding, changing this mode only affects subsequent
490 Alternatively, TLS mode is @emph{automatically} enabled whenever
491 gopher URLs starting with @code{gophers://} are followed.
493 The mode is sticky, so it remains active until switched off.
494 It can also be automatically switched off when a TLS connection fails.
495 In this case Elpher will prompt for your confirmation to ensure that
496 you can't accidentally make a non-TLS connection.
498 @node Gemini support, Finger support, Encrypted gopher connections, Top
499 @chapter Gemini support
501 @uref{gopher://gemini.circumlunar.space, Gemini}
502 is a new protocol being developed by several members of
503 gopherspace. It aims to solve some of the long-standing technical
504 issues associated with gopher as a protocol, while keeping the major benefits.
505 For instance, it _requires_ encrypted connections, it does away with
506 the selector type, and allows servers to explicitly specify the
507 character coding scheme used for text documents.
509 The latest versions of Elpher aim to provide seamless transitions between
510 gemini and gopher documents. Basically you should be able to open,
511 bookmark, download and otherwise interact with gemini pages in exactly
512 the same way as you do with other non-gemini pages. The only major
513 difference from your perspective as a user is that you should no longer
514 have to worry about manually toggling TLS on or off (for gemini it's
515 always on), and you should never have to manually set a character coding
518 The gemini protocol specification recommends a Trust on First Use (TOFU)
519 behaviour when validating gemini server TLS certificates. This is
520 because many gemini servers rely on self-signed certificates rather
521 than certificates signed by a CA. Sadly however, this TOFU behaviour is
522 far from straight-forward to configure using Emacs' existing Network
523 Security Manager. For this reason, elpher defaults to performing no
524 certificate verification by default. This behaviour can be easily
525 customized by setting the @code{elpher-gemini-TLS-cert-checks}
526 customization variable to non-nil.
528 The gemini specification concerns both the protocol and a simple text
529 document format (mimetype text/gemini) which is like a mixture between
530 gophermap files and markdown-formatted files but simpler than both.
531 Elpher renders gemini responses which are provided in this format in
532 line with the rules in the spec. This includes wrapping long lines at
533 word boundaries. The specific column at which this text is wrapped is
534 defined by the customization variable
535 @code{elpher-gemini-max-fill-width}, which is set to 80 columns by
536 default. (This is slightly wider than Emacs' default fill width of 70
537 columns due to the fact that there are a significant amount of older
538 gemini content which, against the advice of the current spec, hard wraps
539 at <80 columns. The larger default allows this to still look okay,
540 while still keeping content without hard wraps looking pleasant.)
542 The text/gemini format also possesses a section header syntax similar to
543 markdown. Elpher allows different header levels to be drawn with
544 different, customizable, faces. By default, on graphically-capable
545 emacs systems, these faces are given different heights to distinguish
546 among levels. On terminal systems, the level is indicated by the
547 number of preceding # symbols.
549 I should emphasize however that, while it is definitely functional,
550 Elpher's gemini support is still experimental, and various aspects will
551 change as the protocol develops further.
553 @section Client Certificates for Gemini
555 Gemini makes explicit use of the client certificate mechanism that TLS
556 provides for allowing clients to authenticate themselves with servers.
557 The Gemini specification suggests two distinct classes of client
558 certificates: short-lived certificates used to identify you for a single
559 session, and more permanent certificates used to identify you over a
562 When Elpher receives a request for a client certificate from a server,
563 it will present you with the option to create and use a single-use
564 ``throwaway'' certificate, or to use a ``persistent''
565 certificate (optionally creating it or installing pre-existing key and
568 Certificate creation in Elpher requires an installation of OpenSSL, and
569 ---in particular---that Elpher be able to run the @command{openssl} command-line
570 utility. By default, Elpher assumes that the @command{openssl} is on the
571 system path, but the precise location can be set by customizing the
572 @code{elpher-openssl-command} variable.
574 Each generated certificate results in the creation of a .key file and
575 a .crt file. In the case of a throwaway certificate, these files are
576 stored in the temporary directory indicated by the Emacs variable
577 @code{temporary-file-directory} and are deleted when ``forgotten''
578 (as described below).
580 In the case of persistent certificates, these files are stored in the
581 folder defined by the Elpher variable
582 @code{elpher-certificate-directory}, and are never deleted by Elpher.
583 (Of course you can delete them yourself whenever you like.)
584 The base name of the files (i.e. sans extension) is what Elpher uses
585 to identify the certificate.
587 Using throwaway certificates is as simple as pressing the @key{t}
588 key at the prompt which appears following a certificate request from
589 a server. There is nothing more to do.
591 Using a persistent certificate requires instead selecting @key{p} from the same
592 menu. This will result in Elpher asking you for the name identifying
593 the certificate. This entry autocompletes to the list of known certificate
594 names, so you can use @key{TAB} to display the list.
596 In the case that you choose a name that does not belong to the list of
597 known certificates, Elpher will offer to create one for you or to
598 ``install'' one from existing key and certificate files.
599 Pressing the @key{n} key will cause Elpher to begin the process of
600 creating a new persistent certificate, using some additional
601 details for which you will be prompted.
602 Alternatively, pressing the @key{i} key will cause Elpher to ask for the
603 locations of edisting key and certificate files to add to
604 @code{elpher-certificate-directory} under the chosen name.
606 Once a certificate is selected, it will be used for all subsequent TLS
607 transactions to the host for which the certificate was created.
608 It is immediately ``forgotten'' when a TLS connection to another host
609 is attempted, or the following command is issued:
612 @keycmd{@key{F},elpher-forget-certificate}
613 Causes Elpher to immediately forget any currently-loaded client certificate.
616 In either case, ``forgetting'' means that the details of the key and
617 certificate file pair are erased from memory. Furthermore, in the case
618 of throw-away certificates, the corresponding files are deleted.
621 @node Finger support, Customization, Gemini support, Top
622 @chapter Finger support
624 Incidentally, Elpher has native support for querying finger servers.
625 Of course, one could argue that this functionality is more easily
626 provided by one's local telnet client. However finger URLs do appear
627 on occasion in gopherspace, and it's nice to be able to open them
630 Elpher interprets @code{finger://} URLs as follows:
635 The host is determined by the host name portion of the URL.
638 In the case that the @emph{file name} portion of the URL is non-empty (besides
639 the leading slash), this is interpreted as the user to finger.
642 Otherwise, the @emph{user} portion of the URL is interpreted as the user to finger.
645 If no user is provided, the root directory of the finger server is requested.
649 Thus @code{finger://user@@hostname} and @code{finger://hostname/user} are both equivalent.
651 (The precedence of the /user notation over the user@ notation reflects a
652 preference of the community.)
654 @node Customization, Command Index, Finger support, Top
655 @chapter Customization
657 Various parts of Elpher can be customized via the
658 variables belonging to the elpher customization group, accessible
662 @kbd{M-x customize-group elpher @key{RET}}
665 @noindent This group contains a number of faces that can be modified to change
666 the appearance of Elpher, including one face per menu item type.
668 The group also contains variables for customizing the behaviour of
669 Elpher. This includes how to open arbitrary (non-gopher) URLs, whether
670 to display buffer headers, how to deal with ANSI escape sequences in
671 text, the timeout to impose on network connections, and whether to
672 prompt for confirmation when switching away from TLS.
674 See the customization group itself for details.
676 @node Command Index, News, Customization, Top
677 @unnumbered Command Index
681 @node News, Acknowledgements, Command Index, Top
684 This chapter documents the major changes introduced by Elpher releases.
688 @subsection Bookmarks system
690 Bookmarks are now handled by Emacs' own bookmark management system,
691 instead of Elpher's own system.
692 (For details, @xref{Bookmarks, , , emacs, The Emacs Editor}.)
693 This means two things. Firstly,
694 the bookmarks file (elpher-bookmarks by default) and format used by
695 previous versions are now deprecated. If these are detected, Elpher
696 will offer to import your old bookmarks when you first accessing the
697 bookmark list with the new version. A suffix will be added to your
698 old bookmarks file so that Elpher knows that the import is complete.
700 Secondly, the old Elpher bookmark menu has been removed in the new
701 version. Instead, @kbd{B} brings up the menu provided by the Emacs
702 function @code{bookmark-bmenu-list}. This has different key and mouse
703 bindings to Elpher's old menu, but is much more functional. Bookmarks
704 can be renamed, deleted in groups, and much more. (Use @kbd{C-h m} with
705 the menu open to see the complete list.)
709 Browsing history can now be accessed via new bindings to @kbd{s} and @kbd{S}.
710 The former shows the current history ``stack'' (pages accessible with
711 the @kbd{u} key), while the latter shows a list of all pages which have
712 been visited in the current session.
714 @subsection Socks connections
716 Elpher can now use socks connections to browse via TOR.
718 @subsection browse-url, Org and mu4e integration
720 These integrations provide support for elpher-handling of gemini, gopher
721 and finger URLs using @code{browse-url}, in Org documents, and the mu4e
724 @subsection imenu integration
726 Gemini document headers are now navigable via imenu.
727 For details, @xref{Imenu, , , emacs, The Emacs Editor}.
729 @node Acknowledgements, , News, Top
730 @chapter Acknowledgements
732 Elpher was originally written by Tim Vaughan. Recent maintenance has
733 been done by and with the help of Alex Schroeder. In addition, the
734 following people (in alphabetical order) have generously provided
735 assistance and/or patches:
739 @item Christopher Brannon
742 @item Étienne Deparis
744 @item Simon Nicolussi
750 @item Michel Alexandre Salim
752 @item Daniel Semyonov
754 @item Bradley Thornton