From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: TEC <tecosaur@gmail.com>
Cc: Bastien <bzg@gnu.org>, "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: (Feature Request) have org-edit-special work inside non-environment LaTeX blocks, i.e. \( \) and \[ \]
Date: Mon, 25 May 2020 12:09:15 +0200 [thread overview]
Message-ID: <87blmcba2c.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87y2pgfieh.fsf@gmail.com> (TEC's message of "Mon, 25 May 2020 17:55:35 +0800")
TEC <tecosaur@gmail.com> writes:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> LaTeX fragments should not break paragraphs, or tables. So you need to
>> prevent inserting blank lines, or even newlines characters in the case
>> of tables.
>
> I don’t think we need to worry about newlines,
We need to.
| some | table |
| LaTeX | $1 + 1$ |
Here, when editing "$1 + 1$", you certainly don't want to insert
a newline character.
Likewise
Some $1+1$ paragraph
is very different from
Some $1+
1$ paragraph
> Another query from me, with something like a blank line, why is a user-error
> raised? Surely just strip blank lines from the buffer? I can’t think of any
> situation where this would be undesirable.
Some blank lines are meaningful in Org, so removing them could change
the structure of the input. I wasn't sure it was a good idea to do this
on user's behalf.
The code should also prevent footnote definitions to contain two
consecutive blank lines. But that's another story.
next prev parent reply other threads:[~2020-05-25 10:11 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 1:31 (Feature Request) have org-edit-special work inside non-environment LaTeX blocks, i.e. \( \) and \[ \] Timothy
2020-05-19 7:47 ` Nicolas Goaziou
2020-05-19 9:27 ` Timothy
2020-05-19 9:39 ` Nicolas Goaziou
2020-05-19 9:45 ` Timothy
2020-05-19 13:27 ` Nicolas Goaziou
2020-05-19 13:32 ` Timothy
2020-05-19 14:09 ` Nicolas Goaziou
2020-05-19 14:12 ` Timothy
2020-05-19 14:28 ` Nicolas Goaziou
2020-05-19 14:33 ` Timothy
2020-05-23 9:10 ` Bastien
2020-05-23 9:20 ` tecosaur
2020-05-23 9:34 ` Bastien
2020-05-24 15:07 ` TEC
2020-05-24 15:38 ` TEC
2020-05-24 15:43 ` Timothy
2020-05-24 19:33 ` Nicolas Goaziou
2020-05-25 1:33 ` TEC
2020-05-25 7:11 ` Nicolas Goaziou
2020-05-25 9:28 ` TEC
2020-05-25 9:41 ` Nicolas Goaziou
2020-05-25 9:42 ` TEC
2020-05-25 9:55 ` TEC
2020-05-25 10:09 ` Nicolas Goaziou [this message]
2020-05-25 10:09 ` TEC
2020-05-25 10:23 ` Nicolas Goaziou
2020-05-25 10:24 ` TEC
2020-05-25 10:32 ` Nicolas Goaziou
2020-05-25 10:33 ` TEC
2020-05-25 10:05 ` TEC
2020-05-25 10:20 ` Nicolas Goaziou
2020-05-25 10:21 ` TEC
2020-05-25 11:27 ` Nicolas Goaziou
2020-05-25 13:22 ` Timothy
2020-05-25 14:08 ` TEC
2020-05-26 7:56 ` Nicolas Goaziou
2020-05-26 8:39 ` Timothy
2020-05-26 9:11 ` Nicolas Goaziou
2020-05-26 9:23 ` TEC
2020-05-26 13:56 ` TEC
2020-05-26 21:13 ` Nicolas Goaziou
2020-05-26 17:01 ` John Kitchin
2020-05-25 18:58 ` Nicolas Goaziou
2020-05-26 4:48 ` TEC
2020-05-25 10:11 ` Nicolas Goaziou
2020-05-25 10:17 ` TEC
-- strict thread matches above, loose matches on Subject: below --
2020-05-18 6:44 Timothy
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blmcba2c.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).