public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Mark Jackson <mjackson@alumni.caltech.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: nedit -server not working
Date: Fri, 15 Feb 2013 03:08:00 -0000	[thread overview]
Message-ID: <511DA699.8010302@alumni.caltech.edu> (raw)
In-Reply-To: <20130214201411.152581c8@YAAKOV04>

On 2/14/2013 9:14 PM, Yaakov (Cygwin/X) wrote:
> On Thu, 14 Feb 2013 13:16:47 -0500, Mark Jackson wrote:
>> Since updating my (rather stale) Cygwin installation in late December I
>> find that the server mode of nedit isn't working.  Both "nc" (which I
>> had been accustomed to using) and "nedit -server" open nedit as if the
>> server flag were not there.
>
> How so?

Normal behavior - at least as I have experienced it on SunOS and 
Solaris, and Cygwin until the December upgrade - is that the shell 
prompt returns, and subsequent invocations of "nc filename" open 
additional tabs in the nedit window created by the initial invocation.

At present control is not returned to the shell.  Launching nedit as a 
separate process by other means does not result in it acting as a server 
- that is, a subsequent "nc filename" launches a fresh nedit window.

-- 
Mark Jackson - http://www.alumni.caltech.edu/~mjackson
      Sometimes sarcasm helps us think more clearly.
                             - Dogbert (Scott Adams)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2013-02-15  3:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 18:17 Mark Jackson
2013-02-15  2:14 ` Yaakov
2013-02-15  3:08   ` Mark Jackson [this message]
2013-02-25 20:38     ` Mark Jackson

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=511DA699.8010302@alumni.caltech.edu \
    --to=mjackson@alumni.caltech.edu \
    --cc=cygwin-xfree@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).