profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/fj/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

fj/cheryls-birthday-prolog 14

Solving the Cheryl's Birthday problem -- with Prolog!

fj/becamp2009 3

A general hub for beCamp 2009 resources.

fj/awesomesauce 1

Useful improvements to your web experience.

fj/bitsbuilder-blog 1

BitsBuilder's blog.

fj/blogofile 1

A static file blog engine/compiler, inspired by jekyll

fj/countries 1

All sorts of useful information about every country packaged as pretty little country objects. It includes data from ISO 3166 (countries and states/subdivisions ), ISO 4217 (currency), and E.164 (phone numbers). As a bonus it even adds a country_select helper to rails projects.

fj/cucumber 1

BDD that talks to domain experts first and code second

fj/docrails 1

PLEASE CHECK http://github.com/lifo/docrails/wikis

dsvellal/anagram-discussion 0

A sample anagram problem with use-cases to help us navigate through technical discussions

fj/.sample-repository 0

a sample repository

PR closed ManimCommunity/manim

Remove stray or erroneous linebreaks in README needs discussion

<!-- Thank you for contributing to Manim! Learn more about the process in our contributing guidelines: https://docs.manim.community/en/latest/contributing.html -->

Overview: What does this pull request change?

<!-- If there is more information than the PR title that should be added to our release changelog, add it in the following changelog section. This is optional, but recommended for larger pull requests. --> <!--changelog-start-->

<!--changelog-end-->

Motivation and Explanation: Why and how do your changes improve the library?

Corrects inconsistent or incorrect linebreaks in several spots in the README.

Links to added or changed documentation pages

<!-- Please add links to the affected documentation pages (edit the description after opening the PR). The link to the documentation for your PR is https://manimce--####.org.readthedocs.build/en/####/, where #### represents the PR number. --> N/A.

Further Information and Comments

<!-- If applicable, put further comments for the reviewers here. -->

<!-- Thank you again for contributing! Do not modify the lines below, they are for reviewers. -->

