From: daniela-spit@gmx.it
To: Drew Adams <drew.adams@oracle.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: Re: RE: Removing line and column number settings from some buffers
Date: Sun, 6 Dec 2020 00:05:24 +0100 [thread overview]
Message-ID: <trinity-d8a24c23-65e0-41ac-bead-a52bf9a0d791-1607209524319@3c-app-mailcom-bs06> (raw)
In-Reply-To: <a713329e-d621-4e73-b911-3d7140086c85@default>
> Sent: Saturday, December 05, 2020 at 11:57 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: daniela-spit@gmx.it, "Michael Heerdegen" <michael_heerdegen@web.de>
> Cc: help-gnu-emacs@gnu.org
> Subject: RE: Removing line and column number settings from some buffers
>
> > Look at this code. Correct, you don't need a variable for storing,
> > but what is happening with n in the following code.
> >
> > The byte compiler complains about the variable n
> >
> > (defun auto-fill-cycle ()
> > (interactive)
> > (setq-local n (get 'auto-fill-cycle 'state))...)
>
> `n' is a free variable. Add a `defvar' for it, if you
> don't want Emacs to tell you about that.
Would that be a valid approach or is it just to stop emacs complaining?
Was considering to use
(let (n)
...
next prev parent reply other threads:[~2020-12-05 23:05 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 15:34 Removing line and column number settings from some buffers daniela-spit
2020-12-02 21:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-02 23:21 ` daniela-spit
2020-12-02 23:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-02 23:32 ` daniela-spit
2020-12-02 23:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-02 23:57 ` daniela-spit
2020-12-03 0:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-03 22:14 ` Michael Heerdegen
2020-12-03 22:19 ` daniela-spit
2020-12-03 22:22 ` Jean Louis
2020-12-03 22:33 ` daniela-spit
2020-12-03 22:52 ` Jean Louis
2020-12-03 23:09 ` daniela-spit
2020-12-04 0:38 ` Christopher Dimech
2020-12-04 1:16 ` Michael Heerdegen
2020-12-04 1:33 ` Christopher Dimech
2020-12-04 2:10 ` daniela-spit
2020-12-04 2:42 ` Christopher Dimech
2020-12-04 6:10 ` Jean Louis
2020-12-04 6:31 ` Christopher Dimech
2020-12-04 8:40 ` Eli Zaretskii
2020-12-05 5:13 ` Christopher Dimech
2020-12-05 15:41 ` Drew Adams
2020-12-05 17:58 ` Jean Louis
2020-12-05 18:16 ` Drew Adams
2020-12-05 18:57 ` Jean Louis
2020-12-04 2:46 ` Michael Heerdegen
2020-12-04 3:12 ` Christopher Dimech
2020-12-04 4:16 ` daniela-spit
2020-12-04 4:36 ` daniela-spit
2020-12-04 5:58 ` daniela-spit
2020-12-04 7:19 ` Jean Louis
2020-12-05 4:42 ` daniela-spit
2020-12-05 21:32 ` Michael Heerdegen
2020-12-05 21:35 ` Michael Heerdegen
2020-12-05 22:54 ` daniela-spit
2020-12-05 22:57 ` Drew Adams
2020-12-05 23:05 ` daniela-spit [this message]
2020-12-05 23:37 ` Drew Adams
2020-12-05 23:53 ` daniela-spit
2020-12-04 7:40 ` Jean Louis
2020-12-04 6:07 ` Jean Louis
2020-12-03 23:24 ` Michael Heerdegen
2020-12-03 23:36 ` daniela-spit
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-d8a24c23-65e0-41ac-bead-a52bf9a0d791-1607209524319@3c-app-mailcom-bs06 \
--to=daniela-spit@gmx.it \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).