From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: RE: what is the convention for `info' and `Info'?
Date: Tue, 14 Jun 2011 13:42:55 -0700 [thread overview]
Message-ID: <F29C540BC79E4BE799F612216EEF2CD1@us.oracle.com> (raw)
In-Reply-To: <2F534BF7BCA34199A6EBCF37A4382914@us.oracle.com>
Resending - no response. Can one of the maintainers speak to this? What is the
intention/design/convention?
> Library info.el has a mix of vars, faces, and functions with
> names that begin with `info' or `Info'. What is the convention
> here - when to use one or the other? There doesn't seem to be
> any rhyme or (non-hysterical) reason.
>
> There are internal vars and user options that use `Info'.
> All defvars except `info-tool-bar-map' use `Info' (53/54).
> All defcustoms use `Info'. But all
> deffaces (which are also for user customization) use `info'.
>
> There are commands that use `info' and commands that use
> `Info'. Perhaps the intended difference here is commands
> within *info* and commands to be used anywhere (?).
> Similarly, there are non-interactive functions that use one or
> the other.
>
> This cannot, AFAICT, be helpful to users (or to maintainers,
> for that matter).
next prev parent reply other threads:[~2011-06-14 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 19:16 what is the convention for `info' and `Info'? Drew Adams
2011-06-14 20:42 ` Drew Adams [this message]
2011-06-14 21:57 ` Stephen J. Turnbull
2011-06-14 22:18 ` PJ Weisberg
2011-06-14 23:20 ` Stephen J. Turnbull
2011-06-14 22:00 ` Juri Linkov
2011-06-15 23:36 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F29C540BC79E4BE799F612216EEF2CD1@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).