HEX

File: //usr/lib/python3/dist-packages/hgext/__pycache__/fix.cpython-310.pyc
o

�]Lb-��@s\dZddlmZddlZddlZddlZddlZddlZddlm	Z	ddl
mZmZm
Z
ddlmZddlmZmZmZmZmZmZmZmZmZmZmZmZmZm Z m!Z!dZ"iZ#e�$e#�Z$iZ%e�&e%�Z&ddddd	d
d
d�Z'e'�(�D]\Z)Z*e&dd
e)e*d
d�qre&dddd�e&dddd�dMdd�Z+ddd	e	d�fZ,ddge	d�e	d�fZ-ddge	d�e	d�fZ.dd ge	d!�e	d�fZ/d"d#d	e	d$�fZ0dd%d	e	d&�fZ1e	d'�Z2e$de,e-e.e/e0e1ge2e$j3d(�d)d*��Z4d+d,�Z5d-d.�Z6d/d0�Z7d1d2�Z8d3d4�Z9d5d6�Z:d7d8�Z;d9d:�Z<d;d<�Z=d=d>�Z>d?d@�Z?dAdB�Z@dCdD�ZAdEdF�ZBdGdH�ZCdIdJ�ZDGdKdL�dLeE�ZFdS)Na"rewrite file content in changesets or working copy (EXPERIMENTAL)

Provides a command that runs configured tools on the contents of modified files,
writing back any fixes to the working copy or replacing changesets.

Here is an example configuration that causes :hg:`fix` to apply automatic
formatting fixes to modified lines in C++ code::

  [fix]
  clang-format:command=clang-format --assume-filename={rootpath}
  clang-format:linerange=--lines={first}:{last}
  clang-format:pattern=set:**.cpp or **.hpp

The :command suboption forms the first part of the shell command that will be
used to fix a file. The content of the file is passed on standard input, and the
fixed file content is expected on standard output. Any output on standard error
will be displayed as a warning. If the exit status is not zero, the file will
not be affected. A placeholder warning is displayed if there is a non-zero exit
status but no standard error output. Some values may be substituted into the
command::

  {rootpath}  The path of the file being fixed, relative to the repo root
  {basename}  The name of the file being fixed, without the directory path

If the :linerange suboption is set, the tool will only be run if there are
changed lines in a file. The value of this suboption is appended to the shell
command once for every range of changed lines in the file. Some values may be
substituted into the command::

  {first}   The 1-based line number of the first line in the modified range
  {last}    The 1-based line number of the last line in the modified range

Deleted sections of a file will be ignored by :linerange, because there is no
corresponding line range in the version being fixed.

By default, tools that set :linerange will only be executed if there is at least
one changed line range. This is meant to prevent accidents like running a code
formatter in such a way that it unexpectedly reformats the whole file. If such a
tool needs to operate on unchanged files, it should set the :skipclean suboption
to false.

The :pattern suboption determines which files will be passed through each
configured tool. See :hg:`help patterns` for possible values. However, all
patterns are relative to the repo root, even if that text says they are relative
to the current working directory. If there are file arguments to :hg:`fix`, the
intersection of these patterns is used.

There is also a configurable limit for the maximum size of file that will be
processed by :hg:`fix`::

  [fix]
  maxfilesize = 2MB

Normally, execution of configured tools will continue after a failure (indicated
by a non-zero exit status). It can also be configured to abort after the first
such failure, so that no files will be affected if any tool fails. This abort
will also cause :hg:`fix` to exit with a non-zero status::

  [fix]
  failure = abort

When multiple tools are configured to affect a file, they execute in an order
defined by the :priority suboption. The priority suboption has a default value
of zero for each tool. Tools are executed in order of descending priority. The
execution order of tools with equal priority is unspecified. For example, you
could use the 'sort' and 'head' utilities to keep only the 10 smallest numbers
in a text file by ensuring that 'sort' runs before 'head'::

  [fix]
  sort:command = sort -n
  head:command = head -n 10
  sort:pattern = numbers.txt
  head:pattern = numbers.txt
  sort:priority = 2
  head:priority = 1

