node command while defining a coordinate in TikZ Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar ManaraStrange behavior in TikZ draw commandWeird diagonal under legends with TikzpictureHow to define the default vertical distance between nodes?Numerical conditional within tikz keys?Help understanding the coordinate system used in tikzWhy do I get an extra white page before my TikZ picture?figure 2 for Crossed Ladders ProblemTikZ: Drawing an arc from an intersection to an intersectionDrawing rectilinear curves in Tikz, aka an Etch-a-Sketch drawingLine up nested tikz enviroments or how to get rid of themHow to draw a square and its diagonals with arrows?Include node at end point tikz decorations

Why do people think Winterfell crypts is the safest place for women, children & old people?

Did war bonds have better investment alternatives during WWII?

Israeli soda type drink

Does using the Inspiration rules for character defects encourage My Guy Syndrome?

Can gravitational waves pass through a black hole?

Why isPrototypeOf() returns false?

In search of the origins of term censor, I hit a dead end stuck with the greek term, to censor, λογοκρίνω

Protagonist's race is hidden - should I reveal it?

Why does the Cisco show run command not show the full version, while the show version command does?

How would you suggest I follow up with coworkers about our deadline that's today?

Why doesn't the university give past final exams' answers?

How can I wire a 9-position switch so that each position turns on one more LED than the one before?

Co-worker works way more than he should

What's the difference between using dependency injection with a container and using a service locator?

Why did Europeans not widely domesticate foxes?

What is a good proxy for government quality?

Is it accepted to use working hours to read general interest books?

Is it OK if I do not take the receipt in Germany?

Determinant of a matrix with 2 equal rows

What is the evidence that custom checks in Northern Ireland are going to result in violence?

Will I be more secure with my own router behind my ISP's router?

/bin/ls sorts differently than just ls

Arriving in Atlanta after US Preclearance in Dublin. Will I go through TSA security in Atlanta to transfer to a connecting flight?

What *exactly* is electrical current, voltage, and resistance?



node command while defining a coordinate in TikZ



Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar ManaraStrange behavior in TikZ draw commandWeird diagonal under legends with TikzpictureHow to define the default vertical distance between nodes?Numerical conditional within tikz keys?Help understanding the coordinate system used in tikzWhy do I get an extra white page before my TikZ picture?figure 2 for Crossed Ladders ProblemTikZ: Drawing an arc from an intersection to an intersectionDrawing rectilinear curves in Tikz, aka an Etch-a-Sketch drawingLine up nested tikz enviroments or how to get rid of themHow to draw a square and its diagonals with arrows?Include node at end point tikz decorations










6















This question is related to Strange behavior in TikZ draw command but is not the same.



While working with coordinates and nodes in TikZ, I was expecting that:



 coordinate (x) at (4,0) node[right] $x$;
coordinate (y) at (0,3) node[above] $y$;


and



 node[right] at (x) $x$;
node[above] at (y) $y$;


would yield the same result. But they don't. I get the following output:



enter image description here



With coordinate (x) at (4,0) node[right] $x$;, I meant, the system will create a node at (4,0) and will place the text $x$ to its right.



Based on the output, I see the text $x$ is placed at (0,0), with the above command.



Why does this happen.



MWE:



documentclassarticle
usepackagetikz
usetikzlibraryintersections
begindocument
begintikzpicture
coordinate (x) at (4,0) node[right] $x$;
coordinate (y) at (0,3) node[above] $y$;

node[right] at (x) $x$;
node[above] at (y) $y$;

draw[<->,thick] (0,3) |- (4,0);
endtikzpicture
enddocument









share|improve this question



















  • 1





    Why would they? Try path (x) node[right] $x$;path (y) node[above] $y$;. If you give TikZ contradicting instructions, or place the instructions in the wrong order, you will get an unexpected result. BTW, you expect answerers to provide you with a full MWE, i.e. a document that starts with documentclass etc. Could you please consider also using such an MWE in your question?

    – marmot
    Mar 25 at 16:53












  • @marmot - I have added the MWE.

    – subham soni
    Mar 25 at 16:59











  • A trick to solve all these mysteries: just add draw option to the nodes, and you will probably see the difference.

    – JouleV
    Mar 25 at 17:02











  • @JouleV - That would still not explain why it happens. I am more interested in the why part.

    – subham soni
    Mar 25 at 17:07






  • 1





    The "why part" is simply that in coordinate (x) at (4,0) node[right] $x$; the at (4,0) gets eaten up by coordinate (x) at and then TikZ "sees" node[right] $x$ and inserts the default coordinate (0,0) to parse it.

    – marmot
    Mar 25 at 18:51















6















This question is related to Strange behavior in TikZ draw command but is not the same.



While working with coordinates and nodes in TikZ, I was expecting that:



 coordinate (x) at (4,0) node[right] $x$;
coordinate (y) at (0,3) node[above] $y$;


and



 node[right] at (x) $x$;
node[above] at (y) $y$;


would yield the same result. But they don't. I get the following output:



enter image description here



