I don't think that's feasible for all of these apps and it would make the readme extremely long and harder to read. If you have any examples of other readmes that have this many screenshots?
<!-- gh-comment-id:1825183035 -->
@rothgar commented on GitHub (Nov 24, 2023):
I don't think that's feasible for all of these apps and it would make the readme extremely long and harder to read. If you have any examples of other readmes that have this many screenshots?
I don't think that's feasible for all of these apps and it would make the readme extremely long and harder to read. If you have any examples of other readmes that have this many screenshots?
<!-- gh-comment-id:1825185545 -->
@bphd commented on GitHub (Nov 24, 2023):
You can hide them with \<details\>
> I don't think that's feasible for all of these apps and it would make the readme extremely long and harder to read. If you have any examples of other readmes that have this many screenshots?
If you have ideas on how to get screenshots. Many of the project repos don't have screenshots. If you know how to automate screenshots it would be even better.
<!-- gh-comment-id:1825190981 -->
@rothgar commented on GitHub (Nov 24, 2023):
If you have ideas on how to get screenshots. Many of the project repos don't have screenshots. If you know how to automate screenshots it would be even better.
Have thunk about making it slowly with time but yeah maybe you can automatize with a command, something like
for i in $(grep --perl-regexp '#\S+' README.me | sed 's/#//g'); do $i | commandThatCreateVideoOutOfCommandsIveSeenThemInALotOfRepoReadMeGoSearchOut | sed --in-place 's/#i/<details>{}#i/g' README.md; done
<!-- gh-comment-id:1825199669 -->
@bphd commented on GitHub (Nov 24, 2023):
Have thunk about making it slowly with time but yeah maybe you can automatize with a command, something like
`for i in $(grep --perl-regexp '#\S+' README.me | sed 's/#//g'); do $i | commandThatCreateVideoOutOfCommandsIveSeenThemInALotOfRepoReadMeGoSearchOut | sed --in-place 's/#i/<details>{}#i/g' README.md; done`
I'm not sure that would add a lot of benefit for the amount of work it would require. I think adding a collapsible details with a screenshot would make the readme harder to skim/read and screenshot commands would need to be tracked for each command which would add more maintenance
<!-- gh-comment-id:1826620291 -->
@rothgar commented on GitHub (Nov 26, 2023):
I'm not sure that would add a lot of benefit for the amount of work it would require. I think adding a collapsible details with a screenshot would make the readme harder to skim/read and screenshot commands would need to be tracked for each command which would add more maintenance
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @bphd on GitHub (Nov 23, 2023).
Original GitHub issue: https://github.com/rothgar/awesome-tuis/issues/160
@rothgar commented on GitHub (Nov 24, 2023):
I don't think that's feasible for all of these apps and it would make the readme extremely long and harder to read. If you have any examples of other readmes that have this many screenshots?
@bphd commented on GitHub (Nov 24, 2023):
You can hide them with <details>
@bphd commented on GitHub (Nov 24, 2023):
It's done!? What speed! Give link to result
@rothgar commented on GitHub (Nov 24, 2023):
If you have ideas on how to get screenshots. Many of the project repos don't have screenshots. If you know how to automate screenshots it would be even better.
@bphd commented on GitHub (Nov 24, 2023):
Have thunk about making it slowly with time but yeah maybe you can automatize with a command, something like
for i in $(grep --perl-regexp '#\S+' README.me | sed 's/#//g'); do $i | commandThatCreateVideoOutOfCommandsIveSeenThemInALotOfRepoReadMeGoSearchOut | sed --in-place 's/#i/<details>{}#i/g' README.md; done@rothgar commented on GitHub (Nov 26, 2023):
I'm not sure that would add a lot of benefit for the amount of work it would require. I think adding a collapsible details with a screenshot would make the readme harder to skim/read and screenshot commands would need to be tracked for each command which would add more maintenance