From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Cc: rms@gnu.org, Jason Rumney <jasonr@gnu.org>,
David Hunter <hunterd42@comcast.net>,
KOBAYASHI Yasuhiro <kobayays@otsukakj.co.jp>,
Eli Zaretskii <eliz@gnu.org>, "Jan D." <jan.h.d@swipnet.se>
Subject: Re: Hourglass only for X-windows?
Date: Fri, 11 Mar 2005 00:33:16 +0100 [thread overview]
Message-ID: <00b301c525c9$9cf3ba40$0200a8c0@sedrcw11488> (raw)
In-Reply-To: 001901c51df4$1a9400a0$0200a8c0@sedrcw11488
----- Original Message -----
From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
> ----- Original Message -----
> From: "Eli Zaretskii" <eliz@gnu.org>
> > > 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.
>
> Yes, I thought I would implement start_hourglass etc. Maybe someone wants
> to implement it in macfns.c too where the body part also has an empty body
> part.
>
> Whichever way of changing the current "#ifdef HAVE_X_WINDOWS" at those
> places are enough, but removing the ifdef:s and adding a file with empty
> body parts for those ports that does not implement hourglass support makes
> the code easier to read IMO.
I have implemented code for hourglass on w32 now (or rather I should say
Dave Hunter has done it, I just did a small amount of typing). Could we
please get a decision on the issue above so that it is possible to get this
working with the CVS code? (The hourglass code in keyboard.c is currently
only called if HAVE_X_WINDOWS is defined.)
next prev parent reply other threads:[~2005-03-10 23:33 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
2005-03-01 0:17 ` Lennart Borgman
2005-03-10 23:33 ` Lennart Borgman [this message]
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='00b301c525c9$9cf3ba40$0200a8c0@sedrcw11488' \
--to=lennart.borgman.073@student.lu.se \
--cc=eliz@gnu.org \
--cc=hunterd42@comcast.net \
--cc=jan.h.d@swipnet.se \
--cc=jasonr@gnu.org \
--cc=kobayays@otsukakj.co.jp \
--cc=rms@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).