node command while defining a coordinate in TikZ












4















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:



documentclass{article}
usepackage{tikz}
usetikzlibrary{intersections}
begin{document}
begin{tikzpicture}
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);
end{tikzpicture}
end{document}









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
    yesterday













  • @marmot - I have added the MWE.

    – subham soni
    yesterday











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

    – JouleV
    yesterday











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

    – subham soni
    yesterday






  • 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
    yesterday
















4















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:



documentclass{article}
usepackage{tikz}
usetikzlibrary{intersections}
begin{document}
begin{tikzpicture}
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);
end{tikzpicture}
end{document}









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
    yesterday













  • @marmot - I have added the MWE.

    – subham soni
    yesterday











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

    – JouleV
    yesterday











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

    – subham soni
    yesterday






  • 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
    yesterday














4












4








4








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:



documentclass{article}
usepackage{tikz}
usetikzlibrary{intersections}
begin{document}
begin{tikzpicture}
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);
end{tikzpicture}
end{document}









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:



documentclass{article}
usepackage{tikz}
usetikzlibrary{intersections}
begin{document}
begin{tikzpicture}
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);
end{tikzpicture}
end{document}






tikz-pgf






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday







subham soni

















asked yesterday









subham sonisubham soni

4,51983184




4,51983184








  • 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
    yesterday













  • @marmot - I have added the MWE.

    – subham soni
    yesterday











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

    – JouleV
    yesterday











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

    – subham soni
    yesterday






  • 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
    yesterday














  • 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
    yesterday













  • @marmot - I have added the MWE.

    – subham soni
    yesterday











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

    – JouleV
    yesterday











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

    – subham soni
    yesterday






  • 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
    yesterday








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
yesterday







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
yesterday















@marmot - I have added the MWE.

– subham soni
yesterday





@marmot - I have added the MWE.

– subham soni
yesterday













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

– JouleV
yesterday





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

– JouleV
yesterday













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

– subham soni
yesterday





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

– subham soni
yesterday




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
yesterday





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
yesterday










3 Answers
3






active

oldest

votes


















4














try the following:



documentclass{article}
usepackage{tikz}
%usetikzlibrary{intersections} not used in this mwe

begin{document}
begin{tikzpicture}
coordinate[label=right:$x$] (x) at (4,0);
coordinate[label=above:$y$] (y) at (0,3);

draw[<->,thick] (y) |- (x);
end{tikzpicture}
end{document}


enter image description here






