unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Matthias Meulien <orontee@gmail.com>
Cc: "Per Starbäck" <per@starback.se>, emacs-devel@gnu.org
Subject: Re: About LaTeX/TeX modes
Date: Wed, 10 Aug 2022 19:07:16 +0200	[thread overview]
Message-ID: <874jykgh49.fsf@gnu.org> (raw)
In-Reply-To: <CAFEQCfBocSDHcaTA1TdmQJTm7gKdRVYCe1bojuTG7sNUv0ZNGw@mail.gmail.com>

Matthias Meulien <orontee@gmail.com> writes:

>> (...) For what it's worth I still think it would be really good if
>> AucTeX was merged into Emacs. Let's avoid the feeling of "when you
>> use Emacs you really should first customize it like this and this and
>> this". When I use Emacs in demos for students I use a plain no-frills
>> Emacs, because I want it to be what they get themselves if they
>> install on their own computers, but I've "had to" make an exception
>> for TeX, because not using AucTeX would be too hard for me.
>>
>
> My experience is the opposite! The legacy mode worked out of the box,
> AucTeX didn't and I faced a huge manual and got lost in tons of
> options and new commands to narrow, comment, compile...

If it doesn't work out-of-the-box with the AUCTeX ELPA package that's a
bug you should report.

Bye,
Tassilo



  reply	other threads:[~2022-08-10 17:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07  9:03 About LaTeX/TeX modes Angelo Graziosi
2022-08-07 11:11 ` Arash Esbati
2022-08-07 12:32   ` Angelo Graziosi
2022-08-07 13:31   ` T.V Raman
2022-08-07 19:25     ` Arash Esbati
2022-08-08 13:56       ` T.V Raman
2022-08-08 14:29         ` Arash Esbati
2022-08-08 15:32           ` T.V Raman
2022-08-09 10:53             ` Per Starbäck
2022-08-09 11:47               ` Stefan Kangas
2022-08-09 14:01               ` T.V Raman
2022-08-09 20:41               ` Matthias Meulien
2022-08-10 17:07                 ` Tassilo Horn [this message]
2022-08-09 14:50             ` Angelo Graziosi
2022-08-10 23:47             ` Angelo Graziosi

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=874jykgh49.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=orontee@gmail.com \
    --cc=per@starback.se \
    /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).