unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: help-gnu-emacs@gnu.org
Subject: Re: setq-local: Wrong number of arguments
Date: Tue, 4 May 2021 09:59:07 +0200	[thread overview]
Message-ID: <trinity-a60f7886-5d4c-4e9d-820a-6c479f62fa6a-1620115147585@3c-app-mailcom-bs02> (raw)
In-Reply-To: <87o8dr56gl.fsf@fastmail.fm>

If he was using the older Emacs 25, that error will show up when
trying to set two local variables.

---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Tuesday, May 04, 2021 at 6:47 PM
> From: "Joost Kremers" <joostkremers@fastmail.fm>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: setq-local: Wrong number of arguments
>
>
> On Mon, May 03 2021, Christopher Dimech wrote:
> > I am gutting an error saying
> >
> > setq-local: Wrong number of arguments: (2 . 2), 4
> >
> > Have no idea what it means.
>
> The message means that you're calling a function that takes between two and two
> arguments but you're passing it four. Whether this function is indeed
> `setq-local` is doubtful, because `setq-local` can take more than two arguments,
> as long as it has an ever number of arguments and each odd argument is a symbol.
>
> I can't see anything obviously wrong with the code you posted (though I may well
> be overlooking something...) If it were me, this would probably be the point
> where I start edebug...
>
>
> --
> Joost Kremers
> Life has its moments
>



  parent reply	other threads:[~2021-05-04  7:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 21:30 setq-local: Wrong number of arguments Christopher Dimech
2021-05-04  6:47 ` Joost Kremers
2021-05-04  7:07   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-04  7:59   ` Christopher Dimech [this message]
2021-05-04  8:05     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-04  8:14       ` Emacs is stable software Jean Louis
2021-05-04  8:25         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-04  9:03         ` tomas
2021-05-04  9:15           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05  6:26       ` setq-local: Wrong number of arguments Christopher Dimech
2021-05-05  6:32         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05  8:56           ` Christopher Dimech
2021-05-05  9:05             ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 10:01               ` Christopher Dimech
2021-05-05 10:12                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 10:48                   ` Christopher Dimech
2021-05-05 11:00                   ` Christopher Dimech
2021-05-05 15:02                     ` Emanuel Berg via Users list for the GNU Emacs text editor

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-a60f7886-5d4c-4e9d-820a-6c479f62fa6a-1620115147585@3c-app-mailcom-bs02 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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).