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

Added Locating Path Settings Instruction #149

Merged
merged 6 commits into from
Jan 16, 2023

Conversation

programorr
Copy link
Contributor

Put in instructions for finding the path for language specifics. Example is for node but should work with others. Hope that is helpful.

Steven

Put in instructions for finding the path for language specifics.  Example is for node but should work with others.  Hope that is helpful.

Steven
README.md Outdated

1. In your terminal, type 'where node'

![CleanShot 2022-10-21 at 19 03 49@2x](https://user-images.githubusercontent.com/11916140/197303215-07ff9460-201d-4c0a-95a3-3b1263713a35.png)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm not sure which one is preferred between the markdown ![]() syntax or <img> (ln 468), but I don't think they should be mixed for style reasons. I'm open to any opinions/discussion you have re: this! :)

Copy link
Collaborator

Choose a reason for hiding this comment

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

i think that descriptive alt text might help w/ images

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah -- sorry. I was just pasting the images in. I can update that!

Copy link
Collaborator

@milan338 milan338 Oct 22, 2022

Choose a reason for hiding this comment

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

I don't think it matters, ![]() is a lot cleaner, using an <img> tag is only really necessary for manually setting image dimensions (some images take up a lot of space in the readme, it might be good to reduce their size).

README.md Outdated

To avoid or resolve errors from an incorrect path.

1. In your terminal, type 'where node'
Copy link
Collaborator

Choose a reason for hiding this comment

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

where works on Windows, but not Linux. Does it work on Mac? Should we include per-OS instructions?

Copy link
Collaborator

Choose a reason for hiding this comment

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

where works on mac as well

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ahhh --- good. I am on a mac. I will update. Anybody know linux command to find path?

Copy link
Collaborator

Choose a reason for hiding this comment

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

on Linux, it is which :)

@chlohal
Copy link
Collaborator

chlohal commented Oct 22, 2022

thanks for your pr!!!! :D

javascriptooo added 2 commits October 21, 2022 21:13
Updated image styling
README.md Outdated

## Locating Path Settings ( ex. JavaScript | Node )

To avoid or resolve errors from an incorrect path.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I just noticed something else: since you have indentation before each line, your changes are all inside a code block. Was that intentional? sorry

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks -- first pull request. Now it looks right. :)

Copy link
Collaborator

Choose a reason for hiding this comment

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

gotcha :) no worries!!! PRs are always welcome, and thank you very much for working with us to make sure it's the best it can be!!

@chlohal
Copy link
Collaborator

chlohal commented Oct 22, 2022

One more thing that I just noticed: the images appear to be the same

image

I don't think that's on purpose, since your first commit had this image for the second one. I'm sorry I didn't notice that!! (when in the code block, they weren't rendering)

Other than that, LGTM!

fixed image
@programorr
Copy link
Contributor Author

One more thing that I just noticed: the images appear to be the same

image

I don't think that's on purpose, since your first commit had this image for the second one. I'm sorry I didn't notice that!! (when in the code block, they weren't rendering)

Other than that, LGTM!

awesome -- anything else I need to do or just wait for it to be approved? :)

@chlohal
Copy link
Collaborator

chlohal commented Oct 23, 2022

Nope! It's all good; just wait for @twibiral to see it :) he might have more notes, but if he does, usually they're relatively easy to complete. Thank you again for your PR!

@twibiral
Copy link
Owner

twibiral commented Nov 5, 2022

Hi, thank you for adding this explanation to the readme, and sorry for the late response.

Where are the images stored? I would prefer to keep a copy of them in the images folder of this repo so they don't suddenly vanish sometime in the future.

@twibiral twibiral changed the base branch from master to develop January 16, 2023 12:18
@twibiral twibiral merged commit bdd97d5 into twibiral:develop Jan 16, 2023
@twibiral
Copy link
Owner

I saved the images used in the repo and changed the links accordingly. It will be released soon.

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.

4 participants