From eaad302bd6f1d30bed1fbdd02e5091d13ce0c7ba Mon Sep 17 00:00:00 2001 From: Dmitry Gutov Date: Thu, 4 May 2023 01:39:15 +0300 Subject: Rename eglot-update to eglot-upgrade * doc/misc/eglot.texi (Getting the latest version): Update the reference. * lisp/progmodes/eglot.el (eglot-upgrade): Rename from 'eglot-update', as discussed on emacs-devel, in line with 'package-upgrade'. --- doc/misc/eglot.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/misc/eglot.texi b/doc/misc/eglot.texi index 542a4259d66..8ac14372e36 100644 --- a/doc/misc/eglot.texi +++ b/doc/misc/eglot.texi @@ -1307,7 +1307,7 @@ Eglot, use @kbd{M-x package-install}. Often, a newer Eglot version exists that has fixed a longstanding bug, has more LSP features, or just better supports a particular language server. Recent Eglot versions can self-update via the command -@kbd{M-x eglot-update}. This will replace any currently installed +@kbd{M-x eglot-upgrade}. This will replace any currently installed version with the newest one available from the ELPA archives configured in @code{package-archives}. -- cgit v1.2.1 From b42ccb2e5c133070c03ba8691ed8a0c6807b0da9 Mon Sep 17 00:00:00 2001 From: "Basil L. Contovounesios" Date: Thu, 4 May 2023 12:16:57 +0200 Subject: ; Minor grammar fix in treesit manual. --- doc/lispref/modes.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/lispref/modes.texi b/doc/lispref/modes.texi index deaed31aed0..00298d88f43 100644 --- a/doc/lispref/modes.texi +++ b/doc/lispref/modes.texi @@ -4154,7 +4154,7 @@ Other keywords are optional: @end multitable Lisp programs mark patterns in @var{query} with capture names (names -that starts with @code{@@}), and tree-sitter will return matched nodes +that start with @code{@@}), and tree-sitter will return matched nodes tagged with those same capture names. For the purpose of fontification, capture names in @var{query} should be face names like @code{font-lock-keyword-face}. The captured node will be fontified -- cgit v1.2.1 From 2f3a514b6db5e0d0453c56a4f201088ea99d5139 Mon Sep 17 00:00:00 2001 From: Po Lu Date: Thu, 4 May 2023 22:08:44 +0800 Subject: Clarify documentation wrt floating point division by zero and NaN * doc/lispref/numbers.texi (Float Basics) (Arithmetic Operations): Document what happens on a VAX. Tested on NetBSD 9.3. --- doc/lispref/numbers.texi | 39 ++++++++++++++++++++++++++------------- 1 file changed, 26 insertions(+), 13 deletions(-) (limited to 'doc') diff --git a/doc/lispref/numbers.texi b/doc/lispref/numbers.texi index 9bfb771fc07..3e45aa90fda 100644 --- a/doc/lispref/numbers.texi +++ b/doc/lispref/numbers.texi @@ -219,17 +219,25 @@ creates huge integers. @cindex @acronym{IEEE} floating point Floating-point numbers are useful for representing numbers that are -not integral. The range of floating-point numbers is -the same as the range of the C data type @code{double} on the machine -you are using. On all computers supported by Emacs, this is -@acronym{IEEE} binary64 floating point format, which is standardized by -@url{https://standards.ieee.org/standard/754-2019.html,,IEEE Std 754-2019} -and is discussed further in David Goldberg's paper +not integral. The range of floating-point numbers is the same as the +range of the C data type @code{double} on the machine you are using. +On almost all computers supported by Emacs, this is @acronym{IEEE} +binary64 floating point format, which is standardized by +@url{https://standards.ieee.org/standard/754-2019.html,,IEEE Std +754-2019} and is discussed further in David Goldberg's paper ``@url{https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html, -What Every Computer Scientist Should Know About Floating-Point Arithmetic}''. -On modern platforms, floating-point operations follow the IEEE-754 -standard closely; however, results are not always rounded correctly on -some obsolescent platforms, notably 32-bit x86. +What Every Computer Scientist Should Know About Floating-Point +Arithmetic}''. On modern platforms, floating-point operations follow +the IEEE-754 standard closely; however, results are not always rounded +correctly on some systems, notably 32-bit x86. + + On some old computer systems, Emacs may not use IEEE floating-point. +We know of one such system on which Emacs runs correctly, but does not +follow IEEE-754: the VAX running NetBSD using GCC 10.4.0, where the +VAX @samp{D_Floating} format is used instead. IBM System/370-derived +mainframes and their XL/C compiler are also capable of utilizing a +hexadecimal floating point format, but Emacs has not yet been built in +such a configuration. The read syntax for floating-point numbers requires either a decimal point, an exponent, or both. Optional signs (@samp{+} or @samp{-}) @@ -262,6 +270,10 @@ two NaNs as equal when their signs and significands agree. Significands of NaNs are machine-dependent, as are the digits in their string representation. + NaNs are not available on systems which do not use IEEE +floating-point arithmetic; if the read syntax for a NaN is used on a +VAX, for example, the reader signals an error. + When NaNs and signed zeros are involved, non-numeric functions like @code{eql}, @code{equal}, @code{sxhash-eql}, @code{sxhash-equal} and @code{gethash} determine whether values are indistinguishable, not @@ -742,9 +754,10 @@ by rounding the quotient towards zero after each division. @cindex @code{arith-error} in division If you divide an integer by the integer 0, Emacs signals an -@code{arith-error} error (@pxref{Errors}). Floating-point division of -a nonzero number by zero yields either positive or negative infinity -(@pxref{Float Basics}). +@code{arith-error} error (@pxref{Errors}). On systems using IEEE-754 +floating-point, floating-point division of a nonzero number by zero +yields either positive or negative infinity (@pxref{Float Basics}); +otherwise, an @code{arith-error} is signaled as usual. @end defun @defun % dividend divisor -- cgit v1.2.1 From c0ab4e9ca9326c472ff1d9d01a0e3966f20fda27 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20T=C3=A1vora?= Date: Fri, 5 May 2023 14:51:09 +0100 Subject: Eglot: re-rename eglot-upgrade to eglot-upgrade-eglot * doc/misc/eglot.texi (Getting the latest version): Mention eglot-upgrade-eglot. * etc/EGLOT-NEWS: Mention eglot-upgrade-eglot. * lisp/progmodes/eglot.el (eglot-upgrade-eglot): Rename from eglot-update. (eglot-update): New compatibility alias. --- doc/misc/eglot.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/misc/eglot.texi b/doc/misc/eglot.texi index 8ac14372e36..962e6c914ce 100644 --- a/doc/misc/eglot.texi +++ b/doc/misc/eglot.texi @@ -1307,8 +1307,8 @@ Eglot, use @kbd{M-x package-install}. Often, a newer Eglot version exists that has fixed a longstanding bug, has more LSP features, or just better supports a particular language server. Recent Eglot versions can self-update via the command -@kbd{M-x eglot-upgrade}. This will replace any currently installed -version with the newest one available from the ELPA archives +@kbd{M-x eglot-upgrade-eglot}. This will replace any currently +installed version with the newest one available from the ELPA archives configured in @code{package-archives}. You can also update Eglot through other methods, such as -- cgit v1.2.1