With coordinate (x) at (4,0) node[right] $x$;, I meant, the system will create a node at (4,0) and will place the text $x$ to its right.



Based on the output, I see the text $x$ is placed at (0,0), with the above command.



Why does this happen.



MWE:



documentclassarticle
usepackagetikz
usetikzlibraryintersections
begindocument
begintikzpicture
coordinate (x) at (4,0) node[right] $x$;
coordinate (y) at (0,3) node[above] $y$;

node[right] at (x) $x$;
node[above] at (y) $y$;

draw[<->,thick] (0,3) |- (4,0);
endtikzpicture
enddocument









share|improve this question



















  • 1





    Why would they? Try path (x) node[right] $x$;path (y) node[above] $y$;. If you give TikZ contradicting instructions, or place the instructions in the wrong order, you will get an unexpected result. BTW, you expect answerers to provide you with a full MWE, i.e. a document that starts with documentclass etc. Could you please consider also using such an MWE in your question?

    – marmot
    Mar 25 at 16:53












  • @marmot - I have added the MWE.

    – subham soni
    Mar 25 at 16:59











  • A trick to solve all these mysteries: just add draw option to the nodes, and you will probably see the difference.

    – JouleV
    Mar 25 at 17:02











  • @JouleV - That would still not explain why it happens. I am more interested in the why part.

    – subham soni
    Mar 25 at 17:07






  • 1





    The "why part" is simply that in coordinate (x) at (4,0) node[right] $x$; the at (4,0) gets eaten up by coordinate (x) at and then TikZ "sees" node[right] $x$ and inserts the default coordinate (0,0) to parse it.

    – marmot
    Mar 25 at 18:51













6












6








6








This question is related to Strange behavior in TikZ draw command but is not the same.



While working with coordinates and nodes in TikZ, I was expecting that:



 coordinate (x) at (4,0) node[right] $x$;
coordinate (y) at (0,3) node[above] $y$;


and



 node[right] at (x) $x$;
node[above] at (y) $y$;


would yield the same result. But they don't. I get the following output:



enter image description here



With coordinate (x) at (4,0) node[right] $x$;, I meant, the system will create a node at (4,0) and will place the text $x$ to its right.



Based on the output, I see the text $x$ is placed at (0,0), with the above command.



Why does this happen.



MWE:



documentclassarticle
usepackagetikz
usetikzlibraryintersections
begindocument
begintikzpicture
coordinate (x) at (4,0) node[right] $x$;
coordinate (y) at (0,3) node[above] $y$;

node[right] at (x) $x$;
node[above] at (y) $y$;

draw[<->,thick] (0,3) |- (4,0);
endtikzpicture
enddocument









share|improve this question
















This question is related to Strange behavior in TikZ draw command but is not the same.



While working with coordinates and nodes in TikZ, I was expecting that:



 coordinate (x) at (4,0) node[right] $x$;
coordinate (y) at (0,3) node[above] $y$;


and



 node[right] at (x) $x$;
node[above] at (y) $y$;


would yield the same result. But they don't. I get the following output:



enter image description here



With coordinate (x) at (4,0) node[right] $x$;, I meant, the system will create a node at (4,0) and will place the text $x$ to its right.



Based on the output, I see the text $x$ is placed at (0,0), with the above command.



Why does this happen.



MWE:



documentclassarticle
usepackagetikz
usetikzlibraryintersections
begindocument
begintikzpicture
coordinate (x) at (4,0) node[right] $x$;
coordinate (y) at (0,3) node[above] $y$;

node[right] at (x) $x$;
node[above] at (y) $y$;

draw[<->,thick] (0,3) |- (4,0);
endtikzpicture
enddocument






tikz-pgf






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 25 at 16:59







subham soni

















asked Mar 25 at 16:49









subham sonisubham soni

5,07483190




5,07483190







  • 1





    Why would they? Try path (x) node[right] $x$;path (y) node[above] $y$;. If you give TikZ contradicting instructions, or place the instructions in the wrong order, you will get an unexpected result. BTW, you expect answerers to provide you with a full MWE, i.e. a document that starts with documentclass etc. Could you please consider also using such an MWE in your question?

    – marmot
    Mar 25 at 16:53












  • @marmot - I have added the MWE.

    – subham soni
    Mar 25 at 16:59











  • A trick to solve all these mysteries: just add draw option to the nodes, and you will probably see the difference.

    – JouleV
    Mar 25 at 17:02











  • @JouleV - That would still not explain why it happens. I am more interested in the why part.

    – subham soni
    Mar 25 at 17:07






  • 1





    The "why part" is simply that in coordinate (x) at (4,0) node[right] $x$; the at (4,0) gets eaten up by coordinate (x) at and then TikZ "sees" node[right] $x$ and inserts the default coordinate (0,0) to parse it.

    – marmot
    Mar 25 at 18:51












  • 1





    Why would they? Try path (x) node[right] $x$;path (y) node[above] $y$;. If you give TikZ contradicting instructions, or place the instructions in the wrong order, you will get an unexpected result. BTW, you expect answerers to provide you with a full MWE, i.e. a document that starts with documentclass etc. Could you please consider also using such an MWE in your question?

    – marmot
    Mar 25 at 16:53












  • @marmot - I have added the MWE.

    – subham soni
    Mar 25 at 16:59











  • A trick to solve all these mysteries: just add draw option to the nodes, and you will probably see the difference.

    – JouleV
    Mar 25 at 17:02











  • @JouleV - That would still not explain why it happens. I am more interested in the why part.

    – subham soni
    Mar 25 at 17:07






  • 1





    The "why part" is simply that in coordinate (x) at (4,0) node[right] $x$; the at (4,0) gets eaten up by coordinate (x) at and then TikZ "sees" node[right] $x$ and inserts the default coordinate (0,0) to parse it.

    – marmot
    Mar 25 at 18:51







