From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Hourglass only for X-windows?
Date: Tue, 01 Mar 2005 01:05:30 +0200 [thread overview]
Message-ID: <01c51dea$Blat.v2.4$254bbb00@zahav.net.il> (raw)
In-Reply-To: <007801c51dae$4674c560$0200a8c0@sedrcw11488> (lennart.borgman.073@student.lu.se)
> From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
> Cc: <emacs-devel@gnu.org>
> Date: Mon, 28 Feb 2005 16:57:26 +0100
>
> What I was trying to say was this (that it probably are conditioned for X)
> and that it is a problem because with
> #ifdef HAVE_X_WINDOWS
> around hourglass activation/deactivation you can only get things working on
> X.
Which is fine, as long as other platforms don't implement the required
infrastructure.
> For the w32 port there are also
> #if 0
> around the body part of the functions that do the actual job
> (start_hourglass, hide_hourglass), since it is (as far as I understand) not
> implemented on w32 yet.
Exactly.
> I suggest removing the "#ifdef HAVE_X_WINDOWS" completely or (which I
> believe most would like better - but not I) replacing them with something
> like
>
> #ifdef HAS_HOURGLASS
We cannot do the former without adding (possibly empty) functions
called by those snippets to all ports. And we cannot do the latter
without adding some configury stuff that would determine the value of
HAS_HOURGLASS at configure time.
Personally, I think we are fine as we are now. Of course, if you
implement start_hourglass et al for Windows, the HAVE_X_WINDOWS
condition needs to be augmented by something that will enable it for
Windows.
next prev parent reply other threads:[~2005-02-28 23:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 17:57 Hourglass only for X-windows? Lennart Borgman
2005-02-27 20:29 ` Eli Zaretskii
2005-02-28 0:20 ` Lennart Borgman
2005-02-28 4:38 ` Eli Zaretskii
2005-02-28 15:57 ` Lennart Borgman
2005-02-28 23:05 ` Eli Zaretskii [this message]
2005-03-01 0:17 ` Lennart Borgman
2005-03-10 23:33 ` Lennart Borgman
2005-03-11 13:28 ` Eli Zaretskii
2005-03-11 13:44 ` Jason Rumney
2005-03-11 15:51 ` Eli Zaretskii
2005-03-11 16:03 ` Lennart Borgman
2005-03-11 16:15 ` Eli Zaretskii
2005-03-11 16:43 ` Lennart Borgman
2005-03-11 17:25 ` Jan D.
2005-03-11 18:42 ` Lennart Borgman
2005-03-11 20:51 ` Eli Zaretskii
2005-03-12 1:03 ` Lennart Borgman
2005-03-12 2:11 ` Jason Rumney
2005-03-12 9:37 ` Lennart Borgman
2005-03-12 11:43 ` Jan D.
2005-03-12 13:41 ` Stefan Monnier
2005-03-12 15:41 ` Jason Rumney
2005-03-13 3:50 ` David Hunter
2005-03-14 11:28 ` YAMAMOTO Mitsuharu
2005-03-13 15:29 ` Richard Stallman
2005-03-12 10:01 ` Eli Zaretskii
2005-03-12 21:40 ` Lennart Borgman
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='01c51dea$Blat.v2.4$254bbb00@zahav.net.il' \
--to=eliz@gnu.org \
--cc=emacs-devel@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 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).