Error message googling suggestion

[straussed]

In Before we start > Dealing with error messages:

An additional suggestion in these section could be to remind users to remove any object names specific to their code when googling.

If you can’t fix an error yourself, start by googling it. Some error messages are too generic to diagnose a problem (e.g. “subscript out of bounds”). In that case it might help to include the name of the function or package you’re using in your query. >>>>Also note that its best to remove your variable names from the error message when googling to more easily find help online.<<<<

[smflynn121]

^^^ Yes I think this would be super helpful! Half the battle when learning to code is learning how to google. It would be nice if we could bake an example of googling an error into this lesson.

[tobyhodges]

Thanks both for contributing to this discussion. The lesson underwent a major update and reorganisation when https://github.com/datacarpentry/R-ecology-lesson/pull/887 was merged. Although this issue relates to content in a version of the lesson before that update took place, I think the content would benefit from more information about how and where to get help, so I will leave it open.