all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 25776@debbugs.gnu.org
Subject: bug#25776: 24.5; `imenu--generic-function' is not internal
Date: Fri, 26 Jul 2019 14:50:10 +0200	[thread overview]
Message-ID: <8736itm03h.fsf@mouse.gnus.org> (raw)
In-Reply-To: <ad106f29-5edc-4a21-acec-b52e7a05353b@default> (Drew Adams's message of "Fri, 17 Feb 2017 09:01:00 -0800 (PST)")

Drew Adams <drew.adams@oracle.com> writes:

> It is a relatively recent mania to name functions and variables using
> `--' to indicate that they are internal.  This function should not be so
> named.  It is referred to in several doc strings.  We do not (should
> not) name functions specially just because we want to indicate that
> users probably do not want to redefine them or that they are especially
> likely to have their implementations changed in the future.  We don't
> name `forward-char' `forward--char' just because it is (truly)
> "internal".

That's not the meaning of -- - it's that other packages probably
shouldn't rely on them.  Everything should rely on `forward-char', so
that's not a very good comparison.

It is slightly eccentric to name a function that's that user-forward as
`imenu--generic-function' is with two dashes...  My preference would be
to not do that, but we do do similar things here and there with some
filter functions and the like that are meant to be values for variables
that can be tweaked, so I don't think this is so abnormal as all that.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-07-26 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 17:01 bug#25776: 24.5; `imenu--generic-function' is not internal Drew Adams
2019-07-26 12:50 ` Lars Ingebrigtsen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736itm03h.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=25776@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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.