Error while copying code snippets from the README into shell about lorri HOT 12 CLOSED

I renamed the issue accordingly. ;)

Joke aside, that’s a valuable lesson to learn for me as a technical writer. Make stuff copy'n'past-able without changing the execution environment midway through.

from lorri.

you're definitely right @Profpatsch. Instructions were clear but the receiver was broken. Look at it as if you're dealing with very bad input sensor on the other side (me).

from lorri.

Are you running this in your normal shell?

lorri direnv outputs code that is intended to be put in .envrc, which direnv calls with functions like watch_file set.

What part of the tutorial makes you think it has to be run from your shell? We might have to clarify.

from lorri.

Sorry for the dumb issue and late reply. I was just too busy and was not careful enough.

from lorri.

You’re not the first to run into this, we need to print a warning.

from lorri.

that would be definitely good UX improvement assuming people who can't read manual (like me) can at least read the terminal output :D

from lorri.

It’s easy to get wrong and if one does the why is pretty hard to debug (especially if one doesn’t know how direnv works)

from lorri.

This bit in here let me to the same mistake.

Create a file named .envrc in your project's root with the contents:

eval "$(lorri direnv)"

Then, run lorri watch. The first time you run lorri watch on a project, wait for it to print Completed before continuing. Leave this terminal open.

from lorri.

What exactly lead you to the mistake?

from lorri.

@freddie-freeloader do you think this makes it clearer?

from lorri.

@Profpatsch I think seeing a line beginning with eval makes some brains go like "this is surely a shell".

I can imagine two possible (cheap) improvements.

1. Adding comment to the source block repeating the important part (as in my PR)
2. Instead of showing file content add shell command to create the file itself:

echo 'eval "$(lorri direnv)"' > .envrc

from lorri.

@Profpatsch I think seeing a line beginning with eval makes some brains go like "this is surely a shell".

I can imagine two possible (cheap) improvements.

1. Adding comment to the source block repeating the important part (as in my PR)

2. Instead of showing file content add shell command to create the file itself:

echo 'eval "$(lorri direnv)"' > .envrc

This is exactly what I would propose. ☺️

In my case the problem was that I copied the code blindly and executed it. I know, this is not smart, but I think this is a common mistake. 🙂

from lorri.