code-red
Ensure values are ordered consistently in your CSS.
A tiny utility to colorize stdin/stdout
Modify colors using the color-mod() function in CSS
A fully persistent balanced binary search tree
Colors of Google's Material Design made available to coders
This module provides basic ANSI color code support, to allow you to format your console output with foreground and background colors as well as providing bold, italic and underline support.
The fastest Node.js library for formatting terminal text with ANSI colors~!
Colors, formatting and other tools for the console
Convert HEX color to RGBA
Correctly declare progressive enhancements for CSS Custom Properties.
LLM eval & testing toolkit
Merge Tailwind CSS classes without style conflicts
TypeScript definitions for katex
CommonJS version - The smallest and fastest command-line coloring package on the internet
The smallest and fastest command-line coloring package on the internet
Eight colors for the console
The Node-RED admin command line interface
A list of color names and its values
mjml-head-style
Converts an object to a child_process.spawn args array
TailwindCSS v4.0 compatible replacement for `tailwindcss-animate`.
Aquila's internet of things platform nodes for Node-Red.
The color red, in ansi.
Replace blank attributes at definition list items for some custom code, like a red 'No Record Found' span.
Scaffold for code spikes, includes simple boilerplate with Minitest + Guard to make red/green work out-of-the-box.
Red FlatBuffers can generate Ruby code that reads and writes (not implemented yet) FlatBuffers from `.fbfs` (binary FlatBuffers schema). Red FlatBuffers can't compile `.fbs` (FlatBuffers schema) to `.fbfs`. You need to use FlatBuffers to compile `.fbs` to `.bfbs`.
Marso is the beginning of a small lightweight BDD project. Currently, this is just a very simple code sample that only displays a custom message in green or in red depending on the value of a predicate.
Custom assertions functions. This is the beginning of a small lightweight BDD project. Currently, this is just a very simple code sample that only displays a custom message in green or in red depending on the value of a predicate.
Write your HTML pages like Lisp code. CLI utility. Run `sept -h` for info (html (head (title "Hello world") (style ".red { color: blue }")) (body (p.red#cool-and-good "Handy classes and ids. Id must be last") ("p onclick='func()'" "Other attributes are expressed that way") (p "This is %{param}")))
this code will check the input temperature,range and wanted temperature. If the temp is not the same as the wanted temp, then it will put the cooling or heating on. It will show via the led if it cools (blue),if it heats (red) and else it will be green. It's possible to change the unit of the temperature and it will be automatically changed to Celsius.
I don't want a single thing preventing me from starting off (even the smallest) library without a good infrastructure to support TDD and clean coding standards. I got tired of reconfiguring the same tools in basically the same way every time. With this one command you can set up a library, fire up Guard, and jump right into the TDD loop: Red, Green, Refactor.
This is a pure-ruby port of Takuma Ozawa's RBTree. (it has an identical interface and uses the identical unit tests from his version 0.3.0, however it is *not* a Red-Black tree.) It's intended for doing lookups and not for doing lots of insertions or deletions. Please see RBTree docs for a sense of how this is supposed to be used. (This one runs the unit tests about 15% slower than Ozawa's C-version, and 80% less lines of code ;)
TURN is a new way to view Test::Unit results. With longer running tests, it can be very frustrating to see a failure (....F...) and then have to wait till all the tests finish before you can see what the exact failure was. TURN displays each test on a separate line with failures being displayed immediately instead of at the end of the tests. If you have the 'facets' gem installed, then TURN output will be displayed in wonderful technicolor (but only if your terminal supports ANSI color codes). Well, the only colors are green and red, but that is still color.
TURN is a new way to view Test::Unit results. With longer running tests, it can be very frustrating to see a failure (....F...) and then have to wait till all the tests finish before you can see what the exact failure was. TURN displays each test on a separate line with failures being displayed immediately instead of at the end of the tests. If you have the 'ansi' gem installed, then TURN output will be displayed in wonderful technicolor (but only if your terminal supports ANSI color codes). Well, the only colors are green and red, but that is still color.
# Footman This gem is still growing. ## Installation Depends upon having reprepro tool installed (if debian based) or createrepo installed (if red hat based). Ruby 1.9.+ is required to use this gem. 'createrepo' (rpm) tool does not require any pre-setup to the repository or watched directory. - - - 'reprepro' (deb) tool requires pre-setup. The repository directory for deb files must contain: <pre><code> conf/ conf/distributions conf/options conf/override.precise </pre></code> options file is empty, but needed to make reprepro happy distributions file will contain: <pre><code>Origin: Tyler Label: Tyler's Personal Debs Codename: precise Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.precise DscOverride: override.precise Origin: Tyler Label: Tyler's Personal Debs Codename: lenny Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.lenny DscOverride: override.lenny </code></pre> Note that the code name is for each distribution repository you support. for each distribtuion repository you support there must be an override file. override file can be left empty, footman will fill it out when a new package is added. The watched directory must have sub directorys named after each of the distribution repositories you support. For example my watched directory at /path/ will have two subdirectories: <pre><code>/path/lenny/ /path/precise/</code></pre> Packages must be dropped into the subdirectory that corrosponds with the distribution they were built on. - - - Add this line to your application's Gemfile: gem 'footman' And then execute: $ bundle Or install it yourself as: $ gem install footman Or locally: $ gem build footman.gemspec $ gem install footman --local ## Usage footman path/to/watch path/to/repo ## Contributing 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create new Pull Request
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.