From: Julio Emanuel <costaju@gmail.com>
To: cygwin@cygwin.com
Subject: Re: syntax highlighting on Joe
Date: Tue, 27 Jan 2009 13:58:00 -0000 [thread overview]
Message-ID: <af075b00901270352r55d48eacmb8f343341bce4a52@mail.gmail.com> (raw)
In-Reply-To: <497E8BA8.4060907@cygwin.com>
On Tue, Jan 27, 2009 at 04:20, Larry Hall (Cygwin) wrote:
> Julio Emanuel wrote:
>
> <snip>
>
>> I also would like to grab this opportunity to (once again) ring the
>> service bell to whoever maintain this package 'joe'.
>> It's my favorite (actually the only) editor in the Unix/Cygwin
>
> ^^^^^^^^^^^^^^^^^
> Perhaps it's your only favorite editor but it is not the only editor
> in the Unix, Linux, or Cygwin environments, in case anyone gets the
> wrong immression. ;-)
>
Hmmm. Right. Please patch MY mail :)
sed -e 's/the only/MY only/g'
>> environments, and that's unfortunate to see this package negleted,
>> because this seems to be a simple packaging problem. Also, currently
>> the upstream version is already 3.7 (TWO versions beyond the Cygwin
>> current!).
>>
>> Could all this whining give us "joe'ers" a brand new version of this
>> package? Pretty Please? :)
>
> If this really is just a packaging issue, you may have better luck
> reporting it to the cygwin-apps list (where packaging issues are on-
> topic). Jari has responded to things there of-late.
Damn! And I knew it - sorry for the noise :(
I'll send a new mail to the -apps with only the pertinent comments...
> Of course, if
> you're desperate for a newer 'joe' and aren't going to build it yourself,
> you can take advantage of the version packaged and announced here:
>
> <http://cygwin.com/ml/cygwin-apps/2008-11/msg00001.html>
>
I must have missed those mails somehow.
It seems pretty interesting, but also shows that maybe Jari is not
having enough time to handle these requests :(
> Of course, if you go this route, you can't come back to this list with
> your "whining" if something doesn't work. Perhaps it's a small price
> to pay. ;-)
Small indeed. And you forgot the "Do It Yourself" way...
If only I had a few free hours :)
>
> --
> Larry Hall http://www.rfk.com
> RFK Partners, Inc. (508) 893-9779 - RFK Office
> 216 Dalton Rd. (508) 893-9889 - FAX
> Holliston, MA 01746
>
> _____________________________________________________________________
>
> A: Yes.
>> Q: Are you sure?
>>> A: Because it reverses the logical flow of conversation.
>>>> Q: Why is top posting annoying in email?
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Problem reports: http://cygwin.com/problems.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
>
Thanks for the help!
____________
Julio Costa
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2009-01-27 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 19:56 Javier Sedano
2009-01-26 22:31 ` Javier Sedano
2009-01-27 5:29 ` Julio Emanuel
2009-01-27 6:17 ` Larry Hall (Cygwin)
2009-01-27 13:58 ` Julio Emanuel [this message]
2009-01-27 19:50 ` Javier Sedano
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=af075b00901270352r55d48eacmb8f343341bce4a52@mail.gmail.com \
--to=costaju@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).