> Ikumi Keita writes:
> Hi Paul and all,
> Paul Nelson writes:
>> Looks good to me (I prefer it over my original suggestion). Thanks!
> Thanks. If there's no objection, I'll polish my proposal and install it.
> Any comments?
Done. I'll close this bug.
Regards,
Ikumi Keita
Hi Paul and all,
> Paul Nelson writes:
> Looks good to me (I prefer it over my original suggestion). Thanks!
Thanks. If there's no objection, I'll polish my proposal and install it.
Any comments?
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
Hi Uwe,
Paul's inference is right. I made the patch anew, it's intended for the
clean master branch.
> Uwe Brauer writes:
>> Well, I run make clean, reset, pulled again applied the patch to commit
>> 2151c3831fcff9
>> Run make,
>> make install
>> Tried again,
>> But I do see this
> Hi Paul
> Well, I run make clean, reset, pulled again applied the patch to commit
> 2151c3831fcff9
> Run make,
> make install
> Tried again,
> But I do see this behavior, I am now puzzled, and have to investigate
> that further.
It seems also to happen without the patch, uff, right
>>> "PN" == Paul Nelson writes:
Hi Paul
> Hi Uwe,
> I don't see the behavior you describe; on my end, filling does not change
> the latex you provided. I've tried it with LaTeX-fill-environment and
> indent-region.
> Also, with this patch, the setting LaTeX-indent-always-align-end-with-begin
>
Hi Uwe,
I don't see the behavior you describe; on my end, filling does not change
the latex you provided. I've tried it with LaTeX-fill-environment and
indent-region.
Also, with this patch, the setting LaTeX-indent-always-align-end-with-begin
no longer seems relevant. Maybe you tried applying
> Hi Paul and Uwe,
Hi Keita
> I've been gradually inclined to the attached approach. Namely, align "&"
> as well as \end{foo} relative to beg-col, not beg-pos. In this way, the
> above examples turn into
> --
>
Looks good to me (I prefer it over my original suggestion). Thanks!
On Sat, Sep 9, 2023 at 8:52 AM Ikumi Keita wrote:
> Hi Paul and Uwe,
>
> > Paul Nelson writes:
> > As for the "always-align t" case, there are still some natural "broken"
> > examples, as you know:
> > #+begin_src latex
>
Hi Paul and Uwe,
> Paul Nelson writes:
> As for the "always-align t" case, there are still some natural "broken"
> examples, as you know:
> #+begin_src latex
> \begin{equation*}
> g = \begin{pmatrix}
> a & b \\
> c & d \\
> \end{pmatrix},
> \quad
> h =
Hi Ikumi,
Thanks for sharing your tentative patch.
The "always-align nil" behavior looks good to me.
As for the "always-align t" case, there are still some natural "broken"
examples, as you know:
#+begin_src latex
\begin{equation*}
g = \begin{pmatrix}
a & b \\
c & d \\
Hi Uwe and Paul, thank you for your discussion.
> Paul Nelson writes:
> There's no important difference here between indent-region and the
> LaTeX fill commands -- unless I'm mistakaen, they all ultimately call
> LaTeX-indent-line, one line at a time.
That's right. The doc strings of
Hi Uwe,
> Just a short comment, why don't to combine both package to one single
> repository, since czm-tex-edit.el requires dynexp.el?
> That would make it a bit easier to install.
>
>
> I will try to test them in the coming days.
>
Thanks for your feedback on this. I only recently got around
>>> "PN" == Paul Nelson writes:
Hi Paul
> Hi Ikumi and Uwe,
> Thanks to both of you for your feedback.
Thanks for your proposal
> I agree that it's better to have begin/end line up when all else is
> equal, but with the current state of AUCTeX (since this bug was
> introduced), it is a severe
Hi Uwe,
Thanks for your response. First I'll respond to the minor points:
> You say indent-region
>
> I am referring here to the LaTeX-filling-functions, such as
> LaTeX-fill-environment, LaTeX-fill-section etc
There's no important difference here between indent-region and the
LaTeX fill
>>> "PN" == Paul Nelson writes:
Hi Paul
> Hi Uwe,
> Thanks for your response. First I'll respond to the minor points:
>> You say indent-region
>>
>> I am referring here to the LaTeX-filling-functions, such as
>> LaTeX-fill-environment, LaTeX-fill-section etc
> There's no important
>>> "PN" == Paul Nelson writes:
Hi Paul
> Hi Uwe,
> Thanks for your response. First I'll respond to the minor points:
>> You say indent-region
>>
>> I am referring here to the LaTeX-filling-functions, such as
>> LaTeX-fill-environment, LaTeX-fill-section etc
> There's no important
Hi Ikumi and Uwe,
Thanks to both of you for your feedback.
I agree that it's better to have begin/end line up when all else is
equal, but with the current state of AUCTeX (since this bug was
introduced), it is a severe user error to put \begin{array} on a line
following non-whitespace. The
>>> "IK" == Ikumi Keita writes:
> Hi Paul,
>> Paul Nelson writes:
>> A practical workaround for the user is to make sure that \begin{} is
>> always the first non-whitespace on its line (and to enforce that
>> requirement on coauthors via ~(defun fix-tex-buffer ...)~), but that
>> seems
Hi Paul,
> Paul Nelson writes:
> A practical workaround for the user is to make sure that \begin{} is
> always the first non-whitespace on its line (and to enforce that
> requirement on coauthors via ~(defun fix-tex-buffer ...)~), but that
> seems suboptimal.
> The following seems to
Take a LaTeX buffer with a nested environment where the inner \begin{}
follows some non-whitespace:
#+begin_src latex
\begin{equation*}
g=\begin{pmatrix}
a & b \\
c & d \\
\end{pmatrix}
\end{equation*}
#+end_src
After =M-x mark-whole-buffer= and =M-x indent-region=, the outer
\end{}
20 matches
Mail list logo
