How do I find all files that end with a dot












1















How do I find all files that end with a "." (dot) and then delete them? Is there a program that can do this?



Example:



Desktop DB.
mp600osxpd542ej7.






files







share|improve this question







New contributor




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





















  • find -name *. -delete maybe

    – guiverc
    3 hours ago











  • I would to list the files first so that I don't delete something that I want to keep.

    – Kathryn Trucano
    3 hours ago











  • I would never run a command like that first time with a -delete option; run it without the delete so it just finds the files, and you can peruse the files it will delete, then only when happy add the -delete option). find finds files by name, date, permissions or anything, but you can also tell it to execute something for each file, delete them etc. It's a standard *nix command from 1978

    – guiverc
    3 hours ago













  • Do you need this to delete plain files only - or directories as well? does it need to be recursive or just files at one directory level?

    – steeldriver
    3 hours ago
















1















How do I find all files that end with a "." (dot) and then delete them? Is there a program that can do this?



Example:



Desktop DB.
mp600osxpd542ej7.






files







share|improve this question







New contributor




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





















  • find -name *. -delete maybe

    – guiverc
    3 hours ago











  • I would to list the files first so that I don't delete something that I want to keep.

    – Kathryn Trucano
    3 hours ago











  • I would never run a command like that first time with a -delete option; run it without the delete so it just finds the files, and you can peruse the files it will delete, then only when happy add the -delete option). find finds files by name, date, permissions or anything, but you can also tell it to execute something for each file, delete them etc. It's a standard *nix command from 1978

    – guiverc
    3 hours ago













  • Do you need this to delete plain files only - or directories as well? does it need to be recursive or just files at one directory level?

    – steeldriver
    3 hours ago














1












1








1








How do I find all files that end with a "." (dot) and then delete them? Is there a program that can do this?



Example:



Desktop DB.
mp600osxpd542ej7.






files







share|improve this question







New contributor




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












How do I find all files that end with a "." (dot) and then delete them? Is there a program that can do this?



Example:



Desktop DB.
mp600osxpd542ej7.






files




files






share|improve this question







New contributor




Kathryn Trucano 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




Kathryn Trucano 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




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









asked 3 hours ago









Kathryn TrucanoKathryn Trucano

61




61




New contributor




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





New contributor





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






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













  • find -name *. -delete maybe

    – guiverc
    3 hours ago











  • I would to list the files first so that I don't delete something that I want to keep.

    – Kathryn Trucano
    3 hours ago











  • I would never run a command like that first time with a -delete option; run it without the delete so it just finds the files, and you can peruse the files it will delete, then only when happy add the -delete option). find finds files by name, date, permissions or anything, but you can also tell it to execute something for each file, delete them etc. It's a standard *nix command from 1978

    – guiverc
    3 hours ago













  • Do you need this to delete plain files only - or directories as well? does it need to be recursive or just files at one directory level?

    – steeldriver
    3 hours ago



















  • find -name *. -delete maybe

    – guiverc
    3 hours ago











  • I would to list the files first so that I don't delete something that I want to keep.

    – Kathryn Trucano
    3 hours ago











  • I would never run a command like that first time with a -delete option; run it without the delete so it just finds the files, and you can peruse the files it will delete, then only when happy add the -delete option). find finds files by name, date, permissions or anything, but you can also tell it to execute something for each file, delete them etc. It's a standard *nix command from 1978

    – guiverc
    3 hours ago













  • Do you need this to delete plain files only - or directories as well? does it need to be recursive or just files at one directory level?

    – steeldriver
    3 hours ago

















find -name *. -delete maybe

– guiverc
3 hours ago





find -name *. -delete maybe

– guiverc
3 hours ago













I would to list the files first so that I don't delete something that I want to keep.

– Kathryn Trucano
3 hours ago





I would to list the files first so that I don't delete something that I want to keep.

– Kathryn Trucano
3 hours ago













I would never run a command like that first time with a -delete option; run it without the delete so it just finds the files, and you can peruse the files it will delete, then only when happy add the -delete option). find finds files by name, date, permissions or anything, but you can also tell it to execute something for each file, delete them etc. It's a standard *nix command from 1978

– guiverc
3 hours ago







I would never run a command like that first time with a -delete option; run it without the delete so it just finds the files, and you can peruse the files it will delete, then only when happy add the -delete option). find finds files by name, date, permissions or anything, but you can also tell it to execute something for each file, delete them etc. It's a standard *nix command from 1978

