From: Mark Harig <idirectscm@aim.com>
To: cygwin-apps@cygwin.com
Subject: Re: Emacs is coming back - all pleased?
Date: Sun, 22 Jul 2007 19:25:00 -0000 [thread overview]
Message-ID: <46A3AF2C.2000601@aim.com> (raw)
In-Reply-To: <46A3AD35.8060608@aim.com>
Mark Harig wrote:
> Steffen Sledz wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Eric Blake schrieb:
>>
>>> Go ahead and send a release announcement, so hopefully you can get
>>> some more testers willing to try the version while it is still
>>> experimental.
>>>
>>
>> Is there a template for such announcements?
>>
>>
> Because 'etags' has been removed from the standard Emacs distribution,
> it would be
> good for the announcement and the cygwin.readme for Emacs to notify
> users that
> they will need to install the (exhuberant) ctags package if they want
> to generate
> tag files for Emacs Lisp. This is a standard, documented feature of
> Emacs so
> users should be made aware of why it will not work if they only
> install the base
> Cygwin installation plus Emacs.
Correction about the Cygwin README for Emacs: I see that
/usr/share/doc/Cygwin/emacs-22.1.README already mentions the exuberant
ctags dependency:
"Some binaries normally part of the emacs distribution are separated
to avoid conflicts with other packages. If you need b2m or rcs-ckeckin
install xemacs-emacs-common package. If you need ctags or etags
install
ctags package."
Of course, the 'b2m' and 'rcs-checkin' binaries are already installed by
default because the 'xemacs-emacs-common' package is a requirement
of the Cygwin Emacs package.
>
> Alternatively, the 'etags' program could be removed from the ctags
> package
> (which still provides etags via the '-e' command-line option) and
> restored to
> the Emacs package.
>
> ---
>
next prev parent reply other threads:[~2007-07-22 19:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 11:03 Steffen Sledz
2007-07-19 14:02 ` Steffen Sledz
2007-07-20 3:46 ` Eric Blake
2007-07-20 14:36 ` Igor Peshansky
2007-07-22 18:48 ` Steffen Sledz
2007-07-22 19:17 ` Mark Harig
2007-07-22 19:25 ` Mark Harig [this message]
2007-07-22 21:41 ` Eric Blake
2007-07-19 14:15 ` Ken Brown
2007-07-19 19:28 ` Ken Brown
2007-07-20 3:39 ` Eric Blake
2007-07-22 11:37 ` Ken Brown
2007-07-22 15:07 ` Eric Blake
[not found] <Pine.OSF.4.58.0707191628540.19421@ax0rm1.roma1.infn.it>
2007-07-19 21:01 ` Ken Brown
2007-07-20 3:44 ` Eric Blake
2007-07-20 3:56 ` Brian Dessent
2007-07-20 4:05 ` Eric Blake
2007-07-20 8:17 ` Dr. Volker Zell
2007-07-20 12:46 ` Eric Blake
2007-07-22 0:05 ` Mark Harig
2007-07-22 3:44 ` Eric Blake
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=46A3AF2C.2000601@aim.com \
--to=idirectscm@aim.com \
--cc=cygwin-apps@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).