All of SXEmacs' http URLs are now https. WooHoo!

I used this shell snippet  to create this changeset...

for sub in www git issues downloads; do
    git grep -l http://$sub.sxemacs|grep -v ChangeLog.d|
       xargs sed -i "s@\(http\)\(://$sub.sxemacs.org\)@\1s\2@"
done

Signed-off-by: Steve Youngs <steve@sxemacs.org>

diff --git a/BUGS b/BUGS
index a93b52e..db0c9b7 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -13,7 +13,7 @@ it.  But before you do, make sure...
 
        o You have checked the PROBLEMS file and the FAQ (section 2)
          that came with your version of SXEmacs (read the FAQ with:
-         `C-h F'), and also search http://issues.sxemacs.org/ to see
+         `C-h F'), and also search https://issues.sxemacs.org/ to see
          if your bug has already been reported and/or fixed.
 
 If you discover that your bug is already known to us but still hasn't
@@ -21,6 +21,6 @@ been fixed, you should still let us know about it.  Some bugs need a
 little motivating to get fixed. :-)  Unless you have new or different
 information about the bug to add, the simplest way of letting us know
 you are seeing it too is to "vote" for the bug at
-http://issues.sxemacs.org/.
+https://issues.sxemacs.org/.
 
 

diff --git a/INSTALL b/INSTALL
index 6935456..b0b7faf 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -365,7 +365,7 @@ There is a script under contrib called tar-build-failure.sh that
 will attempt to gather this information and create a tar file with
 helpful logs.
 
-Before submitting a report at http://issues.sxemacs.org/, please show
+Before submitting a report at https://issues.sxemacs.org/, please show
 up either on the mailing list or the IRC channel.  The developers can
 tell you in much greater detail what they need and how you can get the
 files and information you need.

diff --git a/PROBLEMS b/PROBLEMS
index e76f5d0..23bb9b9 100644 (file)
--- a/PROBLEMS
+++ b/PROBLEMS
@@ -413,7 +413,7 @@ have a ImageMagick that is using OpenMP (currently only svn HEAD).  To
 fix this you will need to rebuild ImageMagick, making sure that you
 configure it using --disable-openmp.
 
-See: <http://issues.sxemacs.org/show_bug.cgi?id=104>
+See: <https://issues.sxemacs.org/show_bug.cgi?id=104>
 
 ** Multimedia Goodness
 
