unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18205@debbugs.gnu.org
Subject: bug#18205: Obsolete patterns in auto-mode-alist
Date: Thu, 7 Aug 2014 13:02:26 +0100	[thread overview]
Message-ID: <CAOnWdojx_tcOJpo=uVARUuvx4YrfWca4ZRrw8m-STNMXhCNbaQ@mail.gmail.com> (raw)
In-Reply-To: <83k36lnhb1.fsf@gnu.org>

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

On 7 August 2014 03:51, Eli Zaretskii <eliz@gnu.org> wrote:

> > Date: Wed, 6 Aug 2014 23:05:33 +0100
> > From: Reuben Thomas <rrt@sc3d.org>
> > Cc: 18205@debbugs.gnu.org
> >
> > If "_emacs" is to be supported, surely other similar patterns should
> > be added for other dot files?
>
> Which patterns are those?
>

For example, the patterns for bash's dot-files.


> Why do you think we support _emacs for DOS and Windows?
>

I'm not sure why you're asking me, you're the DJGPP maintainer! If you
meant it as an exercise, then I'd say: I have no idea where we support it
on Windows, where, post-Win 3.x (which we don't support), ".emacs" is a
valid filename.

I understood that DJGPP had long filename support too, but maybe that's not
universal? In which case, not only "_emacs", but other GNU dotfiles should
surely be supported with a leading "_"?

In other words, it looks like a quick hack to support the most
commonly-edited Emacs file that would suffer from this problem. I can't
tell whether it's still needed, and if it is, it should be extended
systematically.

-- 
http://rrt.sc3d.org

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

  reply	other threads:[~2014-08-07 12:02 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 23:58 bug#18205: Obsolete patterns in auto-mode-alist Reuben Thomas
2014-08-06 17:41 ` Stefan Monnier
2014-08-06 17:47   ` Reuben Thomas
2014-08-06 18:04     ` Eli Zaretskii
2014-08-07  0:14   ` Glenn Morris
2014-08-07  2:53     ` Eli Zaretskii
2014-08-07  9:39       ` Reuben Thomas
2014-08-07 10:07         ` Reuben Thomas
2014-08-07 10:18           ` Reuben Thomas
2014-08-07 18:24           ` Richard Stallman
2014-08-07 12:23         ` Stefan Monnier
2014-08-07 15:28           ` Eli Zaretskii
2014-08-07 19:12             ` Stefan Monnier
2014-08-07 19:40               ` Eli Zaretskii
2014-08-07 18:24       ` Richard Stallman
2014-08-07 19:34         ` Eli Zaretskii
2014-08-08  5:35           ` Richard Stallman
2014-08-08  6:06             ` Eli Zaretskii
2014-08-08 19:11               ` Richard Stallman
2014-08-08 20:09                 ` Eli Zaretskii
2014-08-08 20:54                 ` Reuben Thomas
2014-08-08 23:19               ` Reuben Thomas
2014-08-09  6:49                 ` Eli Zaretskii
2014-08-09  7:41                   ` Reuben Thomas
2014-08-09  7:44                   ` Reuben Thomas
2014-08-09  8:30                     ` Eli Zaretskii
2014-08-09  9:11                       ` Reuben Thomas
2014-08-09 11:53                         ` Eli Zaretskii
2014-08-09 11:57                           ` Reuben Thomas
2014-08-09 14:27                             ` Eli Zaretskii
2014-08-07  4:25   ` Richard Stallman
2014-08-06 18:01 ` Eli Zaretskii
2014-08-06 22:05   ` Reuben Thomas
2014-08-07  2:51     ` Eli Zaretskii
2014-08-07 12:02       ` Reuben Thomas [this message]
2014-08-07 15:27         ` Eli Zaretskii
2014-08-07 11:54     ` Reuben Thomas
2014-08-06 23:57 ` Glenn Morris

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='CAOnWdojx_tcOJpo=uVARUuvx4YrfWca4ZRrw8m-STNMXhCNbaQ@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=18205@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).