unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: Arthur Miller <arthur.miller@live.com>
Cc: 0278C47F-42CE-45C4-B789-83C57DF1A191@bydasein.com,
	Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org, Boruch Baum <boruch_baum@gmx.com>,
	monnier@iro.umontreal.ca
Subject: Re: declare function/macro private
Date: Tue, 8 Jun 2021 07:49:20 +0200	[thread overview]
Message-ID: <20210608054920.GA17143@tuxteam.de> (raw)
In-Reply-To: <AM9PR09MB4977877ABCC09037790ACAF596379@AM9PR09MB4977.eurprd09.prod.outlook.com>

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

On Tue, Jun 08, 2021 at 06:20:46AM +0200, Arthur Miller wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:

[...]

> > My concern isn't the declaration, but the scope of its consequences. For
> > example, an emacs user who does no elisp programming would be happy to
> > have no private variable/function results appear among completion
> > candidates [...]

> How would Emacs now if it was a programmer asking or not programmer
> asking? :-)

That's exactly my take. Enforcing things because "I think they should
be this way" is not the kind of software I like to interact with.

Cheers
 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2021-06-08  5:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07  3:35 declare function/macro private Boruch Baum
2021-06-07  4:49 ` Paul W. Rankin via Emacs development discussions.
2021-06-07  5:59   ` Stefan Monnier
2021-06-07  6:45     ` Paul W. Rankin via Emacs development discussions.
2021-06-07 12:39 ` Eli Zaretskii
2021-06-08  1:14   ` Boruch Baum
2021-06-08  4:20     ` Arthur Miller
2021-06-08  5:49       ` tomas [this message]
2021-06-08 15:46     ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2021-06-06  4:27 Paul W. Rankin via Emacs development discussions.
2021-06-06  7:09 ` Omar Polo
2021-06-06  7:18   ` Paul W. Rankin via Emacs development discussions.
2021-06-06  9:53 ` Lars Ingebrigtsen
2021-06-06 12:43   ` Paul W. Rankin via Emacs development discussions.
2021-06-08  9:43     ` Lars Ingebrigtsen
2021-06-08 17:26       ` Robin Tarsiger
2021-06-06 18:05 ` Stefan Monnier
2021-06-06 18:12   ` Tassilo Horn
2021-06-06 20:12     ` Stefan Monnier
2021-06-07  0:51       ` Paul W. Rankin via Emacs development discussions.
2021-06-07  1:37         ` Arthur Miller
2021-06-07  1:43           ` Paul W. Rankin via Emacs development discussions.
2021-06-07 13:38             ` Arthur Miller
2021-06-07  0:59   ` Paul W. Rankin via Emacs development discussions.
2021-06-07  2:54     ` Stefan Monnier
2021-06-07 18:24       ` Arthur Miller

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=20210608054920.GA17143@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=0278C47F-42CE-45C4-B789-83C57DF1A191@bydasein.com \
    --cc=arthur.miller@live.com \
    --cc=boruch_baum@gmx.com \
    --cc=eliz@gnu.org \
    --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 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).