From: Christopher Dimech <dimech@gmx.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57481@debbugs.gnu.org
Subject: bug#57481: elisp code utilising derived-mode-parent
Date: Tue, 30 Aug 2022 13:48:17 +0200 [thread overview]
Message-ID: <trinity-2af0ada9-43ad-477a-ba5c-281fc36c20e0-1661860097263@3c-app-mailcom-bs10> (raw)
In-Reply-To: <87zgfm9fwf.fsf@gnus.org>
> Sent: Tuesday, August 30, 2022 at 10:36 PM
> From: "Lars Ingebrigtsen" <larsi@gnus.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: 57481@debbugs.gnu.org
> Subject: bug#57481: elisp code utilising derived-mode-parent
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > Have seen that (get 'latex-mode 'derived-mode-parent) as a normal
> > elisp command.
> > For instance, I cannot run it in "lisp-interaction-mode" or simply make a elisp
> > function that iterates the result of the expression until reacting "nil" to get
> > a tree of all parents.
> >
> > Would be a handy tool to have.
>
> I don't think that would be generally useful -- it's internal data that
> wouldn't be interesting to the vast majority of users.
>
> So I'm closing this as a "wontfix".
I encourage tools that assist the perusing of internal data. Such tools
would be instrumental for people keenly interested in Emacs Internals.
Besides users there should be a separate focus towards developer needs.
Will elevate emacs work substantially.
prev parent reply other threads:[~2022-08-30 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 5:44 bug#57481: elisp code utilising derived-mode-parent Christopher Dimech
2022-08-30 6:37 ` Phil Sainty
2022-08-30 11:33 ` Christopher Dimech
2022-08-30 12:02 ` Phil Sainty
2022-08-30 12:08 ` Christopher Dimech
2022-08-30 12:38 ` Phil Sainty
2022-08-30 12:46 ` Christopher Dimech
2022-08-30 13:02 ` Eli Zaretskii
2022-08-30 13:16 ` Christopher Dimech
2022-08-30 22:07 ` Phil Sainty
2022-08-31 6:24 ` Christopher Dimech
2022-08-31 11:31 ` Christopher Dimech
2022-08-30 10:36 ` Lars Ingebrigtsen
2022-08-30 11:48 ` Christopher Dimech [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=trinity-2af0ada9-43ad-477a-ba5c-281fc36c20e0-1661860097263@3c-app-mailcom-bs10 \
--to=dimech@gmx.com \
--cc=57481@debbugs.gnu.org \
--cc=larsi@gnus.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).