pipe commands inside find -exec?2019 Community Moderator Electionmissing argument to find -execHow to find first match in multiple filesHow does this find command using “find … -exec sh -c '…' sh +” work?Problem combining -or and -exec with find commandConvert order for find … -execHaving issues with FIND commands pruning directoriesCorrect location for piping and redirecting output in find -exec?find -exec ; economyTrying to add multiple grep commands within an execHow to rename a file to have the same name and extension as another file in same directory

Exposing a company lying about themselves in a tight-knitted industry: Is my career at risk on the long run?

Knife as defense against stray dogs

Asserting that Atheism and Theism are both faith based positions

Can "few" be used as a subject? If so, what is the rule?

TDE Master Key Rotation

"Marked down as someone wanting to sell shares." What does that mean?

The English Debate

Probabilities in non-stationary states

Bash prompt display HH:MM:SS

Friend wants my recommendation but I don't want to

Writing in a Christian voice

Norwegian Refugee travel document

Splitting fasta file into smaller files based on header pattern

Print last inputted byte

How to test the sharpness of a knife?

When should a starting writer get his own webpage?

Would mining huge amounts of resources on the Moon change its orbit?

Why does Surtur say that Thor is Asgard's doom?

Determine voltage drop over 10G resistors with cheap multimeter

is this saw blade faulty?

How can I create URL shortcuts/redirects for task/diff IDs in Phabricator?

Align centered, ragged right and ragged left in align environment

What is it called when someone votes for an option that's not their first choice?

Can other pieces capture a threatening piece and prevent a checkmate?



pipe commands inside find -exec?



2019 Community Moderator Electionmissing argument to find -execHow to find first match in multiple filesHow does this find command using “find … -exec sh -c '…' sh +” work?Problem combining -or and -exec with find commandConvert order for find … -execHaving issues with FIND commands pruning directoriesCorrect location for piping and redirecting output in find -exec?find -exec ; economyTrying to add multiple grep commands within an execHow to rename a file to have the same name and extension as another file in same directory










2















Let's suppose I want to find all .txt files and search for some string. I would do:



find ./ -type f -name "*.txt" -exec egrep -iH 'something' '' ;


What if I want to do a more complex filtering, like this:



egrep something file.txt | egrep somethingelse | egrep other


Inside find -exec? (or similar)



Please keep in mind that I'm searching for a solution that I could easily type when I need it. I know that this could be done with a few lines using a shell script, but that isn't what I'm looking for.










share|improve this question









