From: Edgar Lux <edgarlux@mailfence.com>
To: Emacs Orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Warning when creating preview
Date: Sat, 26 Aug 2023 17:39:48 +0200 (CEST) [thread overview]
Message-ID: <862042460.651091.1693064387981@ichabod.co-bxl> (raw)
In-Reply-To: <877cpm8a4m.fsf@localhost>
On Aug 23, 2023 at 9:56 AM, Ihor Radchenko <yantar92@posteo.net>
> 1. Save the equation to file /tmp/bug.org
> 2. Save your `setq' snippet to /tmp/bug.el
> 3. cd /path/to/org/repo
> 4. make repro REPRO_ARGS="-l /tmp/bug.el /tmp/bug.org"
> 5. Move point to "t = 0" line
> 6. C-c C-x C-l (2x)
> 7. The preview appears and then disappears, as expected.
>
> May you please repeat my steps and let me know if your are seeing the warning?
1. emacs (loading my full configuration)
2. find the file of my previous bug report: t.org
3. dedent and mark the equation (without the =_quote=)
4. M-x copy-to-buffer RET bug.org RET
5. Save to /tmp/bug.org
6. add :tangle /tmp/bug.el to the emacs-lisp source block
7. C-u C-c C-v t to tangle (save) the file
8. find /path/to/org/repo (with dired)
9. M-& make repro REPRO_ARGS="-l /tmp/bug.el /tmp/bug.org"
10. M-x switch-to-buffer RET /tmp/bug.org RET
11. Move point to "t = 0" line
12. C-c C-x C-l (2x)
I see the warning.
After step 10, I removed the files in ltximg, ran =emacs -q=, find file /tmp/bug.org, step 11 & 12, and I see no warning. There must be something else in my configuration which triggers the error (if you want to follow the rabbit, let me know).
In this case, the warning was:
#+begin_example
Warning (org-element-cache): org-element--cache: Org parser error in bug.org::22. Resetting.
The error was: (error "Invalid search bound (wrong side of point)")
Backtrace:
" backtrace-to-string(nil)
org-element-at-point()
org-element-context()
org-latex-preview(nil)
funcall-interactively(org-latex-preview nil)
call-interactively(org-latex-preview nil nil)
command-execute(org-latex-preview)
"
Please report this to Org mode mailing list (M-x org-submit-bug-report). Disable showing Disable logging
#+end_example
--
Sent with https://mailfence.com
Secure and private email
next prev parent reply other threads:[~2023-08-26 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 13:20 [BUG] Warning when creating preview Edgar Lux
2023-08-18 16:04 ` Ihor Radchenko
2023-08-19 0:37 ` Edgar Lux
2023-08-22 16:29 ` Edgar Lux
2023-08-23 7:56 ` Ihor Radchenko
2023-08-26 15:39 ` Edgar Lux [this message]
2023-08-26 16:28 ` Ihor Radchenko
2023-08-27 11:13 ` Edgar Lux
2023-08-27 11:28 ` Ihor Radchenko
2023-08-27 17:26 ` Edgar Lux
2023-08-27 17:29 ` Ihor Radchenko
[not found] ` <1064170796.778390.1693179229311@ichabod.co-bxl>
2023-08-28 9:00 ` Ihor Radchenko
2023-09-28 14:21 ` Edgar Lux
2023-09-28 14:53 ` Edgar Lux
2023-10-02 10:14 ` Edgar Lux
2023-10-05 14:31 ` Ihor Radchenko
[not found] ` <1472786502.941.1696851881089@ichabod.co-bxl>
2023-10-09 13:59 ` Edgar Lux
2023-10-09 14:17 ` Edgar Lux
2023-10-11 9:11 ` Ihor Radchenko
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=862042460.651091.1693064387981@ichabod.co-bxl \
--to=edgarlux@mailfence.com \
--cc=emacs-orgmode@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/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).