– guiverc
3 hours ago















Do you need this to delete plain files only - or directories as well? does it need to be recursive or just files at one directory level?

– steeldriver
3 hours ago





Do you need this to delete plain files only - or directories as well? does it need to be recursive or just files at one directory level?

– steeldriver
3 hours ago










2 Answers
2






active

oldest

votes


















3














The following cmd will do:



find . -type f -name '*.' -exec rm -i {} ;


cmd explanation:





  • find: the utility we used to search for files and perform actions on them.


  • -type f:that makes sure that we find files only


  • -name '*.': that tell find to pick up files with names that match the pattern, which has a wildcard *, that matches any number of characters, followed by the dot we're looking for.

    note that we quoted the pattern, this is important to avoid the expansion of the wildcard by the shell.


  • -exec: that tells find to perform the following action on the files that have been found.


  • rm -i {}: the cmd rm -i removes files interactively, which means that it will ask you any time, it wants to delete a file, that's a good option if you want to check your files one by one before deletion, otherwise you can omit the option -i.

    the curly braces are placeholders for the files found by find.

  • finally we end the command executed by find with an escaped semicolon ;






share|improve this answer








New contributor




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




























    0














    find -name "*." -delete



    find will locate files named pattern '*.' (ie. end in a dot) & delete them. The use of -delete also implies -depth too, but adjust to your needs.



    Quotes added as I'd forgotten, thanks @steeldriver






    share|improve this answer

























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      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: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      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
      });


      }
      });






      Kathryn Trucano 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%2faskubuntu.com%2fquestions%2f1128144%2fhow-do-i-find-all-files-that-end-with-a-dot%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









      3














      The following cmd will do:



      find . -type f -name '*.' -exec rm -i {} ;


      cmd explanation:





      • find: the utility we used to search for files and perform actions on them.


      • -type f:that makes sure that we find files only


      • -name '*.': that tell find to pick up files with names that match the pattern, which has a wildcard *, that matches any number of characters, followed by the dot we're looking for.

        note that we quoted the pattern, this is important to avoid the expansion of the wildcard by the shell.


      • -exec: that tells find to perform the following action on the files that have been found.


      • rm -i {}: the cmd rm -i removes files interactively, which means that it will ask you any time, it wants to delete a file, that's a good option if you want to check your files one by one before deletion, otherwise you can omit the option -i.

        the curly braces are placeholders for the files found by find.

      • finally we end the command executed by find with an escaped semicolon ;






      share|improve this answer








      New contributor




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

























        3














        The following cmd will do:



        find . -type f -name '*.' -exec rm -i {} ;


        cmd explanation:





        • find: the utility we used to search for files and perform actions on them.


        • -type f:that makes sure that we find files only


        • -name '*.': that tell find to pick up files with names that match the pattern, which has a wildcard *, that matches any number of characters, followed by the dot we're looking for.

          note that we quoted the pattern, this is important to avoid the expansion of the wildcard by the shell.


        • -exec: that tells find to perform the following action on the files that have been found.


        • rm -i {}: the cmd rm -i removes files interactively, which means that it will ask you any time, it wants to delete a file, that's a good option if you want to check your files one by one before deletion, otherwise you can omit the option -i.

          the curly braces are placeholders for the files found by find.

        • finally we end the command executed by find with an escaped semicolon ;






        share|improve this answer








        New contributor




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























          3












          3








          3







          The following cmd will do:



          find . -type f -name '*.' -exec rm -i {} ;


          cmd explanation:





          • find: the utility we used to search for files and perform actions on them.


          • -type f:that makes sure that we find files only


          • -name '*.': that tell find to pick up files with names that match the pattern, which has a wildcard *, that matches any number of characters, followed by the dot we're looking for.

            note that we quoted the pattern, this is important to avoid the expansion of the wildcard by the shell.


          • -exec: that tells find to perform the following action on the files that have been found.


          • rm -i {}: the cmd rm -i removes files interactively, which means that it will ask you any time, it wants to delete a file, that's a good option if you want to check your files one by one before deletion, otherwise you can omit the option -i.

            the curly braces are placeholders for the files found by find.

          • finally we end the command executed by find with an escaped semicolon ;






          share|improve this answer








          New contributor




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










          The following cmd will do:



          find . -type f -name '*.' -exec rm -i {} ;


          cmd explanation:





          • find: the utility we used to search for files and perform actions on them.


          • -type f:that makes sure that we find files only


          • -name '*.': that tell find to pick up files with names that match the pattern, which has a wildcard *, that matches any number of characters, followed by the dot we're looking for.

            note that we quoted the pattern, this is important to avoid the expansion of the wildcard by the shell.


          • -exec: that tells find to perform the following action on the files that have been found.


          • rm -i {}: the cmd rm -i removes files interactively, which means that it will ask you any time, it wants to delete a file, that's a good option if you want to check your files one by one before deletion, otherwise you can omit the option -i.

            the curly braces are placeholders for the files found by find.

          • finally we end the command executed by find with an escaped semicolon ;







          share|improve this answer








          New contributor




          HElanabi 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




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









          answered 2 hours ago









          HElanabiHElanabi

          392




          392




          New contributor




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





          New contributor





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






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

























              0














              find -name "*." -delete



              find will locate files named pattern '*.' (ie. end in a dot) & delete them. The use of -delete also implies -depth too, but adjust to your needs.



              Quotes added as I'd forgotten, thanks @steeldriver






              share|improve this answer






























                0














                find -name "*." -delete



                find will locate files named pattern '*.' (ie. end in a dot) & delete them. The use of -delete also implies -depth too, but adjust to your needs.



                Quotes added as I'd forgotten, thanks @steeldriver






                share|improve this answer




























                  0












                  0








                  0







                  find -name "*." -delete



                  find will locate files named pattern '*.' (ie. end in a dot) & delete them. The use of -delete also implies -depth too, but adjust to your needs.



                  Quotes added as I'd forgotten, thanks @steeldriver






                  share|improve this answer















                  find -name "*." -delete



                  find will locate files named pattern '*.' (ie. end in a dot) & delete them. The use of -delete also implies -depth too, but adjust to your needs.



                  Quotes added as I'd forgotten, thanks @steeldriver







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 3 hours ago

























                  answered 3 hours ago









                  guivercguiverc

                  5,02121623




                  5,02121623






















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










                      draft saved

                      draft discarded


















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













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












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
















                      Thanks for contributing an answer to Ask Ubuntu!


                      • 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%2faskubuntu.com%2fquestions%2f1128144%2fhow-do-i-find-all-files-that-end-with-a-dot%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

                      SQL Server 17 - Attemping to backup to remote NAS but Access is denied

                      Image
                      .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0; } 0 I was attemping to use Ola Hallengrens scripts to backup to a remote NAS, but it was failing and not giving any direct errors, so I tried doing it manually using Server Management Studio and got the following error: TITLE: Microsoft SQL Server Management Studio Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476 ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The operating system returned the error '0x80070005(Access is denied.)&#
                      Read more

                      Always On Availability groups resolving state after failover - Remote harden of transaction...

                      Image
                      0 My explanation will be opinion based as it is based on my findings. If more information is needed, I am always happy to add it. The setup We have 4 SQL Server 2016 Instances, and all 4 underlying servers are in a WSFC (In my eyes a strange setup since Always On AG's are 2 by 2. But that is a different question.) 4 nodes + Fileshare witness Version: 13.0.5026.0 (all nodes) The instances that are having the failover issues are instances 1 & 2. They have 3 AG's between them. AG1 is primary on instance 1 and is having the issue. AG2 and AG3 are primary on instance 2. Instances 3 and 4 have their own separate AG's (2). AG1's settings The week before Last week, after checking for long running queries (none) and the synchronization state (green accross the board) we initiated a
                      Read more

                      Restoring from pg_dump with foreign key constraints

                      Image
                      5 2 In restoring a database from a pg_dump , a number of errors are being generated and the whole table is subsequently being ignored. An example: ERROR: insert or update on table "channelproducts" violates foreign key constraint "fk_rails_dfaae373a5" DETAIL: Key (channel_id)=(1) is not present in table "channels". Interestingly enough, I've noted that all these instances are popping up because of the sequence of loading. channels is after channelproducts both alphabetically and in the file and thus I can understand why postgres complains about having to create a child without a parent. caveat: the foreign key is being generated automatically by rails 4.2: I could remove the problem at the source but that still does not really solve the problem... version: PostgreSQL
                      Read more