faq-usage typo 'preparse' should be 'preparser'

[DrXyzzy]

In src/doc/en/faq/faq-usage.rst around line 362, text says

You can also disable the preprocessor in your code via
 ``preparse(False)``.

This should read

You can also disable the preprocessor in your code via
 ``preparser(False)``.

Example: try the following in sage command line session. It fails with an exception.

num = 123
num.bit_length()

But this succeeds and produces output:

preparser(False)
num = 123
num.bit_length()

Component: documentation

Keywords: faq-usage faq preparser preparse

Author: Frédéric Chapoton

Branch/Commit: 72c48d1

Reviewer: Paul Masson

Issue created by migration from https://trac.sagemath.org/ticket/21241

[fchapoton]

comment:1

done, please review.

---

New commits:

7074a0c

trac 21241 typo in faq (preparser)

[fchapoton]

Author: Frédéric Chapoton

[fchapoton]

Commit: 7074a0c

[fchapoton]

Branch: public/21241

[paulmasson]

Reviewer: Paul Masson

[paulmasson]

comment:2

In the next sentence please change "can may" to "can" and ". Or switching" to " or switch" for correct grammar.

There are two other instances of "preparse(" in this file on L286 and L333 which are correct. Please correct those as well.

[paulmasson]

comment:3

Also, preparse is no longer located in sage.all as stated on L301. It's now in sage.repl.all. Shouldn't that also be corrected?

[paulmasson]

comment:4

Please also let me know for future reference whether it's simpler for me to make changes like this on a public branch and then have you review them. Happy to do so if that's a better work flow.

[DrXyzzy]

comment:5

References to "preparse(): at L286 and L333 are correct. There are two similarly-named functions. First parameter to preparse() is a line of code. Parameter to preparser() is a boolean.

[paulmasson]

comment:6

Replying to @DrXyzzy:

References to "preparse(): at L286 and L333 are correct. There are two similarly-named functions. First parameter to preparse() is a line of code. Parameter to preparser() is a boolean.

Right you are. Sorry for the confusion. Will update previous comment.

[sagetrac-git]

Changed commit from 7074a0c to 72c48d1

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

72c48d1

trac 21241 details

[fchapoton]

comment:8

done. The import of line 301 still works, so does not need to be changed.

[vbraun]

Changed branch from public/21241 to 72c48d1