# Why is mark\_as\_advanced() considered a scripting command

**URL:** https://discourse.cmake.org/t/why-is-mark-as-advanced-considered-a-scripting-command/2387
**Category:** Development
**Created:** [December 17, 2020, 12:07pm UTC](https://discourse.cmake.org/t/why-is-mark-as-advanced-considered-a-scripting-command/2387 "2020-12-17T12:07:22Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![craig.scott](https://discourse.cmake.org/user_avatar/discourse.cmake.org/craig.scott/32/20_2.png) [@craig.scott](https://discourse.cmake.org/u/craig.scott)
#### Post date: [December 17, 2020, 12:07pm UTC](https://discourse.cmake.org/t/why-is-mark-as-advanced-considered-a-scripting-command/2387/1 "2020-12-17T12:07:22Z")

</div>

I’m wondering why the `mark_as_advanced()` command is considered a scripting command. It’s sole purpose is for marking cache variables as advanced or not, but cache variables only make sense for projects. Does this command have any effect at all in script mode? If not, should its role and documentation be changed to reflect this?

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)
#### Post date: [December 17, 2020, 12:44pm UTC](https://discourse.cmake.org/t/why-is-mark-as-advanced-considered-a-scripting-command/2387/2 "2020-12-17T12:44:16Z")

</div>

See [https://gitlab.kitware.com/cmake/cmake/-/commit/732788d191afca01f19a147b74bfe145ce36b957](https://gitlab.kitware.com/cmake/cmake/-/commit/732788d191afca01f19a147b74bfe145ce36b957).

Basically, `find_package` should work in script mode and if `mark_as_advanced` isn’t scriptable, some modules won’t work.