9ahmed
/
boo-bee-macs
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

added stuff

This commit is contained in:
9ahmed 2021-04-16 06:22:13 +05:00
parent 5bf7591cd3
commit dc714f4f46
8 changed files with 2876 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
elpa/elpher-20200919.1025/dir Normal file
View File

@ -0,0 +1,18 @@
This is the file .../info/dir, which contains the
topmost node of the Info hierarchy, called (dir)Top.
The first time you invoke Info you start off looking at this node.

File: dir, Node: Top This is the top of the INFO tree
This (the Directory node) gives a menu of major topics.
Typing "q" exits, "H" lists all Info commands, "d" returns here,
"h" gives a primer for first-timers,
"mEmacs<Return>" visits the Emacs manual, etc.
In Emacs, you can click mouse button 2 on a menu item or cross reference
to select it.
* Menu:
Emacs
* Elpher: (elpher). A gopher and gemini client for Emacs.

29
elpa/elpher-20200919.1025/elpher-autoloads.el Normal file
View File

@ -0,0 +1,29 @@
;;; elpher-autoloads.el --- automatically extracted autoloads -*- lexical-binding: t -*-
;;
;;; Code:
(add-to-list 'load-path (directory-file-name
(or (file-name-directory #$) (car load-path))))
;;;### (autoloads nil "elpher" "elpher.el" (0 0 0 0))
;;; Generated autoloads from elpher.el
(autoload 'elpher "elpher" "\
Start elpher with default landing page." t nil)
(register-definition-prefixes "elpher" '("elpher-"))
;;;***
;;;### (autoloads nil nil ("elpher-pkg.el") (0 0 0 0))
;;;***
;; Local Variables:
;; version-control: never
;; no-byte-compile: t
;; no-update-autoloads: t
;; coding: utf-8
;; End:
;;; elpher-autoloads.el ends here

12
elpa/elpher-20200919.1025/elpher-pkg.el Normal file
View File

@ -0,0 +1,12 @@
(define-package "elpher" "20200919.1025" "A friendly gopher and gemini client"
'((emacs "26.2"))
:commit "3561c2815bc6bc896fc7a6da8f094edca48c55b8" :authors
'(("Tim Vaughan" . "plugd@thelambdalab.xyz"))
:maintainer
'("Tim Vaughan" . "plugd@thelambdalab.xyz")
:keywords
'("comm" "gopher")
:url "http://thelambdalab.xyz/elpher")
;; Local Variables:
;; no-byte-compile: t
;; End:

2020
elpa/elpher-20200919.1025/elpher.el Normal file
View File

File diff suppressed because it is too large Load Diff

BIN
elpa/elpher-20200919.1025/elpher.elc Normal file
View File

Binary file not shown.

711
elpa/elpher-20200919.1025/elpher.info Normal file
View File

@ -0,0 +1,711 @@
This is elpher.info, produced by makeinfo version 6.7 from elpher.texi.
This manual documents Elpher, a gopher and gemini client for Emacs.
Copyright (C) 2019, 2020 Tim Vaughan
The source and documentation of Elpher is free software. You can
redistribute it and/or modify it under the terms of the GNU General
Public License as published by the Free Software Foundation; either
version 3, or (at your option) any later version.
Elpher is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNElpher FOR A PARTICULAR PURPOSE. See the GNU
General Public License in the file COPYING in the same directory as
this file for more details.
INFO-DIR-SECTION Emacs
START-INFO-DIR-ENTRY
* Elpher: (elpher). A gopher and gemini client for Emacs.
END-INFO-DIR-ENTRY

File: elpher.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
Elpher
******
This manual documents Elpher, a gopher and gemini client for Emacs.
Copyright (C) 2019, 2020 Tim Vaughan
The source and documentation of Elpher is free software. You can
redistribute it and/or modify it under the terms of the GNU General
Public License as published by the Free Software Foundation; either
version 3, or (at your option) any later version.
Elpher is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNElpher FOR A PARTICULAR PURPOSE. See the GNU
General Public License in the file COPYING in the same directory as
this file for more details.
* Menu:
* Introduction:: Elpher Overview: what's this all about?
* Installation:: Installing Elpher
* Quick Start:: Get up and running quickly
* Navigation:: Fundamentals of Elpher navigation
* Bookmarks:: How to record and visit bookmarks
* Gopher character encodings:: How Elpher selects encodings for gopher pages
* Encrypted gopher connections:: How and when TLS is enabled for gopher
* Gemini support:: Support for the Gemini protocol
* Finger support:: Support for the Finger protocol
* Customization:: How to customize various aspects of Elpher
* Command Index::
-- The Detailed Node Listing --
Navigation
* Within-page navigation:: Moving about within a page
* Between-page navigation:: Commands for moving between pages
* History and Caching:: Explanation of how Elpher represents history

File: elpher.info, Node: Introduction, Next: Installation, Prev: Top, Up: Top
1 Introduction
**************
Elpher aims to be a capable and practical gopher and gemini client for
Emacs. Its focus is on easy keyboard-driven navigation based on
sensible default bindings (with out-of-the-box support for Evil). It is
intended to be robust and behave in non-surprising ways at all times.
Additionally, Elpher provides the following bells and whistles:
* followable web and gopher links in plain text,
* an easily navigable history, sporting caching of visited pages
(both content and cursor position),
* auto-completing menu item navigation,
* direct visualization of image files where supported (no writing to
disk),
* a bookmark management system,
* basic support for the new "heavier than gopher, lighter than the
web" Gemini protocol,
* support for the Finger protocol.
Elpher is still under active development. Although we try very hard
to ensure that releases are bug-free, this cannot be guaranteed.
However, this also means that any usability features that you feel are
missing can likely by incorporated quickly, so please get in touch if
you have some ideas.

File: elpher.info, Node: Installation, Next: Quick Start, Prev: Introduction, Up: Top
2 Installation
**************
Elpher is available from the MELPA package repository. If you have
never installed packages from this repository before, you'll need to
follow the instructions at <https://melpa.org/#/getting-started>.
To install Elpher, enter the following:
M-x package-install <RET> elpher <RET>
To uninstall, use
M-x package-delete <RET> elpher <RET>.
While not recommended, it is also possible to install Elpher directly
by downloading the file 'elpher.el' from
<gopher://thelambdalab.xyz/1/projects/elpher/>, adding it to a directory
in your 'load-path', and then adding
(require 'elpher)
to your Emacs initialization file.

File: elpher.info, Node: Quick Start, Next: Navigation, Prev: Installation, Up: Top
3 Quick Start
*************
Before diving into the minutiae of the different commands available, we
will quickly describe how to get up and running with Elpher.
Once installed, you can launch Elpher using
M-x elpher <RET>
This will switch to the *Elpher* buffer and display a start page, with
information on each of the default keyboard bindings.
From here you can move point between links (which may be menu items
or inline URLs in text files) by using <TAB> and 'S-<TAB>', as in Info.
You can also jump directly to a menu item using <m>, or use the standard
Emacs or Evil motion and search commands to find your way around. To
open a link, press <RET>. (Where a mouse is available, Clicking on a
link with the mouse cursor has the same effect.)
To return to the page you just followed the link from, press <u>.
Elpher caches (for the duration of an Emacs session) both page
contents and the position of point on each of the pages (gopher menus,
gemini pages, query results, or text pages) you visit, restoring these
when you next visit the same page. Thus, pressing <u> displays the
previous page in exactly the same state as when you left, meaning that
you can quickly and visually explore the different documents in a menu
without having to wait for anything to reload.
Of course, sometimes you'll _want_ to reload the current page rather
than stick with the cached version. To do this use <R>. (This is
particularly useful for search query results, where this allows you to
perform a different search.)
That's more-or-less it. Elpher supports a number of other features,
such as bookmarking, support for different coding schemes and TLS
encryption, and a variety of customization options, all of which are
explained in the rest of this document. However the emphasis is on
keeping the basic navigation experience as intuitive and responsive as
possible.

File: elpher.info, Node: Navigation, Next: Bookmarks, Prev: Quick Start, Up: Top
4 Navigation
************
Throughout this manual, we use the word "page" to refer to any
visualization of a response from a gopher or gemini server, be it a
menu/directory, query result, text file or image. We use
Elpher's navigation interface is inspired by the Emacs Info mode.
Movement within a page is essentially the same as moving around any
other text file in Emacs, but with special keys for quickly jumping
between menu items and URLs in text files. Movement between pages is
facilitated by a simple linear history coupled with caching of pages and
cursor position.
* Menu:
* Within-page navigation:: Moving about within a page
* Between-page navigation:: Commands for moving between pages
* History and Caching:: Explanation of how Elpher represents history

File: elpher.info, Node: Within-page navigation, Next: Between-page navigation, Prev: Navigation, Up: Navigation
4.1 Within-page navigation
==========================
To move about within a page, you should be able use the same keys you
usually use to browse files in Emacs. This is even true when Evil mode
is enabled. Paragraph hopping, searching etc should work as usual.
In addition, the following commands are provided for quickly moving
between links and menu items.
<TAB> ('elpher-next-link')
Move to the next link or menu item in the file.
'Shift-<TAB>'/<backtab> ('elpher-prev-link')
Move to the previous link or menu item in the file.
<m> ('elpher-jump')
Jump directly to a link within a file by specifying its display
string or link text. (Unlike the previous two commands, this
immediately opens the selected link.
The following commands can be used to retrieve information about the
current page, or the address of the link at point:
<i> ('elpher-info-link')
Display host, port and selector information for the link at point.
<I> ('elpher-info-current')
Display host, port and selector information for the current page.
<c> ('elpher-copy-link-url')
Add URL representing address of link at point to the kill-ring and
the system clipboard (if available).
<C> ('elpher-copy-current-url')
Add URL representing address of the current page to the kill-ring
and the system clipboard (if available).
<d> ('elpher-download')
Download link at point and save the result as a file. The
minibuffer will prompt for the name of the file to write, with the
default name being the display string (if available) associated
with the link.
<D> ('elpher-download-current')
This is similar to 'elpher-download', but instead applies to the
current page rather than a link.
<.> ('elpher-view-raw')
This displays the raw server response for the current page. While
not useful for general browsing, it is useful for debugging
incorrect rendering or out-of-spec server responses.

File: elpher.info, Node: Between-page navigation, Next: History and Caching, Prev: Within-page navigation, Up: Navigation
4.2 Between-page navigation
===========================
Moving to a different page can be accomplished in several ways,
described by the following command:
<RET>, 'mouse-1' ('elpher-follow-link')
Follow the menu item or link at point (or selected with the mouse).
Exactly what is meant by "follow" depends on the kind of item
selected:
* For text or menu type items or links, the current page text is
replaced by the text of this item. Unless the customization
variable 'elpher-use-header' (*note Customization::) is 'nil',
the display string of the link is displayed in the buffer
header. Links to images behave similarly on Emacs systems
supporting the display of bitmap graphics, however their
content is not cached in memory by default.
* When followed, links to search/query items (type 7) prompt for
input in the minibuffer then display the results in the same
way as for text and menu items.
* Following links to binary files (and image files on
unsupported systems) causes Elpher to prompt for a filename in
which to save the content.
* Following links of type 'h' with a selector having the 'URL:'
prefix, or unsuported URLs in text files, will result in
Elpher using an external programme to open the URL. This will
be either the default system browser or, if the
'elpher-open-urls-with-eww' customization variable is non-nil,
Emacs' own EWW browser. (See *note Customization::.)
Once a text, menu or query response page has been displayed, its
contents are cached for the duration of the Emacs session.
<g> ('elpher-go')
Open a particular page by specifying either its full URL or just
entering a gopher host name. (The protocol defaults to gopher, so
gemini links must include the 'gemini://' prefix.
If a unsupported protocol is used in the URL the result will be the
same as following a URL link of the same type from a link in a
page.
<o> ('elpher-go-current')
Prompts for a URL similar to 'elpher-go', but initialized to the
URL of the current page. This allows you to easily try other
selectors for the same server.
Remember however, that the Gopher RFC 1436 provides _no_ guarantees
about the structure of selectors.
<O> ('elpher-root-dir')
Open the root page (empty selector) on the current host.
<u>, 'mouse-3' ('elpher-back')
Return to the previous page, where "previous" means the page where
the page which was displayed immediately before the current page.

File: elpher.info, Node: History and Caching, Prev: Between-page navigation, Up: Navigation
4.3 History and Caching
=======================
The history and caching strategy in Elpher is extremely simple, but may
be confusing without a good mental model of how it works. That is what
this section attempts to provide.
Essentially, *every* time you navigate to a new page, either by
clicking or pressing <RET> on a link, using <g> to jump to a new page by
its address, or using <O> to open the root selector, the following two
things occur:
1. the cursor position and content for the original page are recorded
in an in-memory cache, and
2. the original page is set as the "parent" of the new page.
The only way to return to pages in this history is by using <u>,
which returns to the previous of the current page. (1)
One aspect that may seem peculiar is that Elpher lacks a
corresponding "next" or "forward" command. However, since Elpher caches
the position of point, this will be automatically positioned on the link
that was most recently followed from a given page. This means that, at
least for links followed from menus and text files, the inverse of <u>
is actually just <RET>.
---------- Footnotes ----------
(1) The addition of the new page to the history happens even if the
new page is one that has been seen before. This is mostly the desired
behaviour. However, opening an explicit "back" link provided by a
gopher menu or gemini page will also add a new entry to the history.
Unless you haven't yet visited that menu, it's therefore better to use
<u> to go back in this case.

File: elpher.info, Node: Bookmarks, Next: Gopher character encodings, Prev: Navigation, Up: Top
5 Bookmarks
***********
Elpher has a very simple link bookmarking system involving the following
commands:
<a> ('elpher-bookmark-link')
Add a bookmark for the link at point. The minibuffer will prompt
for a name for the bookmark, which defaults to the display string.
<A> ('elpher-bookmark-current')
Add a bookmark for the current page. The minibuffer will prompt
for a name for the bookmark, defaulting to the display string
associated with the link that was followed to reach the current
page.
<x> ('elpher-unbookmark-link')
Immediately remove the bookmark (if one exists) to the link at
point.
<X> ('elpher-unbookmark-current')
Immediately remove the bookmark (if one exists) to the current
page.
<B> ('elpher-bookmarks')
Open a page displaying all current bookmarks. Note that this
bookmark page is added to the history just as if you had opened it
using a link. Thus to return to the previous page, use 'u'. This
also means that you can peruse the various bookmarks by visiting
them in turn, using 'u' to return to the bookmark page (where the
position of point is cached), then moving to another bookmarked
link and so on.
Bookmarks are stored as a s-exp in the file 'elpher-bookmarks' in the
user emacs directory (usually '~/.emacs.d/'). Any command which
modifies the list of bookmarks immediately updates this file.

File: elpher.info, Node: Gopher character encodings, Next: Encrypted gopher connections, Prev: Bookmarks, Up: Top
6 Gopher character encodings
****************************
Responses Elpher retrieves from servers are initially read as pure
binary data. When the data is intended to be interpreted as textual (as
determined by the type parameter of the gopher menu item or the gopher
URL), this data needs to be _decoded_ into a sequence of characters. To
do this properly requires knowledge of the encoding system used by
whoever authored the document.
Unfortunately gopher lacks a systematic way of acquiring this
necessary information. Thus, the details of the coding system must be
either inferred from the binary data, or must be specified by the user.
By default, Elpher applies Emacs' built-in character encoding
detection system to the full (undecoded) response data and uses this to
attempt to convert it into a character string. (See *note Recognizing
coding systems: (emacs)Recognize coding.) While this approach can be
okay, it is important to realize that its inference algorithm is
extremely primitive and depends heavily on assumptions based on the
language settings of your emacs system.
The alternative is to explicitly set the coding system used for
decoding using the following command:
<S> ('elpher-set-coding-system')
Causes a elpher to prompt for a coding system to use for decoding
future gopher text. The <TAB> key can be used at this prompt to
display a list of alternatives (which is extensive) and to
auto-complete. An empty response will cause Elpher to return to
its default auto-detection behaviour.
Note that changing the coding system only affects newly loaded text.
Thus, if text has already been decoded using an incorrect system, you
will need to select the correct coding and then reload the text using
<R>.

File: elpher.info, Node: Encrypted gopher connections, Next: Gemini support, Prev: Gopher character encodings, Up: Top
7 Encrypted gopher connections
******************************
While RFC 1436 does not broach the topic of encryption at all, several
modern gopher servers can serve content over encrypted connections, and
a common choice for this is TLS.
Elpher can retrieve selectors using Emacs' built-in TLS support which
uses the GnuTLS library. (It is possible to build emacs without GnuTLS,
in which case encryption is not supported.)
To retrieve documents using TLS, Elpher's TLS mode must be enabled.
This can be directly toggled using <T>, but note that just as with the
character encoding, changing this mode only affects subsequent
connections.
Alternatively, TLS mode is _automatically_ enabled whenever gopher
URLs starting with 'gophers://' are followed.
The mode is sticky, so it remains active until switched off. It can
also be automatically switched off when a TLS connection fails. In this
case Elpher will prompt for your confirmation to ensure that you can't
accidentally make a non-TLS connection.

File: elpher.info, Node: Gemini support, Next: Finger support, Prev: Encrypted gopher connections, Up: Top
8 Gemini support
****************
Gemini (gopher://gemini.circumlunar.space) is a new protocol being
developed by several members of gopherspace. It aims to solve some of
the long-standing technical issues associated with gopher as a protocol,
while keeping the major benefits. For instance, it _requires_ encrypted
connections, it does away with the selector type, and allows servers to
explicitly specify the character coding scheme used for text documents.
The latest versions of Elpher aim to provide seamless transitions
between gemini and gopher documents. Basically you should be able to
open, bookmark, download and otherwise interact with gemini pages in
exactly the same way as you do with other non-gemini pages. The only
major difference from your perspective as a user is that you should no
longer have to worry about manually toggling TLS on or off (for gemini
it's always on), and you should never have to manually set a character
coding scheme.
The gemini protocol specification recommends a Trust on First Use
(TOFU) behaviour when validating gemini server TLS certificates. This
is because many gemini servers rely on self-signed certificates rather
than certificates signed by a CA. Sadly however, this TOFU behaviour is
far from straight-forward to configure using Emacs' existing Network
Security Manager. For this reason, elpher defaults to performing no
certificate verification by default. This behaviour can be easily
customized by setting the 'elpher-gemini-TLS-cert-checks' customization
variable to non-nil.
The gemini specification concerns both the protocol and a simple text
document format (mimetype text/gemini) which is like a mixture between
gophermap files and markdown-formatted files but simpler than both.
Elpher renders gemini responses which are provided in this format in
line with the rules in the spec. This includes wrapping long lines at
word boundaries. The specific column at which this text is wrapped is
defined by the customization variable 'elpher-gemini-max-fill-width',
which is set to 80 columns by default. (This is slightly wider than
Emacs' default fill width of 70 columns due to the fact that there are a
significant amount of older gemini content which, against the advice of
the current spec, hard wraps at <80 columns. The larger default allows
this to still look okay, while still keeping content without hard wraps
looking pleasant.)
The text/gemini format also possesses a section header syntax similar
to markdown. Elpher allows different header levels to be drawn with
different, customizable, faces. By default, on graphically-capable
emacs systems, these faces are given different heights to distinguish
among levels. On terminal systems, the level is indicated by the number
of preceding # symbols.
I should emphasize however that, while it is definitely functional,
Elpher's gemini support is still experimental, and various aspects will
change as the protocol develops further.
8.1 Client Certificates for Gemini
==================================
Gemini makes explicit use of the client certificate mechanism that TLS
provides for allowing clients to authenticate themselves with servers.
The Gemini specification suggests two distinct classes of client
certificates: short-lived certificates used to identify you for a single
session, and more permanent certificates used to identify you over a
longer time period.
When Elpher receives a request for a client certificate from a
server, it will present you with the option to create and use a
single-use "throwaway" certificate, or to use a "persistent" certificate
(optionally creating it or installing pre-existing key and certificate
files).
Certificate creation in Elpher requires an installation of OpenSSL,
and --in particular--that Elpher be able to run the 'openssl'
command-line utility. By default, Elpher assumes that the 'openssl' is
on the system path, but the precise location can be set by customizing
the 'elpher-openssl-command' variable.
Each generated certificate results in the creation of a .key file and
a .crt file. In the case of a throwaway certificate, these files are
stored in the temporary directory indicated by the Emacs variable
'temporary-file-directory' and are deleted when "forgotten" (as
described below).
In the case of persistent certificates, these files are stored in the
folder defined by the Elpher variable 'elpher-certificate-directory',
and are never deleted by Elpher. (Of course you can delete them
yourself whenever you like.) The base name of the files (i.e. sans
extension) is what Elpher uses to identify the certificate.
Using throwaway certificates is as simple as pressing the <t> key at
the prompt which appears following a certificate request from a server.
There is nothing more to do.
Using a persistent certificate requires instead selecting <p> from
the same menu. This will result in Elpher asking you for the name
identifying the certificate. This entry autocompletes to the list of
known certificate names, so you can use <TAB> to display the list.
In the case that you choose a name that does not belong to the list
of known certificates, Elpher will offer to create one for you or to
"install" one from existing key and certificate files. Pressing the <n>
key will cause Elpher to begin the process of creating a new persistent
certificate, using some additional details for which you will be
prompted. Alternatively, pressing the <i> key will cause Elpher to ask
for the locations of edisting key and certificate files to add to
'elpher-certificate-directory' under the chosen name.
Once a certificate is selected, it will be used for all subsequent
TLS transactions to the host for which the certificate was created. It
is immediately "forgotten" when a TLS connection to another host is
attempted, or the following command is issued:
<F> ('elpher-forget-certificate')
Causes Elpher to immediately forget any currently-loaded client
certificate.
In either case, "forgetting" means that the details of the key and
certificate file pair are erased from memory. Furthermore, in the case
of throw-away certificates, the corresponding files are deleted.

File: elpher.info, Node: Finger support, Next: Customization, Prev: Gemini support, Up: Top
9 Finger support
****************
Incidentally, Elpher has native support for querying finger servers. Of
course, one could argue that this functionality is more easily provided
by one's local telnet client. However finger URLs do appear on occasion
in gopherspace, and it's nice to be able to open them in place.
Elpher interprets 'finger://' URLs as follows:
* The host is determined by the host name portion of the URL.
* In the case that the _file name_ portion of the URL is non-empty
(besides the leading slash), this is interpreted as the user to
finger.
* Otherwise, the _user_ portion of the URL is interpreted as the user
to finger.
* If no user is provided, the root directory of the finger server is
requested.
Thus 'finger://user@hostname' and 'finger://hostname/user' are both
equivalent.
(The precedence of the /user notation over the user notation reflects
a preference of the community.)

File: elpher.info, Node: Customization, Next: Command Index, Prev: Finger support, Up: Top
10 Customization
****************
Various parts of Elpher can be customized via the variables belonging to
the elpher customization group, accessible using
M-x customize-group elpher <RET>
This group contains a number of faces that can be modified to change the
appearance of Elpher, including one face per menu item type.
The group also contains variables for customizing the behaviour of
Elpher. This includes how to open arbitrary (non-gopher) URLs, whether
to display buffer headers, how to deal with ANSI escape sequences in
text, the timeout to impose on network connections, and whether to
prompt for confirmation when switching away from TLS.
See the customization group itself for details.

File: elpher.info, Node: Command Index, Prev: Customization, Up: Top
Command Index
*************
[index]
* Menu:
* elpher-back: Between-page navigation.
(line 62)
* elpher-bookmark-current: Bookmarks. (line 14)
* elpher-bookmark-link: Bookmarks. (line 10)
* elpher-bookmarks: Bookmarks. (line 28)
* elpher-copy-current-url: Within-page navigation.
(line 38)
* elpher-copy-link-url: Within-page navigation.
(line 34)
* elpher-download: Within-page navigation.
(line 42)
* elpher-download-current: Within-page navigation.
(line 48)
* elpher-follow-link: Between-page navigation.
(line 10)
* elpher-forget-certificate: Gemini support. (line 115)
* elpher-go: Between-page navigation.
(line 42)
* elpher-go-current: Between-page navigation.
(line 51)
* elpher-info-current: Within-page navigation.
(line 31)
* elpher-info-link: Within-page navigation.
(line 28)
* elpher-jump: Within-page navigation.
(line 20)
* elpher-next-link: Within-page navigation.
(line 14)
* elpher-prev-link: Within-page navigation.
(line 17)
* elpher-root-dir: Between-page navigation.
(line 59)
* elpher-set-coding-system: Gopher character encodings.
(line 29)
* elpher-unbookmark-current: Bookmarks. (line 24)
* elpher-unbookmark-link: Bookmarks. (line 20)
* elpher-view-raw: Within-page navigation.
(line 52)

Tag Table:
Node: Top892
Node: Introduction2631
Node: Installation3856
Node: Quick Start4619
Node: Navigation6609
Node: Within-page navigation7492
Node: Between-page navigation9590
Node: History and Caching12396
Ref: History and Caching-Footnote-113652
Node: Bookmarks14031
Node: Gopher character encodings15561
Node: Encrypted gopher connections17461
Node: Gemini support18611
Node: Finger support24962
Node: Customization26018
Node: Command Index26833

End Tag Table

Local Variables:
coding: utf-8
End:

5
elpher-bookmarks Normal file
View File

@ -0,0 +1,5 @@
;;;; Emacs Bookmark Format Version 1;;;; -*- coding: utf-8-emacs; mode: lisp-data -*-
;;; This format is meant to be slightly human-readable;
;;; nevertheless, you probably don't want to edit it.
;;; -*- End Of Bookmark File Format Version Stamp -*-
()

82
init.el
View File

@ -63,6 +63,9 @@
term-mode-hook
shell-mode-hook
erc-mode-hook
mu4e-main-mode-hook
mu4e-headers-mode-hook
mu4e-view-mode-hook
eshell-mode-hook))
(add-hook mode (lambda () (display-line-numbers-mode 0))))
@ -151,7 +154,7 @@
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.
'(package-selected-packages
'(evil-mu4e exwm org-inline-pdf mu4e evil-magit magit general workgroups2 ERC dashboard doom-themes counsel ivy-rich which-key rainbow-delimiters doom-modeline use-package shrink-path ivy command-log-mode all-the-icons))
'(elpher evil-mu4e exwm org-inline-pdf mu4e evil-magit magit general workgroups2 ERC dashboard doom-themes counsel ivy-rich which-key rainbow-delimiters doom-modeline use-package shrink-path ivy command-log-mode all-the-icons))
'(send-mail-function 'smtpmail-send-it)
'(smtpmail-smtp-server "disroot.org")
'(smtpmail-smtp-service 25))
@ -176,3 +179,80 @@
(setq user-full-name "Syed Ahmed")
(setq user-mail-address "9ahmed@disroot.org")
(setq mu4e-get-mail-command "mbsync -a")
(require 'mu4e)
(setq user-full-name "Syed Ahmed")
(setq user-mail-address "syedahmed@riseup.net")
(setq mu4e-get-mail-command "mbsync -a")
(require 'erc)
(setq
erc-autojoin-timing 'ident
erc-fill-function 'erc-fill-static
erc-join-channel 'general
erc-hide-list '("JOIN" "PART" "QUIT")
erc-fill-static-center 0
erc-server-reconnect-attempts 5
erc-server-reconnect-timeout 3)
(global-set-key "\C-ch"
(lambda ()
(interactive)
(erc :server "rnbunker.ydns.eu"
:port "6667"
:nick "ahmd"
:full-name "Am")))
(use-package mu4e
:ensure nil
:config
;; This is set to 't' to avoid mail syncing issues when using mbsync
(setq mu4e-change-filenames-when-moving t)
;; Refresh mail using isync every 10 minutes
(setq mu4e-update-interval (* 10 60))
(setq mu4e-get-mail-command "mbsync -a")
(setq mu4e-maildir "~/Mail")
(setq mu4e-contexts
(list
;; Work account
(make-mu4e-context
:name "Work"
:match-func
(lambda (msg)
(when msg
(string-prefix-p "/Riseup" (mu4e-message-field msg :maildir))))
:vars '((user-mail-address . "syedahmed@riseup.net")
(user-full-name . "Syed Ahmed")
(mu4e-drafts-folder . "/Riseup/[Riseup]/Drafts")
(mu4e-sent-folder . "/Riseup/[Riseup]/Sent Mail")
(mu4e-refile-folder . "/Riseup/[Riseup]/All Mail")
(mu4e-trash-folder . "/Riseup/[Riseup]/Trash")))
;; Personal account
(make-mu4e-context
:name "Personal"
:match-func
(lambda (msg)
(when msg
(string-prefix-p "/Disroot" (mu4e-message-field msg :maildir))))
:vars '((user-mail-address . "9ahmed@disroot.org")
(user-full-name . "Syed Ahmed")
(mu4e-drafts-folder . "/Disroot/Drafts")
(mu4e-sent-folder . "/Disroot/Sent")
(mu4e-refile-folder . "/Disroot/Archive")
(mu4e-trash-folder . "/Disroot/Trash")))))
(setq mu4e-maildir-shortcuts
'(("/Inbox" . ?i)
("/Riseup/[Riseup]/Sent Mail" . ?s)
("/Riseup/[Riseup]/Trash" . ?t)
("/Riseup/[Riseup]/Drafts" . ?d)
("/Riseup/[Riseup]/All Mail" . ?a))))