From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: emacsclient problem
Date: Mon, 21 Feb 2011 20:26:00 -0000 [thread overview]
Message-ID: <4D62CA50.5060908@cornell.edu> (raw)
In-Reply-To: <4D62A796.8070503@developernotes.com>
On 2/21/2011 12:57 PM, Nick Parker wrote:
> Hello,
>
> I am attempting to use the cygwin version of emacs and emacsclient,
> however I am running into an issue. The scenario that I am attempting
> is as follows:
>
> 1. Launching emacs from mintty (both of which were installed from the
> cygwin installer).
> 2. A simple init.el inside the .emacs.d directory that looks like this
> (http://pastie.org/1590067).
> 3. Background emacs with C-z
> 4. Launch emacsclient somefile.txt to edit the file.
>
> When I perform step 4, the command prompt doesn't appear to invoke
> emacsclient, the display does not change, and I do not see the file I am
> attempting to view. I have to issue a C-c to break the prompt back to
> normal user input.
>
> Version Information:
> mintty: 0.9.5
> emacs: 23.2.1
> emacsclient: 23.2
>
> Does anyone have any suggestions on what might be the cause of this
> behavior? Should this in fact work? Any suggestions would be
> appreciated. Thanks.
I don't see anything in the emacsclient documentation that suggest that
the emacs server should continue to run after being suspended with C-z.
Here are two alternatives that do seem to work (but see the
documentation for much more information):
1. Start emacs (and the emacs server) in one mintty window and run
emacsclient in another.
2. Start emacs with the --daemon option.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-02-21 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 17:57 Nick Parker
2011-02-21 20:26 ` Ken Brown [this message]
2011-02-21 20:47 ` Nick Parker
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=4D62CA50.5060908@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.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.
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).