From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Visiting open processes when killing emacs
Date: Tue, 21 Dec 2010 21:13:07 -0700 [thread overview]
Message-ID: <iertsk$12o$1@dough.gmane.org> (raw)
In-Reply-To: <jwv7hfb11d2.fsf-monnier+gnu.emacs.help@gnu.org>
On 12/15/10 8:51 AM, Stefan Monnier wrote:
>> Unfortunately, my Emacs Lisp-fu is weak after lack of practice and it
>> does not help that list-processes is implemented in C.
>
> FWIW, we have two Lisp versions currently competing for inclusion in
> Emacs-24.
Cool.
Could this be done via font-lock, and in such a way that it would work
for both the current C version and the proposed Lisp versions?
--
Kevin Rodgers
Denver, Colorado, USA
prev parent reply other threads:[~2010-12-22 4:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 18:30 Visiting open processes when killing emacs Michael Hoffman
2010-12-15 5:09 ` Kevin Rodgers
2010-12-15 9:45 ` Leo
2010-12-22 4:24 ` Kevin Rodgers
[not found] ` <mailman.3.1292389761.26985.help-gnu-emacs@gnu.org>
2010-12-15 15:51 ` Stefan Monnier
2010-12-22 4:13 ` Kevin Rodgers [this message]
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='iertsk$12o$1@dough.gmane.org' \
--to=kevin.d.rodgers@gmail.com \
--cc=help-gnu-emacs@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.
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).