Pragmater

Table of Contents

From the command line, type: pragmater --help

Both the insert and remove commands support the same options for specifying pragmas and/or included files. Example:

The insert and remove commands default to the current working directory so a path isn’t necessary unless you want to run Pragmater in a directory structure other than your current working directory.

This gem can be configured via a global configuration: $HOME/.config/pragmater/configuration.yml

It can also be configured via XDG environment variables.

The default configuration is as follows:

Feel free to take the above configuration, modify, and save as your own custom configuration.yml.

The configuration.yml file can be configured as follows:

• comments: Defines the array of pragmas you want to insert into your source files. Whatever is defined here will be the default used for insert and remove operations.

• includes: Defines the array file patterns to apply to. Whatever is defined here will be the default used for insert and remove operations.

• root_dir: Defines the root directory to apply the includes patterns too. By default, this will be the current directory you are running Pragmater from but can be a different directory entirely.

With Ruby 2.3 and higher, the following pragmas are available:

• # encoding: Defaults to UTF-8 but any supported encoding can be used. For a list of values, launch an IRB session and run Encoding.name_list.

• # coding: The shorthand for # encoding:. Supports the same values as mentioned above.

• # frozen_string_literal: Defaults to false but can take either true or false as a value. When enabled, Ruby will throw errors when strings are used in a mutable fashion.

• # warn_indent: Defaults to false but can take either true or false as a value. When enabled, and running Ruby with the -w option, it’ll throw warnings for code that isn’t indented by two spaces.

The pragma syntax allows for two kinds of styles. Example:

Only the former syntax is supported by this gem as the latter syntax is more verbose and requires additional typing.

When different multiple pragmas are defined, they all take precedence:

In the above example, both binary encoding and frozen string literals behavior will be applied.

When defining multiple pragmas that are similar, behavior can differ based on the kind of pragma used. The following walks through each use case so you know what to expect:

In the above example, only the binary encoding will be applied while the UTF-8 encoding will be ignored (same principle applies for the coding pragma too).

In the above example, frozen string literal support will be enabled instead of being disabled.

In the above example, indentation warnings will be enabled instead of being disabled.

Support for frozen string literals was added in Ruby 2.3.0. The ability to freeze strings within a source can be done by placing a frozen string pragma at the top of each source file. Example:

This is great for selective enablement of frozen string literals but might be too much work for some (even with the aid of this gem). As an alternative, frozen string literals can be enabled via the following Ruby command line option:

It is important to note that, once enabled, this freezes strings program-wide – It’s an all or nothing option.

Regardless of whether you leverage the capabilities of this gem or the Ruby command line option mentioned above, the following Ruby command line option is available to aid debugging and tracking down frozen string literal issues:

Finally, you can use --debug (or $DEBUG=true) to force all raised exceptions to print to the console whether they are rescued or not. This is best used in conjunction with the above.

Ruby 2.3.0 also added the following methods to the String class:

• String#+@: Answers a duplicated, mutable, string if not already frozen. Example:

  immutable = "test".freeze
  mutable = +immutable
  
  mutable.frozen?      # false
  mutable.capitalize!  # "Test"

• String#-@: Answers a immutable string if not already frozen. Example:

  mutable = "test"
  immutable = -mutable
  
  immutable.frozen?      # true
  immutable.capitalize!  # FrozenError

You can also use the methods, shown above, for variable initialization. Example:

💡 Use of String#-@ was enhanced in Ruby 2.5.0 to deduplicate all instances of the same string thus reducing your memory footprint. This can be valuable in situations where you are not using the frozen string comment and need to selectively freeze strings.

💡 Use of String#dup was significantly enhanced in Ruby 3.3.0 to be as performant as String#+@ so you can use String#dup instead of String#+@ since String#dup is easier to read.

As an added bonus, this gem ensures pragmas for all analyzed files are formatted in a consistent style. This means there is always a space after the octothorp (#). Here are multiple pragmas presented together for a visual comparison:

One oddity to the above is the use of # !/usr/bin/env ruby is not allowed but #! /usr/bin/env ruby is which is why spacing is slightly different for shell pragmas.