From: Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Heime <heimeborgia@protonmail.com>
Cc: Jean Louis <bugs@gnu.support>,
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Mode hooks for latex and tex files
Date: Sun, 01 Dec 2024 21:20:20 +0000 [thread overview]
Message-ID: <Eb_WPmFjGKBsUHCvJON3s1uQMH9GF9kchd6MasfKStNA3YMujvQ7t3TT454oG8O_cCP6O7lA-TTajFIA4tTLsa3by2QKwDB6W57Mq7yvPwU=@protonmail.com> (raw)
In-Reply-To: <d2GewtuxiNzGGBD-NH2h5G5JhpGyKphVd2sVmsEm9v7ClFXCQGn5ImiIro0ICAYmQ9XX8eeXtANvL54vDhfQwfHMn1iyHx3uRKtjoKRE8Xg=@protonmail.com>
On Monday, December 2nd, 2024 at 2:58 AM, Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> Sent with Proton Mail secure email.
>
> On Monday, December 2nd, 2024 at 2:43 AM, Jean Louis bugs@gnu.support wrote:
>
> > * Heime via Users list for the GNU Emacs text editor help-gnu-emacs@gnu.org [2024-11-30 22:57]:
> >
> > > What are the mode hooks for latex and tex files?
> > >
> > > Using latex and tex is currently very non-intuitive, with things
> > > like LaTex-mode, TeX-mode. This mixed capitalisation is all too
> > > confusing because ordinary users see only a latex or tex configuration
> > > for their modes, rather than the nuances of capitalisation changes.
> >
> > You could do:
> >
> > M-x find-library RET latex TAB to see what is available
> >
> > Then go into the library and search for "hook"
> >
> > Then you position cursor on name of the hook and C-h v or C-h f to describe variable or function.
> >
> > You need to learn to use help functions within Emacs, you will otherwise never get out of problems.
> >
> > --
> > Jean Louis
>
>
> I do not see how that would be a productive endeavour, going through the libraries to figure
> out what might be going on. Emacs should have just a standard latex and tex modes. And other
> libraries should start with the library name as emacs is supposed to require, instead of playing
> around with changes in capitalisation to do different things. The whole thing becomes confusion
> 101.
>
> The design should be not to get others into problems, not about encouraging them to hack around
> trying to get out of emacs self-inflicted ones!
What are the built-in default modes fol latex and tex?
next prev parent reply other threads:[~2024-12-01 21:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 19:55 Mode hooks for latex and tex files Heime via Users list for the GNU Emacs text editor
2024-12-01 14:43 ` Jean Louis
2024-12-01 14:58 ` Heime via Users list for the GNU Emacs text editor
2024-12-01 21:20 ` Heime via Users list for the GNU Emacs text editor [this message]
2024-12-02 10:17 ` Jean Louis
2024-12-02 11:13 ` Joel Reicher
2024-12-02 13:17 ` Arash Esbati
2024-12-02 15:58 ` Heime via Users list for the GNU Emacs text editor
2024-12-02 16:15 ` Heime via Users list for the GNU Emacs text editor
2024-12-02 20:17 ` Arash Esbati
2024-12-02 20:29 ` Heime via Users list for the GNU Emacs text editor
2024-12-02 20:38 ` Arash Esbati
2024-12-02 20:44 ` 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='Eb_WPmFjGKBsUHCvJON3s1uQMH9GF9kchd6MasfKStNA3YMujvQ7t3TT454oG8O_cCP6O7lA-TTajFIA4tTLsa3by2QKwDB6W57Mq7yvPwU=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=bugs@gnu.support \
--cc=heimeborgia@protonmail.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.
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).