all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Vikas Rawal <vikasrawal@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-fold documentation
Date: Sat, 07 May 2022 12:15:54 +0800	[thread overview]
Message-ID: <87leveyo3p.fsf@localhost> (raw)
In-Reply-To: <CALtzAB3mWy2h82ep3o5_qm5yEOaR9KqjuGwi+eRWnyk-5rhR4g@mail.gmail.com>

Vikas Rawal <vikasrawal@gmail.com> writes:

> After upgrading to 9.5.3, I am getting warnings such as this, which I
> suspect are due to org-fold.et.
>
> Warning (comp): org-fold.el:834:27: Warning: Unused lexical variable
> `org-hide-macro-markers' Disable showing Disable logging
> Warning (comp): org.el:76:30: Warning: Package cl is deprecated Disable
> showing Disable logging
> Warning (comp): ox.el:79:1: Warning: the function ‘org-back-to-heading’
> might not be defined at runtime. Disable showing Disable logging
> Warning (comp): ox.el:79:1: Warning: the function
> ‘org-next-visible-heading’ might not be defined at runtime. Disable showing
> Disable logging
> Warning (comp): ox.el:79:1: Warning: the function ‘org-at-heading-p’ might
> not be defined at runtime. Disable showing Disable logging
>
> Is org-fold.el documented already? Any pointers to what might be causing
> the above?

These are native-comp warnings. They are not uncommon when
native-compiling Org (not only org-fold.el) and generally harmless.
If you are sufficiently annoyed with them, most of these warnings can be
"fixed" by declaring the missing functions. The functions are available
at runtime, but not during native-compilation.

Best,
Ihor


  reply	other threads:[~2022-05-07  4:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 18:03 org-fold documentation Vikas Rawal
2022-05-07  4:15 ` Ihor Radchenko [this message]
2022-05-07  4:26   ` Samuel Wales
2022-05-07  4:41     ` Ihor Radchenko
2022-05-07  4:45       ` Samuel Wales
2022-05-07  5:17         ` Ihor Radchenko
2022-05-07  7:34   ` Max Nikulin
2022-05-08  7:18     ` Ihor Radchenko
2022-05-07  9:25   ` Vikas Rawal
2022-05-07 10:22     ` Eric S Fraga

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87leveyo3p.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=vikasrawal@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.