Using one for_window and assign, or just for_window?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
-1
down vote

favorite












I want to both



  • move my irssi window to a specific workspace

  • remove the border and title

Before I removed the border I had



assign [class="^kitty$" instance="^__irssi__"] → $ws10


This worked great, but now I want to remove the border so I add



for_window [class="^kitty$" instance="^__irssi__"] border none


That does exactly what I want, but I can drop the assign and just have the for_window with,



for_window [class="^kitty$" instance="^__irssi__"] move to workspace $ws10, border none


I know the i3 docs say this about for_window,




The difference between assign and for_window <criteria> move to workspace is that the former will only be executed when the application maps the window (mapping means actually displaying it on the screen) but the latter will be executed whenever a window changes its properties to something that matches the specified criteria.




But that doesn't seem to provide me any guidance when I don't care about that. It also raises the question does anyone really care? It seems like assign protects you against a window that both,



  • Changes properties after initialization

  • Would otherwise trigger a rule after one of those changes because you could not make the rule more specific to exclude the window's new properties?

Am I missing something here? I just have a feeling like that's a very small use case and I must be reading it wrong. Should I care about this difference? When would I care? And what should I do here, have an assign and for_workspace, or just merge them into a single for_workspace?










share|improve this question



























    up vote
    -1
    down vote

    favorite












    I want to both



    • move my irssi window to a specific workspace

    • remove the border and title

    Before I removed the border I had



    assign [class="^kitty$" instance="^__irssi__"] → $ws10


    This worked great, but now I want to remove the border so I add



    for_window [class="^kitty$" instance="^__irssi__"] border none


    That does exactly what I want, but I can drop the assign and just have the for_window with,



    for_window [class="^kitty$" instance="^__irssi__"] move to workspace $ws10, border none


    I know the i3 docs say this about for_window,




    The difference between assign and for_window <criteria> move to workspace is that the former will only be executed when the application maps the window (mapping means actually displaying it on the screen) but the latter will be executed whenever a window changes its properties to something that matches the specified criteria.




    But that doesn't seem to provide me any guidance when I don't care about that. It also raises the question does anyone really care? It seems like assign protects you against a window that both,



    • Changes properties after initialization

    • Would otherwise trigger a rule after one of those changes because you could not make the rule more specific to exclude the window's new properties?

    Am I missing something here? I just have a feeling like that's a very small use case and I must be reading it wrong. Should I care about this difference? When would I care? And what should I do here, have an assign and for_workspace, or just merge them into a single for_workspace?










    share|improve this question

























      up vote
      -1
      down vote

      favorite









      up vote
      -1
      down vote

      favorite











      I want to both



      • move my irssi window to a specific workspace

      • remove the border and title

      Before I removed the border I had



      assign [class="^kitty$" instance="^__irssi__"] → $ws10


      This worked great, but now I want to remove the border so I add



      for_window [class="^kitty$" instance="^__irssi__"] border none


      That does exactly what I want, but I can drop the assign and just have the for_window with,



      for_window [class="^kitty$" instance="^__irssi__"] move to workspace $ws10, border none


      I know the i3 docs say this about for_window,




      The difference between assign and for_window <criteria> move to workspace is that the former will only be executed when the application maps the window (mapping means actually displaying it on the screen) but the latter will be executed whenever a window changes its properties to something that matches the specified criteria.




      But that doesn't seem to provide me any guidance when I don't care about that. It also raises the question does anyone really care? It seems like assign protects you against a window that both,



      • Changes properties after initialization

      • Would otherwise trigger a rule after one of those changes because you could not make the rule more specific to exclude the window's new properties?

      Am I missing something here? I just have a feeling like that's a very small use case and I must be reading it wrong. Should I care about this difference? When would I care? And what should I do here, have an assign and for_workspace, or just merge them into a single for_workspace?










      share|improve this question















      I want to both



      • move my irssi window to a specific workspace

      • remove the border and title

      Before I removed the border I had



      assign [class="^kitty$" instance="^__irssi__"] → $ws10


      This worked great, but now I want to remove the border so I add



      for_window [class="^kitty$" instance="^__irssi__"] border none


      That does exactly what I want, but I can drop the assign and just have the for_window with,



      for_window [class="^kitty$" instance="^__irssi__"] move to workspace $ws10, border none


      I know the i3 docs say this about for_window,




      The difference between assign and for_window <criteria> move to workspace is that the former will only be executed when the application maps the window (mapping means actually displaying it on the screen) but the latter will be executed whenever a window changes its properties to something that matches the specified criteria.




      But that doesn't seem to provide me any guidance when I don't care about that. It also raises the question does anyone really care? It seems like assign protects you against a window that both,



      • Changes properties after initialization

      • Would otherwise trigger a rule after one of those changes because you could not make the rule more specific to exclude the window's new properties?

      Am I missing something here? I just have a feeling like that's a very small use case and I must be reading it wrong. Should I care about this difference? When would I care? And what should I do here, have an assign and for_workspace, or just merge them into a single for_workspace?







      configuration i3






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 30 at 2:35

























      asked Nov 30 at 2:28









      Evan Carroll

      5,01994178




      5,01994178

























          active

          oldest

          votes











          Your Answer








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

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

          else
          createEditor();

          );

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



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485055%2fusing-one-for-window-and-assign-or-just-for-window%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          draft saved

          draft discarded
















































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


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

          But avoid


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

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

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





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


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

          But avoid


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

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

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




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485055%2fusing-one-for-window-and-assign-or-just-for-window%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 check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay