Correct invalid Texinfo markup
* doc/emacs/files.texi (Visiting): Don't enclose an entire form within @var, use @code for the whole form and @var for individual variables within instead. * doc/lispref/commands.texi (Key Sequence Input): @xref must be followed by either , or .. * doc/lispref/processes.texi (Filter Functions): Introduce punctuation absent from the last sentence of a paragraph.
This commit is contained in:
parent
c86100d46c
commit
de495477f9
3 changed files with 8 additions and 8 deletions
|
@ -372,12 +372,12 @@ you could say:
|
|||
'(("src/emacs/[^/]+/\\(.*\\)\\'" "src/emacs/.*/\\1")))
|
||||
@end lisp
|
||||
|
||||
As you can see, this is a list of @var{(MATCH EXPANSION...)} elements.
|
||||
The @var{match} is a regular expression that matches the visited file
|
||||
name, and each @var{expansion} may refer to match groups by using
|
||||
@samp{\\1} and so on. The resulting expansion string is then applied
|
||||
to the file system to see if any files match this expansion
|
||||
(interpreted as a regexp).
|
||||
As you can see, this is a list of @w{@code{(@var{MATCH}
|
||||
@var{EXPANSION}...)}} elements. The @var{match} is a regular
|
||||
expression that matches the visited file name, and each
|
||||
@var{expansion} may refer to match groups by using @samp{\\1} and so
|
||||
on. The resulting expansion string is then applied to the file system
|
||||
to see if any files match this expansion (interpreted as a regexp).
|
||||
|
||||
@vindex find-file-hook
|
||||
@vindex find-file-not-found-functions
|
||||
|
|
|
@ -3284,7 +3284,7 @@ one key sequence.
|
|||
The argument @var{disable-text-conversion}, if non-@code{nil}, means
|
||||
that system input methods will not directly perform edits to buffer
|
||||
text while this key sequence is being read; user input will always
|
||||
generated individual key events instead. @xref{Misc Events} for more
|
||||
generated individual key events instead. @xref{Misc Events}, for more
|
||||
about text conversion.
|
||||
|
||||
In the following example, Emacs displays the prompt @samp{?} in the
|
||||
|
|
|
@ -1775,7 +1775,7 @@ program was running when the filter function was started. However, if
|
|||
This makes it possible to use the Lisp debugger to debug filter
|
||||
functions. @xref{Debugger}. If an error is caught, Emacs pauses for
|
||||
@code{process-error-pause-time} seconds so that the user sees the
|
||||
error. @xref{Asynchronous Processes}
|
||||
error. @xref{Asynchronous Processes}.
|
||||
|
||||
Many filter functions sometimes (or always) insert the output in the
|
||||
process's buffer, mimicking the actions of the default filter.
|
||||
|
|
Loading…
Add table
Reference in a new issue