unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: bjorn.bidar@thaodan.de, acorallo@gnu.org, 74946@debbugs.gnu.org
Subject: bug#74946: [PATCH] * lisp/files.el (auto-mode-alist): Include gdbinit too
Date: Thu, 19 Dec 2024 10:14:00 +0200	[thread overview]
Message-ID: <86o718ks3b.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkWiHYiDxbV5mhcrtQDieWu=Y3FGFShUDX99ahhG2-udQ@mail.gmail.com> (message from Stefan Kangas on Wed, 18 Dec 2024 20:00:37 -0500)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 18 Dec 2024 20:00:37 -0500
> Cc: Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <acorallo@gnu.org>
> 
> > Please also include into Emacs 30 if possible.
> 
> If Eli and Andrea agrees, I think we could do it.

It looks innocent enough, but at this point I'd like to limit changes
on the release branch to only really urgent and important ones (or
documentation).  We have lived with this outdated code for several
years (GDB 11.1 was released in 2022), so this change doesn't look
urgent to me.

Btw, if we want to fix this entry, we should perhaps do a more
thorough job.  For example, on my system I have files with the
following base names:

  .gdbinit.in
  .gdbinit
  _gdbinit (for MS-DOS)
  gdb.ini (likewise)
  gdbinit
  gdbinit.in
  SOMETHING-gdbinit
  .gdbinit.loader
  gdbinit-history.exp (not a GDB init file)
  gdbinit.5 (likewise)
  gdbinit.c (likewise)
  .gdbinit.py.in (likewise)

Should we improve the regexp to DTRT for those additional files, but
without false positives?





      reply	other threads:[~2024-12-19  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 14:19 bug#74946: [PATCH] * lisp/files.el (auto-mode-alist): Include gdbinit too Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19  1:00 ` Stefan Kangas
2024-12-19  8:14   ` Eli Zaretskii [this message]

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=86o718ks3b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74946@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --cc=stefankangas@gmail.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.
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).