summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2019-09-22 23:53:39 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2019-09-23 00:12:52 -0700
commit946a56a10fed769646a8b7c4ebc53f53c84be896 (patch)
tree33a93593b428789b7e49376427eac09d21082808 /doc
parent78669517dc3db4d6d51fb26d71073fc0c196ab5d (diff)
downloademacs-946a56a10fed769646a8b7c4ebc53f53c84be896.tar.gz
Update some URLs
This mostly changes http: to https: in URLs. It also updates some URLs that have moved, removes some URLs that no longer work, recommends against using procmail (procmail.org no longer works), and removes some mentions of the no-longer-existing Gmane, LPF and VTW. It doesn't update all URLs, just the ones I had time for. * GNUmakefile (help): * admin/admin.el (manual-doctype-string): * admin/charsets/Makefile.in (${charsetdir}/ALTERNATIVNYJ.map): * admin/charsets/mapconv: * lisp/net/soap-client.el (soap-create-envelope): * lisp/org/org.el (org-doi-server-url): * lisp/textmodes/bibtex.el (bibtex-generate-url-list): Prefer https: to http: un URLs.
Diffstat (limited to 'doc')
-rw-r--r--doc/emacs/emacs.texi2
-rw-r--r--doc/emacs/mule.texi2
-rw-r--r--doc/emacs/package.texi2
-rw-r--r--doc/lispref/frames.texi2
-rw-r--r--doc/lispref/nonascii.texi6
-rw-r--r--doc/lispref/os.texi2
-rw-r--r--doc/lispref/package.texi4
-rw-r--r--doc/lispref/processes.texi4
-rw-r--r--doc/lispref/text.texi4
-rw-r--r--doc/lispref/tips.texi2
-rw-r--r--doc/misc/auth.texi4
-rw-r--r--doc/misc/autotype.texi3
-rw-r--r--doc/misc/cc-mode.texi12
-rw-r--r--doc/misc/dbus.texi12
-rw-r--r--doc/misc/efaq.texi27
-rw-r--r--doc/misc/eieio.texi2
-rw-r--r--doc/misc/emacs-gnutls.texi2
-rw-r--r--doc/misc/epa.texi2
-rw-r--r--doc/misc/erc.texi6
-rw-r--r--doc/misc/ert.texi6
-rw-r--r--doc/misc/eudc.texi4
-rw-r--r--doc/misc/eww.texi2
-rw-r--r--doc/misc/gnus-faq.texi43
-rw-r--r--doc/misc/gnus.texi38
-rw-r--r--doc/misc/message.texi4
-rw-r--r--doc/misc/mh-e.texi67
-rw-r--r--doc/misc/newsticker.texi5
-rw-r--r--doc/misc/org.texi2
-rw-r--r--doc/misc/url.texi3
-rw-r--r--doc/misc/wisent.texi2
30 files changed, 122 insertions, 154 deletions
diff --git a/doc/emacs/emacs.texi b/doc/emacs/emacs.texi
index ad4be90aaf3..17aaaea7364 100644
--- a/doc/emacs/emacs.texi
+++ b/doc/emacs/emacs.texi
@@ -1316,7 +1316,7 @@ Emacs editors, all sharing common principles of organization. For
information on the underlying philosophy of Emacs and the lessons
learned from its development, see @cite{Emacs, the Extensible,
Customizable Self-Documenting Display Editor}, available from
-@url{http://hdl.handle.net/1721.1/5736}.
+@url{https://dspace.mit.edu/handle/1721.1/5736}.
This version of the manual is mainly intended for use with GNU Emacs
installed on GNU and Unix systems. GNU Emacs can also be used on
diff --git a/doc/emacs/mule.texi b/doc/emacs/mule.texi
index dfd464c827c..bca917de105 100644
--- a/doc/emacs/mule.texi
+++ b/doc/emacs/mule.texi
@@ -1790,7 +1790,7 @@ Reordering of bidirectional text into the @dfn{visual} order happens
at display time. As a result, character positions no longer increase
monotonically with their positions on display. Emacs implements the
Unicode Bidirectional Algorithm (UBA) described in the
-@uref{http://unicode.org/reports/tr9/, Unicode Standard Annex #9}, for
+@uref{https://unicode.org/reports/tr9/, Unicode Standard Annex #9}, for
reordering of bidirectional text for display.
It deviates from the UBA only in how continuation lines are displayed
when text direction is opposite to the base paragraph direction,
diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi
index 4b33f250c49..2c09ca89024 100644
--- a/doc/emacs/package.texi
+++ b/doc/emacs/package.texi
@@ -179,7 +179,7 @@ maintained by the Emacs developers. This is controlled by the
variable @code{package-archives}, whose value is a list of package
archives known to Emacs. Each list element must have the form
@code{(@var{id} . @var{location})}, where @var{id} is the name of a
-package archive and @var{location} is the @acronym{HTTP} address or
+package archive and @var{location} is the @acronym{URL} or
name of the package archive directory. You can alter this list if you
wish to use third party package archives---but do so at your own risk,
and use only third parties that you think you can trust!
diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
index 618ea16fcf2..8596db7421f 100644
--- a/doc/lispref/frames.texi
+++ b/doc/lispref/frames.texi
@@ -3861,7 +3861,7 @@ drop.
@vindex dnd-protocol-alist
When an URL is dropped on Emacs it may be a file, but it may also be
-another URL type (ftp, http, etc.). Emacs first checks
+another URL type (https, etc.). Emacs first checks
@code{dnd-protocol-alist} to determine what to do with the URL@. If
there is no match there and if @code{browse-url-browser-function} is
an alist, Emacs looks for a match there. If no match is found the
diff --git a/doc/lispref/nonascii.texi b/doc/lispref/nonascii.texi
index a56a365e9ea..612c362f4a2 100644
--- a/doc/lispref/nonascii.texi
+++ b/doc/lispref/nonascii.texi
@@ -453,13 +453,13 @@ during text processing and display. Thus, character properties are an
important part of specifying the character's semantics.
@c FIXME: Use the latest URI of this chapter?
-@c http://www.unicode.org/versions/latest/ch04.pdf
+@c https://www.unicode.org/versions/latest/ch04.pdf
On the whole, Emacs follows the Unicode Standard in its implementation
of character properties. In particular, Emacs supports the
-@uref{http://www.unicode.org/reports/tr23/, Unicode Character Property
+@uref{https://www.unicode.org/reports/tr23/, Unicode Character Property
Model}, and the Emacs character property database is derived from the
Unicode Character Database (@acronym{UCD}). See the
-@uref{http://www.unicode.org/versions/latest/ch04.pdf, Character
+@uref{https://www.unicode.org/versions/Unicode12.1.0/ch04.pdf, Character
Properties chapter of the Unicode Standard}, for a detailed
description of Unicode character properties and their meaning. This
section assumes you are already familiar with that chapter of the
diff --git a/doc/lispref/os.texi b/doc/lispref/os.texi
index ddbc8a82946..fae23cb0758 100644
--- a/doc/lispref/os.texi
+++ b/doc/lispref/os.texi
@@ -2718,7 +2718,7 @@ interpreted as icon name.
@item :category @var{category}
The type of notification this is, a string. See the
-@uref{http://developer.gnome.org/notification-spec/#categories,
+@uref{https://developer.gnome.org/notification-spec/#categories,
Desktop Notifications Specification} for a list of standard
categories.
diff --git a/doc/lispref/package.texi b/doc/lispref/package.texi
index eb34b8e0af2..57f4cbc5db3 100644
--- a/doc/lispref/package.texi
+++ b/doc/lispref/package.texi
@@ -159,7 +159,7 @@ the various headers, as illustrated by the following example:
;; Version: 1.3
;; Package-Requires: ((flange "1.0"))
;; Keywords: multimedia, hypermedia
-;; URL: http://example.com/jrhacker/superfrobnicate
+;; URL: https://example.com/jrhacker/superfrobnicate
@dots{}
@@ -351,7 +351,7 @@ for a multi-file package, it is the package tar file.
You can also sign the archive's contents file in the same way.
Make the @file{.sig} files available in the same location as the packages.
You should also make your public key available for people to download;
-e.g., by uploading it to a key server such as @url{http://pgp.mit.edu/}.
+e.g., by uploading it to a key server such as @url{https://pgp.mit.edu/}.
When people install packages from your archive, they can use
your public key to verify the signatures.
diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi
index 4c7853bae86..2ba5b1c893a 100644
--- a/doc/lispref/processes.texi
+++ b/doc/lispref/processes.texi
@@ -2690,8 +2690,8 @@ override this.
@item :service @var{service}
@var{service} specifies a port number to connect to; or, for a server,
the port number to listen on. It should be a service name like
-@samp{"http"} that translates to a port number, or an integer like @samp{80}
-or an integer string like @samp{"80"} that specifies the port number
+@samp{"https"} that translates to a port number, or an integer like @samp{443}
+or an integer string like @samp{"443"} that specifies the port number
directly. For a server, it can also be @code{t}, which means to let
the system select an unused port number.
diff --git a/doc/lispref/text.texi b/doc/lispref/text.texi
index 955ad6130ca..d7b04d2934f 100644
--- a/doc/lispref/text.texi
+++ b/doc/lispref/text.texi
@@ -5310,7 +5310,7 @@ the value if contains a valid JSON object; otherwise it signals the
The @code{jsonrpc} library implements the @acronym{JSONRPC}
specification, version 2.0, as it is described in
-@uref{http://www.jsonrpc.org/}. As the name suggests, JSONRPC is a
+@uref{https://www.jsonrpc.org/}. As the name suggests, JSONRPC is a
generic @dfn{Remote Procedure Call} protocol designed around
@acronym{JSON} objects, which you can convert to and from Lisp objects
(@pxref{Parsing JSON}).
@@ -5325,7 +5325,7 @@ generic @dfn{Remote Procedure Call} protocol designed around
@node JSONRPC Overview
@subsection Overview
-Quoting from the @uref{http://www.jsonrpc.org/, spec}, JSONRPC "is
+Quoting from the @uref{https://www.jsonrpc.org/, spec}, JSONRPC "is
transport agnostic in that the concepts can be used within the same
process, over sockets, over http, or in many various message passing
environments."
diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
index 855b284a157..6d84cfef53b 100644
--- a/doc/lispref/tips.texi
+++ b/doc/lispref/tips.texi
@@ -958,7 +958,7 @@ explains these conventions, starting with an example:
;; Created: 14 Jul 2010
@group
;; Keywords: languages
-;; URL: http://example.com/foo
+;; URL: https://example.com/foo
;; This file is not part of GNU Emacs.
diff --git a/doc/misc/auth.texi b/doc/misc/auth.texi
index 850441e25d2..93a301dcb1a 100644
--- a/doc/misc/auth.texi
+++ b/doc/misc/auth.texi
@@ -279,7 +279,7 @@ machine gmail2 login account2@@gmail.com password "account2 password" port imap
@chapter Secret Service API
The @dfn{Secret Service API} is a standard from
-@uref{http://www.freedesktop.org/wiki/Specifications/secret-storage-spec,,freedesktop.org}
+@uref{https://www.freedesktop.org/wiki/Specifications/secret-storage-spec/,,freedesktop.org}
to securely store passwords and other confidential information. This
API is implemented by system daemons such as the GNOME Keyring and the
KDE Wallet (these are GNOME and KDE packages respectively and should
@@ -442,7 +442,7 @@ then fall back to @file{~/.authinfo.gpg}.
@node The Unix password store
@chapter The Unix password store
-@uref{http://www.passwordstore.org,,The standard unix password
+@uref{https://www.passwordstore.org,,The standard unix password
manager} (or just @code{pass}) stores your passwords in
@code{gpg}-protected files following the Unix philosophy. The store
location (any directory) must be specified in the
diff --git a/doc/misc/autotype.texi b/doc/misc/autotype.texi
index 96262fcb530..a354383cc9f 100644
--- a/doc/misc/autotype.texi
+++ b/doc/misc/autotype.texi
@@ -592,8 +592,7 @@ specify that @kbd{M-x quickurl} should insert @var{URL} if the word
@example
(("FSF" "https://www.fsf.org/" "The Free Software Foundation")
- ("emacs" . "http://www.emacs.org/")
- ("hagbard" "http://www.hagbard.demon.co.uk" "Hagbard's World"))
+ ("emacs" . "https://www.gnu.org/software/emacs/"))
@end example
@findex quickurl-add-url
diff --git a/doc/misc/cc-mode.texi b/doc/misc/cc-mode.texi
index 1df9dce2279..217261090bf 100644
--- a/doc/misc/cc-mode.texi
+++ b/doc/misc/cc-mode.texi
@@ -393,7 +393,7 @@ version 5.34.
@ccmode{} supports the editing of C, C++, Objective-C,
Java, CORBA's Interface Definition Language, Pike@footnote{A C-like
scripting language with its roots in the LPC language used in some MUD
-engines. See @uref{http://pike.ida.liu.se/}.} and AWK files. In this
+engines. See @uref{https://pike.lysator.liu.se/}.} and AWK files. In this
way, you can easily set up consistent font locking and coding styles for
use in editing all of these languages, although AWK is not yet as
uniformly integrated as the other languages.
@@ -2693,7 +2693,7 @@ The classic Stroustrup style for C++ code.
Popular C++ coding standards as defined by ``Programming in C++, Rules
and Recommendations,'' Erik Nyquist and Mats Henricson,
Ellemtel@footnote{This document is available at
-@uref{http://www.doc.ic.ac.uk/lab/cplus/c++.rules/} among other
+@uref{https://www.doc.ic.ac.uk/lab/cplus/c++.rules/} among other
places.}.
@c N.B. This URL was still valid at 2005/8/28 (ACM).
@@ -2705,7 +2705,7 @@ C coding standard for Linux (the kernel).
@cindex Python style
C coding standard for Python extension modules@footnote{Python is a
high level scripting language with a C/C++ foreign function interface.
-For more information, see @uref{http://www.python.org/}.}.
+For more information, see @uref{https://www.python.org/}.}.
@item java
@cindex Java style
@@ -6014,7 +6014,7 @@ set_line (line_t @{point_t@{0.4, 0.2@},
^ enclosing parenthesis.
@end group
@end example
-
+
The middle line of that example will have a syntactic context with
three syntactic symbols, @code{arglist-cont-nonempty},
@@ -6059,7 +6059,7 @@ struct STR @{
@sssTBasicOffset{}
@end group
@end example
-
+
Note that the syntactic context of the @code{brace-list-intro} line
also has a syntactic element with the symbol @code{brace-list-entry}
@@ -6100,7 +6100,7 @@ struct STR @{
@};
@end group
@end example
-
+
Note that the syntactic context of the @code{brace-list-intro} line
also has a syntactic element with the symbol @code{brace-list-entry}
diff --git a/doc/misc/dbus.texi b/doc/misc/dbus.texi
index 7c7612f579c..43bf2f75fe3 100644
--- a/doc/misc/dbus.texi
+++ b/doc/misc/dbus.texi
@@ -47,7 +47,7 @@ modify this GNU manual.''
This manual documents an API for usage of D-Bus in Emacs. D-Bus is a
message bus system, a simple way for applications to talk to one
another. An overview of D-Bus can be found at
-@uref{http://dbus.freedesktop.org/}.
+@uref{https://dbus.freedesktop.org/}.
@ifnottex
@insertcopying
@@ -328,7 +328,7 @@ and @code{direction}. The @code{name} attribute is optional. The
in D-Bus. For a discussion of D-Bus types and their Lisp
representation see @ref{Type Conversion}.@footnote{D-Bus signatures
are explained in the D-Bus specification
-@uref{http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-signatures}.}
+@uref{https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-signatures}.}
The @code{direction} attribute of an @code{arg} element can be only
@samp{in} or @samp{out}; in case it is omitted, it defaults to
@samp{in}.
@@ -415,7 +415,7 @@ string and 2 boolean values.@footnote{ The interfaces of the service
@samp{org.freedesktop.Hal} are described in
@c Previous link is gone. Since HAL is now obsolete, this URL
@c (unchanged in ~ 4 years) feels like it might go too...
-@uref{http://people.freedesktop.org/~dkukawka/hal-spec-git/hal-spec.html#interfaces,
+@uref{https://people.freedesktop.org/~dkukawka/hal-spec-git/hal-spec.html#interfaces,
the HAL specification}.}
@end defun
@@ -663,13 +663,13 @@ returned by @code{dbus-introspect-get-signal-names}. Example:
Interfaces can have properties. These can be exposed via the
@samp{org.freedesktop.DBus.Properties} interface@footnote{See
-@uref{http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties}}.
+@uref{https://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties}}.
That is, properties can be retrieved and changed during lifetime of an
element.
A generalized interface is
@samp{org.freedesktop.DBus.Objectmanager}@footnote{See
-@uref{http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager}},
+@uref{https://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager}},
which returns objects, their interfaces and properties for a given
service in just one call.
@@ -839,7 +839,7 @@ belong to. Example:
@end lisp
Default annotation names@footnote{See
-@uref{http://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format}}
+@uref{https://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format}}
are
@table @samp
diff --git a/doc/misc/efaq.texi b/doc/misc/efaq.texi
index a591b882017..219ad248cca 100644
--- a/doc/misc/efaq.texi
+++ b/doc/misc/efaq.texi
@@ -280,9 +280,8 @@ For information on some of the files in the @file{etc} directory,
@pxref{Informational files for Emacs}.
@node Common acronyms
-@section What are FSF, LPF, GNU, RMS, FTP, and GPL?
+@section What are FSF, GNU, RMS, FTP, and GPL?
@cindex FSF, definition of
-@cindex LPF, definition of
@cindex GNU, definition of
@cindex RMS, definition of
@cindex Stallman, Richard, acronym for
@@ -297,9 +296,6 @@ For information on some of the files in the @file{etc} directory,
@item FSF
Free Software Foundation
-@item LPF
-League for Programming Freedom
-
@item GNU
GNU's Not Unix
@@ -314,10 +310,6 @@ GNU General Public License
@end table
-Avoid confusing the FSF and the LPF@. The LPF opposes
-look-and-feel copyrights and software patents. The FSF aims to make
-high quality free software available for everyone.
-
The word ``free'' in the title of the Free Software Foundation refers to
``freedom,'' not ``zero cost.'' Anyone can charge any price for
GPL-covered software that they want to. However, in practice, the
@@ -334,7 +326,6 @@ This chapter contains general questions having to do with Emacs, the
Free Software Foundation, and related organizations.
@menu
-* The LPF::
* Real meaning of copyleft::
* Guidelines for newsgroup postings::
* Newsgroup archives::
@@ -343,17 +334,6 @@ Free Software Foundation, and related organizations.
* Contacting the FSF::
@end menu
-@node The LPF
-@section What is the LPF?
-@cindex LPF, description of
-@cindex League for Programming Freedom
-@cindex Software patents, opposition to
-@cindex Patents for software, opposition to
-
-The LPF opposes the expanding danger of software patents and
-look-and-feel copyrights. More information on the LPF's views is
-available at @uref{http://progfree.org/, the LPF home page}.
-
@node Real meaning of copyleft
@section What is the real legal meaning of the GNU copyleft?
@cindex Copyleft, real meaning of
@@ -427,11 +407,6 @@ Web-based Usenet search services, such as
@uref{http://groups.google.com/groups/dir?q=gnu&, Google}, also
archive the @code{gnu.*} groups.
-You can also read the archives of the @code{gnu.*} groups and post new
-messages at @uref{http://gmane.org/, Gmane}. Gmane is a service that
-presents mailing lists as newsgroups (even those without a traditional
-mail-to-news gateway).
-
@node Reporting bugs
@section Where should I report bugs and other problems with Emacs?
@cindex Bug reporting
diff --git a/doc/misc/eieio.texi b/doc/misc/eieio.texi
index f56b2b67a40..f20af3bb22b 100644
--- a/doc/misc/eieio.texi
+++ b/doc/misc/eieio.texi
@@ -1006,7 +1006,7 @@ what CLOS does when a monotonic class structure is defined.
This is derived from the Dylan language documents by
Kim Barrett et al.: A Monotonic Superclass Linearization for Dylan
-Retrieved from: http://192.220.96.201/dylan/linearization-oopsla96.html
+Retrieved from: https://doi.org/10.1145/236338.236343
@end table
@node Predicates
diff --git a/doc/misc/emacs-gnutls.texi b/doc/misc/emacs-gnutls.texi
index add79d12e42..36a490b1ae1 100644
--- a/doc/misc/emacs-gnutls.texi
+++ b/doc/misc/emacs-gnutls.texi
@@ -90,7 +90,7 @@ alias of the second.
There's one way to find out if GnuTLS is available, by calling
@code{gnutls-available-p}. This is a little bit trickier on the W32
(Windows) platform, but if you have the GnuTLS DLLs (available from
-@url{http://sourceforge.net/projects/ezwinports/files/} thanks to Eli
+@url{https://sourceforge.net/projects/ezwinports/files/} thanks to Eli
Zaretskii) in the same directory as Emacs, you should be OK.
@defun gnutls-available-p
diff --git a/doc/misc/epa.texi b/doc/misc/epa.texi
index 330ce7092f9..b1ca8d92a25 100644
--- a/doc/misc/epa.texi
+++ b/doc/misc/epa.texi
@@ -312,7 +312,7 @@ blobs inside a message body, not using modern MIME format.
NOTE: Inline OpenPGP is not recommended and you should consider to use
PGP/MIME@. See
-@uref{http://josefsson.org/inline-openpgp-considered-harmful.html,
+@uref{https://josefsson.org/inline-openpgp-considered-harmful.html,
Inline OpenPGP in E-mail is bad@comma{} Mm'kay?}.
@noindent
diff --git a/doc/misc/erc.texi b/doc/misc/erc.texi
index e1d2217806a..a6b39c2cbe8 100644
--- a/doc/misc/erc.texi
+++ b/doc/misc/erc.texi
@@ -699,7 +699,7 @@ stuff, to the current ERC buffer."
;; This causes ERC to connect to the IRC server on your own machine (if
;; you have one) upon hitting C-c e b. Replace MYNICK with your IRC
-;; nick. Often, people like to run bitlbee (http://bitlbee.org/) as an
+;; nick. Often, people like to run bitlbee (https://bitlbee.org/) as an
;; AIM/Jabber/MSN to IRC gateway, so that they can use ERC to chat with
;; people on those networks.
(global-set-key "\C-ceb" (lambda () (interactive)
@@ -801,7 +801,7 @@ or if you have bugs to report, there are several places you can go.
@itemize @bullet
@item
-@uref{http://www.emacswiki.org/cgi-bin/wiki/ERC} is the
+@uref{https://www.emacswiki.org/emacs/ERC} is the
emacswiki.org page for ERC@. Anyone may add tips, hints, etc.@: to it.
@item
@@ -838,7 +838,7 @@ general.
@c mlang@@delysid.org, alex@@gnu.org
In June 2001, Mario Lang and Alex Schroeder
took over development and created a ERC Project at
-@uref{http://sourceforge.net/projects/erc}.
+@uref{https://sourceforge.net/projects/erc}.
In reaction to a mail about the new ERC development effort, Sergey
Berezin said, ``First of all, I'm glad that my version of ERC is being
diff --git a/doc/misc/ert.texi b/doc/misc/ert.texi
index d2d86555e3c..2dbba095d61 100644
--- a/doc/misc/ert.texi
+++ b/doc/misc/ert.texi
@@ -53,7 +53,7 @@ ERT is similar to tools for other environments such as JUnit, but has
unique features that take advantage of the dynamic and interactive
nature of Emacs. Despite its name, it works well both for test-driven
development (see
-@url{http://en.wikipedia.org/wiki/Test-driven_development}) and for
+@url{https://en.wikipedia.org/wiki/Test-driven_development}) and for
traditional software development methods.
@menu
@@ -899,11 +899,11 @@ For information on mocks, stubs, fixtures, or test suites, see below.
Stubbing out functions or using so-called @emph{mocks} can make it
easier to write tests. See
-@url{http://en.wikipedia.org/wiki/Mock_object} for an explanation of
+@url{https://en.wikipedia.org/wiki/Mock_object} for an explanation of
the corresponding concepts in object-oriented languages.
ERT does not have built-in support for mocks or stubs. The package
-@code{el-mock} (see @url{http://www.emacswiki.org/emacs/el-mock.el})
+@code{el-mock} (see @url{https://www.emacswiki.org/emacs/el-mock.el})
offers mocks for Emacs Lisp and can be used in conjunction with ERT.
diff --git a/doc/misc/eudc.texi b/doc/misc/eudc.texi
index 568f94ba7c1..9e91871673a 100644
--- a/doc/misc/eudc.texi
+++ b/doc/misc/eudc.texi
@@ -131,7 +131,7 @@ complement to the DAP itself.
LDAP servers usually store (but are not limited to) information about
people such as their name, phone number, email address, office
location, etc@enddots{} More information about LDAP can be found at
-@url{http://www.openldap.org/}.
+@url{https://www.openldap.org/}.
EUDC requires external support to access LDAP directory servers
(@pxref{LDAP Configuration})
@@ -193,7 +193,7 @@ email composition buffers (@pxref{Inline Query Expansion})
LDAP support is added by means of @file{ldap.el}, which is part of
Emacs. @file{ldap.el} needs an external program called
@command{ldapsearch}, available as part of OpenLDAP
-(@url{http://www.openldap.org/}). The configurations in this section
+(@url{https://www.openldap.org/}). The configurations in this section
were tested with OpenLDAP 2.4.23.
Most servers use LDAP-over-SSL these days; the examples here reflect
diff --git a/doc/misc/eww.texi b/doc/misc/eww.texi
index 63f676ec756..315b4b0194d 100644
--- a/doc/misc/eww.texi
+++ b/doc/misc/eww.texi
@@ -319,7 +319,7 @@ Gnus. He started writing an Emacs HTML rendering library,
@code{shr.el}, to read blogs in Gnus. He eventually added a web
browser front end and HTML form support. Which resulted in EWW, the
Emacs Web Wowser. EWW was announced on 16 June 2013:
-@url{http://lars.ingebrigtsen.no/2013/06/16/eww/}.
+@url{https://lars.ingebrigtsen.no/2013/06/16/eww/}.
EWW was then moved from the Gnus repository to GNU Emacs and several
developers started contributing to it as well.
diff --git a/doc/misc/gnus-faq.texi b/doc/misc/gnus-faq.texi
index f295c997cbd..b0dc9c3ba3b 100644
--- a/doc/misc/gnus-faq.texi
+++ b/doc/misc/gnus-faq.texi
@@ -164,7 +164,7 @@ Gnus is released independent from releases of Emacs. Therefore, the
version bundled with Emacs might not be up to date (e.g., Gnus 5.9
bundled with Emacs 21 is outdated).
You can get the latest released version of Gnus from
-@uref{http://www.gnus.org/dist/gnus.tar.gz}
+@uref{https://www.gnus.org/dist/gnus.tar.gz}
or from
@uref{https://ftp.gnus.org/pub/gnus/gnus.tar.gz}.
@@ -178,10 +178,9 @@ What to do with the tarball now?
Untar it via @samp{tar xvzf gnus.tar.gz} and do the common
@samp{./configure; make; make install} circle.
(under MS-Windows either get the Cygwin environment from
-@uref{http://www.cygwin.com}
+@uref{https://www.cygwin.com}
which allows you to do what's described above or unpack the
-tarball with some packer (e.g., Winace from
-@uref{http://www.winace.com})
+tarball with some packer (e.g., Winace)
and use the batch-file make.bat included in the tarball to install
Gnus.) If you don't want to (or aren't allowed to) install Gnus
system-wide, you can install it in your home directory and add the
@@ -1367,12 +1366,12 @@ Is there a spell-checker? Perhaps even on-the-fly spell-checking?
You can use ispell.el to spell-check stuff in Emacs. So the
first thing to do is to make sure that you've got either
-@uref{http://fmg-www.cs.ucla.edu/fmg-members/geoff/ispell.html, ispell}
-or @uref{http://aspell.sourceforge.net/, aspell}
+@uref{https://www.cs.hmc.edu/~geoff/ispell.html, ispell}
+or @uref{http://aspell.net, aspell}
installed and in your Path. Then you need
-@uref{http://www.kdstevens.com/~stevens/ispell-page.html, ispell.el}
+ispell.el
and for on-the-fly spell-checking
-@uref{http://www-sop.inria.fr/members/Manuel.Serrano/flyspell/flyspell.html, flyspell.el}.
+@uref{https://www-sop.inria.fr/members/Manuel.Serrano/flyspell/flyspell.html, flyspell.el}.
Ispell.el is shipped with Emacs,
flyspell.el is shipped with Emacs, so there should be no need to install them
manually.
@@ -1515,7 +1514,7 @@ cat file.face | sed 's/["\\]/\\&/g' > file.face.quoted
@noindent
If you can't use compface, there's an online X-face converter at
-@uref{http://www.dairiki.org/xface/}.
+@uref{https://www.dairiki.org/xface/}.
If you use MS Windows, you could also use the WinFace program,
which used to be available from
@indicateurl{http://www.xs4all.nl/~walterln/winface/}.
@@ -1713,7 +1712,7 @@ The easiest way is to tell your old mail program to
export the messages in mbox format. Most Unix mailers
are able to do this, if you come from the MS Windows
world, you may find tools at
-@uref{http://mbx2mbox.sourceforge.net/}.
+@uref{https://sourceforge.net/projects/mbx2mbox/}.
Now you've got to import this mbox file into Gnus. To do
this, create a nndoc group based on the mbox file by
@@ -1787,7 +1786,7 @@ How to search for a specific message?
There are several ways for this, too. For a posting from
a Usenet group the easiest solution is probably to ask
-@uref{http://groups.google.com, groups.google.com},
+@uref{https://groups.google.com, groups.google.com},
if you found the posting there, tell Google to display
the raw message, look for the message-id, and say
@samp{M-^ the@@message.id @key{RET}} in a
@@ -1942,21 +1941,21 @@ when you're online.
Let's talk about Unix systems first: For the news part,
the easiest solution is a small nntp server like
@uref{http://www.leafnode.org/, Leafnode} or
-@uref{http://infa.abo.fi/~patrik/sn/, sn},
+@uref{http://patrik.iki.fi/sn/, sn},
of course you can also install a full featured news
server like
-@uref{http://www.isc.org/software/inn/, inn}.
+@uref{https://www.isc.org/othersoftware/, inn}.
Then you want to fetch your Mail, popular choices
-are @uref{http://www.catb.org/~esr/fetchmail/, fetchmail}
+are @uref{http://www.fetchmail.info/, fetchmail}
and @uref{http://pyropus.ca/software/getmail/, getmail}.
You should tell those to write the mail to your disk and
Gnus to read it from there. Last but not least the mail
sending part: This can be done with every MTA like
-@uref{http://www.sendmail.org/, sendmail} or
-@uref{http://www.exim.org/, exim}.
+@uref{https://www.proofpoint.com/us/open-source-email-solution, sendmail} or
+@uref{https://www.exim.org/, exim}.
On windows boxes I'd vote for
-@uref{http://www.tglsoft.de/, Hamster},
+@uref{http://www.tglsoft.de/freeware_hamster.html, Hamster},
it's a small freeware, open-source program which fetches
your mail and news from remote servers and offers them
to Gnus (or any other mail and/or news reader) via nntp
@@ -2100,7 +2099,7 @@ Which websites should I know?
@subsubheading Answer
The most important one is the
-@uref{http://www.gnus.org, official Gnus website}.
+@uref{https://www.gnus.org, official Gnus website}.
Tell me about other sites which are interesting.
@@ -2111,9 +2110,7 @@ Which mailing lists and newsgroups are there?
@subsubheading Answer
-There's the newsgroup gnu.emacs.gnus (also available as
-@uref{http://dir.gmane.org/gmane.emacs.gnus.user,
-gmane.emacs.gnus.user}) which deals with general Gnus
+There's the newsgroup gnu.emacs.gnus which deals with general Gnus
questions. If you have questions about development versions of
Gnus, you should better ask on the ding mailing list, see below.
@@ -2124,9 +2121,7 @@ the above groups). If you speak German, there's
de.comm.software.gnus.
The ding mailing list (ding@@gnus.org) deals with development of
-Gnus. You can read the ding list via NNTP, too under the name
-@uref{http://dir.gmane.org/gmane.emacs.gnus.general,
-gmane.emacs.gnus.general} from news.gmane.org.
+Gnus.
@node FAQ 8-5
@subsubheading Question 8.5
diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi
index 4824cdc9621..afa45d10f09 100644
--- a/doc/misc/gnus.texi
+++ b/doc/misc/gnus.texi
@@ -2629,6 +2629,9 @@ type. @xref{Document Groups}.
Create one of the groups mentioned in @code{gnus-useful-groups}
(@code{gnus-group-make-useful-group}).
+@c FIXME: Gmane.org is no longer working; fix the Gmane referrences
+@c in this file accordingly.
+
@item G w
@kindex G w @r{(Group)}
@findex gnus-group-make-web-group
@@ -3234,7 +3237,7 @@ group by reverse date to see the latest news at the top and an
Debian daily news group @code{gmane.linux.debian.user.news} from
news.gmane.org. The @acronym{RSS} group corresponds to the Debian
weekly news RSS feed
-@url{http://packages.debian.org/unstable/newpkg_main.en.rdf},
+@url{https://packages.debian.org/unstable/newpkg_main.en.rdf},
@xref{RSS}.
@lisp
@@ -9164,10 +9167,10 @@ Use @uref{http://emacs-w3m.namazu.org/, emacs-w3m}.
Use @uref{http://w3m.sourceforge.net/, w3m}.
@item links
-Use @uref{http://links.sf.net/, Links}.
+Use @uref{https://almende.github.io/chap-links-library/, CHAP Links}.
@item lynx
-Use @uref{http://lynx.isc.org/, Lynx}.
+Use @uref{https://lynx.browser.org/, Lynx}.
@item html2text
Use html2text---a simple @acronym{HTML} converter included with Gnus.
@@ -9591,7 +9594,7 @@ Picons, on the other hand, reside on your own system, and Gnus will
try to match the headers to what you have (@pxref{Picons}).
Gravatars reside on-line and are fetched from
-@uref{http://www.gravatar.com/} (@pxref{Gravatars}).
+@uref{https://en.gravatar.com/} (@pxref{Gravatars}).
All these functions are toggles---if the elements already exist,
they'll be removed.
@@ -13897,7 +13900,7 @@ installed. You then define a server as follows:
@findex nntp-open-ssl-stream
@item nntp-open-ssl-stream
Opens a connection to a server over a @dfn{secure} channel. To use
-this you must have @uref{http://www.openssl.org, OpenSSL}
+this you must have @uref{https://www.openssl.org/, OpenSSL}
@ignore
@c Defunct URL, ancient package, so don't mention it.
or @uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL, SSLeay}
@@ -16411,7 +16414,7 @@ have to set this variable to @code{t}. The default is @code{nil}.
@code{nnmaildir} stores mail in the maildir format, with each maildir
corresponding to a group in Gnus. This format is documented here:
-@uref{http://cr.yp.to/proto/maildir.html}. @code{nnmaildir}
+@uref{https://cr.yp.to/proto/maildir.html}. @code{nnmaildir}
also stores extra information in the @file{.nnmaildir/} directory
within a maildir.
@@ -17083,7 +17086,7 @@ Some web sites have an RDF Site Summary (@acronym{RSS}).
@acronym{RSS} is a format for summarizing headlines from news related
sites (such as BBC or CNN). But basically anything list-like can be
presented as an @acronym{RSS} feed: weblogs, changelogs or recent
-changes to a wiki (e.g., @url{http://cliki.net/site/recent-changes}).
+changes to a wiki (e.g., @url{https://cliki.net/site/recent-changes}).
@acronym{RSS} has a quite regular and nice interface, and it's
possible to get the information Gnus needs to keep groups updated.
@@ -20864,6 +20867,7 @@ The kill to score conversion package isn't included in Emacs by default.
You can fetch it from the contrib directory of the Gnus distribution or
from
@uref{http://heim.ifi.uio.no/~larsi/ding-various/gnus-kill-to-score.el}.
+@c FIXME: The above URL no longer works.
If your old kill files are very complex---if they contain more
non-@code{gnus-kill} forms than not, you'll have to convert them by
@@ -21370,9 +21374,6 @@ to get a group name. By default this is @code{$HOME/Mail}.
FIXME: Say something more here.
-Documentation for swish-e may be found at the swish-e homepage
-@uref{http://swish-e.org}
-
@table @code
@item nnir-swish-e-program
@@ -23557,7 +23558,7 @@ represent the author of the message.
@cindex face
@findex gnus-article-display-face
The contents of a @code{Face} header must be a base64 encoded PNG image.
-See @uref{http://quimby.gnus.org/circus/face/} for the precise
+See @uref{https://quimby.gnus.org/circus/face/} for the precise
specifications.
The @code{gnus-face-properties-alist} variable affects the appearance of
@@ -23681,7 +23682,7 @@ in either monochrome @code{XBM} format or color @code{XPM} and
@vindex gnus-picon-databases
For instructions on obtaining and installing the picons databases,
point your Web browser at
-@uref{http://www.cs.indiana.edu/picons/ftp/index.html}.
+@uref{https://cs.indiana.edu/ftp/faces/picons/}.
If you are using Debian GNU/Linux, saying @samp{apt-get install
picon-.*} will install the picons where Gnus can find them.
@@ -23750,7 +23751,7 @@ interesting.
A gravatar is an image registered to an e-mail address.
-You can submit yours on-line at @uref{http://www.gravatar.com}.
+You can submit yours on-line at @uref{https://en.gravatar.com/}.
The following variables offer control over how things are displayed.
@@ -24147,8 +24148,7 @@ compute a hash collision up to a certain number of bits. The
resulting hashcash cookie is inserted in a @samp{X-Hashcash:} header.
For more details, and for the external application @code{hashcash} you
need to install to use this feature, see
-@uref{http://www.hashcash.org/}. Even more information can be found
-at @uref{http://www.camram.org/}.
+@uref{http://www.hashcash.org/}.
If you wish to generate hashcash for each message you send, you can
customize @code{message-generate-hashcash} (@pxref{Mail Headers, ,Mail
@@ -24999,7 +24999,7 @@ added to a group's @code{spam-process} parameter, the spam-marked
articles groups will be reported to the Gmane administrators via a
HTTP request.
-Gmane can be found at @uref{http://gmane.org}.
+Gmane was formerly found at @uref{http://gmane.org}.
@emph{WARNING}
@@ -26505,7 +26505,7 @@ but at the common table.@*
If you want to investigate the person responsible for this outrage,
you can point your (feh!) web browser to
-@uref{http://quimby.gnus.org/}. This is also the primary
+@uref{https://quimby.gnus.org/}. This is also the primary
distribution point for the new and spiffy versions of Gnus, and is
known as The Site That Destroys Newsrcs And Drives People Mad.
@@ -26567,9 +26567,7 @@ Gnus 5.10 on May 1st 2003 (24 releases).
On the January 4th 2004, No Gnus was begun.
-On April 19, 2010 Gnus development was moved to Git. See
-http://git.gnus.org for details (http://www.gnus.org will be updated
-with the information when possible).
+On April 19, 2010 Gnus development was moved to Git.
On the January 31th 2012, Ma Gnus was begun.
diff --git a/doc/misc/message.texi b/doc/misc/message.texi
index 7089bb5dfe3..9b79fe687d2 100644
--- a/doc/misc/message.texi
+++ b/doc/misc/message.texi
@@ -1143,7 +1143,7 @@ standards, OpenSSL and so on.
The @acronym{S/MIME} support in Message (and @acronym{MML}) can use
OpenSSL@. OpenSSL performs the actual @acronym{S/MIME} sign/encrypt
-operations. OpenSSL can be found at @uref{http://www.openssl.org/}.
+operations. OpenSSL can be found at @uref{https://www.openssl.org/}.
OpenSSL 0.9.6 and later should work. Version 0.9.5a cannot extract mail
addresses from certificates, and it insert a spurious CR character into
@acronym{MIME} separators so you may wish to avoid it if you would like
@@ -1291,7 +1291,7 @@ to change this behavior you can customize the
This causes to sign and encrypt in two passes, thus generating a
message that can be understood by PGP version 2.
-(Refer to @uref{http://www.gnupg.org/gph/en/pgp2x.html} for more
+(Refer to @uref{https://www.gnupg.org/gph/en/pgp2x.html} for more
information about the problem.)
@node Encrypt-to-self
diff --git a/doc/misc/mh-e.texi b/doc/misc/mh-e.texi
index 25dd53c4fb9..9d249fb0ecd 100644
--- a/doc/misc/mh-e.texi
+++ b/doc/misc/mh-e.texi
@@ -17,8 +17,8 @@
@set UPDATE-MONTH April, 2016
@c Other variables.
-@set MH-BOOK-HOME http://rand-mh.sourceforge.net/book/mh
-@set MH-E-HOME http://mh-e.sourceforge.net/
+@set MH-BOOK-HOME https://rand-mh.sourceforge.io/book/
+@set MH-E-HOME https://mh-e.sourceforge.io/
@c Copyright
@copying
@@ -256,9 +256,9 @@ This manual is available in both Info and online formats. The Info
version is distributed with Emacs and can be accessed with the
@command{info} command (@samp{info mh-e}) or within Emacs (@kbd{C-h i
m mh-e @key{RET}}). The online version is available at
-@uref{http://mh-e.sourceforge.net/manual/, SourceForge}. Another great
+@uref{https://mh-e.sourceforge.io/manual/, SourceForge}. Another great
online resource is the book
-@uref{http://rand-mh.sourceforge.net/book/, @cite{MH & nmh: Email for
+@uref{https://rand-mh.sourceforge.io/book/, @cite{MH & nmh: Email for
Users & Programmers}} (also known as @dfn{the MH book}).
I hope you enjoy this manual! If you have any comments, or suggestions
@@ -554,8 +554,8 @@ to install MH or tell MH-E where to find MH.
If you don't have MH on your system already, you must install a
variant of MH@. The Debian mh-e package does this for you
automatically (@pxref{Getting MH-E}). Most people use
-@uref{http://www.nongnu.org/nmh/, nmh}, but you may be interested in
-trying out @uref{http://mailutils.org/, GNU mailutils MH}, which
+@uref{https://www.nongnu.org/nmh/, nmh}, but you may be interested in
+trying out @uref{https://mailutils.org/, GNU mailutils MH}, which
supports IMAP@. Your GNU/Linux distribution probably has packages for
both of these.
@@ -2092,7 +2092,7 @@ This feature will be turned on by default if your system supports it.
The first header field used, if present, is the Gnus-specific
@samp{Face:} field@footnote{The @samp{Face:} field appeared in GNU
Emacs 21 and XEmacs. For more information, see
-@uref{http://quimby.gnus.org/circus/face/}.}.
+@uref{https://quimby.gnus.org/circus/face/}.}.
@cindex @command{uncompface}
@cindex Emacs, packages, @samp{x-face}
@@ -2100,6 +2100,7 @@ Emacs 21 and XEmacs. For more information, see
@cindex @samp{x-face} package
@vindex mh-show-xface
+@c FIXME: These URLs do not seem to work any more.
Next is the traditional @samp{X-Face:} header field@footnote{The
display of this field requires the
@uref{ftp://ftp.cs.indiana.edu/pub/faces/compface/compface.tar.Z,
@@ -2122,7 +2123,7 @@ Finally, MH-E will display images referenced by the
@samp{X-Face:} fields are present@footnote{The display of the images
requires the @uref{https://www.gnu.org/software/wget/wget.html,
@command{wget} program} to fetch the image and the @command{convert}
-program from the @uref{http://www.imagemagick.org/script/index.php,
+program from the @uref{https://www.imagemagick.org/script/index.php,
ImageMagick suite}.}. Of the three header fields this is the most
efficient in terms of network usage since the image doesn't need to be
transmitted with every single mail. The option
@@ -2509,9 +2510,9 @@ For additional information on buttons, see
@ref{Article Buttons,,,gnus}, and @ref{MIME Commands,,,gnus}.
@end ifinfo
@ifnotinfo
-the chapters @uref{http://www.gnus.org/manual/gnus_101.html#SEC101,
+the chapters @uref{https://www.gnus.org/manual/gnus_101.html#SEC101,
Article Buttons} and
-@uref{http://www.gnus.org/manual/gnus_108.html#SEC108, MIME Commands}
+@uref{https://www.gnus.org/manual/gnus_108.html#SEC108, MIME Commands}
in the @cite{The Gnus Manual}.
@end ifnotinfo
@@ -2603,7 +2604,7 @@ and @code{mm-html-inhibit-images}
(@pxref{Display Customization,,,emacs-mime}).
@end ifinfo
@ifnotinfo
-(see section @uref{http://www.gnus.org/manual/emacs-mime_6.html,
+(see section @uref{https://www.gnus.org/manual/emacs-mime_6.html,
Display Customization} in the @cite{The Emacs MIME Manual}).
@end ifnotinfo
@c -------------------------
@@ -2623,7 +2624,7 @@ the option @code{mm-w3m-safe-url-regexp}
(@pxref{Display Customization,,,emacs-mime}).
@end ifinfo
@ifnotinfo
-(see section @uref{http://www.gnus.org/manual/emacs-mime_6.html,
+(see section @uref{https://www.gnus.org/manual/emacs-mime_6.html,
Display Customization} in the @cite{The Emacs MIME Manual}).
@end ifnotinfo
@c -------------------------
@@ -2647,10 +2648,10 @@ For a couple more sources of information about
the Gnus command @kbd{W h} (@pxref{Article Washing,,,gnus}).
@end ifinfo
@ifnotinfo
-see section @uref{http://www.gnus.org/manual/emacs-mime_6.html,
+see section @uref{https://www.gnus.org/manual/emacs-mime_6.html,
Display Customization} in the @cite{The Emacs MIME Manual} and the
documentation for the Gnus command @kbd{W h} (see section
-@uref{http://www.gnus.org/manual/gnus_48.html#Article-Washing, Article
+@uref{https://www.gnus.org/manual/gnus_48.html#Article-Washing, Article
Washing} in the
@cite{The Gnus Manual}).
@end ifnotinfo
@@ -2729,7 +2730,7 @@ Drafts}).
You can read encrypted or signed PGP or GPG messages with
MH-E@footnote{This feature depends on post-5.10 versions of Gnus.
@cite{MIME Security with OpenPGP} is documented in
-@uref{http://www.rfc-editor.org/rfc/rfc3156.txt, RFC 3156}. However,
+@uref{https://www.rfc-editor.org/rfc/rfc3156.txt, RFC 3156}. However,
MH-E can also decrypt old-style PGP messages that are not in MIME
format.}. This section assumes that you already have a good
understanding of GPG and have set up your keys appropriately.
@@ -5050,7 +5051,7 @@ for the next hook function. The standard prefix
@vindex mh-yank-behavior
For example, if you use the hook function
-@uref{http://www.emacswiki.org/emacs/TrivialCite,
+@uref{https://www.emacswiki.org/emacs/TrivialCite,
@code{trivial-cite}} (which is NOT part of Emacs), set
@code{mh-yank-behavior} to @samp{Body and Header}.
@@ -5166,11 +5167,11 @@ contains the value of the @samp{X-Face:} header field.
The @samp{X-Face:} header field, which is a low-resolution, black and
white image, can be generated using the
@uref{ftp://ftp.cs.indiana.edu/pub/faces/compface/compface.tar.Z,
-@command{compface}} command. The @uref{http://www.dairiki.org/xface/,
+@command{compface}} command. The @uref{https://www.dairiki.org/xface/,
@cite{Online X-Face Converter}} is a useful resource for quick
conversion of images into @samp{X-Face:} header fields.
-Use the @uref{http://quimby.gnus.org/circus/face/make-face,
+Use the @uref{https://quimby.gnus.org/circus/face/make-face,
@command{make-face}} script to convert a JPEG image to the higher
resolution, color, @samp{Face:} header field.
@@ -5198,7 +5199,7 @@ defined by this option doesn't exist.
MH-E has the capability to create multimedia messages. It uses the
@sc{mime} (Multipurpose Internet Mail Extensions)
protocol@footnote{@sc{mime} is defined in
-@uref{http://www.rfc-editor.org/rfc/rfc2045.txt, RFC 2045}.} The
+@uref{https://www.rfc-editor.org/rfc/rfc2045.txt, RFC 2045}.} The
@sc{mime} protocol allows you to incorporate images, sound, video,
binary files, and even commands that fetch a file with @samp{ftp} when
your recipient reads the message!
@@ -5231,7 +5232,7 @@ Meta Language) tags@footnote{
@end ifinfo
@ifnotinfo
See the section Composing in
-@uref{http://www.gnus.org/manual/emacs-mime.html, @cite{The Emacs MIME
+@uref{https://www.gnus.org/manual/emacs-mime.html, @cite{The Emacs MIME
Manual}}.
@end ifnotinfo
}. The option @code{mh-compose-insertion} can be used to choose
@@ -5537,7 +5538,7 @@ been formatted by @kbd{C-c C-e}.
@cindex RFC 3156
MH-E can sign and encrypt messages as defined in
-@uref{http://www.rfc-editor.org/rfc/rfc3156.txt, RFC 3156}. If you
+@uref{https://www.rfc-editor.org/rfc/rfc3156.txt, RFC 3156}. If you
should choose to sign or encrypt your message, use one of the
following commands to do so any time before sending your message.
@@ -6909,7 +6910,7 @@ IndexDir /home/user/Mail
IndexFile /home/user/Mail/.swish/index
IndexName "Mail Index"
IndexDescription "Mail Index"
-IndexPointer "http://nowhere"
+IndexPointer "https://nowhere"
IndexAdmin "nobody"
#MetaNames automatic
IndexReport 3
@@ -7630,7 +7631,7 @@ Whitelisted message face
@cindex spam filters, SpamAssassin
@cindex spam filters, bogofilter
-MH-E depends on @uref{http://spamassassin.apache.org/, SpamAssassin},
+MH-E depends on @uref{https://spamassassin.apache.org/, SpamAssassin},
@uref{http://bogofilter.sourceforge.net/, bogofilter}, or
@uref{http://spamprobe.sourceforge.net/, SpamProbe} to throw the dreck
away. This chapter describes briefly how to configure these programs
@@ -7705,7 +7706,7 @@ MH-E can work with.
SpamAssassin is one of the more popular spam filtering programs. Get
it from your local distribution or from the
-@uref{http://spamassassin.apache.org/, SpamAssassin web site}.
+@uref{https://spamassassin.apache.org/, SpamAssassin web site}.
To use SpamAssassin, add the following recipes to @file{~/.procmailrc}:
@@ -8530,11 +8531,13 @@ expressions to ensure that MH-E and highlighting perform well.
@cindex Unix commands, @command{procmail}
@cindex mailing lists, reading
-This appendix explains how to use @uref{http://www.procmail.org/,
-procmail} to file mail from mailing lists into folders which can then
+This appendix explains how to use procmail, which can
+file mail from mailing lists into folders which can then
be read easily with MH-E@footnote{The MH equivalent, @command{slocal},
-can be used as well, but procmail is more flexible and more packages
-exist for procmail than for slocal.}. Some mailing lists have such
+can be used as well, but procmail was more flexible and more packages
+exist for procmail than for slocal.}. Unfortunately, procmail is no
+longer recommended due to its security vulnerabilities.
+Some mailing lists have such
high traffic that Gnus must be used and I discuss how to use Gnus
side-by-side with MH-E.
@@ -8764,7 +8767,7 @@ in all new releases).
@cindex Debian
If you use Debian, you can install the Debian
-@uref{http://packages.debian.org/unstable/mail/mh-e, mh-e package}
+@uref{https://packages.debian.org/unstable/mail/mh-e, mh-e package}
instead.
@cindex files, @samp{MH-E-NEWS}
@@ -8813,7 +8816,7 @@ hands several times since then. Jim Larus wanted to do something
similar for GNU Emacs, and ended up completely rewriting it that same
year. In 1989, Stephen Gildea picked it up and added many
improvements. Bill Wohler then took over in 2000 and moved its
-development to @uref{http://sourceforge.net/, SourceForge} where it
+development to @uref{https://sourceforge.net/, SourceForge} where it
lives today.
@menu
@@ -9040,8 +9043,8 @@ Bill Wohler, August 2008
@c LocalWords: Tennex texi texinfo Thelen thelenm
@c LocalWords: UCI undeleted whatnow wohler xmh ypcat
@c
-@c See http://www.oreilly.com/oreilly/author/stylesheet.html.
-@c See http://en.wikipedia.org/.
+@c See https://oreillymedia.github.io/production-resources/styleguide/.
+@c See https://en.wikipedia.org/.
@c
@c Note the lowercase mh which is needed to avoid hits in the
@c functions and variables. Occasionally, check for accidental
diff --git a/doc/misc/newsticker.texi b/doc/misc/newsticker.texi
index 5db3f43b2b9..502ed1d5b1f 100644
--- a/doc/misc/newsticker.texi
+++ b/doc/misc/newsticker.texi
@@ -39,7 +39,6 @@ modify this GNU manual.''
@title Newsticker---a feed reader for Emacs
@author Ulf Jasper
@author @email{ulf.jasper@@web.de}
-@author @uref{http://ulf.epplejasper.de/}
@page
@vskip 0pt plus 1filll
@insertcopying
@@ -590,8 +589,8 @@ Newsticker works with the standard RSS and Atom formats listed below
@itemize
@item RSS 0.91 (see @uref{http://backend.userland.com/rss091})
@item RSS 0.92 (see @uref{http://backend.userland.com/rss092})
-@item RSS 1.0 (see @uref{http://purl.org/rss/1.0/spec})
-@item RSS 2.0 (see @uref{http://blogs.law.harvard.edu/tech/rss})
+@item RSS 1.0 (see @uref{http://web.resource.org/rss/1.0/spec})
+@item RSS 2.0 (see @uref{https://cyber.harvard.edu/rss/rss.html})
@end itemize
@subheading Atom formats
diff --git a/doc/misc/org.texi b/doc/misc/org.texi
index de3b7bbed49..adb795e1e6c 100644
--- a/doc/misc/org.texi
+++ b/doc/misc/org.texi
@@ -3527,7 +3527,7 @@ string followed by a colon. There can be no space after the colon. The
following list shows examples for each link type.
@example
-http://www.astro.uva.nl/~dominik @r{on the web}
+https://api.uva.nl/ @r{on the web}
doi:10.1000/182 @r{DOI for an electronic resource}
file:/home/dominik/images/jupiter.jpg @r{file, absolute path}
/home/dominik/images/jupiter.jpg @r{same as above}
diff --git a/doc/misc/url.texi b/doc/misc/url.texi
index bad7701daf1..e72d9bfe3d2 100644
--- a/doc/misc/url.texi
+++ b/doc/misc/url.texi
@@ -440,8 +440,7 @@ Specifies whether confirmation is required to accept cookies.
@defopt url-cookie-multiple-line
Specifies whether to put all cookies for the server on one line in the
-HTTP request to satisfy broken servers like
-@url{http://www.hotmail.com}.
+HTTP request to satisfy broken servers.
@end defopt
@defopt url-cookie-trusted-urls
diff --git a/doc/misc/wisent.texi b/doc/misc/wisent.texi
index b404c2a82dc..2cf3b2e2fce 100644
--- a/doc/misc/wisent.texi
+++ b/doc/misc/wisent.texi
@@ -135,7 +135,7 @@ technique of F. DeRemer and T. Pennello described in:
@quotation
@cite{Efficient Computation of LALR(1) Look-Ahead Sets}@*
October 1982, ACM TOPLAS Vol 4 No 4, 615--49,
-@uref{http://dx.doi.org/10.1145/69622.357187}.
+@uref{https://doi.org/10.1145/69622.357187}.
@end quotation
@item