unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master e0ee41d: Allow customizing the display of project file names when reading
Date: Thu, 16 May 2019 00:11:49 +0100	[thread overview]
Message-ID: <87mujn9utm.fsf@tcd.ie> (raw)
In-Reply-To: <424646bc-288c-d12a-d890-94c0b75f7915@yandex.ru> (Dmitry Gutov's message of "Wed, 15 May 2019 23:31:57 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 15.05.2019 20:46, Basil L. Contovounesios wrote:
>> Sorry if this has been discussed before, and maybe it's just me, but I
>> don't think it makes sense to offer internal double hyphen functions as
>> alternatives for a user option, let alone to point the user to such an
>> internal function which lacks a docstring, "for the argument list".
>
> No, we never discussed this in particular. So I pushed the cleanest version that
> made sense to me.

I'm grateful for the addition, but I think user options ought to also
make sense to the user.

> Do we not do that (put internal functions as possible values of a user option)?

Sorry, the emphasis in my last message was meant to be on the lack of
any description of the user option's arglist.  If the defcustom is to
refer the user elsewhere, that place might at least have a docstring.

Though I don't understand why the user would be presented with internal
functions as options (it makes it harder to distinguish internal from
external definitions and APIs), I don't feel strongly enough about it to
argue against it.

Thanks,

-- 
Basil



  reply	other threads:[~2019-05-15 23:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190514021209.16750.6451@vcs0.savannah.gnu.org>
     [not found] ` <20190514021212.977E5206A2@vcs0.savannah.gnu.org>
2019-05-15 17:46   ` [Emacs-diffs] master e0ee41d: Allow customizing the display of project file names when reading Basil L. Contovounesios
2019-05-15 20:31     ` Dmitry Gutov
2019-05-15 23:11       ` Basil L. Contovounesios [this message]
2019-05-16  9:51         ` Basil L. Contovounesios
2019-05-16 13:35           ` Dmitry Gutov
2019-05-16 22:31             ` Basil L. Contovounesios
2019-05-15 21:11     ` Stefan Monnier
2019-05-15 23:12       ` Basil L. Contovounesios

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=87mujn9utm.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=dgutov@yandex.ru \
    --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 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).