Using `printf` to print variable containing `%` percent sign results in “bash: printf: `p': invalid format...





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I want to use printf to print a variable. It might be possible that this variable contains a % percent sign.



Minimal example:



$ TEST="contains % percent"
$ echo "${TEST}"
contains % percent
$ printf "${TEST}n"
bash: printf: `p': invalid format character
contains $


(echo provides the desired output.)










share|improve this question




















  • 1





    The docs are pretty clear that the first parameter is supposed to be a format string.

    – David Schwartz
    May 16 at 21:12






  • 1





    Not sure why some people need to downvote this. A lot of newcomers will make that mistake, so imo it's a very valuable question.

    – pLumo
    May 17 at 7:06




















0















I want to use printf to print a variable. It might be possible that this variable contains a % percent sign.



Minimal example:



$ TEST="contains % percent"
$ echo "${TEST}"
contains % percent
$ printf "${TEST}n"
bash: printf: `p': invalid format character
contains $


(echo provides the desired output.)










share|improve this question




















  • 1





    The docs are pretty clear that the first parameter is supposed to be a format string.

    – David Schwartz
    May 16 at 21:12






  • 1





    Not sure why some people need to downvote this. A lot of newcomers will make that mistake, so imo it's a very valuable question.

    – pLumo
    May 17 at 7:06
















0












0








0








I want to use printf to print a variable. It might be possible that this variable contains a % percent sign.



Minimal example:



$ TEST="contains % percent"
$ echo "${TEST}"
contains % percent
$ printf "${TEST}n"
bash: printf: `p': invalid format character
contains $


(echo provides the desired output.)










share|improve this question
















I want to use printf to print a variable. It might be possible that this variable contains a % percent sign.



Minimal example:



$ TEST="contains % percent"
$ echo "${TEST}"
contains % percent
$ printf "${TEST}n"
bash: printf: `p': invalid format character
contains $


(echo provides the desired output.)







bash variable echo escape-characters printf






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 16 at 15:32







finefoot

















asked May 16 at 15:31









finefootfinefoot

424112




424112








  • 1





    The docs are pretty clear that the first parameter is supposed to be a format string.

    – David Schwartz
    May 16 at 21:12






  • 1





    Not sure why some people need to downvote this. A lot of newcomers will make that mistake, so imo it's a very valuable question.

    – pLumo
    May 17 at 7:06
















  • 1





    The docs are pretty clear that the first parameter is supposed to be a format string.

    – David Schwartz
    May 16 at 21:12






  • 1





    Not sure why some people need to downvote this. A lot of newcomers will make that mistake, so imo it's a very valuable question.

    – pLumo
    May 17 at 7:06










1




1





The docs are pretty clear that the first parameter is supposed to be a format string.

– David Schwartz
May 16 at 21:12





The docs are pretty clear that the first parameter is supposed to be a format string.

– David Schwartz
May 16 at 21:12




1




1





Not sure why some people need to downvote this. A lot of newcomers will make that mistake, so imo it's a very valuable question.

– pLumo
May 17 at 7:06







Not sure why some people need to downvote this. A lot of newcomers will make that mistake, so imo it's a very valuable question.

– pLumo
May 17 at 7:06












3 Answers
3






active

oldest

votes


















12














Use printf in its normal form:



printf '%sn' "${TEST}"


From man printf:




SYNOPSIS
printf FORMAT [ARGUMENT]...





You should never pass a variable to the FORMAT string as it may lead to errors and security vulnerabilities.





Btw:



if you want to have % sign as part of the FORMAT, you need to enter %%, e.g.:



$ printf '%d%%n' 100
100%





share|improve this answer


























  • Do you really need "${TEST}", can't it be "$TEST"?

    – Ferrybig
    May 16 at 17:15











  • "$TEST" is enough.

    – pLumo
    May 16 at 17:41








  • 2





    +1. But it's not just 'normal', it's necessary. Passing a variable to printf's first parameter is Christmas to hackers. Never do it. That is part of secure software dev 101.

    – Jeffrey
    May 16 at 21:24











  • @Jeffrey Most of the potential vulnerabilities in printf are only applicable to the C function. There aren't as many evil things you can do by passing a bad format string to /usr/bin/printf (or the equivalent shell builtin).

    – duskwuff
    May 16 at 21:56











  • @duskwuff you can do variable assignment using bash's printf, and variable assignments can lead to a lot more (e.g., shellshock in days past)

    – muru
    May 17 at 1:56



















9














You should never put variable content in the format string given to printf. Use this instead:



printf '%sn' "${TEST}"





share|improve this answer































    3














    printf takes one guaranteed parameter, and then a number of additional parameters based on what you pass. So something like this:



    printf '%07.2f' 5


    gets turned into:



    0005.00


    The first parameter, called "format", is always present. If it contains no %strings, it's simply printed. Thus:



    printf Hello


    produces simply Hello (notably, without the trailing newline echo would add in its default mode). In expecting your example to work, you have been misled by your own previous (unknowing) abuse of this fact; because you only passed strings without %s into format, from printf's point of view, you kept asking it to output things that required no substitutions, so it pretty much functioned like echo -ne.



    If you want to do this right, you probably want to start forming your printable strings with printf's builtin substitution capabilities. Lines like this appear all over my code:



    printf '%20s: %6d %05d.%02d%%' "$key" $val $((val/max)) $((val*100/max%100))


    If you want exactly what you're currently doing now to work, you want echo -ne, as so:



    TEST="contains % percent"
    echo -ne "${TEST}n"


    That preserves the (questionable) behavior of interpreting escapes inside the variable. It also seems a little silly to supply -n and then stick the n back on, but I offer it because it's a global find-and-replace you can apply to everything you're current doing. A cleaner version that still keeps escapes working in the variable would be:



    TEST="contains % percent"
    echo -e "$TEST"





    share|improve this answer
























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "106"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f519315%2fusing-printf-to-print-variable-containing-percent-sign-results-in-bash-p%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      12














      Use printf in its normal form:



      printf '%sn' "${TEST}"


      From man printf:




      SYNOPSIS
      printf FORMAT [ARGUMENT]...





      You should never pass a variable to the FORMAT string as it may lead to errors and security vulnerabilities.





      Btw:



      if you want to have % sign as part of the FORMAT, you need to enter %%, e.g.:



      $ printf '%d%%n' 100
      100%





      share|improve this answer


























      • Do you really need "${TEST}", can't it be "$TEST"?

        – Ferrybig
        May 16 at 17:15











      • "$TEST" is enough.

        – pLumo
        May 16 at 17:41








      • 2





        +1. But it's not just 'normal', it's necessary. Passing a variable to printf's first parameter is Christmas to hackers. Never do it. That is part of secure software dev 101.

        – Jeffrey
        May 16 at 21:24











      • @Jeffrey Most of the potential vulnerabilities in printf are only applicable to the C function. There aren't as many evil things you can do by passing a bad format string to /usr/bin/printf (or the equivalent shell builtin).

        – duskwuff
        May 16 at 21:56











      • @duskwuff you can do variable assignment using bash's printf, and variable assignments can lead to a lot more (e.g., shellshock in days past)

        – muru
        May 17 at 1:56
















      12














      Use printf in its normal form:



      printf '%sn' "${TEST}"


      From man printf:




      SYNOPSIS
      printf FORMAT [ARGUMENT]...





      You should never pass a variable to the FORMAT string as it may lead to errors and security vulnerabilities.





      Btw:



      if you want to have % sign as part of the FORMAT, you need to enter %%, e.g.:



      $ printf '%d%%n' 100
      100%





      share|improve this answer


























      • Do you really need "${TEST}", can't it be "$TEST"?

        – Ferrybig
        May 16 at 17:15











      • "$TEST" is enough.

        – pLumo
        May 16 at 17:41








      • 2





        +1. But it's not just 'normal', it's necessary. Passing a variable to printf's first parameter is Christmas to hackers. Never do it. That is part of secure software dev 101.

        – Jeffrey
        May 16 at 21:24











      • @Jeffrey Most of the potential vulnerabilities in printf are only applicable to the C function. There aren't as many evil things you can do by passing a bad format string to /usr/bin/printf (or the equivalent shell builtin).

        – duskwuff
        May 16 at 21:56











      • @duskwuff you can do variable assignment using bash's printf, and variable assignments can lead to a lot more (e.g., shellshock in days past)

        – muru
        May 17 at 1:56














      12












      12








      12







      Use printf in its normal form:



      printf '%sn' "${TEST}"


      From man printf:




      SYNOPSIS
      printf FORMAT [ARGUMENT]...





      You should never pass a variable to the FORMAT string as it may lead to errors and security vulnerabilities.





      Btw:



      if you want to have % sign as part of the FORMAT, you need to enter %%, e.g.:



      $ printf '%d%%n' 100
      100%





      share|improve this answer















      Use printf in its normal form:



      printf '%sn' "${TEST}"


      From man printf:




      SYNOPSIS
      printf FORMAT [ARGUMENT]...





      You should never pass a variable to the FORMAT string as it may lead to errors and security vulnerabilities.





      Btw:



      if you want to have % sign as part of the FORMAT, you need to enter %%, e.g.:



      $ printf '%d%%n' 100
      100%






      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited May 17 at 7:01

























      answered May 16 at 15:32









      pLumopLumo

      5,9371225




      5,9371225













      • Do you really need "${TEST}", can't it be "$TEST"?

        – Ferrybig
        May 16 at 17:15











      • "$TEST" is enough.

        – pLumo
        May 16 at 17:41








      • 2





        +1. But it's not just 'normal', it's necessary. Passing a variable to printf's first parameter is Christmas to hackers. Never do it. That is part of secure software dev 101.

        – Jeffrey
        May 16 at 21:24











      • @Jeffrey Most of the potential vulnerabilities in printf are only applicable to the C function. There aren't as many evil things you can do by passing a bad format string to /usr/bin/printf (or the equivalent shell builtin).

        – duskwuff
        May 16 at 21:56











      • @duskwuff you can do variable assignment using bash's printf, and variable assignments can lead to a lot more (e.g., shellshock in days past)

        – muru
        May 17 at 1:56



















      • Do you really need "${TEST}", can't it be "$TEST"?

        – Ferrybig
        May 16 at 17:15











      • "$TEST" is enough.

        – pLumo
        May 16 at 17:41








      • 2





        +1. But it's not just 'normal', it's necessary. Passing a variable to printf's first parameter is Christmas to hackers. Never do it. That is part of secure software dev 101.

        – Jeffrey
        May 16 at 21:24











      • @Jeffrey Most of the potential vulnerabilities in printf are only applicable to the C function. There aren't as many evil things you can do by passing a bad format string to /usr/bin/printf (or the equivalent shell builtin).

        – duskwuff
        May 16 at 21:56











      • @duskwuff you can do variable assignment using bash's printf, and variable assignments can lead to a lot more (e.g., shellshock in days past)

        – muru
        May 17 at 1:56

















      Do you really need "${TEST}", can't it be "$TEST"?

      – Ferrybig
      May 16 at 17:15





      Do you really need "${TEST}", can't it be "$TEST"?

      – Ferrybig
      May 16 at 17:15













      "$TEST" is enough.

      – pLumo
      May 16 at 17:41







      "$TEST" is enough.

      – pLumo
      May 16 at 17:41






      2




      2





      +1. But it's not just 'normal', it's necessary. Passing a variable to printf's first parameter is Christmas to hackers. Never do it. That is part of secure software dev 101.

      – Jeffrey
      May 16 at 21:24





      +1. But it's not just 'normal', it's necessary. Passing a variable to printf's first parameter is Christmas to hackers. Never do it. That is part of secure software dev 101.

      – Jeffrey
      May 16 at 21:24













      @Jeffrey Most of the potential vulnerabilities in printf are only applicable to the C function. There aren't as many evil things you can do by passing a bad format string to /usr/bin/printf (or the equivalent shell builtin).

      – duskwuff
      May 16 at 21:56





      @Jeffrey Most of the potential vulnerabilities in printf are only applicable to the C function. There aren't as many evil things you can do by passing a bad format string to /usr/bin/printf (or the equivalent shell builtin).

      – duskwuff
      May 16 at 21:56













      @duskwuff you can do variable assignment using bash's printf, and variable assignments can lead to a lot more (e.g., shellshock in days past)

      – muru
      May 17 at 1:56





      @duskwuff you can do variable assignment using bash's printf, and variable assignments can lead to a lot more (e.g., shellshock in days past)

      – muru
      May 17 at 1:56













      9














      You should never put variable content in the format string given to printf. Use this instead:



      printf '%sn' "${TEST}"





      share|improve this answer




























        9














        You should never put variable content in the format string given to printf. Use this instead:



        printf '%sn' "${TEST}"





        share|improve this answer


























          9












          9








          9







          You should never put variable content in the format string given to printf. Use this instead:



          printf '%sn' "${TEST}"





          share|improve this answer













          You should never put variable content in the format string given to printf. Use this instead:



          printf '%sn' "${TEST}"






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered May 16 at 15:32









          Stephen KittStephen Kitt

          190k26448524




          190k26448524























              3














              printf takes one guaranteed parameter, and then a number of additional parameters based on what you pass. So something like this:



              printf '%07.2f' 5


              gets turned into:



              0005.00


              The first parameter, called "format", is always present. If it contains no %strings, it's simply printed. Thus:



              printf Hello


              produces simply Hello (notably, without the trailing newline echo would add in its default mode). In expecting your example to work, you have been misled by your own previous (unknowing) abuse of this fact; because you only passed strings without %s into format, from printf's point of view, you kept asking it to output things that required no substitutions, so it pretty much functioned like echo -ne.



              If you want to do this right, you probably want to start forming your printable strings with printf's builtin substitution capabilities. Lines like this appear all over my code:



              printf '%20s: %6d %05d.%02d%%' "$key" $val $((val/max)) $((val*100/max%100))


              If you want exactly what you're currently doing now to work, you want echo -ne, as so:



              TEST="contains % percent"
              echo -ne "${TEST}n"


              That preserves the (questionable) behavior of interpreting escapes inside the variable. It also seems a little silly to supply -n and then stick the n back on, but I offer it because it's a global find-and-replace you can apply to everything you're current doing. A cleaner version that still keeps escapes working in the variable would be:



              TEST="contains % percent"
              echo -e "$TEST"





              share|improve this answer




























                3














                printf takes one guaranteed parameter, and then a number of additional parameters based on what you pass. So something like this:



                printf '%07.2f' 5


                gets turned into:



                0005.00


                The first parameter, called "format", is always present. If it contains no %strings, it's simply printed. Thus:



                printf Hello


                produces simply Hello (notably, without the trailing newline echo would add in its default mode). In expecting your example to work, you have been misled by your own previous (unknowing) abuse of this fact; because you only passed strings without %s into format, from printf's point of view, you kept asking it to output things that required no substitutions, so it pretty much functioned like echo -ne.



                If you want to do this right, you probably want to start forming your printable strings with printf's builtin substitution capabilities. Lines like this appear all over my code:



                printf '%20s: %6d %05d.%02d%%' "$key" $val $((val/max)) $((val*100/max%100))


                If you want exactly what you're currently doing now to work, you want echo -ne, as so:



                TEST="contains % percent"
                echo -ne "${TEST}n"


                That preserves the (questionable) behavior of interpreting escapes inside the variable. It also seems a little silly to supply -n and then stick the n back on, but I offer it because it's a global find-and-replace you can apply to everything you're current doing. A cleaner version that still keeps escapes working in the variable would be:



                TEST="contains % percent"
                echo -e "$TEST"





                share|improve this answer


























                  3












                  3








                  3







                  printf takes one guaranteed parameter, and then a number of additional parameters based on what you pass. So something like this:



                  printf '%07.2f' 5


                  gets turned into:



                  0005.00


                  The first parameter, called "format", is always present. If it contains no %strings, it's simply printed. Thus:



                  printf Hello


                  produces simply Hello (notably, without the trailing newline echo would add in its default mode). In expecting your example to work, you have been misled by your own previous (unknowing) abuse of this fact; because you only passed strings without %s into format, from printf's point of view, you kept asking it to output things that required no substitutions, so it pretty much functioned like echo -ne.



                  If you want to do this right, you probably want to start forming your printable strings with printf's builtin substitution capabilities. Lines like this appear all over my code:



                  printf '%20s: %6d %05d.%02d%%' "$key" $val $((val/max)) $((val*100/max%100))


                  If you want exactly what you're currently doing now to work, you want echo -ne, as so:



                  TEST="contains % percent"
                  echo -ne "${TEST}n"


                  That preserves the (questionable) behavior of interpreting escapes inside the variable. It also seems a little silly to supply -n and then stick the n back on, but I offer it because it's a global find-and-replace you can apply to everything you're current doing. A cleaner version that still keeps escapes working in the variable would be:



                  TEST="contains % percent"
                  echo -e "$TEST"





                  share|improve this answer













                  printf takes one guaranteed parameter, and then a number of additional parameters based on what you pass. So something like this:



                  printf '%07.2f' 5


                  gets turned into:



                  0005.00


                  The first parameter, called "format", is always present. If it contains no %strings, it's simply printed. Thus:



                  printf Hello


                  produces simply Hello (notably, without the trailing newline echo would add in its default mode). In expecting your example to work, you have been misled by your own previous (unknowing) abuse of this fact; because you only passed strings without %s into format, from printf's point of view, you kept asking it to output things that required no substitutions, so it pretty much functioned like echo -ne.



                  If you want to do this right, you probably want to start forming your printable strings with printf's builtin substitution capabilities. Lines like this appear all over my code:



                  printf '%20s: %6d %05d.%02d%%' "$key" $val $((val/max)) $((val*100/max%100))


                  If you want exactly what you're currently doing now to work, you want echo -ne, as so:



                  TEST="contains % percent"
                  echo -ne "${TEST}n"


                  That preserves the (questionable) behavior of interpreting escapes inside the variable. It also seems a little silly to supply -n and then stick the n back on, but I offer it because it's a global find-and-replace you can apply to everything you're current doing. A cleaner version that still keeps escapes working in the variable would be:



                  TEST="contains % percent"
                  echo -e "$TEST"






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered May 16 at 20:39









                  BMDanBMDan

                  1313




                  1313






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f519315%2fusing-printf-to-print-variable-containing-percent-sign-results-in-bash-p%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Bruad Bilen | Luke uk diar | NawigatsjuunCommonskategorii: BruadCommonskategorii: RunstükenWikiquote: Bruad

                      What is the offset in a seaplane's hull?

                      Slayer Innehåll Historia | Stil, komposition och lyrik | Bandets betydelse och framgångar | Sidoprojekt och samarbeten | Kontroverser | Medlemmar | Utmärkelser och nomineringar | Turnéer och festivaler | Diskografi | Referenser | Externa länkar | Navigeringsmenywww.slayer.net”Metal Massacre vol. 1””Metal Massacre vol. 3””Metal Massacre Volume III””Show No Mercy””Haunting the Chapel””Live Undead””Hell Awaits””Reign in Blood””Reign in Blood””Gold & Platinum – Reign in Blood””Golden Gods Awards Winners”originalet”Kerrang! Hall Of Fame””Slayer Looks Back On 37-Year Career In New Video Series: Part Two””South of Heaven””Gold & Platinum – South of Heaven””Seasons in the Abyss””Gold & Platinum - Seasons in the Abyss””Divine Intervention””Divine Intervention - Release group by Slayer””Gold & Platinum - Divine Intervention””Live Intrusion””Undisputed Attitude””Abolish Government/Superficial Love””Release “Slatanic Slaughter: A Tribute to Slayer” by Various Artists””Diabolus in Musica””Soundtrack to the Apocalypse””God Hates Us All””Systematic - Relationships””War at the Warfield””Gold & Platinum - War at the Warfield””Soundtrack to the Apocalypse””Gold & Platinum - Still Reigning””Metallica, Slayer, Iron Mauden Among Winners At Metal Hammer Awards””Eternal Pyre””Eternal Pyre - Slayer release group””Eternal Pyre””Metal Storm Awards 2006””Kerrang! Hall Of Fame””Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Bullet-For My Valentine booed at Metal Hammer Golden Gods Awards””Unholy Aliance””The End Of Slayer?””Slayer: We Could Thrash Out Two More Albums If We're Fast Enough...””'The Unholy Alliance: Chapter III' UK Dates Added”originalet”Megadeth And Slayer To Co-Headline 'Canadian Carnage' Trek”originalet”World Painted Blood””Release “World Painted Blood” by Slayer””Metallica Heading To Cinemas””Slayer, Megadeth To Join Forces For 'European Carnage' Tour - Dec. 18, 2010”originalet”Slayer's Hanneman Contracts Acute Infection; Band To Bring In Guest Guitarist””Cannibal Corpse's Pat O'Brien Will Step In As Slayer's Guest Guitarist”originalet”Slayer’s Jeff Hanneman Dead at 49””Dave Lombardo Says He Made Only $67,000 In 2011 While Touring With Slayer””Slayer: We Do Not Agree With Dave Lombardo's Substance Or Timeline Of Events””Slayer Welcomes Drummer Paul Bostaph Back To The Fold””Slayer Hope to Unveil Never-Before-Heard Jeff Hanneman Material on Next Album””Slayer Debut New Song 'Implode' During Surprise Golden Gods Appearance””Release group Repentless by Slayer””Repentless - Slayer - Credits””Slayer””Metal Storm Awards 2015””Slayer - to release comic book "Repentless #1"””Slayer To Release 'Repentless' 6.66" Vinyl Box Set””BREAKING NEWS: Slayer Announce Farewell Tour””Slayer Recruit Lamb of God, Anthrax, Behemoth + Testament for Final Tour””Slayer lägger ner efter 37 år””Slayer Announces Second North American Leg Of 'Final' Tour””Final World Tour””Slayer Announces Final European Tour With Lamb of God, Anthrax And Obituary””Slayer To Tour Europe With Lamb of God, Anthrax And Obituary””Slayer To Play 'Last French Show Ever' At Next Year's Hellfst””Slayer's Final World Tour Will Extend Into 2019””Death Angel's Rob Cavestany On Slayer's 'Farewell' Tour: 'Some Of Us Could See This Coming'””Testament Has No Plans To Retire Anytime Soon, Says Chuck Billy””Anthrax's Scott Ian On Slayer's 'Farewell' Tour Plans: 'I Was Surprised And I Wasn't Surprised'””Slayer””Slayer's Morbid Schlock””Review/Rock; For Slayer, the Mania Is the Message””Slayer - Biography””Slayer - Reign In Blood”originalet”Dave Lombardo””An exclusive oral history of Slayer”originalet”Exclusive! Interview With Slayer Guitarist Jeff Hanneman”originalet”Thinking Out Loud: Slayer's Kerry King on hair metal, Satan and being polite””Slayer Lyrics””Slayer - Biography””Most influential artists for extreme metal music””Slayer - Reign in Blood””Slayer guitarist Jeff Hanneman dies aged 49””Slatanic Slaughter: A Tribute to Slayer””Gateway to Hell: A Tribute to Slayer””Covered In Blood””Slayer: The Origins of Thrash in San Francisco, CA.””Why They Rule - #6 Slayer”originalet”Guitar World's 100 Greatest Heavy Metal Guitarists Of All Time”originalet”The fans have spoken: Slayer comes out on top in readers' polls”originalet”Tribute to Jeff Hanneman (1964-2013)””Lamb Of God Frontman: We Sound Like A Slayer Rip-Off””BEHEMOTH Frontman Pays Tribute To SLAYER's JEFF HANNEMAN””Slayer, Hatebreed Doing Double Duty On This Year's Ozzfest””System of a Down””Lacuna Coil’s Andrea Ferro Talks Influences, Skateboarding, Band Origins + More””Slayer - Reign in Blood””Into The Lungs of Hell””Slayer rules - en utställning om fans””Slayer and Their Fans Slashed Through a No-Holds-Barred Night at Gas Monkey””Home””Slayer””Gold & Platinum - The Big 4 Live from Sofia, Bulgaria””Exclusive! Interview With Slayer Guitarist Kerry King””2008-02-23: Wiltern, Los Angeles, CA, USA””Slayer's Kerry King To Perform With Megadeth Tonight! - Oct. 21, 2010”originalet”Dave Lombardo - Biography”Slayer Case DismissedArkiveradUltimate Classic Rock: Slayer guitarist Jeff Hanneman dead at 49.”Slayer: "We could never do any thing like Some Kind Of Monster..."””Cannibal Corpse'S Pat O'Brien Will Step In As Slayer'S Guest Guitarist | The Official Slayer Site”originalet”Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Kerrang! Awards 2006 Blog: Kerrang! Hall Of Fame””Kerrang! Awards 2013: Kerrang! Legend”originalet”Metallica, Slayer, Iron Maien Among Winners At Metal Hammer Awards””Metal Hammer Golden Gods Awards””Bullet For My Valentine Booed At Metal Hammer Golden Gods Awards””Metal Storm Awards 2006””Metal Storm Awards 2015””Slayer's Concert History””Slayer - Relationships””Slayer - Releases”Slayers officiella webbplatsSlayer på MusicBrainzOfficiell webbplatsSlayerSlayerr1373445760000 0001 1540 47353068615-5086262726cb13906545x(data)6033143kn20030215029