From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 'Eli Zaretskii' <eliz@gnu.org>, emacs-devel@gnu.org
Subject: RE: next emacs version?
Date: Sat, 20 Mar 2010 16:26:02 -0700 [thread overview]
Message-ID: <15F967F7C7B2462D889160D499BF7B5E@us.oracle.com> (raw)
In-Reply-To: <A0F8070B5E0947C2AEBA46B5152946E3@us.oracle.com>
> And as I said, I cannot even reproduce the bug itself on
> Windows, starting with emacs -Q, in any release that I have.
> That seems to indicate that the bug (and hence your approach)
> might be platform-specific. (Or perhaps the bug report and
> fix description are not clear.)
Indeed, the bug history does indicates that this is platform-specific. As you
yourself said in the bug history, it depends whether your `ls' supports --dired.
The bug history then says that it fails if you set `dired-use-ls-dired' to nil.
So that could presumably be tested in the "unit-test" code you suggest
inserting.
But even that isn't true on Windows (perhaps because it uses `ls-lisp'). Setting
`dired-use-ls-dired' to nil does not manifest the bug.
> Whereas a simple `emacs-version' test has to work (since the
> fix is in only in newer versions), code that addresses the
> bug case directly will do the wrong thing on any platforms
> where the bug was not manifested. The buggy file name can
> only serve to identify which regexp is which if in fact one
> of the regexps (the old one) is buggy on the current platform.
next prev parent reply other threads:[~2010-03-20 23:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 11:23 next emacs version? Drew Adams
2010-03-19 13:22 ` Eli Zaretskii
2010-03-19 17:29 ` Drew Adams
2010-03-19 18:09 ` Eli Zaretskii
2010-03-19 18:46 ` Drew Adams
2010-03-19 19:02 ` Eli Zaretskii
2010-03-19 20:02 ` Drew Adams
2010-03-19 21:15 ` Eli Zaretskii
2010-03-19 21:23 ` Drew Adams
2010-03-20 2:35 ` Ken Raeburn
2010-03-20 2:39 ` Lennart Borgman
2010-03-20 3:42 ` Óscar Fuentes
2010-03-20 15:51 ` Lennart Borgman
2010-03-20 5:31 ` Ken Raeburn
2010-03-23 2:05 ` Stephen J. Turnbull
2010-03-20 3:38 ` Drew Adams
2010-03-20 5:31 ` Ken Raeburn
2010-03-20 6:51 ` Drew Adams
2010-03-20 5:31 ` Ken Raeburn
2010-03-20 6:51 ` Drew Adams
2010-03-23 2:34 ` Stephen J. Turnbull
2010-03-23 5:01 ` Miles Bader
2010-03-23 5:39 ` Drew Adams
2010-03-20 3:51 ` Jason Rumney
2010-03-20 6:47 ` Drew Adams
2010-03-20 8:39 ` Eli Zaretskii
2010-03-20 14:58 ` Drew Adams
2010-03-20 16:22 ` Eli Zaretskii
2010-03-20 8:11 ` Eli Zaretskii
2010-03-19 20:55 ` Stefan Monnier
2010-03-19 21:16 ` Drew Adams
2010-03-20 19:10 ` Stefan Monnier
2010-03-20 20:29 ` Drew Adams
2010-03-20 21:53 ` Stefan Monnier
2010-03-20 23:09 ` Drew Adams
2010-03-20 23:26 ` Drew Adams [this message]
2010-03-22 1:22 ` Stefan Monnier
2010-03-22 7:22 ` Drew Adams
2010-03-22 13:52 ` Stefan Monnier
2010-03-21 21:34 ` Thien-Thi Nguyen
2010-03-21 23:20 ` Drew Adams
2010-03-19 14:52 ` Chong Yidong
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15F967F7C7B2462D889160D499BF7B5E@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).