From: Ihor Radchenko <yantar92@posteo.net>
To: Edgar Lux <edgarlux@mailfence.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Warning when creating preview
Date: Mon, 28 Aug 2023 09:00:08 +0000 [thread overview]
Message-ID: <874jkj4k4n.fsf@localhost> (raw)
In-Reply-To: <1064170796.778390.1693179229311@ichabod.co-bxl>
Edgar Lux <edgarlux@mailfence.com> writes:
> On Aug 27, 2023 at 7:29 PM, Ihor Radchenko <yantar92@posteo.net> wrote:
>> I recommend https://github.com/Malabarba/elisp-bug-hunter to narrow down
>> which part of the config is the culprit.
>
> We have a winner:
>
> ;; Bug hunter error ---
> ;; https://github.com/nicolaisingh/saveplace-pdf-view.git
> (if (file-directory-p "/path/to/packages/saveplace-pdf-view")
> (progn
> (push "/path/to/packages/saveplace-pdf-view" load-path)
> (require 'saveplace-pdf-view)
> (save-place-mode 1)))
> ;; --- end bug hunter error
>
> The error is gone when I comment this out. I know it's not magic, but OMP! (oh, my penguin).
Even with this, I am unable to reproduce.
So, it may only be a part of the problem. Some part of the configuration
before this snippet may be the extra required trigger (in combination
with saveplace-pdf-view).
What happens if you put the save-place-pdf-view snippet near the
beginning of your config and try to bisect again?
> The authors of the package are in Bcc. I like the functionality that it provides and will just ignore the message. If you need more info, let me know.
I do not see any extra BCC.
Also, do note that parser errors might lead to Org file corruption. There
is a reason why we throw this kind of warning into users.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-08-28 9:01 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
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 [this message]
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=874jkj4k4n.fsf@localhost \
--to=yantar92@posteo.net \
--cc=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).