From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Change in emacsclient behavior
Date: Sat, 01 Sep 2007 10:26:44 +0200 [thread overview]
Message-ID: <85y7fqaj0b.fsf@lola.goethe.zz> (raw)
In-Reply-To: <uzm06vnmi.fsf@gnu.org> (Eli Zaretskii's message of "Sat\, 01 Sep 2007 10\:41\:25 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Richard Stallman <rms@gnu.org>
>> CC: emacs-devel@gnu.org
>> Date: Fri, 31 Aug 2007 14:21:35 -0400
>>
>> > For people that normally don't make new frames, this will be a hassle.
>>
>> Yes, I agree. Frames popping up without my say-so are a nuisance.
>>
>> Would you like to fix this?
>
> I don't think this is a good idea, since my free time will be
> severely limited in the near future, and on top of that, I'm not
> familiar at all with the multi-tty code and the changes it
> introduced into Emacs.
It is not like we have an abundance of those who are familiar with it
and have time working on it. Is there even one? At least, the set
might be so small that it does not include people beyond the creators,
so they might not be overly inclined to back out changes they
considered a good idea.
As far as I can tell, multi-tty is one package including several
things, some of which may more reflect the author's personal
preferences rather than actual technical requirements for the
multi-tty functionality.
Boiling down the multi-tty work to a level where it basically includes
those things necessary and desirable will be work. It might have been
easier to manage while there was still a separate branch, but there
was ample opportunity to do so before the merge, and it did not really
make people work on that (myself very much included). Like before,
things don't fix and document and simplify themselves.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-09-01 8:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 20:50 Change in emacsclient behavior Richard Stallman
2007-08-30 21:04 ` Drew Adams
2007-08-31 18:21 ` Richard Stallman
2007-08-31 18:26 ` Drew Adams
2007-08-30 21:23 ` Eli Zaretskii
2007-08-30 21:41 ` Henrik Enberg
2007-08-31 18:21 ` Richard Stallman
2007-09-01 7:41 ` Eli Zaretskii
2007-09-01 8:26 ` David Kastrup [this message]
2007-08-31 6:39 ` Stefan Monnier
2007-08-31 8:06 ` Tassilo Horn
2007-08-31 14:31 ` Stefan Monnier
2007-09-02 18:52 ` Juri Linkov
2007-09-02 19:20 ` David Kastrup
2007-09-02 20:14 ` Juri Linkov
2007-09-02 20:34 ` David Kastrup
2007-09-02 20:44 ` Tom Tromey
2007-09-03 18:26 ` Richard Stallman
2007-09-02 23:20 ` Manoj Srivastava
2007-09-02 19:34 ` Tassilo Horn
2007-09-02 20:14 ` Juri Linkov
2007-09-03 19:15 ` Tassilo Horn
2007-09-03 15:31 ` Jeremy Maitin-Shepard
2007-09-03 18:26 ` Richard Stallman
2007-09-03 20:37 ` Stefan Monnier
2007-09-03 23:46 ` Juri Linkov
2007-09-04 23:08 ` Davis Herring
2007-09-05 20:02 ` Richard Stallman
2007-09-05 20:34 ` David Kastrup
2007-09-07 6:30 ` Richard Stallman
2007-09-07 7:06 ` David Kastrup
2007-09-08 7:01 ` Richard Stallman
2007-08-31 8:09 ` David Kastrup
2007-08-31 14:29 ` Stefan Monnier
2007-09-03 5:47 ` Edward O'Connor
2007-09-04 0:56 ` Richard Stallman
2007-09-04 5:56 ` David Kastrup
2007-09-04 22:57 ` Richard Stallman
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=85y7fqaj0b.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).