From: steve-humphreys@gmx.com
To: steve-humphreys@gmx.com
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Changing buffer-local variables to cycle emacs options
Date: Tue, 29 Dec 2020 07:28:51 +0100 [thread overview]
Message-ID: <trinity-08bfcf88-4b4a-4239-9fd9-628d4c9ce0f6-1609223330916@3c-app-mailcom-bs13> (raw)
In-Reply-To: <trinity-8284d63c-135a-4770-894e-a4db06e86e07-1609218831254@3c-app-mailcom-bs13>
;;(defvar gstate 0)
(defun gstate-cycle ()
"Toggle Display-Line-Numbers mode in all buffers."
(interactive)
(let ((n gstate))
(pcase n
(1 (setq-local gstate 2)
(message "%s" "gstate 1"))
(2 (setq-local gstate 3)
(message "%s" "gstate 2"))
(_ (setq-local gstate 1)
(message "%s" "gstate _")) )))
(global-set-key (kbd "H-1") #'gstate-cycle)
> Sent: Tuesday, December 29, 2020 at 10:43 AM
> From: steve-humphreys@gmx.com
> To: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Changing buffer-local variables to cycle emacs options
>
> I am getting the following Lisp error
>
> Debugger entered--Lisp error: (void-variable gstate)
> (let ((n gstate)) (cond ((eql n 1) (set (make-local-variable 'gstate) 2) (message "%s" "gstate 1")) ((eql n 2) (set (make-local-variable 'gstate) 3) (message "%s" "gstate 2")) (t (set (make-local-variable 'gstate) 1) (message "%s" "gstate _"))))
> gstate-cycle()
> funcall-interactively(gstate-cycle)
> call-interactively(gstate-cycle nil nil)
> command-execute(gstate-cycle)
>
> I am using the function below. The problem occurs when I comment out
> "(defvar gstate 0)". When I introduce the variable, the Lisp Error is
> not reported.
>
> One confusion that exists is that I want gstate buffer-local. But I think
> that using defvar is a mistake. Another think is to avoid defining gstate
> before calling the function. My plan was to have "pcase" do to the "(_"
> part if the buffer-local variable "gstate" is not defined, and then define
> it using "(setq-local gstate 1)".
>
> How can I code this properly?
>
> -------- code --------
>
> ;;(defvar gstate 0)
>
> (defun gstate-cycle ()
> (interactive)
>
> (let ((n gstate))
>
> (pcase n
> (1 (setq-local gstate 2)
> (message "%s" "gstate 1"))
>
> (2 (setq-local gstate 3)
> (message "%s" "gstate 2"))
>
> (_ (setq-local gstate 1)
> (message "%s" "gstate _")) )))
>
> (global-set-key (kbd "H-1") #'gstate-cycle)
>
>
>
>
>
>
next prev parent reply other threads:[~2020-12-29 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 5:13 Changing buffer-local variables to cycle emacs options steve-humphreys
2020-12-29 6:28 ` steve-humphreys [this message]
2020-12-29 14:17 ` Yuri Khan
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=trinity-08bfcf88-4b4a-4239-9fd9-628d4c9ce0f6-1609223330916@3c-app-mailcom-bs13 \
--to=steve-humphreys@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).