all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: library/package filename prefixes
Date: Sat, 2 May 2020 14:35:53 -0400	[thread overview]
Message-ID: <E43E23A3-CA9E-46E8-9956-F10E2C58A929@gmail.com> (raw)
In-Reply-To: <bd915695-9b5d-4c8f-9732-8a73dda5ce78@default>



> On May 1, 2020, at 5:07 PM, Drew Adams <drew.adams@oracle.com> wrote:
> 
> FWIW -
> 
> I think the "Emacs Lisp Coding Conventions" node
> of the Elisp manual should be amended to say that
> a library/package prefix should be at least 2
> chars followed by a hyphen (`-').  And even add
> that 3 or more is preferable.
> 

I agree

> https://www.gnu.org/software/emacs/manual/html_node/elisp/Coding-Conventions.html
> 
> (Should we also say that the first char should
> not be a hyphen, or that not all prefix chars
> should be hyphens, or ...?)
> 
> I think it's misguided, short-sighted, and even
> perhaps a bit self-centered for people to have
> named libraries `-.el', `s.el', etc. and used
> function and variable names with prefix `-',
> `s-', etc.
> 

That might be too strong, but indeed that lacks some consideration.

Yuan




  reply	other threads:[~2020-05-02 18:35 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 [this message]
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
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=E43E23A3-CA9E-46E8-9956-F10E2C58A929@gmail.com \
    --to=casouri@gmail.com \
    --cc=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 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.