From: uzibalqa <uzibalqa@proton.me>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: uzibalqa via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Remove auctex from emacs
Date: Tue, 20 Sep 2022 22:36:58 +0000 [thread overview]
Message-ID: <UESN_9utmFxfwuk-fHiYV3hT2TBSFzTXHtQIr449HxzB7HdS3JCvCTnyjkkAIa5ZZiPRWpgYfcr03ks1sDPMqmtKVgRLa5vZl9UxPxWqRnc=@proton.me> (raw)
In-Reply-To: <87czbq57sz.fsf@mbork.pl>
------- Original Message -------
On Tuesday, September 20th, 2022 at 4:29 PM, Marcin Borkowski <mbork@mbork.pl> wrote:
> On 2022-09-19, at 19:35, uzibalqa uzibalqa@proton.me wrote:
>
> > > > > Not sure what do you mean. Worked for me for well over a decade.
> >
> > > > > I assume it might bother you that it doesn't seem to have an entry in
> > > > > `auto-mode-alist' – but that makes sense given that the same file name pattern ("\\\\\\\\.tex$")
> > > > > corresponds to several modes (plain TeX/LaTeX/ConTeXt/possible others, like AMSTeX).
> >
> > Correct, that it disregards `auto-mode-alist'.
> >
> > > > > You could argue that there should be one major AUCTeX mode and plain TeX/LaTeX/etc. minor
> > > > > modes –
> >
> > As there can be many modes, one mode should not take over any other mode.
>
>
> I didn't understand this.
>
> > > > > but it is what it is, and I guess it's way too late to change that.
> >
> > This is where we disagree. There is never a time to say it is too late to change.
> > When it is time to change, the change should be made to happen.
> Well, it is probably a major overhaul of the whole codebase. Which
> means you need substantial effort for little gain (in the sense that
> most users - or so I think - are satisfied with the current approach).
> Such major changes are much easier when the codebase is young, hence my
> "too late" comment.
Have seen that some things have started to happen. Some possibilities
for organisation without a full blown major overhaul. But which could
see some breakages.
> Perhaps if you make a compelling argument for such a change on the
> AUCTeX mailing list, possibly volunteering to help with that effort, you
> might succeed. Personally, I think that the time would be better spent
> elsewhere, but this may be because I didn't think about this issue
> deeply enough and cannot see too many disadvantages of the status quo.
> Change my mind! ;-)
There exists the intention to work on things. But was looking forward to
some focused adjustments from others who would be aware of the details
and what would be considered reasonable to clean up.
prev parent reply other threads:[~2022-09-20 22:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 19:19 Remove auctex from emacs uzibalqa
2022-09-11 20:22 ` Pankaj Jangid
2022-09-11 20:35 ` uzibalqa
2022-09-12 4:21 ` Pankaj Jangid
2022-09-12 10:03 ` uzibalqa
2022-09-11 20:24 ` Jean Louis
2022-09-11 21:08 ` uzibalqa
2022-09-11 21:34 ` Jean Louis
2022-09-11 21:42 ` uzibalqa
2022-09-12 7:16 ` Marcin Borkowski
2022-09-12 10:01 ` uzibalqa
2022-09-12 12:16 ` Marcin Borkowski
2022-09-12 13:18 ` uzibalqa
2022-09-19 17:15 ` Marcin Borkowski
2022-09-19 17:35 ` uzibalqa
2022-09-20 16:29 ` Marcin Borkowski
2022-09-20 21:28 ` Emanuel Berg
2022-09-20 22:36 ` uzibalqa [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='UESN_9utmFxfwuk-fHiYV3hT2TBSFzTXHtQIr449HxzB7HdS3JCvCTnyjkkAIa5ZZiPRWpgYfcr03ks1sDPMqmtKVgRLa5vZl9UxPxWqRnc=@proton.me' \
--to=uzibalqa@proton.me \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
/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).