Renew command > to rangle












2















I would like to use the following commands (in order to simplify writing):



newcommand{<}{langle}
renewcommand{>}{rangle}


Would there be any dangerous consequences of this? I know that by default > inserts medmuskip, but I am not using this command.










share|improve this question







New contributor




Skeeve is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    It is possible that you use this command indirectly without being aware of it, via some package or other.

    – Harald Hanche-Olsen
    4 hours ago











  • Yes, this is exactly what worries me. Any suggestions on how to keep the things safe are welcome!

    – Skeeve
    4 hours ago






  • 1





    Redefining > and < might cause havoc if you need to use the tabbing environment.

    – Mico
    4 hours ago











  • @Mico More precisely, using $<a>$ in a tabbing environment would cause havoc. If this is needed, it's sufficient to use langle and rangle in the special situation. Nothing would happen otherwise.

    – egreg
    2 hours ago


















2















I would like to use the following commands (in order to simplify writing):



newcommand{<}{langle}
renewcommand{>}{rangle}


Would there be any dangerous consequences of this? I know that by default > inserts medmuskip, but I am not using this command.










share|improve this question







New contributor




Skeeve is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    It is possible that you use this command indirectly without being aware of it, via some package or other.

    – Harald Hanche-Olsen
    4 hours ago











  • Yes, this is exactly what worries me. Any suggestions on how to keep the things safe are welcome!

    – Skeeve
    4 hours ago






  • 1





    Redefining > and < might cause havoc if you need to use the tabbing environment.

    – Mico
    4 hours ago











  • @Mico More precisely, using $<a>$ in a tabbing environment would cause havoc. If this is needed, it's sufficient to use langle and rangle in the special situation. Nothing would happen otherwise.

    – egreg
    2 hours ago
















2












2








2








I would like to use the following commands (in order to simplify writing):



newcommand{<}{langle}
renewcommand{>}{rangle}


Would there be any dangerous consequences of this? I know that by default > inserts medmuskip, but I am not using this command.










share|improve this question







New contributor




Skeeve is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I would like to use the following commands (in order to simplify writing):



newcommand{<}{langle}
renewcommand{>}{rangle}


Would there be any dangerous consequences of this? I know that by default > inserts medmuskip, but I am not using this command.







macros






share|improve this question







New contributor




Skeeve is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Skeeve is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Skeeve is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 4 hours ago









SkeeveSkeeve

1112




1112




New contributor




Skeeve is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Skeeve is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Skeeve is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1





    It is possible that you use this command indirectly without being aware of it, via some package or other.

    – Harald Hanche-Olsen
    4 hours ago











  • Yes, this is exactly what worries me. Any suggestions on how to keep the things safe are welcome!

    – Skeeve
    4 hours ago






  • 1





    Redefining > and < might cause havoc if you need to use the tabbing environment.

    – Mico
    4 hours ago











  • @Mico More precisely, using $<a>$ in a tabbing environment would cause havoc. If this is needed, it's sufficient to use langle and rangle in the special situation. Nothing would happen otherwise.

    – egreg
    2 hours ago
















  • 1





    It is possible that you use this command indirectly without being aware of it, via some package or other.

    – Harald Hanche-Olsen
    4 hours ago











  • Yes, this is exactly what worries me. Any suggestions on how to keep the things safe are welcome!

    – Skeeve
    4 hours ago






  • 1





    Redefining > and < might cause havoc if you need to use the tabbing environment.

    – Mico
    4 hours ago











  • @Mico More precisely, using $<a>$ in a tabbing environment would cause havoc. If this is needed, it's sufficient to use langle and rangle in the special situation. Nothing would happen otherwise.

    – egreg
    2 hours ago










1




1





It is possible that you use this command indirectly without being aware of it, via some package or other.

– Harald Hanche-Olsen
4 hours ago





It is possible that you use this command indirectly without being aware of it, via some package or other.

– Harald Hanche-Olsen
4 hours ago













Yes, this is exactly what worries me. Any suggestions on how to keep the things safe are welcome!

– Skeeve
4 hours ago