share|improve this answer































    3














    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}
    begin{document}
    begin{tikzpicture}
    coordinate (x) at (2,0) node[draw,right] {world};
    fill (x) circle (1pt)
    (0,0) circle (1pt);
    end{tikzpicture}
    end{document}


    and we get



    enter image description here



    with this code



    documentclass[tikz]{standalone}
    begin{document}
    begin{tikzpicture}
    node[draw] (x) at (2,0) {Hello} node[draw,right] {world};
    fill (0,0) circle (1pt);
    end{tikzpicture}
    end{document}


    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
      8 hours ago



















    2














    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}
    begin{document}
    begin{tikzpicture}
    draw[<->,thick] (0,3) coordinate (y) node[above] {$y$} |- (4,0) coordinate (x) node[right] {$x$};
    end{tikzpicture}
    end{document}


    enter image description here






    share|improve this answer























      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









      4














      try the following:



      documentclass{article}
      usepackage{tikz}
      %usetikzlibrary{intersections} not used in this mwe

      begin{document}
      begin{tikzpicture}
      coordinate[label=right:$x$] (x) at (4,0);
      coordinate[label=above:$y$] (y) at (0,3);

      draw[<->,thick] (y) |- (x);
      end{tikzpicture}
      end{document}


      enter image description here






      share|improve this answer




























        4














        try the following:



        documentclass{article}
        usepackage{tikz}
        %usetikzlibrary{intersections} not used in this mwe

        begin{document}
        begin{tikzpicture}
        coordinate[label=right:$x$] (x) at (4,0);
        coordinate[label=above:$y$] (y) at (0,3);

        draw[<->,thick] (y) |- (x);
        end{tikzpicture}
        end{document}


        enter image description here






        share|improve this answer


























          4












          4








          4







          try the following:



          documentclass{article}
          usepackage{tikz}
          %usetikzlibrary{intersections} not used in this mwe

          begin{document}
          begin{tikzpicture}
          coordinate[label=right:$x$] (x) at (4,0);
          coordinate[label=above:$y$] (y) at (0,3);

          draw[<->,thick] (y) |- (x);
          end{tikzpicture}
          end{document}


          enter image description here






          share|improve this answer













          try the following:



          documentclass{article}
          usepackage{tikz}
          %usetikzlibrary{intersections} not used in this mwe

          begin{document}
          begin{tikzpicture}
          coordinate[label=right:$x$] (x) at (4,0);
          coordinate[label=above:$y$] (y) at (0,3);

          draw[<->,thick] (y) |- (x);
          end{tikzpicture}
          end{document}


          enter image description here







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered yesterday









          ZarkoZarko

          128k868167




          128k868167























              3














              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}
              begin{document}
              begin{tikzpicture}
              coordinate (x) at (2,0) node[draw,right] {world};
              fill (x) circle (1pt)
              (0,0) circle (1pt);
              end{tikzpicture}
              end{document}


              and we get



              enter image description here



              with this code



              documentclass[tikz]{standalone}
              begin{document}
              begin{tikzpicture}
              node[draw] (x) at (2,0) {Hello} node[draw,right] {world};
              fill (0,0) circle (1pt);
              end{tikzpicture}
              end{document}


              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
                8 hours ago
















              3














              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}
              begin{document}
              begin{tikzpicture}
              coordinate (x) at (2,0) node[draw,right] {world};
              fill (x) circle (1pt)
              (0,0) circle (1pt);
              end{tikzpicture}
              end{document}


              and we get



              enter image description here



              with this code



              documentclass[tikz]{standalone}
              begin{document}
              begin{tikzpicture}
              node[draw] (x) at (2,0) {Hello} node[draw,right] {world};
              fill (0,0) circle (1pt);
              end{tikzpicture}
              end{document}


              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
                8 hours ago














              3












              3








              3







              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}
              begin{document}
              begin{tikzpicture}
              coordinate (x) at (2,0) node[draw,right] {world};
              fill (x) circle (1pt)
              (0,0) circle (1pt);
              end{tikzpicture}
              end{document}


              and we get



              enter image description here



              with this code



              documentclass[tikz]{standalone}
              begin{document}
              begin{tikzpicture}
              node[draw] (x) at (2,0) {Hello} node[draw,right] {world};
              fill (0,0) circle (1pt);
              end{tikzpicture}
              end{document}


              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}
              begin{document}
              begin{tikzpicture}
              coordinate (x) at (2,0) node[draw,right] {world};
              fill (x) circle (1pt)
              (0,0) circle (1pt);
              end{tikzpicture}
              end{document}


              and we get



              enter image description here



              with this code



              documentclass[tikz]{standalone}
              begin{document}
              begin{tikzpicture}
              node[draw] (x) at (2,0) {Hello} node[draw,right] {world};
              fill (0,0) circle (1pt);
              end{tikzpicture}
              end{document}


              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 8 hours ago

























              answered yesterday









              JouleVJouleV

              8,15222153




              8,15222153













              • @Kpym Thanks! Edited.

                – JouleV
                8 hours ago



















              • @Kpym Thanks! Edited.

                – JouleV
                8 hours ago

















              @Kpym Thanks! Edited.

              – JouleV
              8 hours ago





              @Kpym Thanks! Edited.

              – JouleV
              8 hours ago











              2














              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}
              begin{document}
              begin{tikzpicture}
              draw[<->,thick] (0,3) coordinate (y) node[above] {$y$} |- (4,0) coordinate (x) node[right] {$x$};
              end{tikzpicture}
              end{document}


              enter image description here






              share|improve this answer




























                2














                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}
                begin{document}
                begin{tikzpicture}
                draw[<->,thick] (0,3) coordinate (y) node[above] {$y$} |- (4,0) coordinate (x) node[right] {$x$};
                end{tikzpicture}
                end{document}


                enter image description here






                share|improve this answer


























                  2












                  2








                  2







                  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}
                  begin{document}
                  begin{tikzpicture}
                  draw[<->,thick] (0,3) coordinate (y) node[above] {$y$} |- (4,0) coordinate (x) node[right] {$x$};
                  end{tikzpicture}
                  end{document}


                  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}
                  begin{document}
                  begin{tikzpicture}
                  draw[<->,thick] (0,3) coordinate (y) node[above] {$y$} |- (4,0) coordinate (x) node[right] {$x$};
                  end{tikzpicture}
                  end{document}


                  enter image description here







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered yesterday









                  marmotmarmot

                  112k5141267




                  112k5141267






























                      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