all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ej32u--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 43586-done@debbugs.gnu.org
Subject: bug#43586: Flymake can't understand `cl-loop' and `if-let*'.
Date: Sat, 26 Sep 2020 00:24:32 +0000	[thread overview]
Message-ID: <06f1b220-8e06-fe1c-0495-219e59f5d693@protonmail.com> (raw)
In-Reply-To: <87wo0j9qve.fsf@gnus.org>

Thank you, I had missed adding those.

On 9/24/20 10:44 AM, Lars Ingebrigtsen wrote:
> ej32u@protonmail.com writes:
>
>> Flymake is giving many errors, for a command that I believe works. This happens
>> with a clean init file.
> [...]
>
>> Here are some of the errors Flymake reports:
>>
>>      19   0 warning  Unused lexical variable ‘formatted-bookmarks’
>>      22   3 warning  ‘(chosen-cand (selectrum-read "Bookmark: "
> [...]
>
>> You can see that it is treating key words as variables in `cl-loop', and cannot
>> see that `actual-data' is defined in `if-let*'. The command works fine when
>> evaluated.
> Do the warnings go away if you put
>
> (require 'cl-lib)
> (require 'subr-x)
>
> in your file?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>     bloggy blog: http://lars.ingebrigtsen.no







      reply	other threads:[~2020-09-26  0:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <839ce061-6550-666e-bb2e-40cface2549c@protonmail.com>
2020-09-24  2:10 ` bug#43586: Flymake can't understand `cl-loop' and `if-let*' ej32u--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 14:44   ` Lars Ingebrigtsen
2020-09-26  0:24     ` ej32u--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=06f1b220-8e06-fe1c-0495-219e59f5d693@protonmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=43586-done@debbugs.gnu.org \
    --cc=ej32u@protonmail.com \
    /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.