References to variables/functions in doc-strings?

[Pavel Janík]

Hi,

do we want similar patches adding references to other
variables/functions/commands? I found it inconvenient that
e.g. default-file-name-coding-system does not directly reference to its
documentation in the describe-variable output of file-name-coding-system.

--- fileio.c.~1.428.~   Tue Nov 20 07:05:00 2001
+++ fileio.c    Mon Nov 26 09:50:05 2001
@@ -6098,17 +6098,17 @@
 
   DEFVAR_LISP ("file-name-coding-system", &Vfile_name_coding_system,
               doc: /* *Coding system for encoding file names.
-If it is nil, default-file-name-coding-system (which see) is used.  */);
+If it is nil, `default-file-name-coding-system' (which see) is used.  */);
   Vfile_name_coding_system = Qnil;
 
   DEFVAR_LISP ("default-file-name-coding-system",
               &Vdefault_file_name_coding_system,
               doc: /* Default coding system for encoding file names.
-This variable is used only when file-name-coding-system is nil.
+This variable is used only when `file-name-coding-system' is nil.
 
-This variable is set/changed by the command set-language-environment.
+This variable is set/changed by the command `set-language-environment'.
 User should not set this variable manually,
-instead use file-name-coding-system to get a constant encoding
+instead use `file-name-coding-system' to get a constant encoding
 of file names regardless of the current language environment.  */);
   Vdefault_file_name_coding_system = Qnil;
 
-- 
Pavel Janík

/*
 * Hash table gook..
 */
                  -- 2.4.0-test2 fs/buffer.c