unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Klaus Zeitler <kzeitler@alcatel-lucent.com>
To: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: minibuffer-exit when emacsclient executes Lisp code
Date: Wed, 16 May 2007 10:28:30 +0200	[thread overview]
Message-ID: <q5g1whhxjdd.fsf@sfsw51.de.lucent.com> (raw)
In-Reply-To: <464A1C4B.8060504@gmail.com> (Lennart Borgman's message of "Tue\, 15 May 2007 22\:47\:07 +0200")

>>>>> "Lennart" == Lennart Borgman (gmail) <lennart.borgman@gmail.com> writes:
    Lennart> 
    Lennart> Yes, it is probably due to a change a while ago to avoid problems
    Lennart> if the minibuffer was active. How are you calling emacsclient? Is
    Lennart> it to open files or to eval some elisp code?

My script calls emacsclient with --eval to evaluate lisp code.
Here's a simple example:
1. in your emacs do M-x to enter the minibuffer
2. in a shell type e.g.: emacsclient --eval cvs-emacs
=> emacs quits the minibuffer

Klaus

-- 
 --------------------------------------------------
|  Klaus Zeitler      Alcatel-Lucent               |
|  Email:             kzeitler@alcatel-lucent.com  |
 --------------------------------------------------
---
The difference between a fool and a wise man is not
the things they know, it's the questions they ask.

  reply	other threads:[~2007-05-16  8:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 10:10 minibuffer-exit when emacsclient executes Lisp code Klaus Zeitler
2007-05-15 20:47 ` Lennart Borgman (gmail)
2007-05-16  8:28   ` Klaus Zeitler [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2007-05-16 14:01 karoly
2007-05-16 14:18 ` Juanma Barranquero
2007-05-16 14:35   ` Károly Lőrentey
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

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=q5g1whhxjdd.fsf@sfsw51.de.lucent.com \
    --to=kzeitler@alcatel-lucent.com \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@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).