1




1





Why would they? Try path (x) node[right] $x$;path (y) node[above] $y$;. If you give TikZ contradicting instructions, or place the instructions in the wrong order, you will get an unexpected result. BTW, you expect answerers to provide you with a full MWE, i.e. a document that starts with documentclass etc. Could you please consider also using such an MWE in your question?

– marmot
Mar 25 at 16:53






Why would they? Try path (x) node[right] $x$;path (y) node[above] $y$;. If you give TikZ contradicting instructions, or place the instructions in the wrong order, you will get an unexpected result. BTW, you expect answerers to provide you with a full MWE, i.e. a document that starts with documentclass etc. Could you please consider also using such an MWE in your question?

– marmot
Mar 25 at 16:53














@marmot - I have added the MWE.

– subham soni
Mar 25 at 16:59





@marmot - I have added the MWE.

– subham soni
Mar 25 at 16:59













A trick to solve all these mysteries: just add draw option to the nodes, and you will probably see the difference.

– JouleV
Mar 25 at 17:02





A trick to solve all these mysteries: just add draw option to the nodes, and you will probably see the difference.

– JouleV
Mar 25 at 17:02













@JouleV - That would still not explain why it happens. I am more interested in the why part.

– subham soni
Mar 25 at 17:07





@JouleV - That would still not explain why it happens. I am more interested in the why part.

– subham soni
Mar 25 at 17:07




1




1





The "why part" is simply that in coordinate (x) at (4,0) node[right] $x$; the at (4,0) gets eaten up by coordinate (x) at and then TikZ "sees" node[right] $x$ and inserts the default coordinate (0,0) to parse it.

– marmot
Mar 25 at 18:51





The "why part" is simply that in coordinate (x) at (4,0) node[right] $x$; the at (4,0) gets eaten up by coordinate (x) at and then TikZ "sees" node[right] $x$ and inserts the default coordinate (0,0) to parse it.

– marmot
Mar 25 at 18:51










3 Answers
3






active

oldest

votes


















5














It doesn't give you the expected result because the syntax is not appropriate. (At which level do you expect an explanation? Does it help that in coordinate (x) at (4,0) node[right] $x$; at (4,0) got "absorbed" by coordinate (x) so that TikZ adds the default coordinate (0,0) to interpret node[right] $x$?) You can condense all statements to one line.



documentclass[tikz,border=3.14mm]standalone
begindocument
begintikzpicture
draw[<->,thick] (0,3) coordinate (y) node[above] $y$ |- (4,0) coordinate (x) node[right] $x$;
endtikzpicture
enddocument


enter image description here






share|improve this answer























  • Nice explanation. I want to notice that your "one line" can further be simplified to draw[<->,thick] (0,3) |- (4,0) node[right] $x$ node[at start,above] $y$; since the coordinates (x) and (y) seems to be redundant for further purposes (IMHO). But I know you know that fact (you know everything about TikZ).

    – Marian G.
    Mar 27 at 19:10











  • @MarianG. Thanks, I fully agree with that. I was not sure if the OP wants to do something with the coordinates later on, at least their names suggest something like beginscope[x=(x),y=(y)], so I kept them.

    – marmot
    Mar 27 at 20:06


















5














In section 17.2.1 of the TikZ manual, the commands for such works are shown:



  • path ... node ... (1.1)

    or node ... (1.2)


  • path ... coordinate ... (2.1)

    or coordinate ... (2.2)



coordinate ... node ... are not present for the same job! In fact, since coordinate is the same as path coordinate so coordinate (x) at (4,0) node[right] $x$; is understood as



