unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Phil Sainty <psainty@orcon.net.nz>, 57481@debbugs.gnu.org
Subject: bug#57481: elisp code utilising derived-mode-parent
Date: Tue, 30 Aug 2022 15:16:50 +0200	[thread overview]
Message-ID: <trinity-73a7de1c-c80d-4c01-b733-c8cc8466b73b-1661865410141@3c-app-mailcom-bs10> (raw)
In-Reply-To: <8335ddvq8n.fsf@gnu.org>

> Sent: Wednesday, August 31, 2022 at 1:02 AM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: "Phil Sainty" <psainty@orcon.net.nz>
> Cc: dimech@gmx.com, 57481@debbugs.gnu.org
> Subject: Re: bug#57481: elisp code utilising derived-mode-parent
>
> > Cc: 57481@debbugs.gnu.org
> > Date: Wed, 31 Aug 2022 00:38:46 +1200
> > From: Phil Sainty <psainty@orcon.net.nz>
> >
> > On 2022-08-31 00:08, Christopher Dimech wrote:
> > > Can one do something that can be run in elisp code and in
> > > lisp-interaction-mode without requirement that the mode one
> > > is interested in has been loaded?
> >
> > You're asking whether Emacs can tell you things it doesn't know.
>
> Well, it's Emacs, isn't it?  Why shouldn't it have a feature whereby
> it tells us things it doesn't know about?  It certainly sounds useful
> to have.

It could find things through and do what it has to do, without requirements
for user mode loading.





  reply	other threads:[~2022-08-30 13:16 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 [this message]
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

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-73a7de1c-c80d-4c01-b733-c8cc8466b73b-1661865410141@3c-app-mailcom-bs10 \
    --to=dimech@gmx.com \
    --cc=57481@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=psainty@orcon.net.nz \
    /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).