From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Using Cygwin Emacs
Date: Mon, 16 May 2011 02:27:00 -0000 [thread overview]
Message-ID: <4DD08B8E.6090707@cornell.edu> (raw)
In-Reply-To: <BANLkTim20f-zm=m3iZj-fdMsFW3QrvT8CA@mail.gmail.com>
On 5/15/2011 9:27 PM, Sayth Renshaw wrote:
> I first the first time today looked more in depth at the packages
> available in Cygwin as I was seaching for gdb to use as my debugger in
> emacs. I found emacs in the package list!.
>
> Found this wiki page
> http://www.emacswiki.org/cgi-bin/wiki?CygwinizedEmacsHOWTO though its
> layout is a little bit confused, it tries to advise on using emacs in
> cygwin.
That wiki page is way out of date. I would advise you to ignore it. If
you install Cygwin's emacs package, you'll find more up-to-date
information in /usr/share/doc/Cygwin/emacs.README .
> Before I venture down this path are there many people using
> this package? Is it advantageous to use this package(cygwin)? Or is
> there not much upside to a user using the default 23.2 zip package?
There are plenty of Cygwin users who use (Cygwin's) emacs. I don't
understand your last two questions. What do you mean by the "default
23.2 zip package"? But if you want to know what it's like to use
Cygwin's emacs package instead of whatever you're using now, why not
just try it?
Ken Brown
Cygwin's emacs maintainer
--
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 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 1:28 Sayth Renshaw
2011-05-16 2:27 ` Ken Brown [this message]
2011-05-25 8:34 ` Oleksandr Gavenko
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
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=4DD08B8E.6090707@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).