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: Fri, 20 Dec 2024 09:05:41 +0200 [thread overview]
Message-ID: <86o716kf5m.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmm-erfm5LW9cx1AACceGF7UF8_FUtE=sv6ELF4q_54fvw@mail.gmail.com> (message from Stefan Kangas on Thu, 19 Dec 2024 17:55:22 -0500)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 19 Dec 2024 17:55:22 -0500
> Cc: bjorn.bidar@thaodan.de, 74946@debbugs.gnu.org, acorallo@gnu.org
>
> > .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?
>
> Maybe something like the below patch?
Maybe. Try it against any similar name you have on your system. I
used "locate -b gdbinit" to find matching files on mine.
> BTW, should the .gdbinit.py.in file be in python-mode perhaps?
Yes, it should be.
> And what about gdbinit.5?
It's a roff file (source of a man page).
next prev parent reply other threads:[~2024-12-20 7:05 UTC|newest]
Thread overview: 9+ 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
2024-12-19 21:29 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 22:55 ` Stefan Kangas
2024-12-20 1:33 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-20 7:05 ` Eli Zaretskii [this message]
[not found] ` <87frmjtl9f.fsf@>
2024-12-20 6:46 ` Eli Zaretskii
2024-12-20 8:07 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86o716kf5m.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).