New contributor




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
























    2















    Let's suppose I want to find all .txt files and search for some string. I would do:



    find ./ -type f -name "*.txt" -exec egrep -iH 'something' '' ;


    What if I want to do a more complex filtering, like this:



    egrep something file.txt | egrep somethingelse | egrep other


    Inside find -exec? (or similar)



    Please keep in mind that I'm searching for a solution that I could easily type when I need it. I know that this could be done with a few lines using a shell script, but that isn't what I'm looking for.










    share|improve this question









    New contributor




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






















      2












      2








      2








      Let's suppose I want to find all .txt files and search for some string. I would do:



      find ./ -type f -name "*.txt" -exec egrep -iH 'something' '' ;


      What if I want to do a more complex filtering, like this:



      egrep something file.txt | egrep somethingelse | egrep other


      Inside find -exec? (or similar)



      Please keep in mind that I'm searching for a solution that I could easily type when I need it. I know that this could be done with a few lines using a shell script, but that isn't what I'm looking for.










      share|improve this question









      New contributor




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












      Let's suppose I want to find all .txt files and search for some string. I would do:



      find ./ -type f -name "*.txt" -exec egrep -iH 'something' '' ;


      What if I want to do a more complex filtering, like this:



      egrep something file.txt | egrep somethingelse | egrep other


      Inside find -exec? (or similar)



      Please keep in mind that I'm searching for a solution that I could easily type when I need it. I know that this could be done with a few lines using a shell script, but that isn't what I'm looking for.







      shell find pipe






      share|improve this question









      New contributor




      1nt3rn3t 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




      1nt3rn3t 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








      edited 4 hours ago









      terdon

      132k32262441




      132k32262441






      New contributor




      1nt3rn3t 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









      1nt3rn3t1nt3rn3t

      132




      132




      New contributor




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





      New contributor





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






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




















          2 Answers
          2






          active

          oldest

          votes


















          4














          If you must do it from within find, you need to call a shell:



          find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh ;


          Other alternatives include using xargs instead:



          find ./ -type f -name "*.txt" | 
          xargs -I grep -EiH something |
          grep -EiH somethingelse |
          grep -EiH other


          Or, much safer for arbitrary filenames (assuming your find supports -print0):



          find ./ -type f -name "*.txt" -print0 | 
          xargs -0 grep -EiH something |
          grep -Ei somethingelse |
          grep -Ei other


          Or, you could just use a shell loop instead:



          find ./ -type f -name "*.txt" -print0 | 
          while IFS= read -d '' file; do
          grep -Ei something "$file" |
          grep -Ei somethingelse |
          grep -Ei other
          done





          share|improve this answer

























          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • ... and xargs could also be used as xargs -I sh -c '...' sh , if one wanted to (it makes it possible to run parallel jobs with -P if one wanted to).

            – Kusalananda
            3 hours ago


















          0














          You can put bash (or another shell) as your -exec command:



          find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "" | egrep somethingelse | egrep other' ;


          One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:



          for i in $(find -type -f -name "*.txt"); do
          if egrep -iH something "$i" | egrep somethingelse | egrep other; then
          echo "Found something: $i"
          fi
          done





          share|improve this answer








          New contributor




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




















          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • That for loop is a very bad idea.Also known as bash pitfall #1.

            – terdon
            3 hours ago











          • This "" in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named " & rm -rf ~ & : ".txt. Luckily for you -type -f is invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right: find … -exec sh -c '… "$1" …' foo ;.

            – Kamil Maciorowski
            2 hours ago











          • Thanks for the information! Yeah, the -type -f is a typo I make constantly when using find, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.

            – trobinson
            25 mins ago










          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',
          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
          );



          );






          1nt3rn3t 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%2funix.stackexchange.com%2fquestions%2f507023%2fpipe-commands-inside-find-exec%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          4














          If you must do it from within find, you need to call a shell:



          find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh ;


          Other alternatives include using xargs instead:



          find ./ -type f -name "*.txt" | 
          xargs -I grep -EiH something |
          grep -EiH somethingelse |
          grep -EiH other


          Or, much safer for arbitrary filenames (assuming your find supports -print0):



          find ./ -type f -name "*.txt" -print0 | 
          xargs -0 grep -EiH something |
          grep -Ei somethingelse |
          grep -Ei other


          Or, you could just use a shell loop instead:



          find ./ -type f -name "*.txt" -print0 | 
          while IFS= read -d '' file; do
          grep -Ei something "$file" |
          grep -Ei somethingelse |
          grep -Ei other
          done





          share|improve this answer

























          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • ... and xargs could also be used as xargs -I sh -c '...' sh , if one wanted to (it makes it possible to run parallel jobs with -P if one wanted to).

            – Kusalananda
            3 hours ago















          4














          If you must do it from within find, you need to call a shell:



          find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh ;


          Other alternatives include using xargs instead:



          find ./ -type f -name "*.txt" | 
          xargs -I grep -EiH something |
          grep -EiH somethingelse |
          grep -EiH other


          Or, much safer for arbitrary filenames (assuming your find supports -print0):



          find ./ -type f -name "*.txt" -print0 | 
          xargs -0 grep -EiH something |
          grep -Ei somethingelse |
          grep -Ei other


          Or, you could just use a shell loop instead:



          find ./ -type f -name "*.txt" -print0 | 
          while IFS= read -d '' file; do
          grep -Ei something "$file" |
          grep -Ei somethingelse |
          grep -Ei other
          done





          share|improve this answer

























          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • ... and xargs could also be used as xargs -I sh -c '...' sh , if one wanted to (it makes it possible to run parallel jobs with -P if one wanted to).

            – Kusalananda
            3 hours ago













          4












          4








          4







          If you must do it from within find, you need to call a shell:



          find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh ;


          Other alternatives include using xargs instead:



          find ./ -type f -name "*.txt" | 
          xargs -I grep -EiH something |
          grep -EiH somethingelse |
          grep -EiH other


          Or, much safer for arbitrary filenames (assuming your find supports -print0):



          find ./ -type f -name "*.txt" -print0 | 
          xargs -0 grep -EiH something |
          grep -Ei somethingelse |
          grep -Ei other


          Or, you could just use a shell loop instead:



          find ./ -type f -name "*.txt" -print0 | 
          while IFS= read -d '' file; do
          grep -Ei something "$file" |
          grep -Ei somethingelse |
          grep -Ei other
          done





          share|improve this answer















          If you must do it from within find, you need to call a shell:



          find ./ -type f -name "*.txt" -exec sh -c 'grep -EiH something "$1" | grep -E somethingelse | grep -E other' sh ;


          Other alternatives include using xargs instead:



          find ./ -type f -name "*.txt" | 
          xargs -I grep -EiH something |
          grep -EiH somethingelse |
          grep -EiH other


          Or, much safer for arbitrary filenames (assuming your find supports -print0):



          find ./ -type f -name "*.txt" -print0 | 
          xargs -0 grep -EiH something |
          grep -Ei somethingelse |
          grep -Ei other


          Or, you could just use a shell loop instead:



          find ./ -type f -name "*.txt" -print0 | 
          while IFS= read -d '' file; do
          grep -Ei something "$file" |
          grep -Ei somethingelse |
          grep -Ei other
          done






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 3 hours ago









          Kusalananda

          136k17257425




          136k17257425










          answered 3 hours ago









          terdonterdon

          132k32262441




          132k32262441












          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • ... and xargs could also be used as xargs -I sh -c '...' sh , if one wanted to (it makes it possible to run parallel jobs with -P if one wanted to).

            – Kusalananda
            3 hours ago

















          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • ... and xargs could also be used as xargs -I sh -c '...' sh , if one wanted to (it makes it possible to run parallel jobs with -P if one wanted to).

            – Kusalananda
            3 hours ago
















          The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

          – 1nt3rn3t
          3 hours ago





          The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

          – 1nt3rn3t
          3 hours ago













          ... and xargs could also be used as xargs -I sh -c '...' sh , if one wanted to (it makes it possible to run parallel jobs with -P if one wanted to).

          – Kusalananda
          3 hours ago





          ... and xargs could also be used as xargs -I sh -c '...' sh , if one wanted to (it makes it possible to run parallel jobs with -P if one wanted to).

          – Kusalananda
          3 hours ago













          0














          You can put bash (or another shell) as your -exec command:



          find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "" | egrep somethingelse | egrep other' ;


          One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:



          for i in $(find -type -f -name "*.txt"); do
          if egrep -iH something "$i" | egrep somethingelse | egrep other; then
          echo "Found something: $i"
          fi
          done





          share|improve this answer








          New contributor




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




















          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • That for loop is a very bad idea.Also known as bash pitfall #1.

            – terdon
            3 hours ago











          • This "" in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named " & rm -rf ~ & : ".txt. Luckily for you -type -f is invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right: find … -exec sh -c '… "$1" …' foo ;.

            – Kamil Maciorowski
            2 hours ago











          • Thanks for the information! Yeah, the -type -f is a typo I make constantly when using find, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.

            – trobinson
            25 mins ago















          0














          You can put bash (or another shell) as your -exec command:



          find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "" | egrep somethingelse | egrep other' ;


          One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:



          for i in $(find -type -f -name "*.txt"); do
          if egrep -iH something "$i" | egrep somethingelse | egrep other; then
          echo "Found something: $i"
          fi
          done





          share|improve this answer








          New contributor




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




















          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • That for loop is a very bad idea.Also known as bash pitfall #1.

            – terdon
            3 hours ago











          • This "" in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named " & rm -rf ~ & : ".txt. Luckily for you -type -f is invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right: find … -exec sh -c '… "$1" …' foo ;.

            – Kamil Maciorowski
            2 hours ago











          • Thanks for the information! Yeah, the -type -f is a typo I make constantly when using find, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.

            – trobinson
            25 mins ago













          0












          0








          0







          You can put bash (or another shell) as your -exec command:



          find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "" | egrep somethingelse | egrep other' ;


          One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:



          for i in $(find -type -f -name "*.txt"); do
          if egrep -iH something "$i" | egrep somethingelse | egrep other; then
          echo "Found something: $i"
          fi
          done





          share|improve this answer








          New contributor




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










          You can put bash (or another shell) as your -exec command:



          find -type -f -name "*.txt" -exec bash -c 'egrep -iH something "" | egrep somethingelse | egrep other' ;


          One of the downsides of doing it this way is that it creates more potential for nested quoting issues as your commands get more complex. If you want to avoid that, you can break it out into a for-loop:



          for i in $(find -type -f -name "*.txt"); do
          if egrep -iH something "$i" | egrep somethingelse | egrep other; then
          echo "Found something: $i"
          fi
          done






          share|improve this answer








          New contributor




          trobinson 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 answer



          share|improve this answer






          New contributor




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









          answered 3 hours ago









          trobinsontrobinson

          261




          261




          New contributor




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





          New contributor





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






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












          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • That for loop is a very bad idea.Also known as bash pitfall #1.

            – terdon
            3 hours ago











          • This "" in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named " & rm -rf ~ & : ".txt. Luckily for you -type -f is invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right: find … -exec sh -c '… "$1" …' foo ;.

            – Kamil Maciorowski
            2 hours ago











          • Thanks for the information! Yeah, the -type -f is a typo I make constantly when using find, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.

            – trobinson
            25 mins ago

















          • The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

            – 1nt3rn3t
            3 hours ago











          • That for loop is a very bad idea.Also known as bash pitfall #1.

            – terdon
            3 hours ago











          • This "" in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named " & rm -rf ~ & : ".txt. Luckily for you -type -f is invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right: find … -exec sh -c '… "$1" …' foo ;.

            – Kamil Maciorowski
            2 hours ago











          • Thanks for the information! Yeah, the -type -f is a typo I make constantly when using find, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.

            – trobinson
            25 mins ago
















          The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

          – 1nt3rn3t
          3 hours ago





          The first one is exactly what I was looking for. Extremely simple and small enough to type depending on my needs. Thanks.

          – 1nt3rn3t
          3 hours ago













          That for loop is a very bad idea.Also known as bash pitfall #1.

          – terdon
          3 hours ago





          That for loop is a very bad idea.Also known as bash pitfall #1.

          – terdon
          3 hours ago













          This "" in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named " & rm -rf ~ & : ".txt. Luckily for you -type -f is invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right: find … -exec sh -c '… "$1" …' foo ;.

          – Kamil Maciorowski
          2 hours ago





          This "" in your first command may even lead to code injection. Imagine you got files from me and there's a file literally named " & rm -rf ~ & : ".txt. Luckily for you -type -f is invalid, it just saved your home directory. Fix the typo and try again. :) terdon did it right: find … -exec sh -c '… "$1" …' foo ;.

          – Kamil Maciorowski
          2 hours ago













          Thanks for the information! Yeah, the -type -f is a typo I make constantly when using find, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.

          – trobinson
          25 mins ago





          Thanks for the information! Yeah, the -type -f is a typo I make constantly when using find, and I didn't notice it in my answer. Whoops. terdon's answer is better, but I'll leave this for comparative purposes.

          – trobinson
          25 mins ago










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









          draft saved

          draft discarded


















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












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











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














          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f507023%2fpipe-commands-inside-find-exec%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

          acmart: Multiple authors: all with same affiliation, one author an additional affiliationHow to Write Names of Multiple Authors with Shared Affiliation in ACM 2017 Template?Multiple authors with different primary affiliation, but same additional affiliationSame affiliation for all authors without extra packagesIOS-Book-Article.cls: one author with multiple affiliationacmart: Shared Author AffiliationMultiple authors with different primary affiliation, but same additional affiliationAuthor affiliation with only 1 authorAdding Multiple Authors with Different Affiliation in LaTeX ArticleLaTeX: Multiple authors stays on same lineHow to Label Multiple Authors with Same DescriptionHow to make two authors use the same affiliationTwo authors with same affiliation on finished front page

          How to write “ä” and other umlauts and accented letters in bibliography?Accents in BibTeXSorting references with special characters alphabeticallyUse ae ligature in bibliographyEastern European nameInverted circumflex in BibTexBibTex, non-ascii initials and nameptr fproblems with accent in LatexHow to add a Ø to my bibliography from Jabref?References without accentsTroubles when trying to cite St“omer-Verlet in ”title" field of a bib entryComprehensive list of accented charactersHow to type the letter “i” with two dots (diaeresis) in math mode?Problem with glossary text and accented lettersSpecial character in bibliographyAccented letters, Unicode and LaTeX accentsHow to stop natbib from modifying bibliography styleCitation of a paper with non-standard characters by BibtexWrite accented characters to file using writeHow to group the bibliography alphabetically, if some surnames start with “accented” characters?How can I automatically capitalize significant words in my bibliography?

          How to remove border form elements in the last row?Targeting flex items on the last rowHow to vertically wrap content with flexbox?Remove border from IFrameCSS3's border-radius property and border-collapse:collapse don't mix. How can I use border-radius to create a collapsed table with rounded corners?Div width 100% minus fixed amount of pixelsBorder around specific rows in a table?How to remove border (outline) around text/input boxes? (Chrome)How do I remove the space between inline-block elements?Flex-box: Align last row to gridRemove blue border from css custom-styled button in ChromeFill remaining vertical space with CSS using display:flexhow style elements in the last row of flexbox row layout with pure css without js