From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Wrong number of arguments: setq, 1
Date: Fri, 11 Dec 2015 16:19:21 -0500 [thread overview]
Message-ID: <87a8pgk7ja.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: CAFyQvY0AuHUXNLTzfbe9jwy1O-eP1nOOVHgQEX49BwZFZOMZZw@mail.gmail.com
Kaushal Modi <kaushal.modi@gmail.com> writes:
> ...
> Without these fixes, I get an error like: Wrong number of arguments: setq, 1
>
I don't. Version info:
Org-mode version 8.3.2 (release_8.3.2-380-g64aee4 @
/home/nick/elisp/org-mode/lisp/)
GNU Emacs 25.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.15) of
2015-08-16 on alphaville.usersys.redhat.com
> I am not familiar with letrec but for let statements, if I want to set
> a let-bound variable X's value to nil, I would do,
>
> (let (X) ..)
>
> or
>
> (let ((X nil)) ..)
>
> But NOT (let ((X)) ..) (Note the parentheses count).
>
>
> Do the same rules not apply to letrec?
They do not: letrec takes a list, each element of which is
a list (SYMBOL VALUEFORM) - but afaik, an empty VALUEFORM
sets the SYMBOL to nil.
let takes a VARLIST, each element of which is a symbol *or* a
list (SYMBOL VALUEFORM).
See their docstrings.
>
> Here is my org-version:
>
> Org-mode version 8.3.2 (release_8.3.2-380-g64aee4 @
> /home/kmodi/usr_local/apps/6/emacs/emacs-25/share/emacs/site-lisp/org/)
>
> Here is my emacs build info (emacs-25 branch):
>
> Emacs version: GNU Emacs 25.0.50.1 (x86_64-unknown-linux-gnu, GTK+
> Version 2.24.23)
> of 2015-12-10, built using commit d75849e937af0ecbcdc7bf621aa9bcd43aa75df4.
>
My org is the same as yours, but my emacs is a few months old: maybe
some recent change screwed up something.
--
Nick
next prev parent reply other threads:[~2015-12-11 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 19:48 Wrong number of arguments: setq, 1 Kaushal Modi
2015-12-11 20:04 ` Kaushal Modi
2015-12-11 21:19 ` Nick Dokos [this message]
2015-12-11 21:40 ` Kyle Meyer
2015-12-11 22:25 ` Nick Dokos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8pgk7ja.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.