Skip to content

Fix compilation warnings #494 #521

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

Merged
merged 1 commit into from
Jul 9, 2019

Conversation

rpkarlsson
Copy link
Contributor

@rpkarlsson rpkarlsson commented Apr 9, 2019

Fix compilation warnings as stated in #494.


  • The commits are consistent with our contribution guidelines.
  • You've added tests (if possible) to cover your change(s). Bugfix, indentation, and font-lock tests are extremely important!
  • You've run M-x checkdoc and fixed any warnings in the code you've written.
  • You've updated the changelog (if adding/changing user-visible functionality).
  • You've updated the readme (if adding/changing user-visible functionality).

(beginning-of-defun)
(setq clojure-comment-start (point))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you change this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clojure-comment-start was generating a warning and as far as I can tell It is unused? It may be that I'm missunderstanding something?

clojure-mode.el:2023:1:Warning: Unused lexical variable
    ‘clojure-comment-start’

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I think that's supposed to be a buffer local variable. Let me take a closer look at the code - we might have made some real mistake. :-)

@bbatsov bbatsov merged commit 01d168a into clojure-emacs:master Jul 9, 2019
@bbatsov
Copy link
Member

bbatsov commented Jul 9, 2019

Sorry about the long radio silence! After a closer inspection of the changes I feel they are all safe. Thanks!

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

Successfully merging this pull request may close these issues.

2 participants