To account for changes made by each tool, the line numbers used for incremental
formatting are recomputed before executing the next tool. So, each tool may see
different values for the arguments added by the :linerange suboption.

Each fixer tool is allowed to return some metadata in addition to the fixed file
content. The metadata must be placed before the file content on stdout,
separated from the file content by a zero byte. The metadata is parsed as a JSON
value (so, it should be UTF-8 encoded and contain no zero bytes). A fixer tool
is expected to produce this metadata encoding if and only if the :metadata
suboption is true::

  [fix]
  tool:command = tool --prepend-json-metadata
  tool:metadata = true

The metadata values are passed to hooks, which can be used to print summaries or
perform other post-fixing work. The supported hooks are::

  "postfixfile"
    Run once for each file in each revision where any fixer tools made changes
    to the file content. Provides "$HG_REV" and "$HG_PATH" to identify the file,
    and "$HG_METADATA" with a map of fixer names to metadata values from fixer
    tools that affected the file. Fixer tools that didn't affect the file have a
    value of None. Only fixer tools that executed are present in the metadata.

  "postfix"
    Run once after all files and revisions have been handled. Provides
    "$HG_REPLACEMENTS" with information about what revisions were created and
    made obsolete. Provides a boolean "$HG_WDIRWRITTEN" to indicate whether any
    files in the working copy were updated. Provides a list "$HG_METADATA"
    mapping fixer tool names to lists of metadata values returned from
    executions that modified a file. This aggregates the same metadata
    previously passed to the "postfixfile" hook.

Fixer tools are run in the repository's root directory. This allows them to read
configuration files from the working copy, or even write to the working copy.
The working copy is not updated to match the revision being fixed. In fact,
several revisions may be fixed in parallel. Writes to the working copy are not
amended into the revision being fixed; fixer tools should always write fixed
file content back to stdout as documented above.
�)�absolute_importN)�_)�nullid�nullrev�wdirrev)�procutil)�cmdutil�context�copies�error�
logcmdutil�match�mdiff�merge�
mergestate�pycompat�	registrar�rewriteutil�scmutil�util�workersships-with-hg-coreFT)scommands	linerangespatternspriority�metadatas	skipcleansenabled�fixs.*:%s$)�default�generic�maxfilesizes2MB)r�failure�continuecCsJ|�dd�}|dvrtjtd�|ftd�d��|dkr#tj||d��dS)	z)Abort with 'message' if fix.failure=abortrr)r�abortsunknown fix.failure action: %ssuse "continue" or "abort"��hintrN)�configr�Abortr)�ui�messager �action�r&�+/usr/lib/python3/dist-packages/hgext/fix.py�checktoolfailureaction�s��r(��alls)fix all non-public non-obsolete revisions�basesdrevisions to diff against (overrides automatic selection, and applies to every revision being fixed)sREV�r�revsrevisions to fix (ADVANCED)�s�sources1fix the specified revisions and their descendants�wsworking-dirsfix the working directory�wholesalways fix every line of a files[OPTION]... [FILE]...)�helpcategorycs�t����t��ddd�t��dddg������L�����-��d���t����}t	��|��t
��|�|��\}}t��|���t���t
�|��������fdd�}tj�d|t�|d	d
�}t�t�}	t�t�}
i}d	}t|dd�}
�jtd
�td�t|���d���}|D]~\}}}}|j|d�|��D]\}}|
|�|�q�|dur�||	||<|||d�}�j	ddd	it�|���||d8<|
�r
||
d�s
|
��}�|}|tkr�t �||	||�t!|	|�}n
t"��||	||�|	|=|
�r
||
dr�q�Wd�n	1�swYt#�||�|||
d�}�jdddit�|���Wd�n	1�sBwYWd�n1�sRwYWd�dSWd�dS1�skwYdS)a�rewrite file content in changesets or working directory

    Runs any configured tools to fix the content of files. Only affects files
    with changes, unless file arguments are provided. Only affects changed lines
    of files, unless the --whole flag is used. Some tools may always affect the
    whole file regardless of --whole.

    If --working-dir is used, files with uncommitted changes in the working copy
    will be fixed. Note that no backup are made.

    If revisions are specified with --source, those revisions and their
    descendants will be checked, and they may be replaced with new revisions
    that have fixed file content. By automatically including the descendants,
    no merging, rebasing, or evolution will be required. If an ancestor of the
    working copy is included, then the working copy itself will also be fixed,
    and the working copy will be updated to the fixed parent.

    When determining what lines of each file to fix at each revision, the whole
    set of revisions being fixed is considered, so that fixes to earlier
    revisions are not forgotten in later ones. The --base flag can be used to
    override this default behavior, though it is not usually desirable to do so.
    r*r/r-�working_dirrc
