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: Tue, 26 May 2020 09:56:43 +0200 [thread overview]
Message-ID: <87wo4z6sec.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87blmcp0m2.fsf@gmail.com> (TEC's message of "Mon, 25 May 2020 22:08:19 +0800")
Hello,
TEC <tecosaur@gmail.com> writes:
> ---
> lisp/org-src.el | 45 +++++++++++++++++++++++++++++++++++++++++++++
> lisp/org.el | 1 +
> 2 files changed, 46 insertions(+)
Thank you. It looks fine, I will only be nitpicking.
> +(defun org-edit-latex-fragment ()
> + "Edit LaTeX fragment at point."
> + (interactive)
> + (let* ((context (org-element-context))
> + (_ (unless (and (eq (org-element-type context) 'latex-fragment)
> + (org-src--on-datum-p context))
> + (user-error "Not on a LaTeX fragment")))
This is a fancy way to use a let-binding. I suggest to mimic what is
done elsewhere, i.e., first bind `context', then check if we're at
a LaTeX fragment, then bind the rest.
> + ;; Grab the LaTeX fragment for propertization
Missing full stop at the end of the comment.
> + (contents (buffer-substring-no-properties
> + (org-element-property :begin context)
> + (- (org-element-property :end context)
> + (org-element-property :post-blank context))))
> + (delim-length (if (string-match "\\$[^$]" (substring contents 0 2))
Use
(string-match "\\`\\$[^$]" contents)
instead.
or, arguably better,
(string-match (rx (seq string-start "$" (not (any "$"))))
contents)
> + 1 2)))
> + ;; make the LaTeX deliminators read-only
Missing initial capital and final full stop.
> + (add-text-properties
> + 0 delim-length
> + '(read-only "Cannot edit LaTeX deliminator" front-sticky t rear-nonsticky t)
> + contents)
> + (add-text-properties
> + (- (length contents) delim-length)
> + (length contents)
> + '(read-only "Cannot edit LaTeX deliminator" front-sticky nil rear-nonsticky nil)
> + contents)
You could factor out (length contents) so it is only called once.
> + (org-src--edit-element
> + context
> + (org-src--construct-edit-buffer-name (buffer-name) "LaTeX fragment")
> + (org-src-get-lang-mode "latex")
> + (lambda ()
> + ;; Blank lines break things, replace with a single newline
See above.
> + (while (re-search-forward "\n[ \t]*\n" nil t) (replace-match "\n"))
> + ;; If within a table a newline would disrupt the structure,
This comment is truncated.
> + (goto-char (point-min))
> + (when (org-element-lineage context '(table-cell))
> + (while (search-forward "\n" nil t) (replace-match " ")))
> + )
Don't leave parenthesis alone.
Also, make sure your indentation is right, e.g., using M-q on the
definition.
You also need to add a proper commit message and use `git format-patch',
and an entry in ORG-NEWS (probably in Miscellaneous part).
Bonus points if you can add some tests in
"testing/lisp/test-org-src.el".
Could you remind me if you signed the FSF papers already?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2020-05-26 7:57 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
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 [this message]
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=87wo4z6sec.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).