summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNoam Postavsky <npostavs@gmail.com>2018-03-15 07:42:40 -0400
committerNoam Postavsky <npostavs@gmail.com>2018-03-23 08:19:42 -0400
commit8c92a37cb4dd8e2d0adf1ce19f74c372e0ad2e42 (patch)
treee40d58f1573dd4a2592541abf7d36acf09d0c595
parent10b1f2fdd5465407766790131b2ead3500d0798c (diff)
downloademacs-8c92a37cb4dd8e2d0adf1ce19f74c372e0ad2e42.tar.gz
* doc/emacs/trouble.texi: Fix location of `emacs-version' index.
-rw-r--r--doc/emacs/trouble.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index c0dc3d472e3..fc9a64d375e 100644
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -594,7 +594,6 @@ with the manual, one of them must be wrong; that is a bug.
@cindex bug reporting
@cindex report an Emacs bug, how to
-@findex emacs-version
When you decide that there is a bug, it is important to report it
and to report it in a way which is useful. What is most useful is an
exact description of what commands you type, starting with the shell
@@ -717,6 +716,7 @@ should include all these things:
The version number of Emacs. Without this, we won't know whether there is any
point in looking for the bug in the current version of GNU Emacs.
+@findex emacs-version
@kbd{M-x report-emacs-bug} includes this information automatically,
but if you are not using that command for your report you can get the
version number by typing @kbd{M-x emacs-version @key{RET}}. If that