From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56335@debbugs.gnu.org, manuel@ledu-giraud.fr
Subject: bug#56335: 29.0.50; [PATCH] Add more breakpoint chars support to longlines-mode
Date: Sat, 02 Jul 2022 17:39:34 +0200 [thread overview]
Message-ID: <87fsjjzfpl.fsf@gnus.org> (raw)
In-Reply-To: <83pminbrak.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 02 Jul 2022 16:03:15 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> So it was obsoleted because we had visual-line-mode instead, I guess? I
>> guess they have similar use cases, but longlines-mode has the advantage
>> that it's also a hack around the performance issues.
>
> Yes.
It seems like everybody both here and in the other thread agreed that we
should unobsolete longlines.el, so I've now done so in Emacs 29. I've
also applied Manuel's patch to longlines.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-07-02 15:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 10:35 bug#56335: 29.0.50; [PATCH] Add more breakpoint chars support to longlines-mode Manuel Giraud
2022-07-01 13:33 ` Manuel Giraud
2022-07-02 12:14 ` Lars Ingebrigtsen
2022-07-02 12:23 ` Visuwesh
2022-07-02 12:46 ` Phil Sainty
2022-07-02 12:39 ` Eli Zaretskii
2022-07-02 12:44 ` Lars Ingebrigtsen
2022-07-02 13:03 ` Eli Zaretskii
2022-07-02 15:39 ` Lars Ingebrigtsen [this message]
2022-07-02 21:19 ` Manuel Giraud
2022-07-03 5:14 ` Eli Zaretskii
2022-07-04 8:06 ` Manuel Giraud
2022-07-04 11:18 ` Eli Zaretskii
2022-07-05 13:07 ` Manuel Giraud
2022-07-05 16:32 ` Lars Ingebrigtsen
2022-07-06 7:43 ` Manuel Giraud
2022-07-06 11:18 ` Lars Ingebrigtsen
2022-07-06 10:18 ` Manuel Giraud
2022-07-06 11:20 ` Lars Ingebrigtsen
2022-07-06 18:49 ` Juri Linkov
2022-07-06 20:47 ` Manuel Giraud
2022-07-08 3:32 ` Richard Stallman
2022-07-08 7:14 ` Manuel Giraud
2022-07-08 7:22 ` Eli Zaretskii
2022-07-10 8:58 ` Manuel Giraud
2022-07-10 13:02 ` Lars Ingebrigtsen
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=87fsjjzfpl.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=56335@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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.