From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: larsi@gnus.org, 56335@debbugs.gnu.org, rms@gnu.org, juri@linkov.net
Subject: bug#56335: 29.0.50; [PATCH] Add more breakpoint chars support to longlines-mode
Date: Fri, 08 Jul 2022 10:22:05 +0300 [thread overview]
Message-ID: <83h73s3w82.fsf@gnu.org> (raw)
In-Reply-To: <87let45b5g.fsf@elite.giraud> (message from Manuel Giraud on Fri, 08 Jul 2022 09:14:19 +0200)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: juri@linkov.net, larsi@gnus.org, 56335@debbugs.gnu.org, eliz@gnu.org
> Date: Fri, 08 Jul 2022 09:14:19 +0200
>
> "breakpoint" was already used into longlines' code... But now we have a
> user option that contains "breakpoint". I propose to change this option
> from 'longlines-breakpoint-chars' to 'longlines-separators'. What do
> you think?
I suggest 'longlines-break-chars'.
next prev parent reply other threads:[~2022-07-08 7:22 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
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 [this message]
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
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=83h73s3w82.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56335@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=manuel@ledu-giraud.fr \
--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).