3sp�|D]2\}}}�|}||��}t����||��|�\}}||kr'|nd}|D]	}	|	|||fVq+qdS�N)�data�fixfile)
�items�srcrev�path�dstrevs�ctx�olddata�metadata�newdatar5�dstrev��basectxs�	basepaths�fixers�opts�repor#r&r'�getfixess&����zfix.<locals>.getfixesg�?F)�
threadsafeT)�reversesfixingsfiles)�topic�unit�total��itemN)r-spathr�postfixfile�throw����)sreplacementsswdirwrittenr�postfix)rN)rR)$r�byteskwargsr�check_at_most_one_arg�check_incompatible_arguments�wlock�lock�transaction�getrevstofix�getbasectxs�getworkqueue�getbasepaths�	getfixers�_prefetchfilesr�tuple�collections�defaultdict�dict�list�sorted�makeprogressr�sum�values�	incrementr7�append�hook�	strkwargs�popr�writeworkingdir�bool�
replacerev�cleanup)r#rE�patsrD�	revstofix�	workqueue�numitemsrF�results�filedata�aggregatemetadata�replacements�wdirwritten�commitorder�progress�revr9�filerevmetadatar>�	fixername�
fixermetadata�hookargsr;r&r@r'�fix�s�

�&��


���������"���Tr�cCs*dd�t�|�D�}tj||ddd�dS)aCalls scmutil.cleanupnodes() with the given replacements.

    "replacements" is a dict from nodeid to nodeid, with one key and one value
    for every revision that was affected by fixing. This is slightly different
    from cleanupnodes().

    "wdirwritten" is a bool which tells whether the working copy was affected by
    fixing, since it has no entry in "replacements".

    Useful as a hook point for extending "hg fix" with output summarizing the
    effects of the command, though we choose not to output anything here.
    cS�i|]\}}||g�qSr&r&)�.0�prec�succr&r&r'�
<dictcomp>}s�zcleanup.<locals>.<dictcomp>rT)�fixphaseN)r�	iteritemsr�cleanupnodes)rErxryr&r&r'rpps
�rpc
Cst�t�}t�t�}|�dd�}t|�D][}	||	}
t�|
||�}tt|||||||	|
��D]?}|
|}
|
�	�r:q/|
�
�|krO|�td�t
�|�|f�q/tdd�||	D��}||
��||f�|	�||	d7<q/qdd�|��D�}|��||fS)	aConstructs a list of files to fix and which revisions each fix applies to

    To avoid duplicating work, there is usually only one work item for each file
    revision that might need to be fixed. There can be multiple work items per
    file revision if the same file needs to be fixed in multiple changesets with
    different baserevs. Each work item also contains a list of changesets where
    the file's data should be replaced with the fixed data. The work items for
    earlier changesets come earlier in the work queue, to improve pipelining by
    allowing the first changeset to be replaced while fixes are still being
    computed for later changesets.

    Also returned is a map from changesets to the count of work items that might
    affect each changeset. This is used later to count when all of a changeset's
    work items have been finished, without having to inspect the remaining work
    queue in each worker subprocess.

    The example work item (1, "foo/bar.txt", (1, 2, 3)) means that the data of
    bar.txt should be read from revision 1, then fixed, and written back to
    revisions 1, 2 and 3. Revision 1 is called the "srcrev" and the list of
    revisions is called the "dstrevs". In practice the srcrev is always one of
    the dstrevs, and we make that choice when constructing the work item so that
    the choice can't be made inconsistently later on. The dstrevs should all
    have the same file revision for the given path, so the choice of srcrev is
    arbitrary. The wdirrev can be a dstrev and a srcrev.
    rrs!ignoring file larger than %s: %s
