all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jared Finder <jared@finder.org>, emacs-devel@gnu.org
Subject: Re: Reference to free variable ‘xterm-mouse-mode-called’
Date: Mon, 6 Jan 2025 00:58:04 -0800	[thread overview]
Message-ID: <DC3AC281-B29A-44A3-8FC7-6E4EC412B100@gmail.com> (raw)
In-Reply-To: <86r05hahqb.fsf@gnu.org>



> On Jan 4, 2025, at 10:37 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> Date: Sat, 04 Jan 2025 14:03:57 -0800
>> From: Jared Finder <jared@finder.org>
>> Cc: Yuan Fu <casouri@gmail.com>, emacs-devel@gnu.org
>> 
>> On 2025-01-04 12:36, Eli Zaretskii wrote:
>>>> From: Yuan Fu <casouri@gmail.com>
>>>> Date: Sat, 4 Jan 2025 11:56:06 -0800
>>>> 
>>>> I’m seeing
>>>> 
>>>> In xterm--init:
>>>> term/xterm.el:966:19: Warning: reference to free variable 
>>>> ‘xterm-mouse-mode-called’
>>>> 
>>>> when building master. Is this something to be concerned about?
>>> 
>>> On what OS?
>>> 
>>> I don't get that.  If you "touch xterm.el" and rebuild, do you still
>>> see it?
>>> 
>>> Jared, maybe we need a defvar in xtern.el?
>> 
>> I don't get this warning either and I just did a clean build. I marked 
>> xterm-mouse-mode-called with ;;;autoload therefore I expect it to always 
>> be available (unless I'm misunderstanding what ;;;autoload does to 
>> defvar expressions).
> 
> If it's autoloaded, I think this warning is a one-time thing, when the
> file is compiled before the autoloads are updated.

I see. Indeed, I don’t see the warning anymore. Sorry for the noise :-)

Yuan


      reply	other threads:[~2025-01-06  8:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-04 19:56 Reference to free variable ‘xterm-mouse-mode-called’ Yuan Fu
2025-01-04 20:36 ` Eli Zaretskii
2025-01-04 22:03   ` Jared Finder
2025-01-05  6:37     ` Eli Zaretskii
2025-01-06  8:58       ` Yuan Fu [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=DC3AC281-B29A-44A3-8FC7-6E4EC412B100@gmail.com \
    --to=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jared@finder.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.