unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Placement of list within an interactive clause
Date: Mon, 01 Aug 2022 13:52:46 +0200	[thread overview]
Message-ID: <87les8ch9t.fsf@dataswamp.org> (raw)
In-Reply-To: YtE+AfYzGNxwRX/G@protected.localdomain

Jean Louis wrote:

> However, I have explained in the above example of mine that
> such input may be provided in the function itself. And it
> looks to me that it is better handled that way than through
> `interactive' declaration.

Cases that can't be handled by the ARG-DESCRIPTOR argument can
be handled with Lisp, if so the best place for that is within
the `interactive' form ...

> So this is the way to go:
>
> (defun my-fun-2 (&optional name)
>   (interactive)
>   (let ((name (or name (read-from-minibuffer "Name: "))))
>     (message "Hello %s" name)))

Here it is better to make the argument non-optional,
i.e. mandatory from Lisp, and interactively like this

  (interactive "sName: ")

> That means, when there is declaration (interactive), that
> function becomes accessible through M-x invokation, and it
> may be bound to a key.

Yes, it becomes a "command".

I don't know if I like this solution TBH, I think all
functions should be callable from everywhere and make sense
everywhere, called in whatever way they might ...

Dutch total football, if you like ...

> Function `interactive' DOES NOT make function "interactive"
> in the other contexts in English language, there is special
> meaning in the Emacs Lisp context. Programming meaning is
> simply not same to English context.

Programming should always be in English but it isn't
English LOL :D

-- 
underground experts united
https://dataswamp.org/~incal




  parent reply	other threads:[~2022-08-01 11:52 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
2022-07-17  2:46                       ` Christopher Dimech
2022-08-01 11:52       ` Emanuel Berg [this message]
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=87les8ch9t.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --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).