all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Damien Cassou <damien.cassou@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 9674@debbugs.gnu.org
Subject: bug#9674: 24.0.90; Closing an emacsclient frame always kills daemon
Date: Thu, 6 Oct 2011 13:28:28 +0200	[thread overview]
Message-ID: <CA+y5gghf1aRYB_gyo_QeW5+3OHG7Vjyh9fdfWk6BrHduD82ivQ@mail.gmail.com> (raw)
In-Reply-To: <pesjn7e32v.fsf@fencepost.gnu.org>

On Wed, Oct 5, 2011 at 7:54 PM, Glenn Morris <rgm@gnu.org> wrote:
> This seems rather backward. I would have expected the issue that message
> refers to to be the actual problem that you are seeing. There's no way
> you can get that message in a non-GTK build. Maybe your system was
> lacking the necessary libraries for a Lucid toolkit build and defaulted
> to gtk? (I don't even know if that can happen.)

Ok, I understand. When I launch:

$ lib-src/emacsclient --alternate-editor="" -c ~/.bashrc

the daemon is created from /usr/bin/emacs and not from the ./src/emacs
that I have just compiled. I guess it's not possible to choose which
emacs to execute using this --alternate-editor parameter. Bug #9682
prevents me from testing with lucid.


-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry





  reply	other threads:[~2011-10-06 11:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 12:24 24.0.90; Closing an emacsclient frame always kills daemon Damien Cassou
2011-10-05 15:57 ` Richard Riley
2011-10-05 16:26 ` Glenn Morris
2011-10-05 17:54 ` bug#9674: " Glenn Morris
2011-10-06 11:28   ` Damien Cassou [this message]
2011-10-06 15:17     ` Chong Yidong
2011-10-06 16:22       ` Damien Cassou
2011-10-05 21:45 ` Chong Yidong
2011-10-08 18:35 ` Michael Welsh Duggan

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=CA+y5gghf1aRYB_gyo_QeW5+3OHG7Vjyh9fdfWk6BrHduD82ivQ@mail.gmail.com \
    --to=damien.cassou@gmail.com \
    --cc=9674@debbugs.gnu.org \
    --cc=rgm@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.