bug#3314: 23.0.93; Emacs manual, node RegPos

"Drew Adams" <[email protected]>
Newsgroups gmane.emacs.bugs,gmane.emacs.pretest.bugs
Message-ID <[email protected]>
1. The node name, `RegPos', is not too good. There is no need for
camelCase in node names, and `Reg Pos' would still be unnecessarily
abbreviated. Likewise, for the other register nodes (RegText, RegRect
etc.).  Emacs does not normally name Info nodes this way. Good node
names let you find appropriate nodes using completion etc.
 
2. Please mention the use of a prefix arg for`C-x r SPC'.  The doc
string for this command mentions `C-u', but the manual does not.
 
3. Please mention (here) that `C-x r j' will jump to any register that
saves a position (file, window/frame config), not just one created by
`C-x r SPC'. And, in particular, if you used a prefix arg with `C-x r
SPC', the saved frame config is restored.
 
4. Consider reorganizing the register doc, to mention that some
register commands store positional information (e.g. point, file,
window config, frame config), and others do not (text, rectangle,
number).  Mention that you can return to any saved position using `C-x
r j' - i.e., this works for point, file, and so on, and you can insert
any non-positional information using `C-x r i'.
 
IOW, divide the register commands into two groups: positional and
non-positional information.  For the first group, what you do with the
stored information is revisit the location.  For the second group,
what you do with the stored information is either modify it
(e.g. increment a number) or insert it as text in a buffer.  This
provides an overview, and makes clear that (1) `C-x r j' applies to
any saved positional information, and (2) `C-x r i' applies to any
non-positional information.
 
In GNU Emacs 23.0.93.1 (i386-mingw-nt5.1.2600)
 of 2009-05-02 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.