Update MELPA URL

A good reason to update is that the TLS certificate served at the old
domain is currently only valid for the new domain.
This commit is contained in:
Iain Nicol 2015-11-01 13:57:14 +00:00
parent cb33004b7f
commit 937605211d
2 changed files with 4 additions and 4 deletions

View File

@ -6,7 +6,7 @@ Please read: [http://www.mew.org/~kazu/proj/ghc-mod/](http://www.mew.org/~kazu/p
## Using the stable version ## Using the stable version
The Emacs front-end is available from The Emacs front-end is available from
[*stable* MELPA](http://melpa-stable.milkbox.net/). This package should [*stable* MELPA](https://stable.melpa.org/). This package should
always be compatible with the latest version of ghc-mod from hackage. always be compatible with the latest version of ghc-mod from hackage.
To use stable *stable* MELPA add this to your `.emacs`: To use stable *stable* MELPA add this to your `.emacs`:
@ -14,7 +14,7 @@ To use stable *stable* MELPA add this to your `.emacs`:
```elisp ```elisp
(require 'package) (require 'package)
(add-to-list 'package-archives (add-to-list 'package-archives
'("melpa" . "http://melpa-stable.milkbox.net/packages/")) '("melpa" . "https://stable.melpa.org/packages/"))
(package-initialize) (package-initialize)
``` ```

View File

@ -2,12 +2,12 @@
**Downloading **Downloading
Please use *stable* [MELPA http://melpa-stable.milkbox.net/] to download Emacs front-end. So, your "~/.emacs" should be: Please use *stable* [MELPA https://stable.melpa.org/] to download Emacs front-end. So, your "~/.emacs" should be:
>| >|
(require 'package) (require 'package)
(add-to-list 'package-archives (add-to-list 'package-archives
'("melpa" . "http://melpa-stable.milkbox.net/packages/")) '("melpa" . "https://stable.melpa.org/packages/"))
(package-initialize) (package-initialize)
|< |<