public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Updated: emacs-24.5-3 (TEST)
Date: Fri, 29 Jan 2016 16:07:00 -0000	[thread overview]
Message-ID: <56AB7439.7060803@cornell.edu> (raw)
In-Reply-To: <CAFj5VXHt75jfiq7iB9Uy9jK-n61yfjFfP6t+HsL16rukE4UU6A@mail.gmail.com>

On 1/29/2016 9:00 AM, Daniel Daboul wrote:
> On Sun, Jan 24, 2016 at 1:30 AM, Ken Brown <kbrown@cornell.edu> wrote:
>> The following packages have been updated in the Cygwin distribution as
>> test releases:
>>
>> * emacs-24.5-3
>> * emacs-X11-24.5-3
>> * emacs-w32-24.5-3
>> * emacs-el-24.5-3
>> [...]
>> This is a rebuild of the 24.5-2 packages, patched to allow native Windows
>> paths like C:\foo or C:/foo in situations where file names are expected.
>>
>> If you are interested in this feature, please try the test release and let
>> me know whether it works the way you expect.
>
> Thank you for the packages. I have started to use "emacs-w32-24.5-3",
> I like the new
> features and I have not encountered obvious bugs.
>
> A shortcoming of the new version "GNU Emacs 24.5.1 (i686-pc-cygwin) of
> 2016-01-23 on moufang"
> compared to a mingw version "GNU Emacs 24.3.1 (i386-mingw-nt6.2.9200)
> of 2013-03-17 on MARVIN",
> which I also use, is that file-name completion does not work for find-file if
> a windows-style directory path is used. - Daniel

Thanks for the feedback.  I'll see if I can figure out how to make that 
work.

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

  reply	other threads:[~2016-01-29 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56A40D09.1010606@cornell.edu>
2016-01-29 16:05 ` Daniel Daboul
2016-01-29 16:07   ` Ken Brown [this message]
2016-01-29 18:41     ` Ken Brown
2016-02-03 21:45       ` Daniel Daboul
2016-02-04 14:39         ` 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=56AB7439.7060803@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).