From: Dan Nicolaescu <dann@ics.uci.edu>
To: Tom Tromey <tromey@redhat.com>
Cc: emacs-devel@gnu.org
Subject: Re: RFC: status icon support
Date: Fri, 11 Jan 2008 17:57:06 -0800 [thread overview]
Message-ID: <200801120157.m0C1v6WL020654@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <m38x2wkkml.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri, 11 Jan 2008 16:28:18 -0700")
Tom Tromey <tromey@redhat.com> writes:
> +/* Callback which is called when the user clicks on a status icon. */
> +static void
> +activate_icon (widget, data)
> + GtkWidget *widget;
> + gpointer data;
> +{
Please no K&R in new code.
I am not sure if we actually have a policy about this. If we don't we
should make it now required to have K&R in new code. It's already not
possible to compile emacs with a K&R compiler, so please let's not add
to this.
The last thing we want is emacs to regarded as being a backwards project
because it insists on using a language that was standardized in a
different way 19 years ago.
next prev parent reply other threads:[~2008-01-12 1:57 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 23:28 RFC: status icon support Tom Tromey
2008-01-12 1:57 ` Dan Nicolaescu [this message]
2008-01-12 1:28 ` Tom Tromey
2008-01-12 1:38 ` Tom Tromey
2008-01-12 8:45 ` Ulrich Mueller
2008-01-12 17:45 ` Tom Tromey
2008-01-14 2:01 ` Richard Stallman
2008-01-14 1:35 ` Tom Tromey
2008-01-14 17:26 ` Richard Stallman
2008-01-19 5:18 ` Tom Tromey
2008-01-20 6:14 ` Richard Stallman
2008-01-23 4:00 ` Michael Olson
2008-01-14 1:41 ` Tom Tromey
2008-01-14 1:03 ` Michael Olson
2008-01-14 1:01 ` Tom Tromey
2008-01-14 7:03 ` Jan Djärv
2008-01-15 6:01 ` Michael Olson
2008-01-16 1:10 ` Tom Tromey
2008-01-16 4:10 ` Michael Olson
2008-01-12 11:11 ` Richard Stallman
2008-01-12 11:25 ` David Kastrup
2008-01-12 11:27 ` Andreas Schwab
2008-01-12 11:46 ` David Kastrup
2008-01-12 14:10 ` Andreas Schwab
2008-01-12 14:19 ` David Kastrup
2008-01-12 17:33 ` Andreas Schwab
2008-01-14 2:00 ` Richard Stallman
2008-01-14 2:25 ` Stefan Monnier
2008-01-14 7:05 ` Jan Djärv
2008-01-12 13:52 ` Dan Nicolaescu
2008-01-12 14:13 ` Andreas Schwab
2008-01-12 14:26 ` Dan Nicolaescu
2008-01-12 17:36 ` Andreas Schwab
2008-01-12 18:59 ` Dan Nicolaescu
2008-01-12 14:33 ` David Kastrup
2008-01-12 17:45 ` Andreas Schwab
2008-01-12 18:07 ` David Kastrup
2008-01-12 18:16 ` Andreas Schwab
2008-01-14 2:01 ` Richard Stallman
2008-01-14 2:47 ` Dan Nicolaescu
2008-01-14 17:26 ` Richard Stallman
2008-01-14 9:14 ` David Kastrup
2008-01-14 17:26 ` Richard Stallman
2008-01-14 3:47 ` YAMAMOTO Mitsuharu
2008-01-14 3:49 ` Tom Tromey
2008-01-14 13:35 ` Stefan Monnier
2008-01-14 21:40 ` YAMAMOTO Mitsuharu
2008-01-16 1:17 ` Tom Tromey
2008-01-16 11:55 ` YAMAMOTO Mitsuharu
2008-01-14 17:26 ` Richard Stallman
2008-01-14 17:10 ` Tom Tromey
2008-01-16 2:42 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2007-12-30 19:56 Tom Tromey
2007-12-31 17:18 ` Dan Nicolaescu
2007-12-31 18:29 ` Tom Tromey
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=200801120157.m0C1v6WL020654@oogie-boogie.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=tromey@redhat.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).