all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: library/package filename prefixes
Date: Mon, 04 May 2020 22:51:05 -0400	[thread overview]
Message-ID: <E1jVnfl-0005qG-DQ@fencepost.gnu.org> (raw)
In-Reply-To: <519940ba-6cf7-4597-8ca7-13961d11b6ae@default> (message from Drew Adams on Mon, 4 May 2020 09:19:02 -0700 (PDT))

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > FWIW, I proposed a minimum of 2 chars (plus hyphen).
  > I think that's good.  What's a good reason for going
  > to 3 instead of 2?

The namespace of 2-letter prefixes seems somewhat cramped to me.
Every package that uses such a prefix will have to be discussed
regarding whether it is entitled to one.

A rule saying "use at least three" would not cause any real trouble
and would mostly eliminate that problem.

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2020-05-05  2:51 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
2020-05-04 15:49         ` Stefan Monnier
2020-05-04 16:19       ` Drew Adams
2020-05-05  2:51         ` Richard Stallman [this message]
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=E1jVnfl-0005qG-DQ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.