Is updating Emacs and installing Emacs the same thing?Portability of bytecode between Emacs versionsShould I update or install emacs and related packages?default location to install ess not works with the self installed emacsinstalling emacs: which x-toolkit?How can I have the latest version of emacs alwaysIs it possible to install emacs 25.1 and emacs 24 on the same machine?Installing Emacs from source: no 'configure' fileInstalling Emacs from source: 'make' fatal error: 'libxml/tree.h' file not foundInstalling Emacs from source: the command `C-h v` for accessing variables doesn't workAutomatically installing the available version of orgHow to update Org-mode through Emacs' Package Manager?
Why didn't this hurt this character as badly?
TikZ how to make supply and demand arrows for nodes?
Does the EU Common Fisheries Policy cover British Overseas Territories?
Any examples of headwear for races with animal ears?
Examples of non trivial equivalence relations , I mean equivalence relations without the expression " same ... as" in their definition?
Will tsunami waves travel forever if there was no land?
How to figure out whether the data is sample data or population data apart from the client's information?
Pawn Sacrifice Justification
Phrase for the opposite of "foolproof"
Why the difference in metal between 銀行 and お金?
Do I have to worry about players making “bad” choices on level up?
Stark VS Thanos
What does YCWCYODFTRFDTY mean?
Subtleties of choosing the sequence of tenses in Russian
Can a creature tell when it has been affected by a Divination wizard's Portent?
Bayesian Nash Equilibria in Battle of Sexes
Is thermodynamics only applicable to systems in equilibrium?
How to set the font color of quantity objects (Version 11.3 vs version 12)?
Transfer over $10k
Why does Bran Stark feel that Jon Snow "needs to know" about his lineage?
When India mathematicians did know Euclid's Elements?
Python "triplet" dictionary?
Can someone publish a story that happened to you?
Multiple options for Pseudonyms
Is updating Emacs and installing Emacs the same thing?
Portability of bytecode between Emacs versionsShould I update or install emacs and related packages?default location to install ess not works with the self installed emacsinstalling emacs: which x-toolkit?How can I have the latest version of emacs alwaysIs it possible to install emacs 25.1 and emacs 24 on the same machine?Installing Emacs from source: no 'configure' fileInstalling Emacs from source: 'make' fatal error: 'libxml/tree.h' file not foundInstalling Emacs from source: the command `C-h v` for accessing variables doesn't workAutomatically installing the available version of orgHow to update Org-mode through Emacs' Package Manager?
I installed Emacs 26.1 from dnf package manager on Fedora 29.
I would like to install the latest stable Emacs, which is version 26.2.
Emacs 26.2 will be on Fedora 31 in 6 months.
Is updating Emacs the same thing as installing Emacs?
If so, I will be following the instructions on https://www.gnu.org/software/emacs/manual/html_node/efaq/Installing-Emacs.html
Latest Emacs release number is published on https://www.gnu.org/software/emacs/index.html#Releases
Emacs dnf release numbers are published on https://apps.fedoraproject.org/packages/emacs
install
add a comment |
I installed Emacs 26.1 from dnf package manager on Fedora 29.
I would like to install the latest stable Emacs, which is version 26.2.
Emacs 26.2 will be on Fedora 31 in 6 months.
Is updating Emacs the same thing as installing Emacs?
If so, I will be following the instructions on https://www.gnu.org/software/emacs/manual/html_node/efaq/Installing-Emacs.html
Latest Emacs release number is published on https://www.gnu.org/software/emacs/index.html#Releases
Emacs dnf release numbers are published on https://apps.fedoraproject.org/packages/emacs
install
add a comment |
I installed Emacs 26.1 from dnf package manager on Fedora 29.
I would like to install the latest stable Emacs, which is version 26.2.
Emacs 26.2 will be on Fedora 31 in 6 months.
Is updating Emacs the same thing as installing Emacs?
If so, I will be following the instructions on https://www.gnu.org/software/emacs/manual/html_node/efaq/Installing-Emacs.html
Latest Emacs release number is published on https://www.gnu.org/software/emacs/index.html#Releases
Emacs dnf release numbers are published on https://apps.fedoraproject.org/packages/emacs
install
I installed Emacs 26.1 from dnf package manager on Fedora 29.
I would like to install the latest stable Emacs, which is version 26.2.
Emacs 26.2 will be on Fedora 31 in 6 months.
Is updating Emacs the same thing as installing Emacs?
If so, I will be following the instructions on https://www.gnu.org/software/emacs/manual/html_node/efaq/Installing-Emacs.html
Latest Emacs release number is published on https://www.gnu.org/software/emacs/index.html#Releases
Emacs dnf release numbers are published on https://apps.fedoraproject.org/packages/emacs
install
install
edited Apr 25 at 2:11
wolfv
asked Apr 24 at 14:07
wolfvwolfv
578217
578217
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
In your case probably not.
Linux distributions like Fedora
(Ubuntu, Debian, Red Hat and so on) work with packages.
The content of those packages are ready to use programms. Normaly you install them with a package manager.
A package manager unpacks a package and copies its content to the correct location on your hard disk (and runs some helper skripts).
Your Emacs 26.1 most probably came from such a package. To upgrade it you should install a package, which provides a more recent version of emacs (one such package is available on Fedora Rawhide
). Doing this removes the old version, in a clean way, from your harddisk.
The link you posted describes how to compile emacs and then installing it to your harddisk. This comes with multiple problems in the long run, as this operations work without the package manager and you probably end up having 2 versions of emacs installed.
If you are not knowing, what I'm talking about, then do yourself a favour and wait for a Emacs 26.2 package, which you can install, or use the package from rawhide
.
add a comment |
Yes, if you're compiling from source you 'update' by installing the newest Emacs version over top of your old version.
I have installed Emacs from source on my current laptop starting with emacs-25.1.50, and currently I'm running emacs-27.0.50.
When I 'updated' to 27.0.50, I followed the usual compilation steps. The make install
step placed the executable emacs-27.0.50
in /usr/local/bin, and also created the symlink /usr/local/bin/emacs -> emacs-27.0.50
. So I can open this version of emacs with either emacs
, or emacs-27.0.50
.
The previous versions of emacs are still in that directory, so I could run emacs 25 via emacs-25.1.50
- if I was careful to keep the versions of the libraries that I built that emacs with on my system (and assuming no incompatibilities in my config or installed packages). That's only going to be an issue if you are developing packages and want to check compatibility with previous emacs versions. I don't do that, so I've just left the old versions where they are. They take up a tiny bit of disk space, and don't interfere with my current installation.
EDIT
My answer assumes you previously installed emacs by compiling it from source. If you installed it as a package from the Fedora repository, you should either uninstall that package using the package manager before compiling the version you downloaded directly from GNU; or, just stick with the packaged version and wait for Fedora to add 26.2 to their repository (the difference between 26.1 and 26.2 isn't that big).
add a comment |
If you re-install Emacs there remains something to do afterwards:
There may be byte-code incompatibilities and lisp incompatibilities between two versions of Emacs.
You should recompile the packages in the directory registered in variable package-user-dir
:
M-: (byte-recompile-directory package-user-dir nil t)
Byte-code incompatibilities appear as very strange lisp errors.
Lisp incompatibilities are removed symbols of functions and variables, and modified macros. Within a macro the library author is allowed to use all possible internal stuff of the library which may have a short live-time. That stuff remains in your byte-compiled code if you do not re-compile.
I haven't encountered this before, despite lots of re-installations. How often are byte-code incompatibilities introduced between versions? Maybe I've just been lucky so far.
– Tyler
Apr 24 at 15:27
1
@Tyler For a general statement see: emacs.stackexchange.com/questions/3418/…. I have encountered byte-code incompatibilities at updating from Emacs 25 to Emacs 26. One gets very strange errors that are gone when one re-compiles the package directory. More often are changes in macros. Those almost always require re-compilation. You should definitively make re-compilation to a habit after an upgrade. It is also worthy to keep version-separated package directories.
– Tobias
Apr 24 at 15:34
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "583"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2femacs.stackexchange.com%2fquestions%2f50129%2fis-updating-emacs-and-installing-emacs-the-same-thing%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
In your case probably not.
Linux distributions like Fedora
(Ubuntu, Debian, Red Hat and so on) work with packages.
The content of those packages are ready to use programms. Normaly you install them with a package manager.
A package manager unpacks a package and copies its content to the correct location on your hard disk (and runs some helper skripts).
Your Emacs 26.1 most probably came from such a package. To upgrade it you should install a package, which provides a more recent version of emacs (one such package is available on Fedora Rawhide
). Doing this removes the old version, in a clean way, from your harddisk.
The link you posted describes how to compile emacs and then installing it to your harddisk. This comes with multiple problems in the long run, as this operations work without the package manager and you probably end up having 2 versions of emacs installed.
If you are not knowing, what I'm talking about, then do yourself a favour and wait for a Emacs 26.2 package, which you can install, or use the package from rawhide
.
add a comment |
In your case probably not.
Linux distributions like Fedora
(Ubuntu, Debian, Red Hat and so on) work with packages.
The content of those packages are ready to use programms. Normaly you install them with a package manager.
A package manager unpacks a package and copies its content to the correct location on your hard disk (and runs some helper skripts).
Your Emacs 26.1 most probably came from such a package. To upgrade it you should install a package, which provides a more recent version of emacs (one such package is available on Fedora Rawhide
). Doing this removes the old version, in a clean way, from your harddisk.
The link you posted describes how to compile emacs and then installing it to your harddisk. This comes with multiple problems in the long run, as this operations work without the package manager and you probably end up having 2 versions of emacs installed.
If you are not knowing, what I'm talking about, then do yourself a favour and wait for a Emacs 26.2 package, which you can install, or use the package from rawhide
.
add a comment |
In your case probably not.
Linux distributions like Fedora
(Ubuntu, Debian, Red Hat and so on) work with packages.
The content of those packages are ready to use programms. Normaly you install them with a package manager.
A package manager unpacks a package and copies its content to the correct location on your hard disk (and runs some helper skripts).
Your Emacs 26.1 most probably came from such a package. To upgrade it you should install a package, which provides a more recent version of emacs (one such package is available on Fedora Rawhide
). Doing this removes the old version, in a clean way, from your harddisk.
The link you posted describes how to compile emacs and then installing it to your harddisk. This comes with multiple problems in the long run, as this operations work without the package manager and you probably end up having 2 versions of emacs installed.
If you are not knowing, what I'm talking about, then do yourself a favour and wait for a Emacs 26.2 package, which you can install, or use the package from rawhide
.
In your case probably not.
Linux distributions like Fedora
(Ubuntu, Debian, Red Hat and so on) work with packages.
The content of those packages are ready to use programms. Normaly you install them with a package manager.
A package manager unpacks a package and copies its content to the correct location on your hard disk (and runs some helper skripts).
Your Emacs 26.1 most probably came from such a package. To upgrade it you should install a package, which provides a more recent version of emacs (one such package is available on Fedora Rawhide
). Doing this removes the old version, in a clean way, from your harddisk.
The link you posted describes how to compile emacs and then installing it to your harddisk. This comes with multiple problems in the long run, as this operations work without the package manager and you probably end up having 2 versions of emacs installed.
If you are not knowing, what I'm talking about, then do yourself a favour and wait for a Emacs 26.2 package, which you can install, or use the package from rawhide
.
edited Apr 24 at 15:09
answered Apr 24 at 15:00
juejue
1,615112
1,615112
add a comment |
add a comment |
Yes, if you're compiling from source you 'update' by installing the newest Emacs version over top of your old version.
I have installed Emacs from source on my current laptop starting with emacs-25.1.50, and currently I'm running emacs-27.0.50.
When I 'updated' to 27.0.50, I followed the usual compilation steps. The make install
step placed the executable emacs-27.0.50
in /usr/local/bin, and also created the symlink /usr/local/bin/emacs -> emacs-27.0.50
. So I can open this version of emacs with either emacs
, or emacs-27.0.50
.
The previous versions of emacs are still in that directory, so I could run emacs 25 via emacs-25.1.50
- if I was careful to keep the versions of the libraries that I built that emacs with on my system (and assuming no incompatibilities in my config or installed packages). That's only going to be an issue if you are developing packages and want to check compatibility with previous emacs versions. I don't do that, so I've just left the old versions where they are. They take up a tiny bit of disk space, and don't interfere with my current installation.
EDIT
My answer assumes you previously installed emacs by compiling it from source. If you installed it as a package from the Fedora repository, you should either uninstall that package using the package manager before compiling the version you downloaded directly from GNU; or, just stick with the packaged version and wait for Fedora to add 26.2 to their repository (the difference between 26.1 and 26.2 isn't that big).
add a comment |
Yes, if you're compiling from source you 'update' by installing the newest Emacs version over top of your old version.
I have installed Emacs from source on my current laptop starting with emacs-25.1.50, and currently I'm running emacs-27.0.50.
When I 'updated' to 27.0.50, I followed the usual compilation steps. The make install
step placed the executable emacs-27.0.50
in /usr/local/bin, and also created the symlink /usr/local/bin/emacs -> emacs-27.0.50
. So I can open this version of emacs with either emacs
, or emacs-27.0.50
.
The previous versions of emacs are still in that directory, so I could run emacs 25 via emacs-25.1.50
- if I was careful to keep the versions of the libraries that I built that emacs with on my system (and assuming no incompatibilities in my config or installed packages). That's only going to be an issue if you are developing packages and want to check compatibility with previous emacs versions. I don't do that, so I've just left the old versions where they are. They take up a tiny bit of disk space, and don't interfere with my current installation.
EDIT
My answer assumes you previously installed emacs by compiling it from source. If you installed it as a package from the Fedora repository, you should either uninstall that package using the package manager before compiling the version you downloaded directly from GNU; or, just stick with the packaged version and wait for Fedora to add 26.2 to their repository (the difference between 26.1 and 26.2 isn't that big).
add a comment |
Yes, if you're compiling from source you 'update' by installing the newest Emacs version over top of your old version.
I have installed Emacs from source on my current laptop starting with emacs-25.1.50, and currently I'm running emacs-27.0.50.
When I 'updated' to 27.0.50, I followed the usual compilation steps. The make install
step placed the executable emacs-27.0.50
in /usr/local/bin, and also created the symlink /usr/local/bin/emacs -> emacs-27.0.50
. So I can open this version of emacs with either emacs
, or emacs-27.0.50
.
The previous versions of emacs are still in that directory, so I could run emacs 25 via emacs-25.1.50
- if I was careful to keep the versions of the libraries that I built that emacs with on my system (and assuming no incompatibilities in my config or installed packages). That's only going to be an issue if you are developing packages and want to check compatibility with previous emacs versions. I don't do that, so I've just left the old versions where they are. They take up a tiny bit of disk space, and don't interfere with my current installation.
EDIT
My answer assumes you previously installed emacs by compiling it from source. If you installed it as a package from the Fedora repository, you should either uninstall that package using the package manager before compiling the version you downloaded directly from GNU; or, just stick with the packaged version and wait for Fedora to add 26.2 to their repository (the difference between 26.1 and 26.2 isn't that big).
Yes, if you're compiling from source you 'update' by installing the newest Emacs version over top of your old version.
I have installed Emacs from source on my current laptop starting with emacs-25.1.50, and currently I'm running emacs-27.0.50.
When I 'updated' to 27.0.50, I followed the usual compilation steps. The make install
step placed the executable emacs-27.0.50
in /usr/local/bin, and also created the symlink /usr/local/bin/emacs -> emacs-27.0.50
. So I can open this version of emacs with either emacs
, or emacs-27.0.50
.
The previous versions of emacs are still in that directory, so I could run emacs 25 via emacs-25.1.50
- if I was careful to keep the versions of the libraries that I built that emacs with on my system (and assuming no incompatibilities in my config or installed packages). That's only going to be an issue if you are developing packages and want to check compatibility with previous emacs versions. I don't do that, so I've just left the old versions where they are. They take up a tiny bit of disk space, and don't interfere with my current installation.
EDIT
My answer assumes you previously installed emacs by compiling it from source. If you installed it as a package from the Fedora repository, you should either uninstall that package using the package manager before compiling the version you downloaded directly from GNU; or, just stick with the packaged version and wait for Fedora to add 26.2 to their repository (the difference between 26.1 and 26.2 isn't that big).
edited Apr 24 at 15:23
answered Apr 24 at 14:49
TylerTyler
12.5k12355
12.5k12355
add a comment |
add a comment |
If you re-install Emacs there remains something to do afterwards:
There may be byte-code incompatibilities and lisp incompatibilities between two versions of Emacs.
You should recompile the packages in the directory registered in variable package-user-dir
:
M-: (byte-recompile-directory package-user-dir nil t)
Byte-code incompatibilities appear as very strange lisp errors.
Lisp incompatibilities are removed symbols of functions and variables, and modified macros. Within a macro the library author is allowed to use all possible internal stuff of the library which may have a short live-time. That stuff remains in your byte-compiled code if you do not re-compile.
I haven't encountered this before, despite lots of re-installations. How often are byte-code incompatibilities introduced between versions? Maybe I've just been lucky so far.
– Tyler
Apr 24 at 15:27
1
@Tyler For a general statement see: emacs.stackexchange.com/questions/3418/…. I have encountered byte-code incompatibilities at updating from Emacs 25 to Emacs 26. One gets very strange errors that are gone when one re-compiles the package directory. More often are changes in macros. Those almost always require re-compilation. You should definitively make re-compilation to a habit after an upgrade. It is also worthy to keep version-separated package directories.
– Tobias
Apr 24 at 15:34
add a comment |
If you re-install Emacs there remains something to do afterwards:
There may be byte-code incompatibilities and lisp incompatibilities between two versions of Emacs.
You should recompile the packages in the directory registered in variable package-user-dir
:
M-: (byte-recompile-directory package-user-dir nil t)
Byte-code incompatibilities appear as very strange lisp errors.
Lisp incompatibilities are removed symbols of functions and variables, and modified macros. Within a macro the library author is allowed to use all possible internal stuff of the library which may have a short live-time. That stuff remains in your byte-compiled code if you do not re-compile.
I haven't encountered this before, despite lots of re-installations. How often are byte-code incompatibilities introduced between versions? Maybe I've just been lucky so far.
– Tyler
Apr 24 at 15:27
1
@Tyler For a general statement see: emacs.stackexchange.com/questions/3418/…. I have encountered byte-code incompatibilities at updating from Emacs 25 to Emacs 26. One gets very strange errors that are gone when one re-compiles the package directory. More often are changes in macros. Those almost always require re-compilation. You should definitively make re-compilation to a habit after an upgrade. It is also worthy to keep version-separated package directories.
– Tobias
Apr 24 at 15:34
add a comment |
If you re-install Emacs there remains something to do afterwards:
There may be byte-code incompatibilities and lisp incompatibilities between two versions of Emacs.
You should recompile the packages in the directory registered in variable package-user-dir
:
M-: (byte-recompile-directory package-user-dir nil t)
Byte-code incompatibilities appear as very strange lisp errors.
Lisp incompatibilities are removed symbols of functions and variables, and modified macros. Within a macro the library author is allowed to use all possible internal stuff of the library which may have a short live-time. That stuff remains in your byte-compiled code if you do not re-compile.
If you re-install Emacs there remains something to do afterwards:
There may be byte-code incompatibilities and lisp incompatibilities between two versions of Emacs.
You should recompile the packages in the directory registered in variable package-user-dir
:
M-: (byte-recompile-directory package-user-dir nil t)
Byte-code incompatibilities appear as very strange lisp errors.
Lisp incompatibilities are removed symbols of functions and variables, and modified macros. Within a macro the library author is allowed to use all possible internal stuff of the library which may have a short live-time. That stuff remains in your byte-compiled code if you do not re-compile.
answered Apr 24 at 15:09
TobiasTobias
15.7k11036
15.7k11036
I haven't encountered this before, despite lots of re-installations. How often are byte-code incompatibilities introduced between versions? Maybe I've just been lucky so far.
– Tyler
Apr 24 at 15:27
1
@Tyler For a general statement see: emacs.stackexchange.com/questions/3418/…. I have encountered byte-code incompatibilities at updating from Emacs 25 to Emacs 26. One gets very strange errors that are gone when one re-compiles the package directory. More often are changes in macros. Those almost always require re-compilation. You should definitively make re-compilation to a habit after an upgrade. It is also worthy to keep version-separated package directories.
– Tobias
Apr 24 at 15:34
add a comment |
I haven't encountered this before, despite lots of re-installations. How often are byte-code incompatibilities introduced between versions? Maybe I've just been lucky so far.
– Tyler
Apr 24 at 15:27
1
@Tyler For a general statement see: emacs.stackexchange.com/questions/3418/…. I have encountered byte-code incompatibilities at updating from Emacs 25 to Emacs 26. One gets very strange errors that are gone when one re-compiles the package directory. More often are changes in macros. Those almost always require re-compilation. You should definitively make re-compilation to a habit after an upgrade. It is also worthy to keep version-separated package directories.
– Tobias
Apr 24 at 15:34
I haven't encountered this before, despite lots of re-installations. How often are byte-code incompatibilities introduced between versions? Maybe I've just been lucky so far.
– Tyler
Apr 24 at 15:27
I haven't encountered this before, despite lots of re-installations. How often are byte-code incompatibilities introduced between versions? Maybe I've just been lucky so far.
– Tyler
Apr 24 at 15:27
1
1
@Tyler For a general statement see: emacs.stackexchange.com/questions/3418/…. I have encountered byte-code incompatibilities at updating from Emacs 25 to Emacs 26. One gets very strange errors that are gone when one re-compiles the package directory. More often are changes in macros. Those almost always require re-compilation. You should definitively make re-compilation to a habit after an upgrade. It is also worthy to keep version-separated package directories.
– Tobias
Apr 24 at 15:34
@Tyler For a general statement see: emacs.stackexchange.com/questions/3418/…. I have encountered byte-code incompatibilities at updating from Emacs 25 to Emacs 26. One gets very strange errors that are gone when one re-compiles the package directory. More often are changes in macros. Those almost always require re-compilation. You should definitively make re-compilation to a habit after an upgrade. It is also worthy to keep version-separated package directories.
– Tobias
Apr 24 at 15:34
add a comment |
Thanks for contributing an answer to Emacs Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2femacs.stackexchange.com%2fquestions%2f50129%2fis-updating-emacs-and-installing-emacs-the-same-thing%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown