Skip to main content
deleted 24 characters in body
Source Link
Rui F Ribeiro
  • 58k
  • 28
  • 156
  • 238

I'm a Linux newbie, and I only know little about bash (or any Linux shell - but I just use bash). I'm used to using for %c in (*.*) do {something} in cmd in Windows, and I really feel inconvenient without it. I tried wine cmd, but it wouldn't interpret Linux commands (which I need for the {something}) at all, which is not I want. Any help?

In Windows, for %c in (*.*) do {something} runs {something} once per file (ignoring directories). {something} can refer to %c for the current iteration's file name; other modifiers allow the file's path to be extracted, or the file's name without its path, the file's extension, attributes, modification date/time, size... for /d %c in (*.*) ... will process directories instead of files. In both cases *.* is equivalent to * in Unix-style systems, it matches all non-hidden files or directories, even those with no . in their name.

P.S. I know that the cmd "for" has many usages which may not be covered in one command in bash, but I just want to know the equivalent of the command mentioned above.

I'm a Linux newbie, and I only know little about bash (or any Linux shell - but I just use bash). I'm used to using for %c in (*.*) do {something} in cmd in Windows, and I really feel inconvenient without it. I tried wine cmd, but it wouldn't interpret Linux commands (which I need for the {something}) at all, which is not I want. Any help?

In Windows, for %c in (*.*) do {something} runs {something} once per file (ignoring directories). {something} can refer to %c for the current iteration's file name; other modifiers allow the file's path to be extracted, or the file's name without its path, the file's extension, attributes, modification date/time, size... for /d %c in (*.*) ... will process directories instead of files. In both cases *.* is equivalent to * in Unix-style systems, it matches all non-hidden files or directories, even those with no . in their name.

P.S. I know that the cmd "for" has many usages which may not be covered in one command in bash, but I just want to know the equivalent of the command mentioned above.

I only know little about bash (or any Linux shell - but I just use bash). I'm used to using for %c in (*.*) do {something} in cmd in Windows, and I really feel inconvenient without it. I tried wine cmd, but it wouldn't interpret Linux commands (which I need for the {something}) at all, which is not I want. Any help?

In Windows, for %c in (*.*) do {something} runs {something} once per file (ignoring directories). {something} can refer to %c for the current iteration's file name; other modifiers allow the file's path to be extracted, or the file's name without its path, the file's extension, attributes, modification date/time, size... for /d %c in (*.*) ... will process directories instead of files. In both cases *.* is equivalent to * in Unix-style systems, it matches all non-hidden files or directories, even those with no . in their name.

P.S. I know that the cmd "for" has many usages which may not be covered in one command in bash, but I just want to know the equivalent of the command mentioned above.

I'm a Linux newbie, and I only know little about bash (or any Linux shell - but I just use bash). I'm used to using for %c in (*.*) do {something} in cmd in Windows, and I really feel inconvenient without it. I tried wine cmd, but it wouldn't interpret Linux commands (which I need for the {something}) at all, which is not I want. Any help?

In Windows, for %c in (*.*) do {something} runs {something} once per file (ignoring directories). {something} can refer to %c for the current iteration's file name; other modifiers allow the file's path to be extracted, or the file's name without its path, the file's extension, attributes, modification date/time, size... for /d %c in (*.*) ... will process directories instead of files. In both cases *.* is equivalent to * in Unix-style systems, it matches all non-hidden files or directories, even those with no . in their name.

P.S. I know that the cmd "for" has many usages which may not be covered in one command in bash, but I just want to know the equivalent of the command mentioned above.

I'm a Linux newbie, and I only know little about bash (or any Linux shell - but I just use bash). I'm used to using for %c in (*.*) do {something} in cmd in Windows, and I really feel inconvenient without it. I tried wine cmd, but it wouldn't interpret Linux commands (which I need for the {something}) at all, which is not I want. Any help?

P.S. I know that the cmd "for" has many usages which may not be covered in one command in bash, but I just want to know the equivalent of the command mentioned above.

I'm a Linux newbie, and I only know little about bash (or any Linux shell - but I just use bash). I'm used to using for %c in (*.*) do {something} in cmd in Windows, and I really feel inconvenient without it. I tried wine cmd, but it wouldn't interpret Linux commands (which I need for the {something}) at all, which is not I want. Any help?

In Windows, for %c in (*.*) do {something} runs {something} once per file (ignoring directories). {something} can refer to %c for the current iteration's file name; other modifiers allow the file's path to be extracted, or the file's name without its path, the file's extension, attributes, modification date/time, size... for /d %c in (*.*) ... will process directories instead of files. In both cases *.* is equivalent to * in Unix-style systems, it matches all non-hidden files or directories, even those with no . in their name.

P.S. I know that the cmd "for" has many usages which may not be covered in one command in bash, but I just want to know the equivalent of the command mentioned above.

edited tags
Link
terdon
  • 252.3k
  • 69
  • 480
  • 718
added 2 characters in body
Source Link
Archemar
  • 32.3k
  • 18
  • 75
  • 107
Loading
Source Link
Loading