path coordinate (x) at (4,0); % or `coordinate (x) at (4,0);
path node[right] $x$; % (0,0) in case no coordinates are specified



This makes the outputs of coordinate (x) at (4,0) node[right] $x$; and node[right] at (x) $x$; not the same at all.



That is why we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
coordinate (x) at (2,0) node[draw,right] world;
fill (x) circle (1pt)
(0,0) circle (1pt);
endtikzpicture
enddocument


and we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
node[draw] (x) at (2,0) Hello node[draw,right] world;
fill (0,0) circle (1pt);
endtikzpicture
enddocument


So how to solve it? We can't combine (2.2) or (1.2) with ... node ..., but we can do it with (1.1) or (2.1):



path (4,0) coordinate (x) node[right] $x$;


Remember that draw, fill, filldraw... are all daughters of path, so they are all valid. But node and coordinate are not – they are less general versions of path..




I found this using the draw powerful trick :)






share|improve this answer

























  • @Kpym Thanks! Edited.

    – JouleV
    Mar 26 at 11:54


















3














try the following:



documentclassarticle
usepackagetikz
%usetikzlibraryintersections not used in this mwe

begindocument
begintikzpicture
coordinate[label=right:$x$] (x) at (4,0);
coordinate[label=above:$y$] (y) at (0,3);

draw[<->,thick] (y) |- (x);
endtikzpicture
enddocument


enter image description here



addendum:
as response to Martin Argerami coments below my answer, who is convinced that my answer not address op problem (and consequently he apparently down vote it, for what i'm very grateful. his message is very clear: don't show people some possible solution for which they not explicit ask). however let me note some my view on the problem:



  • in answer i only suggest to see if my suggestion can help to op

  • it solve the problem of placement of coordinate labels (in this is all about it, isn't it?)

  • if the answer is not helpful, op can select one from other two answers as the best one and accept it.

  • to be strict to Martins' consideration, that he should down vote many other answers, which try show another possibility to achieve op goal (nice picture, table, etc) or is written as exercise (personal or for op) ...

  • on the end, i'm still convinced, that my answer not harm anyone, it only show another way how to draw coordinates shown in op mwe. is this worth for down voting it?





share|improve this answer




















  • 1





    I don't see how this answers the question.

    – Martin Argerami
    Mar 27 at 15:15











  • is image not enough illustrative? the problem in question is avoided with use of coordinate instead of nodes which also make code shorter.

    – Zarko
    Mar 27 at 15:25












  • The OP knows how to draw the image. The question was why his second set of commands didn't put the x and y where he expected them. That's an issue with tikz syntax, and it is addressed by the other answers.

    – Martin Argerami
    Mar 27 at 16:49











  • well, why than complain on my answer? if op doesn't like mine solution, (in which i show an alternative, to my opinion better solution for his/her problem) (s)he can accept one of other two answers.

    – Zarko
    Mar 27 at 17:26











  • I didn't complain; I stated that it doesn't address OP's question. If OP doesn't like your solution he can choose another answer. If I don't like you solution, I can downvote it. And I can certainly comment that your answer doesn't address OP's question.

    – Martin Argerami
    Mar 27 at 17:57











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
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%2ftex.stackexchange.com%2fquestions%2f481386%2fnode-command-while-defining-a-coordinate-in-tikz%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









5














It doesn't give you the expected result because the syntax is not appropriate. (At which level do you expect an explanation? Does it help that in coordinate (x) at (4,0) node[right] $x$; at (4,0) got "absorbed" by coordinate (x) so that TikZ adds the default coordinate (0,0) to interpret node[right] $x$?) You can condense all statements to one line.



documentclass[tikz,border=3.14mm]standalone
begindocument
begintikzpicture
draw[<->,thick] (0,3) coordinate (y) node[above] $y$ |- (4,0) coordinate (x) node[right] $x$;
endtikzpicture
enddocument


enter image description here






share|improve this answer























  • Nice explanation. I want to notice that your "one line" can further be simplified to draw[<->,thick] (0,3) |- (4,0) node[right] $x$ node[at start,above] $y$; since the coordinates (x) and (y) seems to be redundant for further purposes (IMHO). But I know you know that fact (you know everything about TikZ).

    – Marian G.
    Mar 27 at 19:10











  • @MarianG. Thanks, I fully agree with that. I was not sure if the OP wants to do something with the coordinates later on, at least their names suggest something like beginscope[x=(x),y=(y)], so I kept them.

    – marmot
    Mar 27 at 20:06















5














It doesn't give you the expected result because the syntax is not appropriate. (At which level do you expect an explanation? Does it help that in coordinate (x) at (4,0) node[right] $x$; at (4,0) got "absorbed" by coordinate (x) so that TikZ adds the default coordinate (0,0) to interpret node[right] $x$?) You can condense all statements to one line.



documentclass[tikz,border=3.14mm]standalone
begindocument
begintikzpicture
draw[<->,thick] (0,3) coordinate (y) node[above] $y$ |- (4,0) coordinate (x) node[right] $x$;
endtikzpicture
enddocument


enter image description here






share|improve this answer























  • Nice explanation. I want to notice that your "one line" can further be simplified to draw[<->,thick] (0,3) |- (4,0) node[right] $x$ node[at start,above] $y$; since the coordinates (x) and (y) seems to be redundant for further purposes (IMHO). But I know you know that fact (you know everything about TikZ).

    – Marian G.
    Mar 27 at 19:10











  • @MarianG. Thanks, I fully agree with that. I was not sure if the OP wants to do something with the coordinates later on, at least their names suggest something like beginscope[x=(x),y=(y)], so I kept them.

    – marmot
    Mar 27 at 20:06













5












5








5







It doesn't give you the expected result because the syntax is not appropriate. (At which level do you expect an explanation? Does it help that in coordinate (x) at (4,0) node[right] $x$; at (4,0) got "absorbed" by coordinate (x) so that TikZ adds the default coordinate (0,0) to interpret node[right] $x$?) You can condense all statements to one line.



documentclass[tikz,border=3.14mm]standalone
begindocument
begintikzpicture
draw[<->,thick] (0,3) coordinate (y) node[above] $y$ |- (4,0) coordinate (x) node[right] $x$;
endtikzpicture
enddocument


enter image description here






share|improve this answer













It doesn't give you the expected result because the syntax is not appropriate. (At which level do you expect an explanation? Does it help that in coordinate (x) at (4,0) node[right] $x$; at (4,0) got "absorbed" by coordinate (x) so that TikZ adds the default coordinate (0,0) to interpret node[right] $x$?) You can condense all statements to one line.



documentclass[tikz,border=3.14mm]standalone
begindocument
begintikzpicture
draw[<->,thick] (0,3) coordinate (y) node[above] $y$ |- (4,0) coordinate (x) node[right] $x$;
endtikzpicture
enddocument


enter image description here







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 25 at 17:14









marmotmarmot

121k6158295




121k6158295












  • Nice explanation. I want to notice that your "one line" can further be simplified to draw[<->,thick] (0,3) |- (4,0) node[right] $x$ node[at start,above] $y$; since the coordinates (x) and (y) seems to be redundant for further purposes (IMHO). But I know you know that fact (you know everything about TikZ).

    – Marian G.
    Mar 27 at 19:10











  • @MarianG. Thanks, I fully agree with that. I was not sure if the OP wants to do something with the coordinates later on, at least their names suggest something like beginscope[x=(x),y=(y)], so I kept them.

    – marmot
    Mar 27 at 20:06

















  • Nice explanation. I want to notice that your "one line" can further be simplified to draw[<->,thick] (0,3) |- (4,0) node[right] $x$ node[at start,above] $y$; since the coordinates (x) and (y) seems to be redundant for further purposes (IMHO). But I know you know that fact (you know everything about TikZ).

    – Marian G.
    Mar 27 at 19:10











  • @MarianG. Thanks, I fully agree with that. I was not sure if the OP wants to do something with the coordinates later on, at least their names suggest something like beginscope[x=(x),y=(y)], so I kept them.

    – marmot
    Mar 27 at 20:06
















Nice explanation. I want to notice that your "one line" can further be simplified to draw[<->,thick] (0,3) |- (4,0) node[right] $x$ node[at start,above] $y$; since the coordinates (x) and (y) seems to be redundant for further purposes (IMHO). But I know you know that fact (you know everything about TikZ).

– Marian G.
Mar 27 at 19:10





Nice explanation. I want to notice that your "one line" can further be simplified to draw[<->,thick] (0,3) |- (4,0) node[right] $x$ node[at start,above] $y$; since the coordinates (x) and (y) seems to be redundant for further purposes (IMHO). But I know you know that fact (you know everything about TikZ).

– Marian G.
Mar 27 at 19:10













@MarianG. Thanks, I fully agree with that. I was not sure if the OP wants to do something with the coordinates later on, at least their names suggest something like beginscope[x=(x),y=(y)], so I kept them.

– marmot
Mar 27 at 20:06





@MarianG. Thanks, I fully agree with that. I was not sure if the OP wants to do something with the coordinates later on, at least their names suggest something like beginscope[x=(x),y=(y)], so I kept them.

– marmot
Mar 27 at 20:06











5














In section 17.2.1 of the TikZ manual, the commands for such works are shown:



  • path ... node ... (1.1)

    or node ... (1.2)


  • path ... coordinate ... (2.1)

    or coordinate ... (2.2)



coordinate ... node ... are not present for the same job! In fact, since coordinate is the same as path coordinate so coordinate (x) at (4,0) node[right] $x$; is understood as



path coordinate (x) at (4,0); % or `coordinate (x) at (4,0);
path node[right] $x$; % (0,0) in case no coordinates are specified



