[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Git][lintian/lintian][master] Indent some lists with a single space to fix console output



Title: GitLab

Louis-Philippe Véronneau pushed to branch master at lintian / lintian

Commits:

  • 50aea79b
    by Nicolas Peugnet at 2024-10-29T14:51:47+01:00
    Indent some lists with a single space to fix console output
    
    It seems lintian-explain-tags does not really understand the Markdown
    list syntax, so to keep a single entry by line in the console output
    we indent the lists with a single space. This will not impact the
    output of Lintian SSG, as the list parser has a higher priority than
    the code block parser. Also, most of the lists are already indented
    this way.
    

2 changed files:

Changes:

  • tags/p/privacy-breach-statistics-website.tag
    ... ... @@ -9,13 +9,13 @@ Explanation: This package creates a privacy breach by fetching data from
    9 9
      .
    
    10 10
      This tag covers the following websites:
    
    11 11
      .
    
    12
    - - cruel-carlota.pagodabox.com
    
    13
    - - linkexchange.com (defunct)
    
    14
    - - nedstatbasic.net
    
    15
    - - onestat.com
    
    16
    - - statcounter.com
    
    17
    - - sitemeter.com
    
    18
    - - webstats.motigo.com
    
    12
    +  - cruel-carlota.pagodabox.com
    
    13
    +  - linkexchange.com (defunct)
    
    14
    +  - nedstatbasic.net
    
    15
    +  - onestat.com
    
    16
    +  - statcounter.com
    
    17
    +  - sitemeter.com
    
    18
    +  - webstats.motigo.com
    
    19 19
      .
    
    20 20
      Please replace any scripts, images, or other remote resources with
    
    21 21
      non-remote resources. It is preferable to replace them with text and
    

  • tags/u/unicode-trojan.tag
    ... ... @@ -12,18 +12,18 @@ Explanation: The named text file contains a Unicode codepoint that has been
    12 12
      .
    
    13 13
      Here are the relevant codepoints:
    
    14 14
      .
    
    15
    - - ARABIC LETTER MARK (<code>U+061C</code>)
    
    16
    - - LEFT-TO-RIGHT MARK (<code>U+200E</code>)
    
    17
    - - RIGHT-TO-LEFT MARK (<code>U+200F</code>)
    
    18
    - - LEFT-TO-RIGHT EMBEDDING (<code>U+202A</code>)
    
    19
    - - RIGHT-TO-LEFT EMBEDDING (<code>U+202B</code>)
    
    20
    - - POP DIRECTIONAL FORMATTING (<code>U+202C</code>)
    
    21
    - - LEFT-TO-RIGHT OVERRIDE (<code>U+202D</code>)
    
    22
    - - RIGHT-TO-LEFT OVERRIDE (<code>U+202E</code>)
    
    23
    - - LEFT-TO-RIGHT ISOLATE (<code>U+2066</code>)
    
    24
    - - RIGHT-TO-LEFT ISOLATE (<code>U+2067</code>)
    
    25
    - - FIRST STRONG ISOLATE (<code>U+2068</code>)
    
    26
    - - POP DIRECTIONAL ISOLATE (<code>U+2069</code>)
    
    15
    +  - ARABIC LETTER MARK (<code>U+061C</code>)
    
    16
    +  - LEFT-TO-RIGHT MARK (<code>U+200E</code>)
    
    17
    +  - RIGHT-TO-LEFT MARK (<code>U+200F</code>)
    
    18
    +  - LEFT-TO-RIGHT EMBEDDING (<code>U+202A</code>)
    
    19
    +  - RIGHT-TO-LEFT EMBEDDING (<code>U+202B</code>)
    
    20
    +  - POP DIRECTIONAL FORMATTING (<code>U+202C</code>)
    
    21
    +  - LEFT-TO-RIGHT OVERRIDE (<code>U+202D</code>)
    
    22
    +  - RIGHT-TO-LEFT OVERRIDE (<code>U+202E</code>)
    
    23
    +  - LEFT-TO-RIGHT ISOLATE (<code>U+2066</code>)
    
    24
    +  - RIGHT-TO-LEFT ISOLATE (<code>U+2067</code>)
    
    25
    +  - FIRST STRONG ISOLATE (<code>U+2068</code>)
    
    26
    +  - POP DIRECTIONAL ISOLATE (<code>U+2069</code>)
    
    27 27
      .
    
    28 28
      You can also run a similar check in your shell with that command:
    
    29 29
      .
    


  • Reply to: