When going through objects.texi the oddest part I found,
was the section on comments. To me comments have nothing
to do with objects, and while tangentially related to read syntax
they are not part of any particular object's read syntax.

Since I've only gone through the two files so far, I can only
suggest moving it into intro.texi. This would keep it close to
the beginning of the reference. Below is the old menu from
objects.texi and the menu for where I propose to move the
node in intro.texi. Patch attached, with Changelog entry.

Old placement:

@menu
* Printed Representation::      How Lisp objects are represented as text.
* Comments::                    Comments and their formatting conventions.
* Programming Types::           Types found in all Lisp systems.
* Editing Types::               Types specific to Emacs.
* Circular Objects::            Read syntax for circular structure.
* Type Predicates::             Tests related to types.
* Equality Predicates::         Tests of equality between any two objects.
@end menu

New placement

@menu
* Some Terms::               Explanation of terms we use in this manual.
* nil and t::                How the symbols @code{nil} and @code{t} are used.
* Comments::                    Comments and their formatting conventions.
* Evaluation Notation::      The format we use for examples of evaluation.
* Printing Notation::        The format we use when examples print text.
* Error Messages::           The format we use for examples of errors.
* Buffer Text Notation::     The format we use for buffer contents in examples.
* Format of Descriptions::   Notation for describing functions, variables, etc.
@end menu

To me the node on comments fits more naturally with the
other notation related nodes.

Josh

P.S. I tried to fix the text duplication in the e-mail, hopefully it's
back to normal.

Attachment: comments-move.patch
Description: Binary data

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

Reply via email to