it's more simple and secure: by specifying ActivateScrips to 0, it won't cause infinite-loop,
which could happen if the system error txn triggers some scrips to send mails.

People try to put the bare word true or false into the config setting
with horribly results.

Not passing --listen causes $args{listen} to be undef, which cannot be
de-referenced as an array reference.  Fall back to [] to ensure that
this dies with the useful message, and not "Can't use an undefined value
as an ARRAY reference"

This allows an extension to overwrite a user's intended destination, or
more usefully, detect when someone is logging in at the top level and
redirect instead to a Dashboard (or in RTIR's case, to /RTIR/).

RTIR wants to customize a number of paths during history display (see
RTIR/Display.html and RTIR/Incident/Display.html).  In order to use
delayed history loading, RTIR either needs to pass those as GET
arguments (allowing user injection of paths that we use to build links,
which is dangerous without sanitation) or otherwise get them to
ShowHistory.

With this, RTIR can just callback in the custom arguments (you can also
clobber any of the other arguments to ShowHistory with it).

mason-syntax already ignored swp files, but would try to compile swo
files.  t/web/helper-http-cache-headers.t made no attempt to ignore
anything, so if you're hacking on a Helper this test will fail
spectacularly.

color scheme is from cloos++

The display template (ShowCustomFieldCustomGroupings) takes Groupings as
an argument, for symmetry, also take it during editing.

This allows code to better control which groups are shown
on Create or other editing pages (in particular, RTIR and the multitude
of complex editing/creating pages in that workflow).

Hardcoding ref here meant that if anything extends
RT::CustomField->_GroupingClass, it'll fail to find the groupings and
dump all your CFs into the Custom Fields group.  By calling back in to
GroupingClass, you get the 'magic' type and can look it up in the
groupings.

NewItem provides an empty CustomField with ContextObject set which
overriders of _GroupingClass can use for more context when
LimitoToGrouping is called on an empty object (during object creation)

RTIR uses this to provide an RTIR::Ticket grouping type so you can
separate CF groupings on RTIR tickets from those on core tickets.
Provided to allow better separation of groupings between RTIR CFs and
CFs on other Queues, especially since RTIR uses common names such as
'Customer' and 'IP' which would otherwise complicate using those CFs in
groups in other Queues. Perhaps points towards wanting per-queue CF
groupings.

Launchpad parsing objects to msgids which are not followed by empty
msgstr's in .pot files.

Old "message recorded" is confusing as it doesn't differentiate
between correspond and comment.

For users with a lot of CFs and subsequently a number of groups, this
lets you jump to the right place on the page if you choose to edit a
subset of your CFs.

Closes issues #30195

Passing $@ to loc() causes its value to not be examined until later,
when it is substituted into the string.  Between the ->require error and
then, the loc() machinery attempts to run for the first time, which
_also_ requires files, thus overwriting the original error in $@.

Store the error found in $@ away into a different variable, to ensure
that it is not lost before it is used.  Passing "$@" instead of $@ would
similarly suffice, but the clarity of the extra variable is preferrable.

Fixes I#22991.