css�|]}|��VqdSr4)r|)r�r;r&r&r'�	<genexpr>�s�zgetworkqueue.<locals>.<genexpr>rPcSs$g|]\\}}}}t|�||f�qSr&)�min)r��_filerev�	_baserevsr9r:r&r&r'�
<listcomp>�s��z getworkqueue.<locals>.<listcomp>)r`rarc�int�configbytesrdrr
�
pathstofix�islink�size�warnrr�	bytecountr_�filerevrir7�sort)r#rErqrDrrrA�	dstrevmaprt�maxfilesizer|�fixctxr
r9�fctx�baserevsrsr&r&r'r[�s8

�����r[cCs�|dr
|�d�}n?|dr5t�||d�}t|�d|��}t|vr'|�t�|d��|vr4|�t�ntt�||d��}|�d�rI|�t�t|�dkrSt|vs_t	�
|�t�||d	�t|vrrt
j�|���rrtjd
dd��|s{tjd
dd��|S)z8Returns the set of revision numbers that should be fixedr*s+(not public() and not obsolete()) or wdir()r/s(%ld::) - obsolete()�.r-r3rPrsunresolved conflictssuse 'hg resolve'rsno changesets specifiedsuse --source or --working-dir)�revsr�revrange�setr�addr|�get�lenr�checkunfinishedr�precheck�
mergestatemodr�read�unresolvedcountrr")r#rErDr��source_revsr&r&r'rY�s2

�


��rYc

CsPt�}|D] }|j||t|�t|�d�}	|�tt�|	j|	j|	j|	j	���q|S)z�Returns the set of files that should be fixed in a context

    The result depends on the base contexts; we include any file that has
    changed relative to any of the base contexts. Base contexts should be
    ancestors of the context being fixed.
    )r
�	listclean�listunknown)
r��statusrn�update�	itertools�chain�added�modified�clean�unknown)
r#rErqrDr
rAr��files�basectx�statr&r&r'r��s����r�c
Csn|�d�r
td|�Sg}|D]$}|�|��|��|f|�}||vr(||��}	nd}	|�t|	|��qt|�S)a�Returns the set of line ranges that should be fixed in a file

    Of the form [(10, 20), (30, 40)].

    This depends on the given base contexts; we must consider lines that have
    changed versus any of the base contexts, and whether the file has been
    renamed versus any of them.

    Another way to understand this is that we exclude line ranges that are
    common to the file in all base contexts.
    r1r))r��difflinerangesr|r5�extend�unionranges)
rDr9rBrAr��content2�
rangeslistr��basepath�content1r&r&r'�
lineranges�s

r�cCsn|�d�riSi}|D])\}}}||}||D]}	t�|	|��||�}
|
|	vr3|
||	��|��|f<qq|S)Nr1)r�r
�
pathcopiesr|)rErDrsrArBr8r9�_dstrevsr�r�r�r&r&r'r\s
��r\cCsxtt|��}g}|r|dg|dd�}}|D]!\}}|d\}}||dkr0|�||f�q|t||�f|d<q|S)aReturn the union of some closed intervals

    >>> unionranges([])
    []
    >>> unionranges([(1, 100)])
    [(1, 100)]
    >>> unionranges([(1, 100), (1, 100)])
    [(1, 100)]
    >>> unionranges([(1, 100), (2, 100)])
    [(1, 100)]
    >>> unionranges([(1, 99), (1, 100)])
    [(1, 100)]
    >>> unionranges([(1, 100), (40, 60)])
    [(1, 100)]
    >>> unionranges([(1, 49), (50, 100)])
    [(1, 100)]
    >>> unionranges([(1, 48), (50, 100)])
    [(1, 48), (50, 100)]
    >>> unionranges([(1, 2), (3, 4), (5, 6)])
    [(1, 6)]
    rrPNrQ)rdr�ri�max)r��unioned�a�b�c�dr&r&r'r�#sr�cCsPg}t�||�D]\}}|dd�\}}|dkr%||kr%|�|d|f�q|S)a�Return list of line number ranges in content2 that differ from content1.

    Line numbers are 1-based. The numbers are the first and last line contained
    in the range. Single-line ranges have the same line number for the first and
    last line. Excludes any empty ranges that result from lines that are only
    present in content1. Relies on mdiff's idea of where the line endings are in
    the string.

    >>> from mercurial import pycompat
    >>> lines = lambda s: b'\n'.join([c for c in pycompat.iterbytestr(s)])
    >>> difflineranges2 = lambda a, b: difflineranges(lines(a), lines(b))
    >>> difflineranges2(b'', b'')
    []
    >>> difflineranges2(b'a', b'')
    []
    >>> difflineranges2(b'', b'A')
    [(1, 1)]
    >>> difflineranges2(b'a', b'a')
    []
    >>> difflineranges2(b'a', b'A')
    [(1, 1)]
    >>> difflineranges2(b'ab', b'')
    []
    >>> difflineranges2(b'', b'AB')
    [(1, 2)]
    >>> difflineranges2(b'abc', b'ac')
    []
    >>> difflineranges2(b'ab', b'aCb')
    [(2, 2)]
    >>> difflineranges2(b'abc', b'aBc')
    [(2, 2)]
    >>> difflineranges2(b'ab', b'AB')
    [(1, 2)]
    >>> difflineranges2(b'abcde', b'aBcDe')
    [(2, 2), (4, 4)]
    >>> difflineranges2(b'abcde', b'aBCDe')
    [(2, 4)]
    ���!rP)r�	allblocksri)r�r��ranges�lines�kind�	firstline�lastliner&r&r'r�Fs'�r�cs�|�d�r'tt��|�d���}|sth}�fdd�|D���fdd�|D�St�t��t|�D]&}�|}|��D]}|�	��vrN�|�
�|�	��q:�|�|�q:q0�S)a4Returns a map of the base contexts for each revision

    The base contexts determine which lines are considered modified when we
    attempt to fix just the modified lines in a file. It also determines which
    files we attempt to fix, so it is important to compute this even when
    --whole is used.
    r+csh|]}�|�qSr&r&�r�r|�rEr&r'�	<setcomp>�szgetbasectxs.<locals>.<setcomp>csi|]}|��qSr&r&r�)rAr&r'r��szgetbasectxs.<locals>.<dictcomp>)r�r�rr�rr`rard�parentsr|r�r�)rErDrrr�r|r;�pctxr&)rArEr'rZus