Yes, this is exactly what worries me. Any suggestions on how to keep the things safe are welcome!

– Skeeve
4 hours ago




1




1





Redefining > and < might cause havoc if you need to use the tabbing environment.

– Mico
4 hours ago





Redefining > and < might cause havoc if you need to use the tabbing environment.

– Mico
4 hours ago













@Mico More precisely, using $<a>$ in a tabbing environment would cause havoc. If this is needed, it's sufficient to use langle and rangle in the special situation. Nothing would happen otherwise.

– egreg
2 hours ago







@Mico More precisely, using $<a>$ in a tabbing environment would cause havoc. If this is needed, it's sufficient to use langle and rangle in the special situation. Nothing would happen otherwise.

– egreg
2 hours ago












1 Answer
1






active

oldest

votes


















1














You risk that some obscure package defines something in term of > or define < and > themselves.



A quick search reveals that < is defined in



amsdtx.cls
amsldoc.cls
circ.sty
cjhebrew.sty
gmmeta.sty
greektonoi.sty
jlreq.cls
lhcyralt.sty
lhcyrkoi.sty
lhcyrwin.sty
pax.sty
AlProTex.sty
dev209.sty


The command > is redefined in



bxcjkjatype.sty
gn-logic14.sty
greektonoi.sty
lhcyralt.sty
lhcyrkoi.sty
lhcyrwin.sty
pax.sty
AlProTex.sty
sgamevar.sty
zxjatype.sty


I can't exclude there are other instances where different ways of defining commands are used.



I'd not do it anyway, even if it's not that risky. Better do



usepackage{mathtools}

DeclarePairedDelimiters{foo}{langle}{rangle}


(choose a meaningful name for your application) and use



foo{x} foo[big]{x} foo[Big]{x} foo[bigg]{x} foo[Bigg]{x} foo*{x}


for choosing the size of the delimiters (the last one is for automatic sizing with left and right, use it carefully).



