Extra space after @hangfrom












3















I defined a command tstcmd with one parameter as @hangfrom{[#1]{ }}nobreak. When using this command, I found that there is always an extra space between the right bracket and the text that follows.



Here is the MWE:



documentclass{article}



makeatletter

deftstcmd#1{@hangfrom{[#1]{ }}nobreak}

%%DeclareRobustCommandtstcmd[1]{@hangfrom{[#1]{ }}nobreak}  %%No difference

defhf{@hangfrom}

makeatother



begin{document}



tstcmd{1} fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf

fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd fsdfsd

pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd



hf{[1]{ }}nobreak fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw

hojsoisdjf fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf

fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd



end{document}




Even if DeclareRobustCommand is used, the extra space remains, and apparently the nobreak in tstcmd is not effective. Does anyone know why it is like this and how to fix it? Thanks in advance.






horizontal-alignment







share|improve this question


















  • 1





    DeclareRobustCommand has nothing to do with the problems you described. nobreak should precede a skip (your space), not follow it. Your extraneous space comes from the fact that you write one in { } and another one after tstcmd{1}. I suggest something like newcommand*{tstcmd}[1]{@hangfrom{[#1]nolinebreak }ignorespaces} given your way of using it.

    – frougon
    Mar 21 at 7:15











  • In fact, @hangfrom puts its argument inside a box, therefore the nolinebreak is useless as written in my previous comment. It would be better before the ignorespaces, I think. Thus, newcommand*{tstcmd}[1]{@hangfrom{[#1] }nolinebreakignorespaces}.

    – frougon
    Mar 21 at 7:27













  • There may be exceptions (e.g., if the second space is followed by unskip), but usually, yes. Two space tokens.

    – frougon
    Mar 21 at 7:31











  • @frougon Now I see. Thanks a lot! Maybe you could post this as an answer so I can accept it.

    – Saad
    Mar 21 at 7:32











  • Why did you delete a question? It becomes difficult to follow...

    – frougon
    Mar 21 at 7:32
















3















I defined a command tstcmd with one parameter as @hangfrom{[#1]{ }}nobreak. When using this command, I found that there is always an extra space between the right bracket and the text that follows.



Here is the MWE:



documentclass{article}



makeatletter

deftstcmd#1{@hangfrom{[#1]{ }}nobreak}

%%DeclareRobustCommandtstcmd[1]{@hangfrom{[#1]{ }}nobreak}  %%No difference

defhf{@hangfrom}

makeatother



begin{document}



tstcmd{1} fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf

fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd fsdfsd

pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd



hf{[1]{ }}nobreak fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw

hojsoisdjf fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf

fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd



end{document}




Even if DeclareRobustCommand is used, the extra space remains, and apparently the nobreak in tstcmd is not effective. Does anyone know why it is like this and how to fix it? Thanks in advance.






horizontal-alignment







share|improve this question


















  • 1





    DeclareRobustCommand has nothing to do with the problems you described. nobreak should precede a skip (your space), not follow it. Your extraneous space comes from the fact that you write one in { } and another one after tstcmd{1}. I suggest something like newcommand*{tstcmd}[1]{@hangfrom{[#1]nolinebreak }ignorespaces} given your way of using it.

    – frougon
    Mar 21 at 7:15











  • In fact, @hangfrom puts its argument inside a box, therefore the nolinebreak is useless as written in my previous comment. It would be better before the ignorespaces, I think. Thus, newcommand*{tstcmd}[1]{@hangfrom{[#1] }nolinebreakignorespaces}.

    – frougon
    Mar 21 at 7:27













  • There may be exceptions (e.g., if the second space is followed by unskip), but usually, yes. Two space tokens.

    – frougon
    Mar 21 at 7:31











  • @frougon Now I see. Thanks a lot! Maybe you could post this as an answer so I can accept it.

    – Saad
    Mar 21 at 7:32











  • Why did you delete a question? It becomes difficult to follow...

    – frougon
    Mar 21 at 7:32














3












3








3








I defined a command tstcmd with one parameter as @hangfrom{[#1]{ }}nobreak. When using this command, I found that there is always an extra space between the right bracket and the text that follows.



Here is the MWE:



documentclass{article}



makeatletter

deftstcmd#1{@hangfrom{[#1]{ }}nobreak}

%%DeclareRobustCommandtstcmd[1]{@hangfrom{[#1]{ }}nobreak}  %%No difference

defhf{@hangfrom}

makeatother



begin{document}



tstcmd{1} fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf

fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd fsdfsd

pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd



hf{[1]{ }}nobreak fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw

hojsoisdjf fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf

fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd



end{document}




Even if DeclareRobustCommand is used, the extra space remains, and apparently the nobreak in tstcmd is not effective. Does anyone know why it is like this and how to fix it? Thanks in advance.






horizontal-alignment







share|improve this question














I defined a command tstcmd with one parameter as @hangfrom{[#1]{ }}nobreak. When using this command, I found that there is always an extra space between the right bracket and the text that follows.



Here is the MWE:



documentclass{article}



makeatletter

deftstcmd#1{@hangfrom{[#1]{ }}nobreak}

%%DeclareRobustCommandtstcmd[1]{@hangfrom{[#1]{ }}nobreak}  %%No difference

defhf{@hangfrom}

makeatother



begin{document}



tstcmd{1} fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf

fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd fsdfsd

pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd



hf{[1]{ }}nobreak fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw

hojsoisdjf fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf

fsdfsd fsdfsd pppwp fsdfsd fsdfsd ewrwerw hojsoisdjf fsdfsd



end{document}




Even if DeclareRobustCommand is used, the extra space remains, and apparently the nobreak in tstcmd is not effective. Does anyone know why it is like this and how to fix it? Thanks in advance.






horizontal-alignment




horizontal-alignment






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 21 at 6:07









SaadSaad

152210




152210








  • 1





    DeclareRobustCommand has nothing to do with the problems you described. nobreak should precede a skip (your space), not follow it. Your extraneous space comes from the fact that you write one in { } and another one after tstcmd{1}. I suggest something like newcommand*{tstcmd}[1]{@hangfrom{[#1]nolinebreak }ignorespaces} given your way of using it.

    – frougon
    Mar 21 at 7:15











  • In fact, @hangfrom puts its argument inside a box, therefore the nolinebreak is useless as written in my previous comment. It would be better before the ignorespaces, I think. Thus, newcommand*{tstcmd}[1]{@hangfrom{[#1] }nolinebreakignorespaces}.

    – frougon
    Mar 21 at 7:27













  • There may be exceptions (e.g., if the second space is followed by unskip), but usually, yes. Two space tokens.

    – frougon
    Mar 21 at 7:31











  • @frougon Now I see. Thanks a lot! Maybe you could post this as an answer so I can accept it.

    – Saad
    Mar 21 at 7:32











  • Why did you delete a question? It becomes difficult to follow...

    – frougon
    Mar 21 at 7:32














  • 1





    DeclareRobustCommand has nothing to do with the problems you described. nobreak should precede a skip (your space), not follow it. Your extraneous space comes from the fact that you write one in { } and another one after tstcmd{1}. I suggest something like newcommand*{tstcmd}[1]{@hangfrom{[#1]nolinebreak }ignorespaces} given your way of using it.

    – frougon
    Mar 21 at 7:15











  • In fact, @hangfrom puts its argument inside a box, therefore the nolinebreak is useless as written in my previous comment. It would be better before the ignorespaces, I think. Thus, newcommand*{tstcmd}[1]{@hangfrom{[#1] }nolinebreakignorespaces}.

    – frougon
    Mar 21 at 7:27













  • There may be exceptions (e.g., if the second space is followed by unskip), but usually, yes. Two space tokens.

    – frougon
    Mar 21 at 7:31











  • @frougon Now I see. Thanks a lot! Maybe you could post this as an answer so I can accept it.

    – Saad
    Mar 21 at 7:32











  • Why did you delete a question? It becomes difficult to follow...

    – frougon
    Mar 21 at 7:32








1




1





DeclareRobustCommand has nothing to do with the problems you described. nobreak should precede a skip (your space), not follow it. Your extraneous space comes from the fact that you write one in { } and another one after tstcmd{1}. I suggest something like newcommand*{tstcmd}[1]{@hangfrom{[#1]nolinebreak }ignorespaces} given your way of using it.

– frougon
Mar 21 at 7:15





DeclareRobustCommand has nothing to do with the problems you described. nobreak should precede a skip (your space), not follow it. Your extraneous space comes from the fact that you write one in { } and another one after tstcmd{1}. I suggest something like newcommand*{tstcmd}[1]{@hangfrom{[#1]nolinebreak }ignorespaces} given your way of using it.

– frougon
Mar 21 at 7:15













In fact, @hangfrom puts its argument inside a box, therefore the nolinebreak is useless as written in my previous comment. It would be better before the ignorespaces, I think. Thus, newcommand*{tstcmd}[1]{@hangfrom{[#1] }nolinebreakignorespaces}.

– frougon
Mar 21 at 7:27







In fact, @hangfrom puts its argument inside a box, therefore the nolinebreak is useless as written in my previous comment. It would be better before the ignorespaces, I think. Thus, newcommand*{tstcmd}[1]{@hangfrom{[#1] }nolinebreakignorespaces}.

– frougon
Mar 21 at 7:27















There may be exceptions (e.g., if the second space is followed by unskip), but usually, yes. Two space tokens.

– frougon
Mar 21 at 7:31





There may be exceptions (e.g., if the second space is followed by unskip), but usually, yes. Two space tokens.

– frougon
Mar 21 at 7:31













@frougon Now I see. Thanks a lot! Maybe you could post this as an answer so I can accept it.

– Saad
Mar 21 at 7:32





@frougon Now I see. Thanks a lot! Maybe you could post this as an answer so I can accept it.

– Saad
Mar 21 at 7:32













Why did you delete a question? It becomes difficult to follow...

– frougon
Mar 21 at 7:32





Why did you delete a question? It becomes difficult to follow...

– frougon
Mar 21 at 7:32










1 Answer
1






active

oldest

votes


















4














DeclareRobustCommand has nothing to do with the problems you described. It would be useful if you wanted to put your tstcmd calls inside the argument of a command such as section, where stuff that is not protect'ed gets expanded before it is written to the .toc file. DeclareRobustCommand would make sure the command isn't expanded in such cases, but it doesn't seem very useful here.



nobreak should precede a glue item (here, your space) when you don't want it to be a legal breakpoint, not follow it. Your extraneous space comes from the fact that you wrote one space token in { } inside the macro definition and another one at the call site right after tstcmd{1}. I'd suggest something like:



newcommand*{tstcmd}[1]{%

  @hangfrom{[#1] }nolinebreakignorespaces}


given your way of using the command (i.e., with one space token afterwards that should be ignored).






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%2f480625%2fextra-space-after-hangfrom%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









    4














    DeclareRobustCommand has nothing to do with the problems you described. It would be useful if you wanted to put your tstcmd calls inside the argument of a command such as section, where stuff that is not protect'ed gets expanded before it is written to the .toc file. DeclareRobustCommand would make sure the command isn't expanded in such cases, but it doesn't seem very useful here.



    nobreak should precede a glue item (here, your space) when you don't want it to be a legal breakpoint, not follow it. Your extraneous space comes from the fact that you wrote one space token in { } inside the macro definition and another one at the call site right after tstcmd{1}. I'd suggest something like:



    newcommand*{tstcmd}[1]{%
    
  @hangfrom{[#1] }nolinebreakignorespaces}


    given your way of using the command (i.e., with one space token afterwards that should be ignored).






    share|improve this answer




























      4














      DeclareRobustCommand has nothing to do with the problems you described. It would be useful if you wanted to put your tstcmd calls inside the argument of a command such as section, where stuff that is not protect'ed gets expanded before it is written to the .toc file. DeclareRobustCommand would make sure the command isn't expanded in such cases, but it doesn't seem very useful here.



      nobreak should precede a glue item (here, your space) when you don't want it to be a legal breakpoint, not follow it. Your extraneous space comes from the fact that you wrote one space token in { } inside the macro definition and another one at the call site right after tstcmd{1}. I'd suggest something like:



      newcommand*{tstcmd}[1]{%
      
  @hangfrom{[#1] }nolinebreakignorespaces}


      given your way of using the command (i.e., with one space token afterwards that should be ignored).






      share|improve this answer


























        4












        4








        4







        DeclareRobustCommand has nothing to do with the problems you described. It would be useful if you wanted to put your tstcmd calls inside the argument of a command such as section, where stuff that is not protect'ed gets expanded before it is written to the .toc file. DeclareRobustCommand would make sure the command isn't expanded in such cases, but it doesn't seem very useful here.



        nobreak should precede a glue item (here, your space) when you don't want it to be a legal breakpoint, not follow it. Your extraneous space comes from the fact that you wrote one space token in { } inside the macro definition and another one at the call site right after tstcmd{1}. I'd suggest something like:



        newcommand*{tstcmd}[1]{%
        
  @hangfrom{[#1] }nolinebreakignorespaces}


        given your way of using the command (i.e., with one space token afterwards that should be ignored).






        share|improve this answer













        DeclareRobustCommand has nothing to do with the problems you described. It would be useful if you wanted to put your tstcmd calls inside the argument of a command such as section, where stuff that is not protect'ed gets expanded before it is written to the .toc file. DeclareRobustCommand would make sure the command isn't expanded in such cases, but it doesn't seem very useful here.



        nobreak should precede a glue item (here, your space) when you don't want it to be a legal breakpoint, not follow it. Your extraneous space comes from the fact that you wrote one space token in { } inside the macro definition and another one at the call site right after tstcmd{1}. I'd suggest something like:



        newcommand*{tstcmd}[1]{%
        
  @hangfrom{[#1] }nolinebreakignorespaces}


        given your way of using the command (i.e., with one space token afterwards that should be ignored).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 21 at 7:45









        frougonfrougon

        61969




        61969






























            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%2f480625%2fextra-space-after-hangfrom%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

            How to change which sound is reproduced for terminal bell?

            Image
            3 Recently upgrade to 18.10 from 18.04, and using the terminal is becoming annoying: the new alert sound is a drip ( /usr/share/sounds/gnome/default/alerts/drip.ogg ), and the previous one is still located at ( /usr/share/sounds/ubuntu/stereo/bell.ogg ). My issue is that at the gnome-terminal, when autocompleting or pressing left BOTH sounds are reproduced, at the same time. I want to just have ubuntu/stereo/bell.ogg active, not both . At the moment I have been only able to reduce the volume of the alerts (but still both are played), or turn the alerts down (but I dislike both "solutions"). gnome-terminal 18.10 teminal-bell share | improve this question
            Read more

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

            Image
            up vote 5 down vote favorite 2 I would like to make it so that the vertical space below the title of each chapter is the same when using the Bjornstrup package (i.e. so that the descenders do not affect the spacing - as shown by the red arrow in the picture below). I think I'm fairly happy with the spacing around "A chapter", so I'd really like titles without descenders (e.g. "Contents") to have the same vertical spacing as "A chapter" below the title. I would also like to remove the large "0" in the contents title. Any help appreciated, as always. documentclass[11pt,a4paper]{book} % Packages[![enter image description here][1]][1] usepackage[left=3.5cm, right=3.5cm, top=4.3cm, bottom=4.25cm]{geometry} usepackage[utf8]{inputenc} usepackage{libertine} usepackage[libertine]{newtx
            Read more

            Can I use Tabulator js library in my java Spring + Thymeleaf project?

            Image
            0 I want to add Tabulator js to my java project. I added tabulator.min.js, tabulator.min.css to resources folder. After that added to my html page these dependencies as recommending in readme.md. <link rel="stylesheet" th:href="@{/css/tabulator.min.css}"> <script type="text/javascript" th:src="@{/js/tabulator.min.js}"></script> Now my tables view all elements, that I have in the html page, but not correct. In the documentation of Tabulator is example how to create header and table, var table = new Tabulator("#example-table", { columns:[ {title:"Name", field:"name", sorter:"string", width:200, editor:true}, {title:"Age", field:"age", sorter:"
            Read more