From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 3314@emacsbugs.donarmstrong.com, rms@gnu.org, emacs-pretest-bug@gnu.org
Subject: bug#3314: 23.0.93; Emacs manual, node RegPos
Date: Sun, 17 May 2009 12:00:05 -0700 [thread overview]
Message-ID: <002c01c9d721$b17f91b0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <87eiunsh7c.fsf@mail.jurta.org>
> In your original bug report you wrote:
>
> Good node names let you find appropriate nodes using completion etc.
>
> However, the name `Positional Register' makes it harder to find all
> register related nodes using completion because it doesn't begin
> with a common word. Currently these node names begin with a
> common prefix `Reg'. So it would be better if they all had a
> common prefix that is a complete and clear word `Register':
>
> RegPos -> Register Positions
> RegText -> Register Text
> RegRect -> Register Rectangles
> RegConfig -> Register Configurations
> RegNumbers -> Register Numbers
> RegFiles -> Register Files
I agree 100%. Thanks.
next prev parent reply other threads:[~2009-05-17 19:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 22:29 bug#3314: 23.0.93; Emacs manual, node RegPos Drew Adams
2009-05-17 17:23 ` Richard M Stallman
2009-05-17 17:38 ` Drew Adams
2009-05-17 18:45 ` Juri Linkov
2009-05-17 19:00 ` Drew Adams [this message]
2009-05-17 19:05 ` Drew Adams
2009-05-17 19:17 ` Juri Linkov
2009-05-17 19:47 ` Drew Adams
2009-05-17 21:27 ` Juri Linkov
2009-05-17 21:38 ` Drew Adams
2009-05-18 16:45 ` Richard M Stallman
2009-05-18 3:24 ` Stefan Monnier
2011-07-11 15:42 ` Lars Magne Ingebrigtsen
2011-07-12 19:06 ` Richard Stallman
2011-07-12 19:34 ` Lars Magne Ingebrigtsen
2011-07-13 18:32 ` Richard Stallman
2011-07-12 19:42 ` Lars Magne Ingebrigtsen
2009-05-18 16:44 ` Richard M Stallman
2009-05-22 4:36 ` Kevin Rodgers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002c01c9d721$b17f91b0$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=3314@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=juri@jurta.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.