From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Should prefix variable be used in function argument list
Date: Fri, 08 Jul 2022 19:41:25 +0200 [thread overview]
Message-ID: <87bktzbiyi.fsf@dataswamp.org> (raw)
In-Reply-To: N6Tn2zv--3-2@tutanota.com
carlmarcos--- via Users list for the GNU Emacs text editor wrote:
> When one wants to use the prefix argument when calling an
> interactive function, should one include a prefix variable in
> the function argument list?
Yes, almost always. Keep the function body the same for
interactive/non-interactive by it referring to the function
args and not caring which of those ways they got there.
> Furthermore, should the prefix argument be defined as
> optional?
Yes, when possible, especially when it defaults to something
that makes sense.
All arguments that have a nil they can take on and that makes
sense, all those cand be optional if they appear to the right
of the last argument from that isn't optional. What will
happen it will just be nil which.
> How would one call the function non-interactively for such
> function?
By typing it's name between parenthesis and evaluating it.
> Is it always necessary to have the prefix argument as the
> first argument in the function argument list?
No.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-07-08 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 17:12 Should prefix variable be used in function argument list carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-08 17:40 ` Philip Kaludercic
2022-07-08 17:53 ` Emanuel Berg
2022-07-08 18:11 ` Emanuel Berg
2022-07-09 8:59 ` Philip Kaludercic
2022-07-10 4:14 ` Emanuel Berg
2022-07-08 17:41 ` Emanuel Berg [this message]
2022-07-08 18:09 ` Emanuel Berg
2022-07-08 21:08 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-09 4:57 ` tomas
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=87bktzbiyi.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).