From: Corwin Brust <corwin@bru.st>
To: goncholden <goncholden@protonmail.com>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>,
Emanuel Berg <moasenwood@zoho.eu>
Subject: Re: Function passing flag
Date: Tue, 8 Mar 2022 14:42:07 -0600 [thread overview]
Message-ID: <CAJf-WoQBjv=OfiCaWL=1pp0Z2KPp-mGqwh02X9zGRnhZCVGq6Q@mail.gmail.com> (raw)
In-Reply-To: <yoe8k6YKC0rBdvf-3GNHwY5GxDnE-I07UV_oYZAKAUAVJiitMLeKs-UD8rMf0MnK6c8mRfutbc8Uz9J55bMH3XPVkyKDUVQVhl_moGEQzgY=@protonmail.com>
On Tue, Mar 8, 2022 at 2:28 PM goncholden <goncholden@protonmail.com> wrote:
>
> Would like to use arg as a switch so I can enable or disable some emacs modes (customarily using
> value of 1 to enable, and -1 to disable). If no arg is supplied, I would like to enable the modes.
>
> How would I define the parameter outside the function, and then pass it through. I might require
> a buffer local variable.
>
One typical way of doing this would be to use the "universal
argument", also known as a "prefix argument":
(info "(elisp)Prefix Command Arguments")
Here's an example that would create an interactive command that
enables tool-bars and scroll-bars or, with a prefix argument, disables
them.
(defun my:enable-bars (&optional arg)
"Enable `tool-bar-mode' and `scroll-bar-mode'.
When ARG is non-nill, disable them."
(interactive "P")
(if arg
(progn (tool-bar-mode -1)
(scroll-bar-mode -1))
(tool-bar-mode 1)
(scroll-bar-mode 1)))
Once you evaluate this you can ensure both tool-bar and scroll bar
modes are active with:
M-x my:enable-bar RET
Or, to ensure both tool-bar and scroll-bar modes are disabled:
C-u M-x my:enable-bar RET
next prev parent reply other threads:[~2022-03-08 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 12:24 Function passing flag goncholden via Users list for the GNU Emacs text editor
2022-03-08 18:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-08 19:00 ` goncholden
2022-03-08 19:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-08 19:35 ` goncholden
2022-03-08 20:09 ` Corwin Brust
2022-03-08 20:15 ` Corwin Brust
2022-03-08 20:28 ` goncholden
2022-03-08 20:42 ` Corwin Brust [this message]
2022-03-08 20:55 ` goncholden
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='CAJf-WoQBjv=OfiCaWL=1pp0Z2KPp-mGqwh02X9zGRnhZCVGq6Q@mail.gmail.com' \
--to=corwin@bru.st \
--cc=goncholden@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).