unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs and the Status Notification Specification
Date: Fri, 24 Jun 2011 11:00:44 -0600	[thread overview]
Message-ID: <m3mxh7rwoz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87wrgcz9ks.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 23 Jun 2011 13:28:19 -0500")

Tom> Attached are 2 files to implement the spec for Emacs:
Tom> * status.el, the basic implementation

... which is kind of broken, so I won't be installing it quite yet.

Ted> This is somewhat related to the emacs-panel work I'm doing.  I propose
Ted> we either make a emacs-desktop ELPA package (on the GNU ELPA or
Ted> somewhere else) or we make a lisp/desktop/ directory in Emacs.  My
Ted> preference is for the former, so it can be used in XEmacs and in older
Ted> Emacs versions, and so its development is decoupled from the Emacs
Ted> releases.

I'm not sure this will work.  This code uses some later dbus methods; I
had to upgrade to 24 to get it working.

Ted> Michael Albinus has provided a notifications.el server, which I think
Ted> also makes sense in the emacs-desktop package.

That is already in the core.

I am fine with a GNU ELPA package.
I will try to do that once I've debugged the other problems.
Or, if you still want a unified package -- first, why? -- and second,
perhaps you could set it up.

Tom



  parent reply	other threads:[~2011-06-24 17:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 17:31 Emacs and the Status Notification Specification Tom Tromey
2011-06-23 18:28 ` Ted Zlatanov
2011-06-24  8:54   ` Philipp Haselwarter
2011-06-24 11:59     ` Ted Zlatanov
2011-06-24 17:00   ` Tom Tromey [this message]
2011-06-26  9:31     ` Michael Albinus
2011-06-26 16:18       ` Richard Stallman
2011-06-27  7:22         ` Stephen J. Turnbull
2011-06-27 16:06     ` Ted Zlatanov
2011-06-27 23:02       ` Richard Stallman
2011-06-28 11:52         ` Ted Zlatanov
2011-06-29 23:14           ` Richard Stallman
2011-06-30 12:38             ` Ted Zlatanov
2011-06-30 13:38               ` Juanma Barranquero
2011-06-30 14:58               ` John Yates
2011-06-30 15:27                 ` Juanma Barranquero
2011-06-30 17:41                   ` John Yates
2011-07-01  0:18               ` Richard Stallman
2011-07-01  1:46                 ` Ted Zlatanov
2011-07-01  1:57                   ` David De La Harpe Golden
2011-07-01  3:07                   ` Stefan Monnier
2011-07-01 11:40                     ` Richard Stallman
2011-07-01 13:11                       ` Ted Zlatanov
2011-07-01 14:16                         ` Stefan Monnier
2011-07-01 14:17                       ` Stefan Monnier
2011-07-02  8:11                         ` Richard Stallman
2011-06-30 16:07             ` Chong Yidong
2011-06-26  9:25 ` Michael Albinus

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=m3mxh7rwoz.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --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).