�rZc
szt�}|D]\}}}|tkrq|�||f�q|��D]\\}}}}	|�||	f�q|r;t���fdd�|D��dSdS)Ncs"g|]
\}}|t��|g�f�qSr&)r�
matchfiles)r�r|r9r�r&r'r��s��z"_prefetchfiles.<locals>.<listcomp>)r�rr�r7r�
prefetchfiles)
rErsrB�
toprefetchr8r9r��baserev�fixrevr�r&r�r'r^�s
���r^c	Csli}||��}	t�|�D]�\}
}|�|||�r�t||||||	�}|�|||�}
|
dur-q
|�d|
f�tjt	�
|
�dt	�
|j�tjtjtjd�}|�
|	�\}}|r\t||��|
|�|}|��r�z|�dd�\}}t�|�||
<Wnty�|�td�|
f�Yq
wd||
<|jdkr�|}	q
|s�td	�|jf}t||��|
|�t|td
�td�d�q
||	fS)
a*Run any configured fixers that should affect the file in this context

    Returns the file content that results from applying the fixers in some order
    starting with the file's content in the fixctx. Fixers that support line
    ranges will affect lines that have changed relative to any of the basectxs
    (i.e. they will only avoid lines that are common to all basectxs).

    A fixer tool's stdout will become the file's new content if and only if it
    exits with code zero. The fixer tool's working directory is the repository's
    root.
    Nssubprocess: %s
