From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "'Help-Gnu-Emacs (help-gnu-emacs@gnu.org)'" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Making a function than can only be used interactively
Date: Tue, 5 Jul 2022 14:02:55 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488C35538E29A7ABC29755FF3819@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <jwva69ofqxj.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
> > Depends whether the person coding that function thinks it is.
> > What can he do then? Issue warning as you suggested with `declare`?
>
> I don't think we can answer this in the abstract. So, we'd first need
> to have some concrete scenario before we can start discussing it.
Yup. Has any concrete description been presented
in this thread that makes clear what the real
problem to be solved is - the use case behind the
question?
I've only browsed the thread, so apologies if some
actual problem (and its "why") has been specified.
From just perusing, I haven't noticed any.
As I guessed before, I'm still guessing (so far):
there's an X-Y problem under the covers here
somewhere...)
What is it that OP is _really_ trying to do/solve?
I'm guessing that's behind an inability by folks
who've coded zillions of functions to understand
what's being asked/requested. What's the problem?
https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 14371 bytes --]
next prev parent reply other threads:[~2022-07-05 14:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 21:07 Making a function than can only be used interactively Christopher Dimech
2022-07-04 21:45 ` Stefan Monnier
2022-07-04 22:05 ` Christopher Dimech
2022-07-04 22:35 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-05 14:02 ` Drew Adams [this message]
2022-07-05 15:35 ` RE: [External] : " Christopher Dimech
2022-07-05 16:34 ` Drew Adams
[not found] ` <trinity-568779dc-3120-4001-a48b-df09d38f19a1-1657055684424@3c-app-mailcom-bs14>
2022-07-05 22:40 ` FW: " Drew Adams
2022-07-05 23:05 ` Christopher Dimech
2022-07-04 23:33 ` Christopher Dimech
-- strict thread matches above, loose matches on Subject: below --
2022-07-03 19:16 carlmarcos--- via Users list for the GNU Emacs text editor
[not found] ` <N64WnlX--3-2@missing-mail-id>
2022-07-03 19:36 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-03 20:14 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-03 21:29 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-03 22:01 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-03 22:45 ` carlmarcos--- via Users list for the GNU Emacs text editor
[not found] ` <jwvczelllyq.fsf-monnier+emacs@gnu.org-N65lQ2m----2>
2022-07-04 10:36 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-04 10:55 ` Tassilo Horn
2022-07-04 19:17 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-04 19:40 ` Stefan Monnier
2022-07-04 19:50 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-06 0:07 ` Jean Louis
2022-07-06 20:00 ` Christopher Dimech
2022-07-06 20:29 ` Jean Louis
2022-07-07 21:06 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-07 21:28 ` Emanuel Berg
2022-07-07 22:14 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-08 6:08 ` Yuri Khan
2022-07-08 6:30 ` Emanuel Berg
2022-07-08 6:55 ` Yuri Khan
2022-07-08 16:14 ` Christopher Dimech
2022-07-08 20:29 ` [External] : " Drew Adams
2022-07-08 21:09 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-08 22:17 ` Drew Adams
2022-07-08 22:34 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-09 14:53 ` Drew Adams
2022-08-09 2:24 ` Emanuel Berg
2022-07-09 2:06 ` Emanuel Berg
2022-07-08 23:19 ` Emanuel Berg
2022-07-04 20:53 ` 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
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=SJ0PR10MB5488C35538E29A7ABC29755FF3819@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).