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

Standard way for usethis to manage part of a file #517

Closed
2 of 3 tasks
hadley opened this issue Nov 29, 2018 · 2 comments
Closed
2 of 3 tasks

Standard way for usethis to manage part of a file #517

hadley opened this issue Nov 29, 2018 · 2 comments

Comments

@hadley
Copy link
Member

@hadley hadley commented Nov 29, 2018

By surrounding lines of code with comments

Use in:

  • use_badge(), replacing home grown solution
  • use_rcpp(), use_tibble() for NAMESPACE management (roxygen2 or otherwise)
  • use_conflicted(), use_reprex() etc for .Rprofile insertion
@jennybc jennybc changed the title Standard way for reprex to manage part of a file Standard way for usethis to manage part of a file Nov 29, 2018
@jennybc
Copy link
Member

@jennybc jennybc commented Nov 29, 2018

If you customize your Emacs preferences via the built-in "Easy Customization" tool (hahaha), you get entries prefaced like this at the end of ~/.emacs:

;; custom-set-variables was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.

hadley added a commit that referenced this issue Nov 29, 2018
And use it to implement use_tidy_release_test_env()

Fixes #496. Part of #517.
@hadley
Copy link
Member Author

@hadley hadley commented Nov 29, 2018

I'm not going to include the .Rprofile stuff right now because it doesn't seem as important, and needs more infrastructure in block_insert() so we can have extra explanatory text around it.

@hadley hadley closed this in 0d3b479 Nov 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants