unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: assq_no_quit... huh?
Date: Fri, 20 Dec 2024 09:41:56 +0200	[thread overview]
Message-ID: <86ikrekdh7.fsf@gnu.org> (raw)
In-Reply-To: <m2r0633q4s.fsf@gmail.com> (message from Gerd Möllmann on Fri, 20 Dec 2024 06:00:35 +0100)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Fri, 20 Dec 2024 06:00:35 +0100
> 
> Po Lu <luangruo@yahoo.com> writes:
> 
> > What's the meaning of this code?
> >
> > 	  if (is_tty_frame (f))
> > 	    {
> > 	      /* Ignore all invisble tty frames, children or root.  */
> > 	      if (!FRAME_VISIBLE_P (root_frame (f)))
> > 		continue;
> >
> > 	      /* Remember tty root frames which we've seen.  */
> > 	      if (!FRAME_PARENT_FRAME (f)
> > 		  && NILP (assq_no_quit (frame, tty_root_frames))) <===
> > 		tty_root_frames = Fcons (frame, tty_root_frames);
> > 	    }
> >
> > No alist is being constructed and consequently assq_no_quit always
> > returns nil.
> 
> Thanks, that's a bug. It would have better been memq_no_quit but that
> doesn't seem to exist anymore.

It did exist, in the w32*.c files.  So the change you made to re-add
memq_no_quit broke the MS-Windows build.

Please in the future, when you add a new function, grep _all_ of the
sources for the same symbol, to avoid inadvertent breakage of
platforms where you don't build Emacs routinely.

Thanks.



  parent reply	other threads:[~2024-12-20  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87zfkrp0da.fsf.ref@yahoo.com>
2024-12-20  2:13 ` assq_no_quit... huh? Po Lu
2024-12-20  5:00   ` Gerd Möllmann
2024-12-20  5:18     ` Gerd Möllmann
2024-12-20  7:41     ` Eli Zaretskii [this message]
2024-12-20  7:49       ` Gerd Möllmann

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=86ikrekdh7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=luangruo@yahoo.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).