<!--#set var="css" value="sxemacs.css" -->
<!--#set var="title" value="SXEmacs Website" -->
<!--#set var="banner" value="Redefining Emacs" -->
-<!--#set var="copyright" value="2004 - 2012 Steve Youngs" -->
+<!--#set var="copyright" value="2004 - 2016 Steve Youngs" -->
<!--#include virtual="/templates/header.template" -->
<!--#include virtual="/templates/menu.template" -->
Hmm, that's actually not an easy question to answer. At
least, not easy to answer completely. At the most basic of
levels, SXEmacs is a text editor. If you've ever used
- <a href="http://www.gnu.org/software/emacs/">GNU/Emacs</a> or
+ <a href="https://www.gnu.org/software/emacs/">GNU/Emacs</a> or
<a href="http://www.xemacs.org/">XEmacs</a> you've probably
seen the description that goes something like...
</p>
<b>Embeddable kbd macros</b>.
<p>
This one is for JWZ. See point 1.A of
- <a href="http://www.jwz.org/doc/xemacs-wishlist.html">JWZ's XEmacs wish list</a>
+ <a href="https://www.jwz.org/doc/xemacs-wishlist.html">JWZ's XEmacs wish list</a>
</p>
</li>
<li>
<b>FHS Compliant Install Hierarchy</b>
<p>
SXEmacs now installs to a much more
- <a href="http://www.pathname.com/fhs/">FHS</a> compliant
+ <a href="https://www.pathname.com/fhs/">FHS</a> compliant
location.
</p>
</li>