From 446faf3efa0f2d9ccdaf746348c3173b3eb7be2f Mon Sep 17 00:00:00 2001 From: Dmitry Gutov Date: Mon, 18 Dec 2017 02:30:41 +0200 Subject: [PATCH] Replace the mention of c-indent-defun with js-indent-line * doc/lispref/text.texi (Mode-Specific Indent): Avoid mentioning c-indent-defun in the context of multi-mode indentation. --- doc/lispref/text.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/lispref/text.texi b/doc/lispref/text.texi index 67a303a5994..0ec1998da40 100644 --- a/doc/lispref/text.texi +++ b/doc/lispref/text.texi @@ -2396,9 +2396,9 @@ text at point (@pxref{Completion in Buffers}). syntax belongs to a different major mode. Examples include @dfn{literate programming} source files that combine documentation and snippets of source code, Yacc/Bison programs that include snippets of -plain C code, etc. To correctly indent the embedded chunks, the primary +Python or JS code, etc. To correctly indent the embedded chunks, the primary mode needs to delegate the indentation to another mode's indentation -engine (e.g., call @code{c-indent-defun} for C code or +engine (e.g., call @code{js-indent-line} for JS code or @code{python-indent-line} for Python), while providing it with some context to guide the indentation. Major modes, for their part, should avoid calling @code{widen} in their indentation code and obey -- 2.39.2