From: "Károly Lőrentey" <karoly@lorentey.hu>
To: emacs-devel@gnu.org
Subject: Re: multi-tty branch created
Date: Wed, 16 May 2007 17:04:25 +0200 [thread overview]
Message-ID: <f2f6hu$598$1@sea.gmane.org> (raw)
In-Reply-To: <f7ccd24b0705160646t40086df3x7599a203aa5ef506@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1924 bytes --]
Juanma Barranquero wrote:
> In the merge, the execvp wrapper for Windows has been moved to below
> the point where execvp is used; i.e, execvp is used in fail, but
>
> #undef execvp
> #define execvp w32_execvp
>
> happens quite a bit later. That's an error, I think.
That's right. Could you please fix it?
>> I hope most people would agree that the new emacsclient features are a
>> definite improvement.
>
> As long as the features currently in the trunk are maintained, yes.
They should be. If anything is lost, then that's a bug.
At the very least, emacsclient works good enough not to impede unrelated
Emacs development.
>> Keep in mind that improving emacsclient behaviour is one of the primary
>> results of the multi-tty branch.
>
> Then it should continue to be done in the multi-tty branch until
> merging it to the trunk does not represent a regression.
I don't believe it represents a regression in its current form. As we
know, Windows support is broken, but thankfully people are working on
that now. I argue that it is not a good idea to keep the trunk's
emacsclient a moving target. The more changes you make to it now, the
more probable I create a new regression while merging (i.e.,
reimplementing) your changes in multi-tty.
If there is a good chance that Emacs 23 will be released without
multi-tty, then of course things are different. I think people should
look at the code and report if it is basically sound or not. If not,
then it's better to have that decided early than to waste more time
developing it.
You can also decide to keep a subset of multi-tty changes (C-level
changes, Lisp interface, emacsclient improvements, environment
implementation, Lisp package adaptations, etc.) and discard/reimplement
the rest. For example, David has already expressed his dissatisfaction
with the environment implementation.
--
Karoly
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2007-05-16 15:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 13:31 multi-tty branch created Miles Bader
2007-05-13 14:50 ` David Kastrup
2007-05-13 16:12 ` Miles Bader
2007-05-13 16:14 ` David Kastrup
2007-05-13 16:13 ` David Kastrup
2007-05-13 19:28 ` Robert J. Chassell
2007-05-16 13:24 ` Károly Lo"rentey
2007-05-16 13:46 ` Juanma Barranquero
2007-05-16 15:04 ` Károly Lőrentey [this message]
2007-05-16 15:34 ` David Kastrup
2007-05-16 16:11 ` Károly Lőrentey
2007-05-16 21:17 ` Jason Rumney
2007-05-16 16:20 ` Dan Nicolaescu
2007-05-16 17:39 ` David Kastrup
2007-05-16 20:48 ` Károly Lőrentey
2007-05-17 14:02 ` Stefan Monnier
2007-05-17 16:04 ` Károly Lo"rentey
2007-05-17 23:24 ` Stefan Monnier
2007-05-18 18:02 ` Károly Lo"rentey
2007-05-19 14:07 ` Stefan Monnier
2007-05-13 20:07 ` Jason Rumney
2007-05-14 10:21 ` Karoly Lorentey
2007-05-14 11:55 ` Jason Rumney
2007-05-15 13:03 ` Karoly Lorentey
2007-05-15 22:05 ` Ken Raeburn
2007-05-14 6:00 ` Manoj Srivastava
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='f2f6hu$598$1@sea.gmane.org' \
--to=karoly@lorentey.hu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.