From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Run `fill-paragraph' on all the paragraphs in the currently opened LaTeX document.
Date: Mon, 18 Oct 2021 16:56:57 +0800 [thread overview]
Message-ID: <CAGP6POJzTV2t1g+LCPa_0j_zWNMgJisZGhSg+GRuw6-=Cyb1Kw@mail.gmail.com> (raw)
In-Reply-To: <CAP_d_8Whri3Qg_dV0Hc3=E_WsVaPn9=9q7hTDKwNdRazYz04Gg@mail.gmail.com>
On Mon, Oct 18, 2021 at 12:43 PM Yuri Khan <yuri.v.khan@gmail.com> wrote:
>
> On Mon, 18 Oct 2021 at 07:22, Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
>
> > > Why do you even want that?
> >
> > I use SyncTeX to do the forward and backward search, which is based on
> > linefeed separated line to locate the position in the source LaTeX
> > document. If a paragraph is arranged in one line, the backward search
> > will always jump to a very inaccurate location.
>
> I’m not suggesting
> keeping each paragraph as a single long line.
> What I’m suggesting is
> dividing paragraphs into sentences
> and sentences into phrases
> while keeping each line reasonably short
> but without trying to cram as much as possible into each line.
>
> (This mail uses semantic line breaks,
> as a demonstration.)
So the idea suggested by Emanuel Berg and you now can be combined into
the following:
Iterate the whole buffer line-by-line with a semantic line as the unit
block, and check
each line if it starts with '\' or not, e.g. with (looking-at
"\\\\"). When you find one "beg", start looking for where it
ends, and when you find that push (beg end) onto a list.
Then loop through the list and do (fill-region beg end) for each
list pair item ...
HZ
next prev parent reply other threads:[~2021-10-18 8:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 5:30 Run `fill-paragraph' on all the paragraphs in the currently opened LaTeX document Hongyi Zhao
2021-10-17 6:23 ` Eli Zaretskii
2021-10-17 7:23 ` Hongyi Zhao
2021-10-17 10:25 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-17 12:28 ` Hongyi Zhao
2021-10-17 12:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-17 15:30 ` Yuri Khan
2021-10-17 15:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-17 15:45 ` Yuri Khan
2021-10-17 17:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-18 0:22 ` Hongyi Zhao
2021-10-18 4:42 ` Yuri Khan
2021-10-18 4:50 ` Hongyi Zhao
2021-10-18 14:00 ` Eric S Fraga
2021-10-19 1:21 ` Hongyi Zhao
2021-10-18 8:56 ` Hongyi Zhao [this message]
2021-10-18 16:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-18 16:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-18 16:17 ` Emanuel Berg via Users list for the GNU Emacs text editor
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='CAGP6POJzTV2t1g+LCPa_0j_zWNMgJisZGhSg+GRuw6-=Cyb1Kw@mail.gmail.com' \
--to=hongyi.zhao@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=yuri.v.khan@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.
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).