unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: Clemens Radermacher <clemens.radermacher@posteo.de>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	Adam Porter <adam@alphapapa.net>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal to change naming format to allow package-prefix/function-name
Date: Tue, 31 Dec 2019 16:48:53 +0200	[thread overview]
Message-ID: <8736d05z56.fsf@iki.fi> (raw)
In-Reply-To: <f2bceb8c-0025-c224-7dca-8ae8ff86e296@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

Clemens Radermacher [2019-12-31T13:06:16+01] wrote:

> Maybe using a char suffix would be better so it would better align
> with current conventions and make it easier to search/complete for
> users which expect those:
>
>     package-name-/function-name
>     package-name--/private-fun-name

Not sure if this is a good idea but here is yet another possibility: use
a capital letter in package name words and small letter in others:

    Package-Name-command-name
    Package-Name--private-name

-- 
///  OpenPGP key: 4E1055DC84E9DFF613D78557719D69D324539450
//  https://keys.openpgp.org/search?q=tlikonen@iki.fi
/  https://keybase.io/tlikonen  https://github.com/tlikonen

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 694 bytes --]

      reply	other threads:[~2019-12-31 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30  7:02 Proposal to change naming format to allow package-prefix/function-name Zachary Kanfer
2019-12-30 12:03 ` Juanma Barranquero
2019-12-30 13:12   ` Elias Mårtenson
2019-12-30 21:50   ` Zachary Kanfer
2019-12-31  0:45     ` Richard Stallman
2020-01-02 18:32       ` Sam Steingold
2019-12-31  0:06 ` Adam Porter
2019-12-31 10:14   ` Lars Ingebrigtsen
2019-12-31 10:54     ` Ihor Radchenko
2019-12-31 12:06     ` Clemens Radermacher
2019-12-31 14:48       ` Teemu Likonen [this message]

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=8736d05z56.fsf@iki.fi \
    --to=tlikonen@iki.fi \
    --cc=adam@alphapapa.net \
    --cc=clemens.radermacher@posteo.de \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).