If you decide to use < and > beware that inside a tabbing environment you will have to use langle and rangle because tabbing redefines the two commands for its own purposes (but just inside the environment).






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
    });


    }
    });






    Skeeve is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f481580%2frenew-command-to-rangle%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    You risk that some obscure package defines something in term of > or define < and > themselves.



    A quick search reveals that < is defined in



    amsdtx.cls
    amsldoc.cls
    circ.sty
    cjhebrew.sty
    gmmeta.sty
    greektonoi.sty
    jlreq.cls
    lhcyralt.sty
    lhcyrkoi.sty
    lhcyrwin.sty
    pax.sty
    AlProTex.sty
    dev209.sty


    The command > is redefined in



    bxcjkjatype.sty
    gn-logic14.sty
    greektonoi.sty
    lhcyralt.sty
    lhcyrkoi.sty
    lhcyrwin.sty
    pax.sty
    AlProTex.sty
    sgamevar.sty
    zxjatype.sty


    I can't exclude there are other instances where different ways of defining commands are used.



    I'd not do it anyway, even if it's not that risky. Better do



    usepackage{mathtools}

    DeclarePairedDelimiters{foo}{langle}{rangle}


    (choose a meaningful name for your application) and use



    foo{x} foo[big]{x} foo[Big]{x} foo[bigg]{x} foo[Bigg]{x} foo*{x}


    for choosing the size of the delimiters (the last one is for automatic sizing with left and right, use it carefully).



    If you decide to use < and > beware that inside a tabbing environment you will have to use langle and rangle because tabbing redefines the two commands for its own purposes (but just inside the environment).






    share|improve this answer




























      1














      You risk that some obscure package defines something in term of > or define < and > themselves.



      A quick search reveals that < is defined in



      amsdtx.cls
      amsldoc.cls
      circ.sty
      cjhebrew.sty
      gmmeta.sty
      greektonoi.sty
      jlreq.cls
      lhcyralt.sty
      lhcyrkoi.sty
      lhcyrwin.sty
      pax.sty
      AlProTex.sty
      dev209.sty


      The command > is redefined in



      bxcjkjatype.sty
      gn-logic14.sty
      greektonoi.sty
      lhcyralt.sty
      lhcyrkoi.sty
      lhcyrwin.sty
      pax.sty
      AlProTex.sty
      sgamevar.sty
      zxjatype.sty


      I can't exclude there are other instances where different ways of defining commands are used.



      I'd not do it anyway, even if it's not that risky. Better do



      usepackage{mathtools}

      DeclarePairedDelimiters{foo}{langle}{rangle}


      (choose a meaningful name for your application) and use



      foo{x} foo[big]{x} foo[Big]{x} foo[bigg]{x} foo[Bigg]{x} foo*{x}


      for choosing the size of the delimiters (the last one is for automatic sizing with left and right, use it carefully).



      If you decide to use < and > beware that inside a tabbing environment you will have to use langle and rangle because tabbing redefines the two commands for its own purposes (but just inside the environment).






      share|improve this answer


























        1












        1








        1







        You risk that some obscure package defines something in term of > or define < and > themselves.



        A quick search reveals that < is defined in



        amsdtx.cls
        amsldoc.cls
        circ.sty
        cjhebrew.sty
        gmmeta.sty
        greektonoi.sty
        jlreq.cls
        lhcyralt.sty
        lhcyrkoi.sty
        lhcyrwin.sty
        pax.sty
        AlProTex.sty
        dev209.sty


        The command > is redefined in



        bxcjkjatype.sty
        gn-logic14.sty
        greektonoi.sty
        lhcyralt.sty
        lhcyrkoi.sty
        lhcyrwin.sty
        pax.sty
        AlProTex.sty
        sgamevar.sty
        zxjatype.sty


        I can't exclude there are other instances where different ways of defining commands are used.



        I'd not do it anyway, even if it's not that risky. Better do



        usepackage{mathtools}

        DeclarePairedDelimiters{foo}{langle}{rangle}


        (choose a meaningful name for your application) and use



        foo{x} foo[big]{x} foo[Big]{x} foo[bigg]{x} foo[Bigg]{x} foo*{x}


        for choosing the size of the delimiters (the last one is for automatic sizing with left and right, use it carefully).



        If you decide to use < and > beware that inside a tabbing environment you will have to use langle and rangle because tabbing redefines the two commands for its own purposes (but just inside the environment).






        share|improve this answer













        You risk that some obscure package defines something in term of > or define < and > themselves.



        A quick search reveals that < is defined in



        amsdtx.cls
        amsldoc.cls
        circ.sty
        cjhebrew.sty
        gmmeta.sty
        greektonoi.sty
        jlreq.cls
        lhcyralt.sty
        lhcyrkoi.sty
        lhcyrwin.sty
        pax.sty
        AlProTex.sty
        dev209.sty


        The command > is redefined in



        bxcjkjatype.sty
        gn-logic14.sty
        greektonoi.sty
        lhcyralt.sty
        lhcyrkoi.sty
        lhcyrwin.sty
        pax.sty
        AlProTex.sty
        sgamevar.sty
        zxjatype.sty


        I can't exclude there are other instances where different ways of defining commands are used.



        I'd not do it anyway, even if it's not that risky. Better do



        usepackage{mathtools}

        DeclarePairedDelimiters{foo}{langle}{rangle}


        (choose a meaningful name for your application) and use



        foo{x} foo[big]{x} foo[Big]{x} foo[bigg]{x} foo[Bigg]{x} foo*{x}


        for choosing the size of the delimiters (the last one is for automatic sizing with left and right, use it carefully).



        If you decide to use < and > beware that inside a tabbing environment you will have to use langle and rangle because tabbing redefines the two commands for its own purposes (but just inside the environment).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 1 hour ago









        egregegreg

        729k8819263237




        729k8819263237






















            Skeeve is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            Skeeve is a new contributor. Be nice, and check out our Code of Conduct.













            Skeeve is a new contributor. Be nice, and check out our Code of Conduct.












            Skeeve is a new contributor. Be nice, and check out our Code of Conduct.
















            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%2f481580%2frenew-command-to-rangle%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

            Lallio

            Unable to find Lightning Node

            Futebolista