Reviewer Checklist

  • [ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
  • [ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
  • [ ] If applicable: newly added functions and classes are tested
+7 -22

6 comments

1 changed file

fj

pr closed time in a month

pull request commentManimCommunity/manim

Remove stray or erroneous linebreaks in README

Sounds good; I'll withdraw this PR.

On Tue, Aug 24, 2021, 09:18 Darylgolden ***@***.***> wrote:

From the responses it seems like most of us have a preference for manual line lengths. Since this is purely a matter of preference, I think we should stick to using them.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ManimCommunity/manim/pull/1940#issuecomment-904635139, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAODVO6S6O6R2OF35MK2NDT6OL4FANCNFSM5CQ76EBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

fj

comment created time in a month

push eventfj/manim

Oliver

commit sha 7d2f9837cacd45cf821bfd42f6e5afb471c2e0a8

init (#1931) Co-authored-by: Benjamin Hackl <devel@benjamin-hackl.at>

view details

Harivinay

commit sha dd4c912b94ccc429a9aa34e3b3a2914b6d22fc77

Fixed formatting of parameter description of :class:`~.NumberPlane` (#1939) * Number plane doc fixed white space * format unit_size in note block as code literal Co-authored-by: Benjamin Hackl <devel@benjamin-hackl.at>

view details

Eric Biedert

commit sha 2dabdb70f9f4d99d4c60ab68ad733bda4a1bb1ef

Clean up when render raises an error (#1922) Co-authored-by: Benjamin Hackl <devel@benjamin-hackl.at>

view details

icedcoffeeee

commit sha fba4baef65ac7101bf5d67a24efd57f7111d0b24

Made arrow tips rotate up/down (#1924) * Made arrow tips rotate up/down * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * rounding the doctest * negative zeros * Added notes on some calculations * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * Angled Tip test Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Iced-Tea3 <83535735+Iced-Tea3@users.noreply.github.com>

view details

John Feminella

commit sha 00e5957b33de2d43f984f0996ff1a280cb62770d

Merge branch 'main' into patch-2

view details

push time in a month

pull request commentManimCommunity/manim

Remove stray or erroneous linebreaks in README

Sure:

  1. Double line breaks do have rendering differences — they start new paragraphs in Markdown. The PR removes erroneous double line breaks. The statement that it's an editor-visible concern only isn't accurate in that case, IMO.

  2. Most text editors have natural word wrap (e.g. vim, emacs, vscode, etc.). Certainly this is a matter of preference, but adding nonsemantic line breaks seems like it doesn't add much value.

  3. The lines were not broken at consistent lengths, so even disregarding (2) that still seems like something that ought to be corrected.

Happy to make any changes you'd like if you find this to be not very useful as is.

On Fri, Aug 20, 2021, 19:11 Benjamin Hackl ***@***.***> wrote:

Hello! Can you explain why you feel the line breaks in the README are unnecessary / erroneous?

In principle, they are there so that the lines don't get too long; the linebreaks don't matter for the rendered version of the markdown file, and they should make the text easier to read when opening it in a text-only editor.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ManimCommunity/manim/pull/1940#issuecomment-903001957, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAODVIZN2PJFAH5T5UIOULT53OKZANCNFSM5CQ76EBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

fj

comment created time in a month

PR opened ManimCommunity/manim

Remove stray or erroneous linebreaks in README

<!-- Thank you for contributing to Manim! Learn more about the process in our contributing guidelines: https://docs.manim.community/en/latest/contributing.html -->

Overview: What does this pull request change?

<!-- If there is more information than the PR title that should be added to our release changelog, add it in the following changelog section. This is optional, but recommended for larger pull requests. --> <!--changelog-start-->

<!--changelog-end-->

Motivation and Explanation: Why and how do your changes improve the library?

Corrects inconsistent or incorrect linebreaks in several spots in the README.

Links to added or changed documentation pages

<!-- Please add links to the affected documentation pages (edit the description after opening the PR). The link to the documentation for your PR is https://manimce--####.org.readthedocs.build/en/####/, where #### represents the PR number. --> N/A.

Further Information and Comments

<!-- If applicable, put further comments for the reviewers here. -->

<!-- Thank you again for contributing! Do not modify the lines below, they are for reviewers. -->

Reviewer Checklist

  • [ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
  • [ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
  • [ ] If applicable: newly added functions and classes are tested
+7 -22

0 comment

1 changed file

pr created time in a month

push eventfj/manim

John Feminella

commit sha 350bf1c143f7fcfa053aace4accd2c9a39a4eb74

Remove stray or erroneous linebreaks in README

view details

push time in a month

push eventfj/manim

John Feminella

commit sha e70c290084bf257aef2b41b99a2cfb9194a91d98

Fix stray linebreak in README

view details

push time in a month

fork fj/manim

A community-maintained Python framework for creating mathematical animations.

https://www.manim.community

fork in a month

push eventfj/jxf-site

John Feminella

commit sha e43995f318fb0e81a1e7a56339a7271fb1c89d24

Add submodule for hugo-coder theme

view details

John Feminella

commit sha a656a0e1c803bc0044da8ba20011f47eae1b95ee

Add basic configuration

view details

push time in 2 months

fork fj/hugo-coder

A minimalist blog theme for hugo.

fork in 2 months

issue openedluizdepra/hugo-coder

Discussion: Extensible touchpoints with more modular includes?

Looking across some of the forks of hugo-coder, I've noticed that many people fork to customize or change parts of hugo-coder in appearance or structure, without changing functionality very much.

I think there would be less reason to fork if the touchpoints were extended and explicit. That way, extensions happen using Hugo rather than needing git forks of hugo-coder — you'd simply override a file in your site, rather than editing the theme.

For example, let's say you want to add extra headers or conditional logic to the <head> tag. Right now, there's not necessarily an easy way to do this short of modifying the baseof.html. But if you do that, now you've touched a file in themes/, which means you're running a fork of hugo-coder. Bummer!

How can we improve this? Using this example, if there were, say, a baseof.html like this:

# baseof.html
⋯
<head>
  <!-- many things specific to hugo-coder theme -->
</head>
⋯

might instead look like:

# baseof.html
⋯
<head>
  {{- partial "head-hugo-coder.html" . -}} <!-- specific to hugo-coder -->
  {{- partial "head-extensions.html" . -}} <!-- blank in theme; available for overriding in consumers -->
</head>
⋯

This way, you don't modify a hugo-coder file; you modify a file in your own local repository, and you aren't breaking your compatibility with hugo-coder. Repeat this exercise for every interesting extension point.

If you like this idea, I'd be willing to shepherd this and open a PR for review that would cover a number of such touchpoints. But before proceeding I wanted to gauge interest.

created time in 2 months

push eventfj/jxf-site

John Feminella

commit sha c13e90f3e11f6659c1deffd2bc7346ee748aff4d

Add .gitignore

view details

push time in 2 months

push eventfj/jxf-site

John Feminella

commit sha 41db62281d07ce794e20e6dffbdb606bf97fb484

Add Taskfile to project

view details

push time in 2 months

create barnchfj/jxf-site

branch : main

created branch time in 2 months

created repositoryfj/jxf-site

A home.

created time in 2 months

create barnchfj/jxf-site-core

branch : master

created branch time in 2 months

created repositoryfj/jxf-site-core

created time in 2 months