unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Károly Lőrentey" <karoly@lorentey.hu>
To: emacs-devel@gnu.org
Subject: Re: minibuffer-exit when emacsclient executes Lisp code
Date: Wed, 16 May 2007 16:35:34 +0200	[thread overview]
Message-ID: <f2f4rp$u59$1@sea.gmane.org> (raw)
In-Reply-To: <f7ccd24b0705160718me35baf5i5c83d63eea002d09@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 668 bytes --]

Juanma Barranquero wrote:
> I don't agree. The burden of being mergeable without loss of
> features/bugfixes should be on the multi-tty branch, not on the trunk.
> Not that that means it's OK to make live difficult to the multi-tty
> developers, of course.

That's exactly my point.  I want to make my burden a little lighter.
emacsclient.c and server.el was relatively stable on the trunk for
years, then a few months ago a number of new features have suddenly
started to appear.  That gave me a few headaches, and if possible I
would like to prevent a similar situation now that the branch is easily
accessible for all Emacs developers.

-- 
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

  reply	other threads:[~2007-05-16 14:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 14:01 minibuffer-exit when emacsclient executes Lisp code karoly
2007-05-16 14:18 ` Juanma Barranquero
2007-05-16 14:35   ` Károly Lőrentey [this message]
2007-05-16 14:55     ` Juanma Barranquero
2007-05-17 13:28       ` Dan Nicolaescu
2007-05-16 14:41 ` David Kastrup
2007-05-16 14:58   ` Juanma Barranquero
2007-05-16 15:52   ` Károly Lo"rentey
2007-05-16 23:36   ` Kenichi Handa
  -- strict thread matches above, loose matches on Subject: below --
2007-05-15 10:10 Klaus Zeitler
2007-05-15 20:47 ` Lennart Borgman (gmail)
2007-05-16  8:28   ` Klaus Zeitler
2007-05-16 11:28     ` Lennart Borgman (gmail)
2007-05-16 11:43       ` David Kastrup
2007-05-16 11:49         ` Lennart Borgman (gmail)
2007-05-16 12:58         ` Károly Lo"rentey
2007-05-16 13:04           ` Juanma Barranquero
2007-05-16 13:51           ` David Kastrup
2007-05-16 14:15           ` Klaus Zeitler
2007-05-17 13:48           ` Stefan Monnier
2007-05-16 14:10       ` Klaus Zeitler
2007-05-16 14:47         ` Lennart Borgman (gmail)
2007-05-23  9:59       ` Klaus Zeitler
2007-05-23 10:12         ` Lennart Borgman (gmail)
2007-05-23 15:03           ` Stefan Monnier
2007-05-23 18:56           ` Richard Stallman
2007-05-23 19:42             ` Lennart Borgman (gmail)
2007-05-24 13:13             ` Stefan Monnier
2007-05-25  7:37               ` 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='f2f4rp$u59$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 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).