all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 18716@debbugs.gnu.org, Andreas Schwab <schwab@suse.de>
Subject: bug#18716: 24.3; dired-omit-extensions's default value omits COPYING.LIB
Date: Wed, 15 Oct 2014 20:05:21 +0100	[thread overview]
Message-ID: <CAOnWdoi1NEsY3k-Jz2h0LhX5iq8XJ6HvCaNEKeVwqwZFZ00Tbw@mail.gmail.com> (raw)
In-Reply-To: <jwvy4shz050.fsf-monnier+emacsbugs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]

On 15 October 2014 18:59, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> > This isn't really the forum for discussing the naming of a GNU license
> > file. dired-omit-mode deals sub-optimally with this particular name, and
> > even if the standard name were changed tomorrow, it would continue to
> occur
> > in the wild for years; so the real issue is: does it matter enough to fix
> > Emacs's treatment of it?
>
> I think the problem is in the naming of the file, rather than in Emacs's
> treatment of files that end in ".LIB".
>

Although no-one has yet answered my question why Emacs takes these patterns
to be case-insensitive even on case-sensitive filing systems.


> We could add a special ad-hoc rule for files called COPYING.LIB, but I'd
> rather we fix the original problem instead.
> "For years" is actually not that long ;-)
>

My repeated experience over the decades is that absent considerable effort,
"for years" rapidly becomes "for decades". Given that we're dealing not
just with future but also with past software releases in this case, I'm not
optimistic.

Nor however do I suggest adding special ad-hoc rules if it's possible to
avoid them, hence my question about case.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1989 bytes --]

  reply	other threads:[~2014-10-15 19:05 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 14:50 bug#18716: 24.3; dired-omit-extensions's default value omits COPYING.LIB Reuben Thomas
2014-10-14 23:41 ` Stefan Monnier
2014-10-14 23:51   ` Reuben Thomas
2014-10-15  7:56   ` Andreas Schwab
2014-10-15 14:21     ` Stefan Monnier
2014-10-15 14:26       ` Reuben Thomas
2014-10-15 14:27         ` Reuben Thomas
2014-10-15 17:59         ` Stefan Monnier
2014-10-15 19:05           ` Reuben Thomas [this message]
2014-10-15 22:42             ` Stefan Monnier
2014-10-15 23:00               ` Reuben Thomas
2014-10-16  3:10                 ` Stefan Monnier
2014-10-15 14:26       ` Andreas Schwab
2014-10-15 17:57         ` Stefan Monnier
2014-10-15 20:57           ` Andreas Schwab
2014-10-15 22:44             ` Stefan Monnier
2014-10-15 22:54               ` Glenn Morris
2014-10-16  3:06                 ` Stefan Monnier
2014-10-16  7:13                   ` Andreas Schwab
2014-10-16 13:15                     ` Stefan Monnier
2014-10-16  2:01   ` Richard Stallman
2014-10-16  3:09     ` Stefan Monnier
2014-10-16 18:14       ` Richard Stallman
2014-10-16 20:17         ` Stefan Monnier
2016-11-08 17:51 ` bug#18716: Patch for this bug Reuben Thomas
2016-11-08 20:04   ` Eli Zaretskii
2016-11-08 22:16     ` Reuben Thomas
2016-11-09 19:36       ` Eli Zaretskii
2016-11-09 22:00         ` Reuben Thomas
2016-11-09 22:52           ` Drew Adams
2016-11-09 23:29             ` Reuben Thomas
2016-11-10 17:38           ` Eli Zaretskii
2016-11-26 17:54             ` Reuben Thomas
2016-11-26 18:29               ` Ken Brown
2016-11-28 21:32                 ` Reuben Thomas
2016-12-02  9:40                   ` Eli Zaretskii
2016-12-02 16:10                     ` Reuben Thomas
2016-12-02 16:16                       ` Eli Zaretskii
2016-12-02 16:31                         ` Reuben Thomas
2016-12-03  0:22 ` bug#18716: Reuben Thomas

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=CAOnWdoi1NEsY3k-Jz2h0LhX5iq8XJ6HvCaNEKeVwqwZFZ00Tbw@mail.gmail.com \
    --to=rrt@sc3d.org \
    --cc=18716@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@suse.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.