bug#7154: Documentation: `load-history' entries of the form `atom'

bug#7154: Documentation: `load-history' entries of the form `atom'

[MON KEY]

current with bzr revision 101767

Documentation of `load-history' does not mention that in addition to
the cons forms which occur in the cdr position of each alist element
an entry may also be an atomic symbol.

,---- (documentation 'load-history)
|
| { ... }
|
| Each entry has the form `(provide . FEATURE)',
| (require . FEATURE)', `(defun . FUNCTION)', `(autoload . SYMBOL)',
| (defface . SYMBOL)', or `(t . SYMBOL)'.
|
| { ... }
|
`----

The above statement is incorrect.
An entry may also be an atom of the type:

 <SYMBOL>

This format occurs for `defvar'd and `defconst'd forms provided by a
feature.  For example:

(memq 'Info-menu-entry-name-re
                 (load-history-filename-element "info"))

(atom (car (memq 'Info-menu-entry-name-re
                 (load-history-filename-element "info"))))

(consp (cadr (memq 'Info-menu-entry-name-re
                 (load-history-filename-element "info"))))


--
/s_P\

bug#7154: Documentation: `load-history' entries of the form `atom'

[Lars Magne Ingebrigtsen]

MON KEY <monkey@sandpframing.com> writes:

> Documentation of `load-history' does not mention that in addition to
> the cons forms which occur in the cdr position of each alist element
> an entry may also be an atomic symbol.

This is now fixed.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/