T)�shell�cwd�stdin�stdout�stderr�rPs+ignored invalid output from fixer tool: %s
rsexited with status %d
sno fixes will be appliedsFuse --config fix.failure=continue to apply any successful fixes anywayr)r5rr��affectsr��command�debug�
subprocess�Popenr�tonativestr�root�PIPE�communicate�
showstderrr|�shouldoutputmetadata�split�
json_loads�
ValueErrorr�r�
returncoder()r#rErDrCr�r9rBrAr=r>r~�fixerr�r��procr�r��	newerdata�metadatajsonr$r&r&r'r6�sd�
����
���r6cCsdt�d|�D])}|r/|�d�|dur|jtd�dd�n	|jd|dd�|�d||f�qdS)	a9Writes the lines of the stderr string as warnings on the ui

    Uses the revision number and fixername to give more context to each line of
    the error message. Doesn't include file names, since those take up a lot of
    space and would tend to be included in the error message if they were
    relevant.
    s[
]+�[Nswdirs
evolve.rev)�labels%ds	] %s: %s
)�rer�r�r)r#r|r~r��liner&r&r'r��s
��r�c	Cs�t�|�D]\}}||}|�||���q|j��}|�||�}||krN|j��tks.J�|j�	��t
�|||�Wd�dS1sGwYdSdS)a�Write new content to the working copy and check out the new p1 if any

    We check out a new revision if and only if we fixed something in both the
    working directory and its parent revision. This avoids the need for a full
    update/merge, and means that the working directory simply isn't affected
    unless the --working-dir flag is given.

    Directly updates the dirstate for the affected files.
    N)rr��write�flags�dirstate�p1r��p2r�parentchanger�movedirstate)	rEr;rvrxr9r5r��oldp1�newp1r&r&r'rm�s

"��rmcCs�|j�|���\}}||||}}|�|��|���}	|�|��|���}
|s7|��|vr7|��|vr7dS|����}|��|d<t�	|�}|�
||	�tj||d�t
�|||���|��D]}
||
}|��}|j|
||
|��d�|r�|�|
|�qct�||��dd�|��D��}|j||��||��|	|
f|��d�}|��}|��}||kr�|�d|���dS|||��<dS)	a�Commit a new revision like the given one, but with file content changes

    "ctx" is the original revision to be replaced by a modified one.

    "filedata" is a dict that maps paths to their new file content. All other
    paths will be recreated from the original revision without changes.
    "filedata" may contain paths that didn't exist in the original revision;
    they will be added.

    "replacements" is a dict that maps a single node to a single node, and it is
    updated to indicate the original revision is replaced by the newly created
    one. No entry is added if the replacement's node already exists.

    The new revision has the same parents as the old one, unless those parents
    have already been replaced, in which case those replacements are the parents
    of this new revision. Thus, if revisions are replaced in topological order,
    there is no need to rebase them into the original topology later.
    Ns
