From: Jean Louis <bugs@gnu.support>
To: Heime <heimeborgia@protonmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Covering of prog-mode
Date: Tue, 3 Dec 2024 23:20:09 +0300 [thread overview]
Message-ID: <Z09n-cVjtc8NGyaU@lco2> (raw)
In-Reply-To: <9DcjRFc6mjPoYRJQDQSESEsOIWpwSvvcnILKIFJaESJ6yFQPwvYjvnh9EFf-nYUeVrXNlZbP2FV5D1X3PdxSpO82MJs-xNnaOdbnEuuymYI=@protonmail.com>
* Heime <heimeborgia@protonmail.com> [2024-12-03 15:44]:
> Sent with Proton Mail secure email.
>
> On Tuesday, December 3rd, 2024 at 6:22 PM, Jean Louis <bugs@gnu.support> wrote:
>
> > * Heime via Users list for the GNU Emacs text editor help-gnu-emacs@gnu.org [2024-12-03 03:01]:
> >
> > > How can one figure out that prog-mode covers ?
> >
> >
> > M-x find-library RET prog-mode RET then read
> >
> > --
> > Jean Louis
>
> What should I look for in that file? Is there a command I can call
> on a file that returns me whether it is included in prog-mode?
Look for words, try to distinguish licensing from commentary, then
somewhere there maybe you find an explanation. It is like entering
dark labyrinth, you never know what is out there, but is
interesting. I am not sure any more, but I remember something like
MONITOR command, I could enter into memory of Commodore plus/4 and for
hours I could watch and browse those hex numbers, and watching on
right side the symbols and letters, figuring out what it all means.
To find out all *-mode(s) you can do this:
M-x find-library RET -mode TAB TAB and you will see them all, it is interesting.
Go one by one carefully, enter inside and read commentaries, until you
get tired, then switch to movie, music, or sleeping, keep doing it,
and after many attempts you will get quite new cognition about it.
I am still doing it by the way. I have no idea what people talk about on `git log' but I keep reading.
--
Jean Louis
next prev parent reply other threads:[~2024-12-03 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 23:59 Covering of prog-mode Heime via Users list for the GNU Emacs text editor
2024-12-03 6:22 ` Jean Louis
2024-12-03 12:44 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:20 ` Jean Louis [this message]
2024-12-03 20:27 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:35 ` Jean Louis
2024-12-03 20:49 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 21:05 ` Jean Louis
2024-12-03 21:21 ` Heime via Users list for the GNU Emacs text editor
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=Z09n-cVjtc8NGyaU@lco2 \
--to=bugs@gnu.support \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@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.
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).