From: Ken Brown <kbrown@cornell.edu>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: Using Cygwin Emacs
Date: Mon, 16 May 2011 17:38:00 -0000 [thread overview]
Message-ID: <4DD1611E.9010202@cornell.edu> (raw)
In-Reply-To: <AAC888BE98A741AF8A87B923F7C872C4@cit.wayne.edu>
On 5/16/2011 1:19 PM, Lee Maschmeyer wrote:
> Since the OP mentioned emacs version 22 and since Cygwin's emacs is 23.3.1
> (emacs --version), this makes me wonder if more fundamental suggestions
> might be needed. If the following is self-evident please pardon me but
> perhaps we need to check on some very basic stuff:
>
> 1. All installations of Cygwin packages should be done through Cygwin's
> setup program. Go to cygwin.com, click on the Install Cygwin link, download
> setup.exe and run it. Do this for every installation or update of every
> Cygwin component.
>
> 2. To get Cygwin's Emacs (23.3.1), open the Editors category and click on
> emacs (setup says it's 23.3.2).
>
> 3. If that doesn't work, my guess would be to follow the reporting
> instructions at the end of every message.
>
> 4. And if all else fails, read the friendly manual.
One small correction: Cygwin's current emacs package is 23.3-2. (That's
a hyphen before the 2, not a dot.) But emacs will report its version as
23.3.1. The final ".1" has nothing to do with Cygwin's package
numbering and should be ignored. If you really want to know what it
means, see http://cygwin.com/ml/cygwin/2010-08/msg00891.html .
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-05-16 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 4:35 Sayth Renshaw
2011-05-16 7:27 ` Markus Hoenicka
2011-05-16 10:14 ` Ken Brown
2011-05-16 17:21 ` Lee Maschmeyer
2011-05-16 17:38 ` Ken Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-16 1:28 Sayth Renshaw
2011-05-16 2:27 ` Ken Brown
2011-05-25 8:34 ` Oleksandr Gavenko
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=4DD1611E.9010202@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).