From: Jean Louis <bugs@gnu.support>
To: Christopher Dimech <dimech@gmx.com>
Cc: carlmarcos@tutanota.com, Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Placement of list within an interactive clause
Date: Sun, 17 Jul 2022 05:16:28 +0300 [thread overview]
Message-ID: <YtNw/IR7hDvgbQqG@protected.localdomain> (raw)
In-Reply-To: <trinity-b062cf3f-35ec-48b4-a5b6-191de351b6ed-1658022791215@3c-app-mailcom-bs14>
* Christopher Dimech <dimech@gmx.com> [2022-07-17 04:53]:
> > Emacs is very interactive.
> >
> > Do you maybe think that functions without (interactive) declaration
> > shall not ask user anything?
> >
> > When invoked only from Lisp there are many uses for such functions.
>
> Sure, but if you want a fully non-interactive function, do not call
> minibuffer functionality in the body of the function.
OK and now, how do I apply that advise? If I want X, then do not do
Y. Of course. But how is such advise practically useful?
What you are saying, seem to come from programming theories.
> > Does it really need to be text input to be considered interactive?
> >
> > Logging of activities may be displayed in a buffer, that is
> > interactive too. Input alone is not interaction. Changing Emacs style
> > is also interaction and need not be invoked interactively.
>
> Defining interaction too broadly makes it useless, because it cannot
> distinguish between anything. For emacs, interaction should always
> be associated with direct user input (never with automatic input or
> customisation within the program through elisp, unless you ask the user
> to directly input operational inputs).
If you decide to manipulate paragraph it is direct user input. If you
press button to open browser it is direct user input. All key presses
represent direct user input.
Including sound recording, it is also direct user input.
What would be example of indirect user input? Let me know about it.
> For the broader context one can describe "intercommunication" with emacs.
> Interactive in emacs in most times associated with user interaction via
> M-x or keybinding.
Word may have different definitions. Which definition applies depends
of the context of the word. You are mixing both Emacs definition of
(interactive) and common definitions. And then you insist that a beep,
flash, movement of window borders, text scaling, paragraph
manipulations and similar are not interactive, but only minibuffer
input is to be considered interactive. And now we have a new word
"intercommunication" as well. Too much theory, too little practical
use. In general, theory does not bring nothing without practical use.
What is (interactive) is not same as "interactive" as in English
language.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-07-17 2:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 18:14 Placement of list within an interactive clause carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 18:34 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-14 19:24 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 20:15 ` Philip Kaludercic
2022-07-14 20:30 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-14 20:52 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 21:12 ` Stefan Monnier
2022-07-14 21:15 ` carlmarcos--- via Users list for the GNU Emacs text editor
[not found] ` <jwv7d4f761t.fsf-monnier+emacs@gnu.org-N6yYlrA----2>
2022-07-16 23:01 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-17 2:38 ` Stefan Monnier
[not found] ` <jwvcze4pj2d.fsf-monnier+emacs@gnu.org-N790PCt----2>
2022-07-17 3:02 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-17 13:34 ` Stefan Monnier
2022-07-14 21:23 ` [External] : " Drew Adams
2022-07-14 22:31 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 22:52 ` [External] : " Drew Adams
[not found] ` <SJ0PR10MB54881126A1B0DB238AE8B82BF3889@SJ0PR10MB5488.namprd10.prod.outlook.com-N6yu_1j----2>
2022-07-15 20:05 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-15 7:26 ` Jean Louis
2022-07-15 8:19 ` Christopher Dimech
2022-07-15 10:14 ` Jean Louis
2022-07-15 10:32 ` Christopher Dimech
2022-07-15 21:03 ` Jean Louis
2022-07-15 21:22 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-15 21:31 ` Jean Louis
2022-07-15 22:53 ` Christopher Dimech
[not found] ` <YtHcni0c1ZTL+V8R@protected.localdomain-N72lwEe----2>
2022-07-16 22:08 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-16 23:40 ` Jean Louis
2022-07-17 1:22 ` [External] : " Drew Adams
2022-07-17 2:04 ` RE: [External] : " Christopher Dimech
2022-07-17 1:53 ` Christopher Dimech
2022-07-17 2:16 ` Jean Louis [this message]
2022-07-17 2:46 ` Christopher Dimech
2022-08-01 11:52 ` Emanuel Berg
2022-07-15 19:55 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-15 21:08 ` Jean Louis
2022-07-15 21:54 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-16 10:15 ` Jean Louis
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=YtNw/IR7hDvgbQqG@protected.localdomain \
--to=bugs@gnu.support \
--cc=carlmarcos@tutanota.com \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@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.
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).