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

Readme: add more thorough instructions #6

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rubo77
Copy link

@rubo77 rubo77 commented Jul 14, 2019

This is a first try, but there seems something missing still, see #4

@rubo77
Copy link
Author

rubo77 commented Jul 14, 2019

I appreciate your suggestions for the improved readme file to help people who aren't familiar with Laravel.

The formatting got messed up from how I had it, so I guess I'll try to make similar changes instead of merging the pull request.

What formatting is mixed up?

I added a max lilnewidth of 80 chars and added an empty line between the numbered list.

The github change-view is quite confusing though. If you watch che changes in a better GUI, you see, not so much changed. This is seen in SmartGit:

Bildschirmfoto von 2019-07-14 16-19-19
Bildschirmfoto von 2019-07-14 16-23-44

@ryancwalsh
Copy link
Owner

I don't like using a max line width since I prefer text-wrapping to be configurable by the reader. Most of your other modifications look good. Thanks.

@rubo77
Copy link
Author

rubo77 commented Jul 14, 2019

Ok, I removed the line wrapping changes

@rubo77 rubo77 force-pushed the readme branch 2 times, most recently from 0fdbd80 to e690275 Compare July 14, 2019 19:33
@rubo77
Copy link
Author

rubo77 commented Jan 30, 2024

is this still needed?

it seems like you enhanced the readme in some way already

@ryancwalsh
Copy link
Owner

Every ~60 days, I've been using this repo (running locally on my machine) to backup my StackExchange activity.

It had worked for years.

Suddenly it started getting these errors, which I've not yet figured out: https://stackapps.com/questions/10497/suddenly-getting-couldnt-parse-client-id

I basically haven't looked at this repo at all since ~2019 since it always just worked.

@rubo77 If you'd like to fork it, I can update my readme to point to your forked repo, for people who are interested, since I don't want to spend much (or maybe any) time improving it from here.

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.

None yet

2 participants