This makes the outputs of coordinate (x) at (4,0) node[right] $x$; and node[right] at (x) $x$; not the same at all.



That is why we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
coordinate (x) at (2,0) node[draw,right] world;
fill (x) circle (1pt)
(0,0) circle (1pt);
endtikzpicture
enddocument


and we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
node[draw] (x) at (2,0) Hello node[draw,right] world;
fill (0,0) circle (1pt);
endtikzpicture
enddocument


So how to solve it? We can't combine (2.2) or (1.2) with ... node ..., but we can do it with (1.1) or (2.1):



path (4,0) coordinate (x) node[right] $x$;


Remember that draw, fill, filldraw... are all daughters of path, so they are all valid. But node and coordinate are not – they are less general versions of path..




I found this using the draw powerful trick :)






share|improve this answer

























  • @Kpym Thanks! Edited.

    – JouleV
    Mar 26 at 11:54















5














In section 17.2.1 of the TikZ manual, the commands for such works are shown:



  • path ... node ... (1.1)

    or node ... (1.2)


  • path ... coordinate ... (2.1)

    or coordinate ... (2.2)



coordinate ... node ... are not present for the same job! In fact, since coordinate is the same as path coordinate so coordinate (x) at (4,0) node[right] $x$; is understood as



path coordinate (x) at (4,0); % or `coordinate (x) at (4,0);
path node[right] $x$; % (0,0) in case no coordinates are specified



This makes the outputs of coordinate (x) at (4,0) node[right] $x$; and node[right] at (x) $x$; not the same at all.



That is why we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
coordinate (x) at (2,0) node[draw,right] world;
fill (x) circle (1pt)
(0,0) circle (1pt);
endtikzpicture
enddocument


and we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
node[draw] (x) at (2,0) Hello node[draw,right] world;
fill (0,0) circle (1pt);
endtikzpicture
enddocument


So how to solve it? We can't combine (2.2) or (1.2) with ... node ..., but we can do it with (1.1) or (2.1):



path (4,0) coordinate (x) node[right] $x$;


Remember that draw, fill, filldraw... are all daughters of path, so they are all valid. But node and coordinate are not – they are less general versions of path..




I found this using the draw powerful trick :)






share|improve this answer

























  • @Kpym Thanks! Edited.

    – JouleV
    Mar 26 at 11:54













5












5








5







In section 17.2.1 of the TikZ manual, the commands for such works are shown:



  • path ... node ... (1.1)

    or node ... (1.2)


  • path ... coordinate ... (2.1)

    or coordinate ... (2.2)



coordinate ... node ... are not present for the same job! In fact, since coordinate is the same as path coordinate so coordinate (x) at (4,0) node[right] $x$; is understood as



path coordinate (x) at (4,0); % or `coordinate (x) at (4,0);
path node[right] $x$; % (0,0) in case no coordinates are specified



