From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: monnier@iro.umontreal.ca, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: library/package filename prefixes
Date: Mon, 04 May 2020 17:30:44 +0300 [thread overview]
Message-ID: <83eerzojqj.fsf@gnu.org> (raw)
In-Reply-To: <E1jVRTL-0006Io-69@fencepost.gnu.org> (message from Richard Stallman on Sun, 03 May 2020 23:08:47 -0400)
> From: Richard Stallman <rms@gnu.org>
> Date: Sun, 03 May 2020 23:08:47 -0400
> Cc: drew.adams@oracle.com, emacs-devel@gnu.org
>
> In your list, some of the files do use a two-letter name prefix,
> but others do not.
>
> lisp/cedet/srecode/el.el does not. Neither does
> lisp/cedet/semantic/sb.el.
>
> lisp/emacs-lisp/pp.el does use a two-letter prefix.
> Perhaps we should change it.
>
> lisp/emacs-lisp/gv.el uses a two-letter prefix.
> I expect that the functions named starting 'gv-' are not used from a lot
> of user code, so it should not be hard to rename them.
>
> Does anyone oppose renaming them?
>
> lisp/bs.el does use 'bs-' as a nane prefix.
> I have a hunch the entry points are not called very often.
> Should we rename that?
>
> It would be easy to rename po.el and its one entry point,
> which is called in just one place.
>
> Eli, what do you think about renaming these files
> if doing so is painless?
I see no reason to rename the prefixes of pp, gv, and po. They are
all accepted acronyms. Also, the consensus seems to be that re- is a
good prefix, so why not those?
If we don't rename the prefixes, there's no need to rename the files.
next prev parent reply other threads:[~2020-05-04 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 21:07 library/package filename prefixes Drew Adams
2020-05-02 18:35 ` Yuan Fu
2020-05-03 3:39 ` Richard Stallman
2020-05-03 4:17 ` Stefan Monnier
2020-05-04 3:08 ` Richard Stallman
2020-05-04 12:13 ` Eric Ludlam
2020-05-04 14:30 ` Eli Zaretskii [this message]
2020-05-04 15:49 ` Stefan Monnier
2020-05-04 16:19 ` Drew Adams
2020-05-05 2:51 ` Richard Stallman
2020-05-05 4:39 ` Drew Adams
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=83eerzojqj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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.