From: Adrian Robert <adrian.b.robert@gmail.com>
To: Dan Ports <drkp@mit.edu>
Cc: 4070@emacsbugs.donarmstrong.com
Subject: bug#4070: 23.1; ns: cut buffers don't work with --daemon
Date: Sun, 20 Sep 2009 08:17:08 -0400 [thread overview]
Message-ID: <5B63D4A2-9350-4986-8531-C710089A9EB8@gmail.com> (raw)
In-Reply-To: <20090920045704.GC19788@csail.mit.edu>
On Sep 20, 2009, at 12:57 AM, Dan Ports wrote:
> On Sat, Sep 19, 2009 at 07:36:32AM -0400, Adrian Robert wrote:
>> Thanks for the further info. What is "GNU screen"?
>
> http://www.gnu.org/software/screen/
>
>> (It seems that x-open-connection in nsfns.m is not being called,
>> which in turn means ns-initialize-window-system in lisp/term/ns-
>> win.el is not called, but I'm not sure how that could be. If you hit
>> M-x ns-service- <tab for completion> do you get a list of services?)
>
> Nope, no completions for ns-service-*.
>
> Still at a loss for what's going on. I'm guessing that something about
> the environment is different when run in screen -- maybe an
> environment
> variable or the pty or something. I'll play around with it some
> tomorrow and see what I can figure out.
I compiled and ran screen in the build directory like this "./
screen", then tried to run /Applications/.../Emacs -Q and did not see
the phenomena you describe. So hopefully you'll be able to find
something. One thing you should check is whether ns_term_init() is
being called..
next prev parent reply other threads:[~2009-09-20 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 22:31 bug#4070: 23.1; ns: cut buffers don't work with --daemon Adrian Robert
2009-09-19 7:17 ` Dan Ports
2009-09-19 11:36 ` Adrian Robert
2009-09-20 4:57 ` Dan Ports
2009-09-20 12:17 ` Adrian Robert [this message]
2009-11-28 1:17 ` Dan Ports
2010-01-20 4:54 ` Dan Ports
2010-01-20 15:24 ` Adrian Robert
2010-01-20 17:47 ` Dan Ports
2013-01-04 7:54 ` Glenn Morris
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 22:53 Dan Ports
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=5B63D4A2-9350-4986-8531-C710089A9EB8@gmail.com \
--to=adrian.b.robert@gmail.com \
--cc=4070@emacsbugs.donarmstrong.com \
--cc=drkp@mit.edu \
/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.