From: Paul Nelson <nelson.paul.david@gmail.com>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: Philip Kaludercic <philipk@posteo.net>,
Richard Stallman <rms@gnu.org>,
emacs-devel@gnu.org
Subject: Re: tex-parens package
Date: Sat, 29 Jun 2024 03:28:47 +0200 [thread overview]
Message-ID: <CAOA-32NaHvJqc_Mbu_SNQcjw-rA5eWVDoCPe1P9QYK0ZnGDUaw@mail.gmail.com> (raw)
In-Reply-To: <871q4gitx9.fsf@jeremybryant.net>
On Sat, Jun 29, 2024 at 12:28 AM Jeremy Bryant <jb@jeremybryant.net> wrote:
>
> Paul Nelson <nelson.paul.david@gmail.com> writes:
>
> > I'd be happy to see it integrated further if there's interest, and
> > would then welcome feedback on how best to do that. For instance, it
> > could be included "as is", as a collection of functions that the user
> > can bind, or alternatively as a minor mode ("tex-parens-mode"?) with
> > a keymap that remaps binds for list/sexp commands to their tex-parens
> > counterparts.
> >
>
> Is there a technical solution that makes it work for both the built-in
> modes and auctex?
>
The approaches I mentioned work with both the built-in modes and auctex.
Thinking a bit more: the features of tex-parens should be optional,
since they clash a bit with the defaults of both tex-mode.el and
auctex (which set forward-sexp-function and
beginning-of-defun-function, respectively). This suggests packaging
those features as a minor mode. I've updated the package just now to
contain such a minor mode, tex-parens-mode, which works as a hook for
either tex-mode or TeX-mode. The basic setup thus simplifies to
adding a line such as (add-hook 'tex-mode #'tex-parens-mode) to one's
config.
The only way I can think of to integrate tex-parens further would be
to include it in Emacs and enable the minor mode by default (e.g., in
the setup of tex-mode and TeX-mode), but that seems a bit aggressive?
Any other suggestions would of course be welcome.
prev parent reply other threads:[~2024-06-29 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 3:02 tex-parens package Richard Stallman
2024-06-27 7:46 ` Philip Kaludercic
2024-06-27 11:40 ` Paul Nelson
2024-06-28 22:28 ` Jeremy Bryant
2024-06-29 1:28 ` Paul Nelson [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=CAOA-32NaHvJqc_Mbu_SNQcjw-rA5eWVDoCPe1P9QYK0ZnGDUaw@mail.gmail.com \
--to=nelson.paul.david@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jb@jeremybryant.net \
--cc=philipk@posteo.net \
--cc=rms@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.
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).