fix_source)�wc)r�cSr�r&r&)r��oldnode�newnoder&r&r'r�Jszreplacerev.<locals>.<dictcomp>)�text�branch�extra�dater��usersnode %s already existed
)�	changelog�
parentrevsr|r��noder�copy�hexr	�overlayworkingctx�setbaser�	revert_tor
�graftcopiesr��keys�
copysourcer�r��
markcopiedr�update_hash_refs�descriptionr7�tomemctxrrr�commitr�)r#rEr;rvrx�p1rev�p2rev�p1ctx�p2ctx�	newp1node�	newp2noder�wctxr9r�r�desc�memctx�sucnode�prenoder&r&r'rosP	�
���	roc
Csi}t|�D]n}|�d|d�}|�d|d�}|�d|d�}|�d|d�}|�d|d�}|�d|d�}|�d|d�}	|d	urO|�td
�|f�q|d	ur^|�td�|f�q|si|�d|f�qt||||||	�||<qt�	t
|��d
d�dd��S)z�Returns a map of configured fixer tools indexed by their names

    Each value is a Fixer object with methods that implement the behavior of the
    fixer's config suboptions. Does not validate the config values.
    rs:enableds:commands:patterns
:lineranges	:prioritys	:metadatas
:skipcleanNs,fixer tool has no command configuration: %s
s,fixer tool has no pattern configuration: %s
s!ignoring disabled fixer tool: %s
cSs
|djS)NrP)�	_priorityrLr&r&r'�<lambda>�s
zgetfixers.<locals>.<lambda>T)�keyrH)�
fixernames�
configboolr!�	configintr�rr��Fixerr`�OrderedDictrdr7)
r#rC�name�enabledr��pattern�	linerange�priorityr=�	skipcleanr&r&r'r]^s2��
��r]cCs<t�}|�d�D]\}}d|vr|�|�dd�d�q|S)z>Returns the names of [fix] config options that have suboptionsr�:rPr)r��configitemsr�r�)r#�names�k�vr&r&r'r&�s�r&c@s0eZdZdZdd�Zdd�Zdd�Zdd	�Zd
S)r)z4Wraps the raw config values for a fixer with methodscCs(||_||_||_||_||_||_dSr4)�_command�_pattern�
_lineranger#�	_metadata�
_skipclean)�selfr�r-r.r/r=r0r&r&r'�__init__�s
zFixer.__init__cCs*|��}tj|j|j|jg|d�}||�S)z@Should this fixer run on the file at the given path and context?)r;)rE�matchmodr
r�r7)r;rDr�r9rE�matcherr&r&r'r��s
�z
Fixer.affectscCs|jS)z@Should the stdout of this fixer start with JSON and a null byte?)r9)r;r&r&r'r��szFixer.shouldoutputmetadatac	Csjtj}|||j|tj�|�d��g}|jr0|jr|sdS|D]\}}|�|||j||d���qd�	|�S)z�A shell command to use to invoke this fixer on the given file/lines

        May return None if there is no appropriate command to run for the given
        parameters.
        )srootpathsbasenameN)sfirstslast� )
r�rendercommandtemplater6�osr9�basenamer8r:ri�join)r;r#r9r��expand�parts�first�lastr&r&r'r��s"��
��
z
Fixer.commandN)�__name__�
__module__�__qualname__�__doc__r<r�r�r�r&r&r&r'r)�s
r)r4)GrK�
__future__rr`r�rAr�r��mercurial.i18nr�mercurial.noderrr�mercurial.utilsr�	mercurialrr	r
rrr
r=rrrr�rrrrrr�
testedwith�cmdtabler��configtable�
configitem�FIXER_ATTRSr7r%rr(�allopt�baseopt�revopt�	sourceopt�wdiropt�wholeopt�usage�CATEGORY_FILE_CONTENTSr�rpr[rYr�r�r\r�r�rZr^r6r�rmror]r&�objectr)r&r&r&r'�<module>s�vD

�

����
> #/@L&