Git Product home page Git Product logo

dotfiles's Introduction

Jekyll-Bootstrap

The quickest way to start and publish your Jekyll powered blog. 100% compatible with GitHub pages

Usage

For all usage and documentation please see: http://jekyllbootstrap.com

Version

0.3.0 - stable and versioned using semantic versioning.

NOTE: 0.3.0 introduces a new theme which is not backwards compatible in the sense it won't look like the old version. However, the actual API has not changed at all. You might want to run 0.3.0 in a branch to make sure you are ok with the theme design changes.

Milestones

0.4.0 - next release [ETA 03/29/2015]

GOALS

  • No open PRs against master branch.
  • Squash some bugs.
  • Add some new features (low-hanging fruit).
  • Establish social media presence.

Bugs

Bug Description
#86 ☑ Facebook Comments
#113 ☑ ASSET_PATH w/ page & post
#144 ☐ BASE_PATH w/ FQDN
#227 ☑ Redundant JB/setup

Features

Bug Description
#98 ☑ GIST Integration
#244 ☑ JB/file_exists Helper
#42 ☑ Sort collections of Pages / Posts
#84 ☐ Detecting production mode

TODOS

Review existing pull requests against plusjake/jekyll-bootstrap:master. Merge or close each.

  • Create twitter account. Add link / icon on jekyllbootstrap.com.
  • Create blog posts under plusjade/gh-pages, expose on jekyllbootstrap.com, feed to twitter account.
  • Announce state of project, announce roadmap(s), announce new versions as they’re released.

Contributing

To contribute to the framework please make sure to checkout your branch based on jb-development!! This is very important as it allows me to accept your pull request without having to publish a public version release.

Small, atomic Features, bugs, etc. Use the jb-development branch but note it will likely change fast as pull requests are accepted. Please rebase as often as possible when working. Work on small, atomic features/bugs to avoid upstream commits affecting/breaking your development work.

For Big Features or major API extensions/edits: This is the one case where I'll accept pull-requests based off the master branch. This allows you to work in isolation but it means I'll have to manually merge your work into the next public release. Translation : it might take a bit longer so please be patient! (but sincerely thank you).

Jekyll-Bootstrap Documentation Website.

The documentation website at http://jekyllbootstrap.com is maintained at https://github.com/plusjade/jekyllbootstrap.com

License

MIT

dotfiles's People

Contributors

seeminglyscience avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

dotfiles's Issues

Breakpoints error when using Select-ObjectIndex

About

  • Select-ObjectIndex sometimes breaks $error
  • when it does, referencing that index will print nothing in the term
  • empty ones also create multiple new ErrorRecords every prompt

image

Possible Causes

  • a stale/corrupt debug environment
  • Probably not a design issue -- otherwise why is it working in the same context
  • Maybe scope related -- like referencing $local:error vs $global:error (Debugging inside and outside modules cope issues)
  • Is $errors a ring buffer? It wraps after index 255. Could overflowing past index 255, end up invalidating a previous reference to $error[0] ? Or would it copy the original on write?

Because when debugging things, you can easily wrap 255.

To Reproduce

In my testing, it felt like it was split, either: 100% it would reproduce, or 0%

  • Be in a breakpoint
  • Create some errors, then index it:
  • It felt like hitting 0 before 3 was more likely -- so maybe there's a reference in there?

$Error.count  # returns 130 # existing errors
$Error | Utility\Select-ObjectIndex 0
      # <the first time you get the right error>

$Error | Utility\Select-ObjectIndex 3        # errors don't print
$Error | Utility\Select-ObjectIndex 0        # errors don't print

> Collection was modified, cannot enumerate. 

Once it starts, you can only reference the error in some ways. So when debugging it -- make sure your prompt has $error.count in it.
In the screenshot, Select-Object adds 3 errors, every time ( Maybe it hints to the uncaught error being fired inside the formatter? )

# 169!7.2.6
Pwsh> $error | Select-Object -First 3

# 172!7.2.6
Pwsh> $error | select -First 10

#175!7.2.6
Pwsh> $error | select -First 10

image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.