Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc] on-lexer-valid says "Augments <method not found>" #185

Closed
sorawee opened this issue May 9, 2020 · 11 comments
Closed

[doc] on-lexer-valid says "Augments <method not found>" #185

sorawee opened this issue May 9, 2020 · 11 comments

Comments

@sorawee
Copy link
Contributor

sorawee commented May 9, 2020

I think the title is clear enough. Here's a link to the doc: https://docs.racket-lang.org/framework/Color.html?q=classify-position#%28meth._%28%28%28lib._framework%2Fmain..rkt%29._color~3atext~3c~25~3e%29._on-lexer-valid%29%29

@spdegabrielle
Copy link
Sponsor Member

spdegabrielle commented May 13, 2020

is this caused by the [valid? boolean?] parameter in @defmethod in line 373?

@defmethod[#:mode augment (on-lexer-valid [valid? boolean?]) any]{

Should it be ?

@defmethod[#:mode augment (on-lexer-valid [valid boolean?]) any]{

https://github.com/racket/gui/blob/master/gui-doc/scribblings/framework/color.scrbl#L373

  @defmethod[#:mode augment (on-lexer-valid [valid? boolean?]) any]{
    This method is an observer for when the lexer is working.  It is called
    when the lexer's state changes from valid to invalid (and back).  The
    @racket[valid?] argument indicates if the lexer has finished running over
    the editor (or not).

    The default method just returns @racket[(void?)].
  }

renders as

image

@sorawee
Copy link
Contributor Author

sorawee commented May 13, 2020

Pretty sure it should be #:mode pubment instead.

@sorawee
Copy link
Contributor Author

sorawee commented May 13, 2020

Here's a list of "method not found" problems in other places:

@spdegabrielle
Copy link
Sponsor Member

spdegabrielle commented May 13, 2020

Pretty sure it should be #:mode pubment instead.

Better to test it if you are unsure?

Steps:

  1. raco pkg update --clone <PKG>
  2. fork the racket/ repo on GitHub
  3. add your fork as a remote: git remote add fork https://github.com/<YOUR-USERNAME>/<PKG>
  4. make a new branch, git checkout -b my-edits
  5. do edits
  6. rebuild documentation using scribble colour.scrbl or raco pkg update gui
  7. commit changes, git commit
  8. push to the fork, git push fork my-edits
  9. create a pull request on GitHub

https://blog.racket-lang.org/2017/09/tutorial-contributing-to-racket.html

sorawee added a commit to sorawee/drracket that referenced this issue May 16, 2020
Remove `#:mode override` for methods that are defined with `define/public`.
Change `augment` to `pubment` for `after-many-evals`
@sorawee
Copy link
Contributor Author

sorawee commented May 16, 2020

The above two commits/PRs should fix everything except the four issues on https://docs.racket-lang.org/tools/drracket_unit.html, which I still couldn't figure out what went wrong.

@sorawee
Copy link
Contributor Author

sorawee commented May 18, 2020

@rfindler could you reopen the issue? There're still issues on https://docs.racket-lang.org/tools/drracket_unit.html and the pending PR for racket/gui. Thanks!

@rfindler
Copy link
Member

Oh, sorry! I was just wanting to get your fixes.

And thank you, too!

@rfindler rfindler reopened this May 18, 2020
@rfindler
Copy link
Member

Sorry-- I pushed a commit that closed this issue but it isn't done.

@rfindler
Copy link
Member

Forgot to mention it in the commit, but this fixes two more of them: racket/drracket@15e3a9a

rfindler added a commit to racket/drracket that referenced this issue Jun 14, 2020
so they link to the super methods properly

(there is no export of drracket:unit:definitions-text% so that can't
work as a conduit to track the supers)

related to racket/gui#185
@rfindler
Copy link
Member

I think those two commits fix all the problems in drracket_unit.html.

samth pushed a commit to racket/typed-racket that referenced this issue Jun 23, 2020
* Fix <method not found> and in-fxvector in for form

- Correct the method names that were "not found".
  See also racket/gui#185
- Add unsafe-fxvector-length and unsafe-fxvector-ref
  so that in-fxvector in the for form works correctly.
  Add corresponding tests.
  Thanks to James Cooper who reported the issue in Slack.
bennn pushed a commit to bennn/typed-racket that referenced this issue Jul 3, 2020
* Fix <method not found> and in-fxvector in for form

- Correct the method names that were "not found".
  See also racket/gui#185
- Add unsafe-fxvector-length and unsafe-fxvector-ref
  so that in-fxvector in the for form works correctly.
  Add corresponding tests.
  Thanks to James Cooper who reported the issue in Slack.
@sorawee
Copy link
Contributor Author

sorawee commented Aug 4, 2020

All fixed!

@sorawee sorawee closed this as completed Aug 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants