public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: can't run cygwin emacs or XWin Server
Date: Sun, 25 Dec 2016 15:14:00 -0000	[thread overview]
Message-ID: <062b5d1e-bf39-0018-2566-d960f05598df@gmail.com> (raw)
In-Reply-To: <914c7a91-da0d-5102-f884-3fe0deba5bf3@onetel.com>

On 25/12/2016 13:55, mike wrote:
> I run 32 bit cygwin on a 64 bit machine running Windows 7.
>
> I used to get an XWin Server terminal running bash at startup (logging
> into Windows) from which I could run the emacs packaged in cygwin.
> After a round of updates I don't get the terminal window at startup and
> if I try to manually launch it it fails to launch and AFAICT if I try to
> run emacs from a command prompt I get the native version of emacs that I
> also have installed and not the cygwin one.  The shortcut for XWin
> Server is
>
>    C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe

Question:
Is the Xserver running and you just don't have the Xterm automatically run ?
If yes, the behavior is the current default.


If no, and the Xserver does not run at all, please follow

Problem reports:       http://cygwin.com/problems.html
and provide as attachment the cygcheck.out.

> Merry Christmas
> Mike
>

Buon Natale
Marco

--
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

  reply	other threads:[~2016-12-25 15:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-25 12:55 mike
2016-12-25 15:14 ` Marco Atzeri [this message]
2016-12-25 22:59   ` mike
2016-12-25 23:49     ` Ken Brown
2016-12-26 10:46       ` mike
2016-12-28 10:21       ` mike
2016-12-28 14:29         ` Jon Turney
     [not found]   ` <4d56587d-8b6d-ad01-8b8d-ad08408c2eb6@onetel.com>
     [not found]     ` <37973e96-6891-2500-5bb0-b8bb8fb8959b@gmail.com>
2016-12-26 13:09       ` mike

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=062b5d1e-bf39-0018-2566-d960f05598df@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).