all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Paul Nelson <ultrono@gmail.com>,  emacs-devel@gnu.org
Subject: Re: [ELPA] some tex-related packages
Date: Mon, 20 May 2024 19:37:13 +0200	[thread overview]
Message-ID: <m27cfo75bq.fsf@macmutant.fritz.box> (raw)
In-Reply-To: <87cypgn8oc.fsf@posteo.net> (Philip Kaludercic's message of "Mon,  20 May 2024 09:18:11 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

> Paul Nelson <ultrono@gmail.com> writes:
>
>> How about "latexmk-continuous"?  (The names latex-flymake and
>> auctex-latexmk are both taken, and those packages do different things.  The
>> new feature is that the compilation takes place continuously rather than on
>> demand, with the errors reported in the buffer.)
>
> Sounds good and descriptive!

My suggestion is: For everything that depends on AUCTeX, prefix it with
auctex-, and for others which work with built-in mode as well, take tex-
as prefix.  Rationale: it makes things easier to find once you do 'M-x
list-packages RET'.

>>> This makes me think, have you communicated any of these features to the
>>> AUCTeX developers?  Perhaps it would make more sense to upstream these
>>> as patches instead of having too many little packages?
>>>
>>>
>> They've been communicated, and the first two have been discussed:

I think the agreement was to patch AUCTeX in order to provide enough
compat code so Paul's package would run smoothly.

>> I'd be happy with whatever makes the most sense, but figured submitting to
>> ELPA would make them readily available without introducing additional
>> burden on the AUCTeX maintainers.
>
> I'll let the AUCTeX maintainers decide.  That being said, I am sure
> they'd always appreciate a helping hand in general.

Disussion about upstreaming parts of Paul's code would be the next step,
I think, based on user feedback and request.  Reg. helping hands: Always
welcome, but I really wish that people take over which actually use
LaTeX/AUCTeX/RefTeX on a regular basis.  I can tell for Tassilo and
myself that we don't use LaTeX anymore, and that for many years now.

> It might just be my view, but having too many little packages makes it
> difficult for newcomers to get an overview and understand what they want
> or need.

I think that having small packages which do the job right isn't that
bad.  I wish package writers would be more in contact with AUCTeX
developers (Paul did it right), and the developers would be more
responsive to package author's requests (I tried to help as far as I
could).

Best, Arash



  reply	other threads:[~2024-05-20 17:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-19 17:06 [ELPA] some tex-related packages Paul Nelson
2024-05-20  6:33 ` Philip Kaludercic
2024-05-20  9:01   ` Paul Nelson
2024-05-20  9:18     ` Philip Kaludercic
2024-05-20 17:37       ` Arash Esbati [this message]
2024-05-22 16:10         ` Paul Nelson
2024-05-27 16:13           ` Arash Esbati
2024-05-27 19:07             ` Paul Nelson
2024-06-02 12:51               ` Arash Esbati
2024-06-02 18:44                 ` Philip Kaludercic
2024-06-02 19:11                   ` Paul Nelson
2024-06-02 19:53                     ` Philip Kaludercic
2024-06-02 20:03                       ` Paul Nelson
2024-06-16 16:20                         ` Paul Nelson
2024-06-17 10:45                           ` Philip Kaludercic
2024-06-17 10:52                             ` Philip Kaludercic
2024-06-18  0:53                               ` Paul Nelson
2024-06-18  6:38                                 ` Philip Kaludercic
2024-06-26  5:59                                   ` Paul Nelson
2024-10-12 15:30                                   ` Paul Nelson
2024-10-18 11:00                                     ` Philip Kaludercic
2024-10-18 17:23                                       ` Paul Nelson
2024-10-18 17:46                                         ` Philip Kaludercic
2024-10-18 19:04                                           ` Paul Nelson
2024-10-19 14:54                                             ` Philip Kaludercic

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m27cfo75bq.fsf@macmutant.fritz.box \
    --to=arash@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=ultrono@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.