unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: 60850@debbugs.gnu.org
Subject: bug#60850:
Date: Mon, 16 Jan 2023 16:43:46 +0200	[thread overview]
Message-ID: <83k01m4k0t.fsf@gnu.org> (raw)
In-Reply-To: <CAO48Bk8rYkcwBhk=LyP7PoPMxNpVWnmc7n4SQsBMsY7hGsC2Yw@mail.gmail.com> (message from Pedro Andres Aranda Gutierrez on Mon, 16 Jan 2023 07:29:28 +0100)

> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> Date: Mon, 16 Jan 2023 07:29:28 +0100
> 
> I created a file called /tmp/test.el with the following contents:
> 
> --cut here--
> (require 'org)
> --cut here--
> 
> and then called emacs as
> 
> emacs -Q -l /tmp/test.el
> 
> I get the following message in the *Warnings* buffer:
> 
> ⛔ Warning (comp): org-loaddefs.el.gz:846:61: Warning: Unused lexical variable `org-element-use-cache'

I cannot reproduce this.  Crystal ball says that your org-loaddefs.el
is stale and needs to be regenerated.

> BTW: Isn't ⛔ a bit to "visually drastic" for a _warning_ ? Shouldn't it be
> reserved for things like errors?

Others explained why this uses that particular icon.  I don't see any
serious problem there, as any icon I can think of could be confusing
to someone.





  parent reply	other threads:[~2023-01-16 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16  6:29 bug#60850: Pedro Andres Aranda Gutierrez
2023-01-16  6:50 ` bug#60850: Jim Porter
2023-01-16  7:35   ` bug#60850: Pedro Andres Aranda Gutierrez
2023-01-17  4:57     ` bug#60850: Richard Stallman
2023-01-17  5:44       ` bug#60850: Jim Porter
2023-01-20  4:00         ` bug#60850: Richard Stallman
2023-01-16 14:43 ` Eli Zaretskii [this message]
2023-09-05 23:35   ` bug#60850: Stefan Kangas
2023-09-06  6:57     ` bug#60850: Pedro Andres Aranda Gutierrez
2023-09-06  7:31       ` bug#60850: Stefan Kangas

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=83k01m4k0t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60850@debbugs.gnu.org \
    --cc=paaguti@gmail.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).