@@ -457,7 +457,7 @@ effectively circumvent this issue.
 
 This is a known bug (#13 in our bug database).  At the moment the only
 advise we can give is: do not use sentinels before 22.1.7.
-Also see our bug database at http://issues.sxemacs.org
+Also see our bug database at https://issues.sxemacs.org
 
 *** make-media-stream seems to recognise any file as valid audio
 

diff --git a/configure.ac b/configure.ac
index d6b2c8e..ec40bfb 100644 (file)
--- a/configure.ac
+++ b/configure.ac
@@ -9,7 +9,7 @@ dnl Autoconf startup.
 dnl -------------------------------------------------------------------------
 
 AC_PREREQ([2.62])
-AC_INIT([SXEmacs], [SXEM4CS_VERSION], [http://issues.sxemacs.org/])
+AC_INIT([SXEmacs], [SXEM4CS_VERSION], [https://issues.sxemacs.org/])
 AC_CONFIG_HEADER([src/config.h])
 AC_CONFIG_SRCDIR([src/lisp.h])
 AC_CONFIG_AUX_DIR([.])

diff --git a/contrib/git-for-steve.sh b/contrib/git-for-steve.sh
index e6fd4aa..48b8884 100755 (executable)
--- a/contrib/git-for-steve.sh
+++ b/contrib/git-for-steve.sh
@@ -55,7 +55,7 @@
 ##      format.headers, sendmail.to, sendmail.from
 ##
 ##    It also ensures that origin points to the right place
-##    (http://git.sxemacs.org/sxemacs), optionally makes sure your
+##    (https://git.sxemacs.org/sxemacs), optionally makes sure your
 ##    remote is set up correctly, that you have a "for-steve" tracking
 ##    branch, and adds a devkey.$INITIALS tag containing your public
 ##    GnuPG key if available, which can be pushed to your remote.
@@ -163,18 +163,18 @@ set_email()
 [ -n "$(git config user.email)" ] || set_email
 
 ## Tracking branch "for-steve"
-# Make sure origin points to http://git.sxemacs.org/sxemacs
+# Make sure origin points to https://git.sxemacs.org/sxemacs
 CHECK_ORIGIN=${CHECK_ORIGIN:-true}
 if [ "${CHECK_ORIGIN}" != "false" ]; then
     ORIGIN_URL=$(git config remote.origin.url)
-    if [ "${ORIGIN_URL}" != "http://git.sxemacs.org/sxemacs" ]; then
+    if [ "${ORIGIN_URL}" != "https://git.sxemacs.org/sxemacs" ]; then
        cat<<EOF
 
 **[Bad origin]********************************************************
 WARNING: origin URL is WRONG.
 
  It is currently set to: ${ORIGIN_URL}
-But it SHOULD be set to: http://git.sxemacs.org/sxemacs
+But it SHOULD be set to: https://git.sxemacs.org/sxemacs
 
 It you are absolutely 110% sure that your origin is correct, abort now
 with C-c, and re-run this script with the environment variable, 
@@ -184,7 +184,7 @@ are going to reset it for you.
                             Hit [RETURN] to continue, or C-c to abort.
 EOF
        read junk
-       git remote set-url origin http://git.sxemacs.org/sxemacs
+       git remote set-url origin https://git.sxemacs.org/sxemacs
     fi
 fi
 
@@ -677,7 +677,7 @@ cat<<EOF
 | or from the command line via 'info sppm'.                          |
 |                                                                    |
 | Also, now would be a good time for you to head over to             |
-| http://www.sxemacs.org/lists.html and subscribe to our mailing     |
+| https://www.sxemacs.org/lists.html and subscribe to our mailing     |
 | lists.                                                             |
 |--------------------------------------------------------------------|
 | Thank you, and do drop into #sxemacs on freenode IRC for a chat    |

diff --git a/etc/BETA b/etc/BETA
index 9499761..2af46fe 100644 (file)
--- a/etc/BETA
+++ b/etc/BETA
@@ -52,7 +52,7 @@ with the list itself, they should be brought to the attention of the
 SXEmacs Mailing List Owner <sxemacs-LIST-owner@sxemacs.org>.  All
 public mailing lists are archived.  The URL is
 
-            http://www.sxemacs.org/list-archives/html/sxemacs-LIST
+            https://www.sxemacs.org/list-archives/html/sxemacs-LIST
 
 Note that the sxemacs-LIST-admin address is used internally by the
 Mailman software; it is NOT a synonym for sxemacs-LIST-request.
@@ -62,7 +62,7 @@ Mailman software; it is NOT a synonym for sxemacs-LIST-request.
 
 Subscription, unsubscription, and options (such as digests and
 temporarily suspending delivery) can be accomplished via the web
-interface at <http://www.sxemacs.org/mailman/listinfo/sxemacs-LIST>.
+interface at <https://www.sxemacs.org/mailman/listinfo/sxemacs-LIST>.
 
 *** Subscribing by e-mail
 -------------------------

diff --git a/etc/DISTRIB b/etc/DISTRIB
index f4f92df..c25d953 100644 (file)
--- a/etc/DISTRIB
+++ b/etc/DISTRIB
@@ -5,12 +5,12 @@
 SXEmacs is available primarily via the GIT repositories.  The
 main repository is:
 
-      http://git.sxemacs.org/sxemacs
+      https://git.sxemacs.org/sxemacs
 
 The following git commands will "check out" the latest SXEmacs sources
 from the above repository:
 
-       $ git clone http://git.sxemacs.org/sxemacs
+       $ git clone https://git.sxemacs.org/sxemacs
 
 That will "check out" the latest SXEmacs sources and place them into
 $PWD/sxemacs
@@ -21,10 +21,10 @@ to determine what is the most recent version
 
 Source tarballs are available for download at:
 
-     http://downloads.sxemacs.org/releases/
+     https://downloads.sxemacs.org/releases/
 
 
 Occasional "snapshot" tarballs are made available between releases and
 they can be found at:
 
-     http://downloads.sxemacs.org/snapshots/
+     https://downloads.sxemacs.org/snapshots/

diff --git a/etc/MAILINGLISTS b/etc/MAILINGLISTS
index 656a0f2..9742f33 100644 (file)
--- a/etc/MAILINGLISTS
+++ b/etc/MAILINGLISTS
@@ -31,7 +31,7 @@ To unsubscribe, send an email to LISTNAME-request@sxemacs.org with
 List Archives:
 -------------
 A browsable archive of these lists is available at
-http://www.sxemacs.org/list-archives/html/LISTNAME/
+https://www.sxemacs.org/list-archives/html/LISTNAME/
 
 Problems:
 --------

diff --git a/etc/NEWS b/etc/NEWS
index 0a9461e..c35713b 100644 (file)
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -160,7 +160,7 @@ git-isms.
 
 You can now grab the SXEmacs sources via git with...
 
-   git clone http://git.sxemacs.org/sxemacs
+   git clone https://git.sxemacs.org/sxemacs
 
 
 * Changes in SXEmacs 22.1.12 (Fiat)
@@ -301,7 +301,7 @@ It can now take a 2nd arg for extension stripping.
 32, 33, 34, 35, 36, 37, 38, 39, 40, 42, 45, 46, 47, 48, 49, 50, 51,
 53, 54, 55, 56, 57, 58, 59, 60, 61, 62
 
-See http://issues.sxemacs.org/ for the details.
+See https://issues.sxemacs.org/ for the details.
 
 ** Build chain fixes and improvements -- Freundt, Ferreira.
 
@@ -705,7 +705,7 @@ Lots of changes to the autoconf configure script
                dialogs  -- no lucid
                widgets  -- no lucid
        - Set configure's "bugreport address" to
-         http://issues.sxemacs.org. 
+         https://issues.sxemacs.org. 
        - Fix gdbm/berkdb detection
        - Improve libc version detection
 
@@ -810,7 +810,7 @@ SXEmacs now has server sockets (Yay!).  See
 ** bug-reporter update -- Youngs.
 
 `report-sxemacs-bug' now directs people to our BugZilla installation
-at http://issues.sxemacs.org/
+at https://issues.sxemacs.org/
 
 ** Documentation updates/fixes/improvements -- Youngs, Ferreira, Freundt.
 

diff --git a/etc/sample.init.el b/etc/sample.init.el
index f9f283a..85cdb3a 100644 (file)
--- a/etc/sample.init.el
+++ b/etc/sample.init.el
@@ -125,7 +125,7 @@
 ;;;       "member-only" posts because of SPAM issues, but subscribing
 ;;;       isn't all that painful (normal mailman procedure) and the
 ;;;       archives are publically accessible at
-;;;       http://www.sxemacs.org/list-archives/html/
+;;;       https://www.sxemacs.org/list-archives/html/
 
 ;;; -- the XEmacs newsgroup, comp.emacs.xemacs.  The SXEmacs developers
 ;;;       don't normally watch this newsgroup very closely.

diff --git a/etc/sxemacs.1 b/etc/sxemacs.1
index 50da762..981f739 100644 (file)
--- a/etc/sxemacs.1
+++ b/etc/sxemacs.1
@@ -676,7 +676,7 @@ searches for packages in these places by default...
 
 .PP
 .SH BUGS AND HELP
-There is a issue tracker at http://issues.sxemacs.org/, for reporting
+There is a issue tracker at https://issues.sxemacs.org/, for reporting
 .I SXEmacs
 bugs.  But before reporting something
 as a bug, please try to be sure that it really is a bug, not a
@@ -792,7 +792,7 @@ For more information about \fISXEmacs\fP, see the
 look in the file $PREFIX/share/sxemacs-$VERSION/etc/NEWS,
 or point your Web browser at
 .PP
-http://www.sxemacs.org/
+https://www.sxemacs.org/
 .PP
 for up-to-the-minute information about \fISXEmacs\fP.
 .PP
@@ -804,4 +804,4 @@ inside of \fISXEmacs\fP.
 .PP
 The latest version of \fISXEmacs\fP can be downloaded from
 .PP
-http://downloads.sxemacs.org/
+https://downloads.sxemacs.org/

diff --git a/info/internals/internals.texi b/info/internals/internals.texi
index 372db74..486a906 100644 (file)
--- a/info/internals/internals.texi
+++ b/info/internals/internals.texi
@@ -1069,7 +1069,7 @@ code base we would fork from.
 And then, on December 6th, 2004 at 03:24 (GMT) the XEmacs 21.4.16 source
 code was imported into SXEmacs' main source repository.  Three weeks
 later, SXEmacs was announced to the world
-@uref{http://www.sxemacs.org/pipermail/sxemacs-devel/2004-December/000224.html,
+@uref{https://www.sxemacs.org/pipermail/sxemacs-devel/2004-December/000224.html,
 in this post}.
 
 It should be noted that even though some feathers were ruffled by the

diff --git a/info/lispref/ffi.texi b/info/lispref/ffi.texi
index 5546dff..0b29a8d 100644 (file)
--- a/info/lispref/ffi.texi
+++ b/info/lispref/ffi.texi
@@ -938,7 +938,7 @@ The options are keyword-value-pairs and are set via
 @end defun
 
 @example
-(curl:download "http://www.sxemacs.org"
+(curl:download "https://www.sxemacs.org"
   (expand-file-name (make-temp-name "curl") (temp-directory)))
      @result{} 0
 @end example

diff --git a/info/sppm.texi b/info/sppm.texi
index 9d2f81c..98ef198 100644 (file)
--- a/info/sppm.texi
+++ b/info/sppm.texi
@@ -115,7 +115,7 @@ This is the @value{EDITION} edition of the @cite{SXEmacs Policies & Procedures M
 
 This document, as its name implies, is directed towards anyone who is
 actively involved (or thinking of becoming actively involved) in the
-development of @uref{http://www.sxemacs.org/, SXEmacs}.
+development of @uref{https://www.sxemacs.org/, SXEmacs}.
 
 @menu
 * Mission Statement::           Why we do what we do
@@ -170,13 +170,13 @@ Including@dots{}
 
 @itemize @bullet
 @item
-@uref{http://www.sxemacs.org/, The SXEmacs Web Site}
+@uref{https://www.sxemacs.org/, The SXEmacs Web Site}
 @item
-@uref{http://downloads.sxemacs.org/, Release and Snapshot Tarballs}
+@uref{https://downloads.sxemacs.org/, Release and Snapshot Tarballs}
 @item
 @uref{irc://irc.freenode.net/#sxemacs, The SXEmacs IRC channel}
 @item
-@uref{http://issues.sxemacs.org/, The SXEmacs Issue Tracker} @ref{Bug Reports}
+@uref{https://issues.sxemacs.org/, The SXEmacs Issue Tracker} @ref{Bug Reports}
 @ref{Feature Requests} @ref{Support Requests}.
 @item
 @uref{http://store.sxemacs.org/, SXEmacs Merchandise}
@@ -218,11 +218,11 @@ mailing list.
 @cindex source
 @cindex tarball
 
-@uref{http://downloads.sxemacs.org/releases/, SXEmacs release downloads} is
+@uref{https://downloads.sxemacs.org/releases/, SXEmacs release downloads} is
 where you'll find release tarballs and release to release patches
 available for download.
 
-@uref{http://downloads.sxemacs.org/snapshots/, SXEmacs snapshot downloads}
+@uref{https://downloads.sxemacs.org/snapshots/, SXEmacs snapshot downloads}
 is where you can find snapshot tarballs which are uploaded from time
 to time.  Please note that these snapshots can sometimes be very
 unstable.
@@ -302,7 +302,7 @@ No IRC client
 
 You don't have an IRC client but still want to shoot the breeze with
 us on IRC?  Then we have an answer for you@dots{}
-@uref{http://www.sxemacs.org/irc.html, Chat from the web}.
+@uref{https://www.sxemacs.org/irc.html, Chat from the web}.
 @end itemize
 
 @node Merchandise,, IRC, Online Presence
@@ -942,7 +942,7 @@ correct, and set up your ``for-steve'' tracking branch.
 @subheading Preparing a patch from a git repo
 
 Are you in the right place?  You cloned the SXEmacs sources with
-@code{git clone http://git.sxemacs.org/sxemacs}.
+@code{git clone https://git.sxemacs.org/sxemacs}.
 
 Yes?  OK, great, read on.
 
@@ -1117,7 +1117,7 @@ acknowledge it quickly.
 So how quick is quickly?  Anything greater than 48 hours is @emph{slow}.
 We should try to get an initial ack out within 24 hours of the feature
 request hitting the mailing list@footnote{All legitimate feature requests
-should eventually end up on the @uref{http://issues.sxemacs.org/, SXEmacs
+should eventually end up on the @uref{https://issues.sxemacs.org/, SXEmacs
 Issue Tracker}.}.  I totally understand that the 24 hour turn-around
 won't always be possible.  Often there'll be extenuating circumstances
 (I'm writing this right now in the middle of a 2 week period with no
@@ -1145,7 +1145,7 @@ feature request that is more than 48 hours old and hasn't been
 acknowledged, it is @strong{YOUR} responsibility to do something about
 it.
 
-A feature request on our @uref{http://issues.sxemacs.org/, Issue
+A feature request on our @uref{https://issues.sxemacs.org/, Issue
 Tracker} is a issue that has the @dfn{FeatReq} flag set and the
 severity set to @dfn{enhancement}.
 
@@ -1175,7 +1175,7 @@ As a matter of fact, worry if you don't see any bug reports.  That
 would mean we aren't working hard enough. :-)
 
 All bug reports have to be submitted to our
-@uref{http://issues.sxemacs.org/, Issue Tracker}.  So it goes without
+@uref{https://issues.sxemacs.org/, Issue Tracker}.  So it goes without
 saying that you already have an account on our Issue Tracker, and if
 you don't, go get one @emph{now}.
 
@@ -1185,7 +1185,7 @@ the issue tracker itself.  @emph{DO NOT} follow up to a bug report on
 the mailing list.  If a bug report is submitted to the mailing list
 initially (because the submitter wasn't aware of our Issue Tracker),
 the person submitting the report should be directed to our
-@uref{http://issues.sxemacs.org/, Issue Tracker}.  If they are
+@uref{https://issues.sxemacs.org/, Issue Tracker}.  If they are
 unwilling or unable to do so, one of us will do so.
 
 If a bug report results in a patch and merge request, the summary of
@@ -1204,7 +1204,7 @@ lead, or whoever is responsible for making releases.
 
 From time to time, at the project lead's discretion, a release
 will be made and tarballs created and made available on
-@uref{http://downloads.sxemacs.org/releases/, the SXEmacs download site}.
+@uref{https://downloads.sxemacs.org/releases/, the SXEmacs download site}.
 
 The decision as to @emph{when} to cut a release is generally
 influenced by two factors:
@@ -1327,7 +1327,7 @@ done
 @end smallexample
 @item
 Move the tarballs, diffs, GnuPG sigs, and md5sums to
-@uref{http://downloads.sxemacs.org/releases/, SXEmacs Download Site}.
+@uref{https://downloads.sxemacs.org/releases/, SXEmacs Download Site}.
 
 @smallexample
 for file in *.@{bz2,gz,lzma,xz,md5,asc@}; do
@@ -1473,10 +1473,10 @@ We don't actively try to recruit new developers in any kind of formal
 way.  What we do is use SXEmacs for everything everyday and not hide
 the fact that we do. :-)  That in itself makes people curious and some
 ask about this thing called @dfn{SXEmacs}.  Show them what it is,
-point them to the @uref{http://www.sxemacs.org/, web site}, encourage
+point them to the @uref{https://www.sxemacs.org/, web site}, encourage
 them to subscribe to @email{sxemacs-devel@@sxemacs.org, SXEmacs
 Devel}, and even help them get an account on
-@uref{http://issues.sxemacs.org/, Our Issue Tracker}.  And low and
+@uref{https://issues.sxemacs.org/, Our Issue Tracker}.  And low and
 behold!  We have a new developer.
 
 One recruitment tool that we do have is @dfn{sxemacs.org} email
@@ -1514,13 +1514,13 @@ The main repository is that of the Project Lead (@sy{}).  It is
 located at:
 
 @smallexample
-  http://git.sxemacs.org/sxemacs
+  https://git.sxemacs.org/sxemacs
 @end smallexample
 
 Checking out a copy of SXEmacs is as easy as:
 
 @smallexample
-  git clone http://git.sxemacs.org/sxemacs
+  git clone https://git.sxemacs.org/sxemacs
 @end smallexample
 
 The chapter on patches @pxref{Patches} will show you how to prepare
@@ -1559,7 +1559,7 @@ user@@host ~ $ cd !$
 user@@host ~/sxemacs $ git init --bare
 user@@host ~/sxemacs $ echo @dfn{Your Name's SXEmacs Repo} > description
 user@@host ~/sxemacs $ exit
-user@@localhost ~ $ git clone http://git.sxemacs.org/sxemacs
+user@@localhost ~ $ git clone https://git.sxemacs.org/sxemacs
 user@@localhost ~ $ cd sxemacs
 user@@localhost ~/sxemacs $ contrib/git-for-steve.sh
 @end smallexample
@@ -1694,7 +1694,7 @@ Git makes it as easy to create a private repo as getting a checkout
 of the source code. In fact, that is all you have to do.
 
 @smallexample
-  git clone http://git.sxemacs.org/sxemacs
+  git clone https://git.sxemacs.org/sxemacs
 @end smallexample
 
 You may want to follow some of the steps in @xref{Automating with
@@ -1717,7 +1717,7 @@ More details at @xref{Setting up a publicly accessible repo}.
 
 As previously mentioned, the master SXEmacs repo is at:
 @smallexample
-  http://git.sxemacs.org/sxemacs
+  https://git.sxemacs.org/sxemacs
 @end smallexample
 
 Some of these repos may not be publicly accessible or may not be
@@ -1746,8 +1746,8 @@ git://github.com/hroptatyr/sxemacs.git
 
 And of course the main repo (Steve's) is at:
 
-http://git.sxemacs.org/sxemacs
-http://git.sxemacs.org/website  (our website is under git too)
+https://git.sxemacs.org/sxemacs
+https://git.sxemacs.org/website  (our website is under git too)
 
 @subheading The tla repository for versions upto 22.1.12
 

diff --git a/info/sxemacs-faq.texi b/info/sxemacs-faq.texi
index 8f016c4..4cdd3d9 100644 (file)
--- a/info/sxemacs-faq.texi
+++ b/info/sxemacs-faq.texi
@@ -519,14 +519,14 @@ The current development line will become 22.1.16.
 The canonical source can be found on the web at:
 
 @example
-@uref{http://downloads.sxemacs.org/}
+@uref{https://downloads.sxemacs.org/}
 @end example
 
 Occasionally there are also snapshots of the current development line
 available.  These can be found at:
 
 @example
-@uref{http://downloads.sxemacs.org/snapshots/}
+@uref{https://downloads.sxemacs.org/snapshots/}
 @end example
 
 
@@ -705,10 +705,10 @@ and developing issues.
 @unnumberedsec Q1.0.7: Where are the mailing lists archived?
 
 The archives can be found at
-@uref{http://www.sxemacs.org/list-archives/html/sxemacs-devel/}.
+@uref{https://www.sxemacs.org/list-archives/html/sxemacs-devel/}.
 
 Subscription can be done via
-@uref{http://www.sxemacs.org/mailman/listinfo}
+@uref{https://www.sxemacs.org/mailman/listinfo}
 
 
 @node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
@@ -720,7 +720,7 @@ The most common pronounciation is @samp{sexy macs}.
 @node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
 @unnumberedsec Q1.0.9: What does SXEmacs look like?
 
-Look at the screenshot section at @uref{http://www.sxemacs.org}.
+Look at the screenshot section at @uref{https://www.sxemacs.org}.
 
 
 @node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
@@ -762,7 +762,7 @@ Pre-printed manuals are not available.  If you are familiar with
 TeX, you can generate your own manual from the SXEmacs sources.
 
 HTML and Postscript versions of SXEmacs manuals are available from the
-SXEmacs web site at @uref{http://www.sxemacs.org}.
+SXEmacs web site at @uref{https://www.sxemacs.org}.
 @c are they?
 @c HTML are, but they may be a little out of date. --SY
 
@@ -6639,7 +6639,7 @@ Compiler fixes (gcc 2.95) -- Freundt.
 bug-reporter update -- Youngs.
 
 `report-sxemacs-bug' now directs people to our BugZilla installation
-at @url{http://issues.sxemacs.org/}
+at @url{https://issues.sxemacs.org/}
 
 @item
 Documentation updates/fixes/improvements -- Youngs, Ferreira, Freundt.

diff --git a/info/sxemacs/sxemacs.texi b/info/sxemacs/sxemacs.texi
index 238924e..75433e6 100644 (file)
--- a/info/sxemacs/sxemacs.texi
+++ b/info/sxemacs/sxemacs.texi
@@ -687,7 +687,7 @@ You need not ask for permission to do so, or tell any one else; just copy
 it.
 
 If you have access to the Internet, you can get the latest version of
-SXEmacs from our download site at @uref{http://downloads.sxemacs.org}.
+SXEmacs from our download site at @uref{https://downloads.sxemacs.org}.
 
 
 @unnumberedsec Getting Other Versions of Emacs

diff --git a/lisp/about.el b/lisp/about.el
index 74098d1..cb817ec 100644 (file)
--- a/lisp/about.el
+++ b/lisp/about.el
@@ -226,7 +226,7 @@
     (steve-inits . "http://bastard.steveyoungs.com/~steve/SXEmacs/htmlinits/")
     (steve-twit . "https://twitter.com/SteveYoungs")
     (stigb      . "http://www.tihlde.hist.no/~stigb/")
-    (sxemacs    . "http://www.sxemacs.org/")
+    (sxemacs    . "https://www.sxemacs.org/")
     (sxemacs-shop . "http://store.sxemacs.org/")
     (vin        . "http://www.upa.org/")
     (vladimir   . "http://www.leonora.org/~vladimir/")

diff --git a/lisp/emod-utils.el b/lisp/emod-utils.el
index 4b2d17c..50ef6e0 100644 (file)
--- a/lisp/emod-utils.el
+++ b/lisp/emod-utils.el
@@ -5,7 +5,7 @@
 ;; Author:     Steve Youngs <steve@sxemacs.org>
 ;; Maintainer: SXEmacs Development Team <sxemacs-devel@sxemacs.org>
 ;; Created:    <2008-05-01>
-;; Homepage:   http://www.sxemacs.org/
+;; Homepage:   https://www.sxemacs.org/
 ;; Keywords:   util, module, emodule, dumped
 
 ;; This file is part of SXEmacs.

diff --git a/lisp/ffi/ffi-magic.el b/lisp/ffi/ffi-magic.el
index d10b77f..4aee8cd 100644 (file)
--- a/lisp/ffi/ffi-magic.el
+++ b/lisp/ffi/ffi-magic.el
@@ -5,7 +5,7 @@
 ;; Author:     Steve Youngs <steve@sxemacs.org>
 ;; Maintainer: Steve Youngs <steve@sxemacs.org>
 ;; Created:    <2008-04-02>
-;; Homepage:   http://www.sxemacs.org
+;; Homepage:   https://www.sxemacs.org
 ;; Keywords:   ffi, file, magic, extension
 
 ;; This file is part of SXEmacs.

diff --git a/lisp/help.el b/lisp/help.el
index f586ee5..93564f5 100644 (file)
--- a/lisp/help.el
+++ b/lisp/help.el
@@ -749,7 +749,7 @@ of the key sequence that ran this command."
   "Go to the SXEmacs World Wide Web page."
   (interactive)
   (if-fboundp 'browse-url
-      (browse-url "http://www.sxemacs.org/")
+      (browse-url "https://www.sxemacs.org/")
     (error "sxemacs-www-page requires browse-url")))
 
 (defalias 'xemacs-www-page 'sxemacs-www-page)
@@ -758,7 +758,7 @@ of the key sequence that ran this command."
   "View the latest and greatest SXEmacs FAQ using the World Wide Web."
   (interactive)
   (if-fboundp 'browse-url
-      (browse-url "http://www.sxemacs.org/faq/index.html")
+      (browse-url "https://www.sxemacs.org/faq/index.html")
     (error "sxemacs-www-faq requires browse-url")))
 
 (defalias 'xemacs-www-faq 'sxemacs-www-faq)

diff --git a/lisp/issue-tracker.el b/lisp/issue-tracker.el
index 59e03ff..27bc2df 100644 (file)
--- a/lisp/issue-tracker.el
+++ b/lisp/issue-tracker.el
@@ -5,7 +5,7 @@
 ;; Author:        Steve Youngs <steve@sxemacs.org>
 ;; Maintainer:    Steve Youngs <steve@sxemacs.org>
 ;; Created:       <2005-01-10>
-;; Homepage:      http://www.sxemacs.org/
+;; Homepage:      https://www.sxemacs.org/
 ;; Keywords:      bugs issues
 
 ;; This file is part of SXEmacs.
@@ -361,7 +361,7 @@ and send the mail again.") nil) "*Bug Help*")))
   "Save C and lisp backtrace buffers to files.
 
 This is a convenience for reporting SXEmacs issues at
-http://issues.sxemacs.org/.  Returns t if any backtrace buffers are
+https://issues.sxemacs.org/.  Returns t if any backtrace buffers are
 found and saved, nil otherwise."
   (let ((ctrace (or (get-buffer (concat "*gdb-sxemacs-"
                                        emacs-program-version
@@ -386,7 +386,7 @@ found and saved, nil otherwise."
   "Save `Installation-string' to file.
 
 This is a convenience for reporting SXEmacs issues at
-http://issues.sxemacs.org/.  Returns t on success, nil otherwise."
+https://issues.sxemacs.org/.  Returns t on success, nil otherwise."
   (let ((file (expand-file-name "Installation" (temp-directory)))
        (str (and (boundp 'Installation-string)
                  (stringp Installation-string)
@@ -412,7 +412,7 @@ If you are not familar with SXEmacs debugging and/or gdb, you can simply
 you just reproduce the bug/problem and a *Backtrace* buffer should pop
 up.  Once you have a backtrace, run `M-x report-sxemacs-bug' again and
 it will be automatically saved to a file so you can attach it to your
-bug at http://issues.sxemacs.org/.
+bug at https://issues.sxemacs.org/.
 
 OK, that was for a lisp backtrace, but don't forget a C trace as well.
 Sometimes they are just as useful, if not more so, as the lisp trace.
@@ -432,7 +432,7 @@ Q2.1.15 of the FAQ \(`C-h F'\).
 ========================================================
 
 SXEmacs bug and issue tracking is handled by our BugZilla installation
-at http://issues.sxemacs.org/.  To complete your report, you will have
+at https://issues.sxemacs.org/.  To complete your report, you will have
 to submit the bug/issue there.
 
 Look in: `%s'

diff --git a/lisp/startup.el b/lisp/startup.el
index f2ffff6..dee4a1b 100644 (file)
--- a/lisp/startup.el
+++ b/lisp/startup.el
@@ -1033,7 +1033,7 @@ a new format, when variables have changed, etc."
 (defun splash-frame-body ()
   `[((face (blue bold underline)
           "\nDistribution, copying license, warranty:\n\n")
-     "Please visit the SXEmacs website at http://www.sxemacs.org !\n\n"
+     "Please visit the SXEmacs website at https://www.sxemacs.org !\n\n"
      ((key describe-no-warranty)
       ": "(face (red bold) "SXEmacs comes with ABSOLUTELY NO WARRANTY\n"))
      ((key describe-copying)

diff --git a/modules/configure.ac b/modules/configure.ac
index fcacee8..6eab3a6 100644 (file)
--- a/modules/configure.ac
+++ b/modules/configure.ac
@@ -2,7 +2,7 @@ dnl SXEmacs emodules configure script
 dnl -------------------------------------------------------------------------
 
 AC_PREREQ(2.59)
-AC_INIT([SXEmacs modules], [22.1.15],[http://issues.sxemacs.org/])
+AC_INIT([SXEmacs modules], [22.1.15],[https://issues.sxemacs.org/])
 AC_CONFIG_HEADERS([config.emods.h])
 AC_LANG(C)
 

diff --git a/modules/dbus/dbusbind.c b/modules/dbus/dbusbind.c
index 8c57740..049b7e9 100644 (file)
--- a/modules/dbus/dbusbind.c
+++ b/modules/dbus/dbusbind.c
@@ -4,7 +4,7 @@
  * Time-stamp: <Sunday Jan 29, 2012 17:41:26 steve>
  * Created:    <2012-01-03>
  * Maintainer: Steve Youngs <steve@sxemacs.org>
- * Homepage:   http://www.sxemacs.org/
+ * Homepage:   https://www.sxemacs.org/
  */
 
 /*

diff --git a/modules/dbus/dbusbind.h b/modules/dbus/dbusbind.h
index 505af77..1f57280 100644 (file)
--- a/modules/dbus/dbusbind.h
+++ b/modules/dbus/dbusbind.h
@@ -9,7 +9,7 @@
  * Created:    <2012-01-22>
  * Author:     Steve Youngs <steve@sxemacs.org>
  * Maintainer: Steve Youngs <steve@sxemacs.org>
- * Homepage:   http://www.sxemacs.org/
+ * Homepage:   https://www.sxemacs.org/
  */
 
 /*

diff --git a/src/dired.c b/src/dired.c
index c0cd01e..1ee2fca 100644 (file)
--- a/src/dired.c
+++ b/src/dired.c
@@ -636,7 +636,7 @@ yourself, or want to feed the result to further processing.
 
 For compatibility with XEmacs' NOSORT argument to this function,
 RESULT-TYPE can also be any non-nil value.  In that case it will
-return an unsorted list. (http://issues.sxemacs.org/show_bug.cgi?id=163)
+return an unsorted list. (https://issues.sxemacs.org/show_bug.cgi?id=163)
 
 Optional argument FILES-ONLY can be one of:
 - t  to return only files and symlinks in DIRECTORY