procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document the 'list-FOO' convention

Browse source 
* doc/lispref/tips.texi (Coding Conventions): Document the
list-FOO convention.
This commit is contained in:
Eli Zaretskii 2017-09-22 12:41:00 +03:00
parent d24ec58540
commit 0273916618
1 changed files with 7 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/lispref/tips.texi
View file

@ -68,10 +68,13 @@ costs.}. Use two hyphens to separate prefix and name if the symbol is
not meant to be used by other packages. not meant to be used by other packages.
Occasionally, for a command name intended for users to use, it is more Occasionally, for a command name intended for users to use, it is more
convenient if some words come before the package's name prefix. And convenient if some words come before the package's name prefix. For
constructs that define functions, variables, etc., work better if they example, it is our convention to have commands that list objects named
start with @samp{defun} or @samp{defvar}, so put the name prefix later as @samp{list-@var{something}}, e.g., a package called @samp{frob}
on in the name. could have a command @samp{list-frobs}, when its other global symbols
begin with @samp{frob-}. Also, constructs that define functions,
variables, etc., work better if they start with @samp{defun} or
@samp{defvar}, so put the name prefix later on in the name.
This recommendation applies even to names for traditional Lisp This recommendation applies even to names for traditional Lisp
primitives that are not primitives in Emacs Lisp---such as primitives that are not primitives in Emacs Lisp---such as