unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: taylanbayirli@gmail.com (Taylan Ulrich B.)
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: Guile Mailing List <guile-user@gnu.org>,
	BT Templeton <bt@hcoop.net>,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Guile-Emacs update
Date: Mon, 22 Jul 2013 09:52:36 +0200	[thread overview]
Message-ID: <87y58zav5n.fsf@taylan.uni.cx> (raw)
In-Reply-To: <CA+U71=OsAAz4SysS-Epy-wsOW2uf=gAUoJ3jkfJhzqGpJD2EEw@mail.gmail.com> (Noah Lavine's message of "Sat, 20 Jul 2013 21:32:36 -0400")

Great news! :)

Noah Lavine <noah.b.lavine@gmail.com> writes:

> I looked at the emacswiki page you linked. It links to a page called
> GuileEmacsTodo, but that doesn't seem to be your current to-do list
> (it was edited too long ago).

The GSoC project has a better to-do list if I'm not mistaken.

By the way I've had it in mind for some time that we might want to
hijack the GuileEmacs page on EmacsWiki for the current
(i.e. Templeton's) project, updating and merging it with GuileEmacsTodo,
and moving the old contents of the GuileEmacs page to
"GuileEmacsHistory".  I'm saying this because it feels like the current
project has achieved a very mature state, much farther than any old
attempts (correct me), and might just be merged with upstream in the
next few years or so.  Tell me if I'm being silly.

> Could you say what differences a user would notice between Guile Emacs
> and regular Emacs (if any)? Are there any things that don't work, or
> any performance regressions?

Before this new series of changes, the two user-visible changes listed
at the bottom were up to date (unless the July-upstream rebase made a
difference), and the now-mentioned changes don't immediately sound
relevant to them, so I wouldn't be surprised if they're still up to
date.  I'll definitely test the latest version later today and update
the list as necessary though.  (Feel free to do so before me, of
course.)

Taylan



  reply	other threads:[~2013-07-22  7:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-20 23:54 Guile-Emacs update BT Templeton
2013-07-21  1:32 ` Noah Lavine
2013-07-22  7:52   ` Taylan Ulrich B. [this message]
2013-07-24 21:50   ` BT Templeton
2013-07-31 18:54 ` joakim
2013-07-31 20:28   ` Paul Smith
2013-07-31 20:46     ` joakim
2013-07-31 22:17       ` Óscar Fuentes
2013-07-31 22:17       ` Taylan Ulrich B.
2013-09-07  9:29         ` Andy Wingo
2013-09-07 10:02           ` Eli Zaretskii
2013-09-07 11:14             ` Andy Wingo

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=87y58zav5n.fsf@taylan.uni.cx \
    --to=taylanbayirli@gmail.com \
    --cc=bt@hcoop.net \
    --cc=emacs-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=noah.b.lavine@gmail.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).