This makes the outputs of coordinate (x) at (4,0) node[right] $x$; and node[right] at (x) $x$; not the same at all.



That is why we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
coordinate (x) at (2,0) node[draw,right] world;
fill (x) circle (1pt)
(0,0) circle (1pt);
endtikzpicture
enddocument


and we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
node[draw] (x) at (2,0) Hello node[draw,right] world;
fill (0,0) circle (1pt);
endtikzpicture
enddocument


So how to solve it? We can't combine (2.2) or (1.2) with ... node ..., but we can do it with (1.1) or (2.1):



path (4,0) coordinate (x) node[right] $x$;


Remember that draw, fill, filldraw... are all daughters of path, so they are all valid. But node and coordinate are not – they are less general versions of path..




I found this using the draw powerful trick :)






share|improve this answer















In section 17.2.1 of the TikZ manual, the commands for such works are shown:



  • path ... node ... (1.1)

    or node ... (1.2)


  • path ... coordinate ... (2.1)

    or coordinate ... (2.2)



coordinate ... node ... are not present for the same job! In fact, since coordinate is the same as path coordinate so coordinate (x) at (4,0) node[right] $x$; is understood as



path coordinate (x) at (4,0); % or `coordinate (x) at (4,0);
path node[right] $x$; % (0,0) in case no coordinates are specified



This makes the outputs of coordinate (x) at (4,0) node[right] $x$; and node[right] at (x) $x$; not the same at all.



That is why we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
coordinate (x) at (2,0) node[draw,right] world;
fill (x) circle (1pt)
(0,0) circle (1pt);
endtikzpicture
enddocument


and we get



enter image description here



with this code



documentclass[tikz]standalone
begindocument
begintikzpicture
node[draw] (x) at (2,0) Hello node[draw,right] world;
fill (0,0) circle (1pt);
endtikzpicture
enddocument


So how to solve it? We can't combine (2.2) or (1.2) with ... node ..., but we can do it with (1.1) or (2.1):



path (4,0) coordinate (x) node[right] $x$;


Remember that draw, fill, filldraw... are all daughters of path, so they are all valid. But node and coordinate are not – they are less general versions of path..




I found this using the draw powerful trick :)







share|improve this answer














share|improve this answer



share|improve this answer








edited Mar 28 at 14:55

























answered Mar 25 at 17:15









JouleVJouleV

15.4k22667




15.4k22667












  • @Kpym Thanks! Edited.

    – JouleV
    Mar 26 at 11:54

















  • @Kpym Thanks! Edited.

    – JouleV
    Mar 26 at 11:54
















@Kpym Thanks! Edited.

– JouleV
Mar 26 at 11:54





@Kpym Thanks! Edited.

– JouleV
Mar 26 at 11:54











3














try the following:



documentclassarticle
usepackagetikz
%usetikzlibraryintersections not used in this mwe

begindocument
begintikzpicture
coordinate[label=right:$x$] (x) at (4,0);
coordinate[label=above:$y$] (y) at (0,3);

draw[<->,thick] (y) |- (x);
endtikzpicture
enddocument


enter image description here



addendum:
as response to Martin Argerami coments below my answer, who is convinced that my answer not address op problem (and consequently he apparently down vote it, for what i'm very grateful. his message is very clear: don't show people some possible solution for which they not explicit ask). however let me note some my view on the problem:



  • in answer i only suggest to see if my suggestion can help to op

  • it solve the problem of placement of coordinate labels (in this is all about it, isn't it?)

  • if the answer is not helpful, op can select one from other two answers as the best one and accept it.

  • to be strict to Martins' consideration, that he should down vote many other answers, which try show another possibility to achieve op goal (nice picture, table, etc) or is written as exercise (personal or for op) ...

  • on the end, i'm still convinced, that my answer not harm anyone, it only show another way how to draw coordinates shown in op mwe. is this worth for down voting it?





share|improve this answer




















  • 1





    I don't see how this answers the question.

    – Martin Argerami
    Mar 27 at 15:15











  • is image not enough illustrative? the problem in question is avoided with use of coordinate instead of nodes which also make code shorter.

    – Zarko
    Mar 27 at 15:25












  • The OP knows how to draw the image. The question was why his second set of commands didn't put the x and y where he expected them. That's an issue with tikz syntax, and it is addressed by the other answers.

    – Martin Argerami
    Mar 27 at 16:49











  • well, why than complain on my answer? if op doesn't like mine solution, (in which i show an alternative, to my opinion better solution for his/her problem) (s)he can accept one of other two answers.

    – Zarko
    Mar 27 at 17:26











  • I didn't complain; I stated that it doesn't address OP's question. If OP doesn't like your solution he can choose another answer. If I don't like you solution, I can downvote it. And I can certainly comment that your answer doesn't address OP's question.

    – Martin Argerami
    Mar 27 at 17:57















3














try the following:



documentclassarticle
usepackagetikz
%usetikzlibraryintersections not used in this mwe

begindocument
begintikzpicture
coordinate[label=right:$x$] (x) at (4,0);
coordinate[label=above:$y$] (y) at (0,3);

draw[<->,thick] (y) |- (x);
endtikzpicture
enddocument


enter image description here



addendum:
as response to Martin Argerami coments below my answer, who is convinced that my answer not address op problem (and consequently he apparently down vote it, for what i'm very grateful. his message is very clear: don't show people some possible solution for which they not explicit ask). however let me note some my view on the problem:



  • in answer i only suggest to see if my suggestion can help to op

  • it solve the problem of placement of coordinate labels (in this is all about it, isn't it?)

  • if the answer is not helpful, op can select one from other two answers as the best one and accept it.

  • to be strict to Martins' consideration, that he should down vote many other answers, which try show another possibility to achieve op goal (nice picture, table, etc) or is written as exercise (personal or for op) ...

  • on the end, i'm still convinced, that my answer not harm anyone, it only show another way how to draw coordinates shown in op mwe. is this worth for down voting it?





share|improve this answer




















  • 1





    I don't see how this answers the question.

    – Martin Argerami
    Mar 27 at 15:15











  • is image not enough illustrative? the problem in question is avoided with use of coordinate instead of nodes which also make code shorter.

    – Zarko
    Mar 27 at 15:25












  • The OP knows how to draw the image. The question was why his second set of commands didn't put the x and y where he expected them. That's an issue with tikz syntax, and it is addressed by the other answers.

    – Martin Argerami
    Mar 27 at 16:49











  • well, why than complain on my answer? if op doesn't like mine solution, (in which i show an alternative, to my opinion better solution for his/her problem) (s)he can accept one of other two answers.

    – Zarko
    Mar 27 at 17:26











  • I didn't complain; I stated that it doesn't address OP's question. If OP doesn't like your solution he can choose another answer. If I don't like you solution, I can downvote it. And I can certainly comment that your answer doesn't address OP's question.

    – Martin Argerami
    Mar 27 at 17:57













3












3








3







try the following:



documentclassarticle
usepackagetikz
%usetikzlibraryintersections not used in this mwe

begindocument
begintikzpicture
coordinate[label=right:$x$] (x) at (4,0);
coordinate[label=above:$y$] (y) at (0,3);

draw[<->,thick] (y) |- (x);
endtikzpicture
enddocument


enter image description here



addendum:
as response to Martin Argerami coments below my answer, who is convinced that my answer not address op problem (and consequently he apparently down vote it, for what i'm very grateful. his message is very clear: don't show people some possible solution for which they not explicit ask). however let me note some my view on the problem:



  • in answer i only suggest to see if my suggestion can help to op

  • it solve the problem of placement of coordinate labels (in this is all about it, isn't it?)

  • if the answer is not helpful, op can select one from other two answers as the best one and accept it.

  • to be strict to Martins' consideration, that he should down vote many other answers, which try show another possibility to achieve op goal (nice picture, table, etc) or is written as exercise (personal or for op) ...

  • on the end, i'm still convinced, that my answer not harm anyone, it only show another way how to draw coordinates shown in op mwe. is this worth for down voting it?





share|improve this answer















try the following:



documentclassarticle
usepackagetikz
%usetikzlibraryintersections not used in this mwe

begindocument
begintikzpicture
coordinate[label=right:$x$] (x) at (4,0);
coordinate[label=above:$y$] (y) at (0,3);

draw[<->,thick] (y) |- (x);
endtikzpicture
enddocument


enter image description here



addendum:
as response to Martin Argerami coments below my answer, who is convinced that my answer not address op problem (and consequently he apparently down vote it, for what i'm very grateful. his message is very clear: don't show people some possible solution for which they not explicit ask). however let me note some my view on the problem:



  • in answer i only suggest to see if my suggestion can help to op

  • it solve the problem of placement of coordinate labels (in this is all about it, isn't it?)

  • if the answer is not helpful, op can select one from other two answers as the best one and accept it.

  • to be strict to Martins' consideration, that he should down vote many other answers, which try show another possibility to achieve op goal (nice picture, table, etc) or is written as exercise (personal or for op) ...

  • on the end, i'm still convinced, that my answer not harm anyone, it only show another way how to draw coordinates shown in op mwe. is this worth for down voting it?






share|improve this answer














share|improve this answer



share|improve this answer








edited Mar 27 at 18:38

























answered Mar 25 at 17:14









ZarkoZarko

131k869170




131k869170







  • 1





    I don't see how this answers the question.

    – Martin Argerami
    Mar 27 at 15:15











  • is image not enough illustrative? the problem in question is avoided with use of coordinate instead of nodes which also make code shorter.

    – Zarko
    Mar 27 at 15:25












  • The OP knows how to draw the image. The question was why his second set of commands didn't put the x and y where he expected them. That's an issue with tikz syntax, and it is addressed by the other answers.

    – Martin Argerami
    Mar 27 at 16:49











  • well, why than complain on my answer? if op doesn't like mine solution, (in which i show an alternative, to my opinion better solution for his/her problem) (s)he can accept one of other two answers.

    – Zarko
    Mar 27 at 17:26











  • I didn't complain; I stated that it doesn't address OP's question. If OP doesn't like your solution he can choose another answer. If I don't like you solution, I can downvote it. And I can certainly comment that your answer doesn't address OP's question.

    – Martin Argerami
    Mar 27 at 17:57












  • 1





    I don't see how this answers the question.

    – Martin Argerami
    Mar 27 at 15:15











  • is image not enough illustrative? the problem in question is avoided with use of coordinate instead of nodes which also make code shorter.

    – Zarko
    Mar 27 at 15:25












  • The OP knows how to draw the image. The question was why his second set of commands didn't put the x and y where he expected them. That's an issue with tikz syntax, and it is addressed by the other answers.

    – Martin Argerami
    Mar 27 at 16:49











  • well, why than complain on my answer? if op doesn't like mine solution, (in which i show an alternative, to my opinion better solution for his/her problem) (s)he can accept one of other two answers.

    – Zarko
    Mar 27 at 17:26











  • I didn't complain; I stated that it doesn't address OP's question. If OP doesn't like your solution he can choose another answer. If I don't like you solution, I can downvote it. And I can certainly comment that your answer doesn't address OP's question.

    – Martin Argerami
    Mar 27 at 17:57







1




1





I don't see how this answers the question.

– Martin Argerami
Mar 27 at 15:15





I don't see how this answers the question.

– Martin Argerami
Mar 27 at 15:15













is image not enough illustrative? the problem in question is avoided with use of coordinate instead of nodes which also make code shorter.

– Zarko
Mar 27 at 15:25






is image not enough illustrative? the problem in question is avoided with use of coordinate instead of nodes which also make code shorter.

– Zarko
Mar 27 at 15:25














The OP knows how to draw the image. The question was why his second set of commands didn't put the x and y where he expected them. That's an issue with tikz syntax, and it is addressed by the other answers.

– Martin Argerami
Mar 27 at 16:49





The OP knows how to draw the image. The question was why his second set of commands didn't put the x and y where he expected them. That's an issue with tikz syntax, and it is addressed by the other answers.

– Martin Argerami
Mar 27 at 16:49













well, why than complain on my answer? if op doesn't like mine solution, (in which i show an alternative, to my opinion better solution for his/her problem) (s)he can accept one of other two answers.

– Zarko
Mar 27 at 17:26





well, why than complain on my answer? if op doesn't like mine solution, (in which i show an alternative, to my opinion better solution for his/her problem) (s)he can accept one of other two answers.

– Zarko
Mar 27 at 17:26













I didn't complain; I stated that it doesn't address OP's question. If OP doesn't like your solution he can choose another answer. If I don't like you solution, I can downvote it. And I can certainly comment that your answer doesn't address OP's question.

– Martin Argerami
Mar 27 at 17:57





I didn't complain; I stated that it doesn't address OP's question. If OP doesn't like your solution he can choose another answer. If I don't like you solution, I can downvote it. And I can certainly comment that your answer doesn't address OP's question.

– Martin Argerami
Mar 27 at 17:57

















draft saved

draft discarded
















































Thanks for contributing an answer to TeX - LaTeX 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%2ftex.stackexchange.com%2fquestions%2f481386%2fnode-command-while-defining-a-coordinate-in-tikz%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

Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum

He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

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