From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: (interactive) and &optional Date: Sat, 25 Mar 2023 00:42:49 +0300 Message-ID: References: <25628.42021.832534.376361@woitok.gmail.com> <87sfdt6feg.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29609"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.2.9+54 (af2080d) (2022-11-21) Cc: Dr Rainer Woitok , Help-Gnu-Emacs@Gnu.Org To: Philip Kaludercic Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sat Mar 25 15:13:02 2023 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pg4di-0007Sf-Hs for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 25 Mar 2023 15:13:02 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pg4cw-0007Td-5M; Sat, 25 Mar 2023 10:12:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pg4cr-0007TK-7Q for Help-Gnu-Emacs@gnu.org; Sat, 25 Mar 2023 10:12:09 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pg4cp-0000EF-GU for Help-Gnu-Emacs@gnu.org; Sat, 25 Mar 2023 10:12:08 -0400 Original-Received: from localhost ([::ffff:197.239.5.205]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 00000000000F5D08.00000000641F0119.00003329; Sat, 25 Mar 2023 07:11:36 -0700 Mail-Followup-To: Philip Kaludercic , Dr Rainer Woitok , Help-Gnu-Emacs@Gnu.Org Content-Disposition: inline In-Reply-To: <87sfdt6feg.fsf@posteo.net> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -6 X-Spam_score: -0.7 X-Spam_bar: / X-Spam_report: (-0.7 / 5.0 requ) BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, RCVD_IN_SBL=0.141, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:143110 Archived-At: * Philip Kaludercic [2023-03-24 23:54]: > > I do not like involving `interactive' at all, so I do the handling by > > providing optional argument and telling function to check for it, or > > ask for it. > > > > (defun search-something (&optional query) > > "Search something by using QUERY." > > (interactive) > > (let* ((query (or query (read-from-minibuffer "Query: ")))) > > (do-the-search query))) > > The issue here is that the function is difficult to re-use from other > scripts. If the interactive stuff is encapsulated within an > (interactive) form then you avoid the issue. I understand the meaning in general, though I do not understand what is the mentioned issue. Could you explain it? It is interesting as I use those functions from other functions. This should be the classic Emacs Lisp approach: (defun search-something (query) "Search something by using QUERY." (interactive "MQuery: ") (message query)) (progn (search-something "Hello")) ➜ "Hello" (progn (search-something)) ➜ "Ok here" This should be my approach: (defun search-something (&optional query) "Search something by using QUERY." (interactive) (let ((query (or query (read-from-minibuffer "Query: ")))) (message query))) (progn (search-something "Hello")) ➜ "Hello" (progn (search-something)) ➜ "Ok here" - while `interactive' declaration may shorten some code, it may as well complicated readability of function Here is short version where buffer must be existing buffer: (defun my-message-buffer (buffer) "Message name of my BUFFER." (interactive "b") (message buffer)) That short function I do not know how to make easy without (interactive "b"). For majority of uses in my code I do not use arguments to `interactive' and there are no issues so far. I find `interactive' complex and would like to know why it was invented. (info "(elisp) Using Interactive") (info "(elisp) Interactive Codes") Tell me examples on what issues you encounter and pointers to implications. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/