From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6245 invoked by alias); 21 Sep 2015 04:06:37 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 36572 Received: (qmail 596 invoked from network); 21 Sep 2015 04:06:36 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:cc:mime-version:content-type; bh=im2D7aUzYVWlGEGulQ4c7d+ETI1zJI7VMLV2/Z5vC1M=; b=dZEMJjxLif6viVbhmEQrxUZ+puAuDI/VXSRFVKrrBEEG+AR3hZ0vKIMyDirKNX3+6n PvxgOeAtmlq05q5ar0lUGUb0CAn0n/TFZZ/mzLnYY6tyRD++fqGjpTUTTeLjbM3oHHss 3NgXH+u/8NR0oCxRuUsm0WwaAB0rDiDqgKUYZPfVef7rE53mFDu2laMswzqOxALQsbpZ Mq67/HMvSkEOYpFz8jOHk/eS7XqaNThXxiAi/2BNTuCM8N9N0aGAtMfs1KG+3gP/xZHp Whu+7LDvheCVu+4n+uAJho1kE2lnonCbWRjdLT+p0Wyox3jS6FO0LfLOtyH2wXA/8ssf uMjQ== X-Gm-Message-State: ALoCoQnQjVvUMCWgSmjTUiQ0+A8JHL3SeIlm71L3gxN64K1TXbN/aKjb8gCjkHhggz7KWzVlLBvs X-Received: by 10.60.63.103 with SMTP id f7mr1050698oes.5.1442808393329; Sun, 20 Sep 2015 21:06:33 -0700 (PDT) From: Bart Schaefer Message-Id: <150920210629.ZM31859@torch.brasslantern.com> Date: Sun, 20 Sep 2015 21:06:29 -0700 In-Reply-To: <55FF3CE5.9070604@petervasil.net> Comments: In reply to Peter Vasil "Re: edit-command-line problem with emacsclient" (Sep 21, 1:10am) References: <55FE9C92.7030203@petervasil.net> <150920083202.ZM31587@torch.brasslantern.com> <55FF3CE5.9070604@petervasil.net> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: edit-command-line problem with emacsclient Cc: Peter Vasil MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Sep 21, 1:10am, Peter Vasil wrote: } } This works but it's not optimal since the emacs window doesn't get } raised and doesn't come to front. And also the terminal is not waiting } for Emacs to return. I guess this means there's no set of common options we can use. Sigh. (How nice that "emacsclient -nw" and "emacs -nw" mean almost exactly the opposite of one another.) So you'll have to help here a little -- would you expect --create-frame or --tty ? Given the context I'd probably chose --tty, but either one seems to force emacsclient to wait for the frame to close.