Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.unix.programmer > #14303 > unrolled thread
| Started by | Spiros Bousbouras <spibou@gmail.com> |
|---|---|
| First post | 2023-08-13 13:55 +0000 |
| Last post | 2023-08-14 21:14 +0000 |
| Articles | 20 on this page of 151 — 33 participants |
Back to article view | Back to comp.unix.programmer
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Piping to stdin Spiros Bousbouras <spibou@gmail.com> - 2023-08-13 13:55 +0000
Re: Piping to stdin Spiros Bousbouras <spibou@gmail.com> - 2023-08-13 14:27 +0000
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 00:59 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-14 03:07 +0000
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 03:12 +0000
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-14 15:14 +0000
Re: Piping to stdin "Gary R. Schmidt" <grschmidt@acm.org> - 2023-08-15 12:50 +1000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-15 04:59 +0000
Re: Piping to stdin Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-14 23:15 -0700
Re: Piping to stdin Richard Kettlewell <invalid@invalid.invalid> - 2023-08-15 08:50 +0100
Dealing with weird filenames (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-15 08:10 +0000
Re: Piping to stdin David Brown <david.brown@hesbynett.no> - 2023-08-15 15:34 +0200
Re: Piping to stdin Richard Harnden <richard.nospam@gmail.com> - 2023-08-15 19:50 +0100
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-15 20:16 +0000
Re: Piping to stdin vallor <vallor@cultnix.org> - 2023-08-16 06:34 +0000
Re: Piping to stdin Richard Kettlewell <invalid@invalid.invalid> - 2023-08-16 17:39 +0100
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-16 17:37 +0000
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-16 17:43 +0000
Re: Piping to stdin Spiros Bousbouras <spibou@gmail.com> - 2023-08-16 19:22 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-16 20:10 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-16 20:11 +0000
Re: Piping to stdin Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-16 13:35 -0700
Re: Piping to stdin Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2023-08-17 13:34 +0100
Re: Piping to stdin Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-17 14:27 -0700
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-17 14:51 +0300
Re: Piping to stdin James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-08-16 01:37 -0400
Re: Piping to stdin David Brown <david.brown@hesbynett.no> - 2023-08-16 13:14 +0200
Re: Piping to stdin Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2023-08-15 12:08 -0600
Re: Piping to stdin Richard Harnden <richard.nospam@gmail.com> - 2023-08-16 09:32 +0100
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-16 17:27 +0300
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-15 14:30 +0000
Re: Piping to stdin Giovanni <lsodgf0@home.net.it> - 2023-08-15 17:14 +0200
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-15 15:48 +0000
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-15 16:12 +0000
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-15 16:15 +0000
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-15 16:22 +0000
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-17 10:26 +0000
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-17 14:23 +0000
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-17 15:25 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-15 17:33 +0000
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-15 23:32 +0300
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-17 10:32 +0000
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-17 14:57 +0300
Re: Piping to stdin Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2023-08-17 13:49 +0100
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-17 15:15 +0000
Wrecking a good thing? (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-17 14:09 +0000
Re: Wrecking a good thing? Phil Carmody <pc+usenet@asdf.org> - 2023-08-18 00:39 +0300
Re: Wrecking a good thing? (Was: Piping to stdin) David Brown <david.brown@hesbynett.no> - 2023-08-18 11:17 +0200
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-17 15:14 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-17 13:52 +0000
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-17 15:20 +0000
Re: Piping to stdin Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-17 13:43 -0700
Re: Piping to stdin David Brown <david.brown@hesbynett.no> - 2023-08-18 11:28 +0200
Re: Piping to stdin Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-17 21:52 +0100
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-19 13:33 +0300
Re: Piping to stdin Oğuz <oguzismailuysal@gmail.com> - 2023-08-19 16:15 +0300
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-19 14:48 +0000
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-20 17:24 +0000
Re: Piping to stdin Muttley@dastardlyhq.com - 2023-08-20 19:21 +0000
Re: Piping to stdin Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-20 21:57 +0100
What language is this? (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-20 22:33 +0000
Re: What language is this? (Was: Piping to stdin) scott@slp53.sl.home (Scott Lurndal) - 2023-08-21 01:26 +0000
Re: What language is this? (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-21 02:57 +0000
Re: What language is this? Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-21 17:16 +0100
Re: What language is this? gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-21 19:10 +0000
Re: What language is this? Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-21 20:31 +0100
Re: What language is this? gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-21 20:29 +0000
Re: What language is this? Rainer Weikusat <rweikusat@talktalk.net> - 2023-08-21 21:48 +0100
Re: What language is this? (Was: Piping to stdin) Muttley@dastardlyhq.com - 2023-08-21 06:50 +0000
Re: Piping to stdin Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-19 21:14 +0100
Re: Piping to stdin kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-20 02:02 +0000
Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2024-08-31 05:57 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Richard Kettlewell <invalid@invalid.invalid> - 2024-08-31 09:27 +0100
Re: Long filenames in DOS/Windows and Unix/Linux Muttley@dastardlyhq.com - 2024-08-31 08:39 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-31 23:34 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-01 07:03 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Nuno Silva <nunojsilva@invalid.invalid> - 2024-09-01 09:10 +0100
Re: Long filenames in DOS/Windows and Unix/Linux Helmut Waitzmann <nn.throttle@xoxy.net> - 2024-09-01 19:51 +0200
Putting arbitrary characters into the shell command line (was: Long filenames in DOS/Windows and Unix/Linux) Helmut Waitzmann <nn.throttle@xoxy.net> - 2024-09-01 21:07 +0200
Re: Long filenames in DOS/Windows and Unix/Linux Wayne <wayne@nospam.invalid> - 2024-09-03 13:56 -0400
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-03 21:54 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-08 07:24 +0200
Arbitrary characters in filenames (was: Long filenames in DOS/Windows and Unix/Linux) Helmut Waitzmann <nn.throttle@xoxy.net> - 2024-09-01 20:06 +0200
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) Muttley@dastardlyhq.com - 2024-08-31 08:37 +0000
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) John Ames <commodorejohn@gmail.com> - 2024-09-03 08:44 -0700
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) scott@slp53.sl.home (Scott Lurndal) - 2024-09-03 15:47 +0000
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2024-09-03 15:54 +0000
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) gazelle@shell.xmission.com (Kenny McCormack) - 2024-09-03 16:10 +0000
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to Muttley@dastardlyhq.com - 2024-09-04 07:27 +0000
User surveys (Was: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to) gazelle@shell.xmission.com (Kenny McCormack) - 2024-09-04 11:27 +0000
Re: User surveys (Was: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to) Muttley@dastardlyhq.com - 2024-09-04 13:12 +0000
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-03 17:37 +0000
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) John Ames <commodorejohn@gmail.com> - 2024-09-03 11:39 -0700
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-03 20:11 +0000
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) John Ames <commodorejohn@gmail.com> - 2024-09-03 13:25 -0700
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) scott@slp53.sl.home (Scott Lurndal) - 2024-09-03 20:34 +0000
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-03 21:52 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-03 15:16 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-03 22:18 +0000
Re: Long filenames in DOS/Windows and Unix/Linux scott@slp53.sl.home (Scott Lurndal) - 2024-09-03 22:59 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-03 16:10 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-03 23:54 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-03 17:27 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-04 00:44 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-03 21:36 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-04 07:05 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Ralf Fassel <ralfixx@gmx.de> - 2024-09-04 11:47 +0200
Re: Long filenames in DOS/Windows and Unix/Linux Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-04 03:44 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Nuno Silva <nunojsilva@invalid.invalid> - 2024-09-04 13:33 +0100
Always use "--" (Was: Long filenames in DOS/Windows and Unix/Linux) gazelle@shell.xmission.com (Kenny McCormack) - 2024-09-04 13:04 +0000
Re: Always use "--" (Was: Long filenames in DOS/Windows and Unix/Linux) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2024-09-04 13:17 +0000
Re: Always use "--" (Was: Long filenames in DOS/Windows and Unix/Linux) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-04 21:35 +0000
Re: Always use "--" (Was: Long filenames in DOS/Windows and Unix/Linux) Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-05 02:29 +0000
Re: Always use "--" (Was: Long filenames in DOS/Windows and Unix/Linux) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2024-09-05 14:48 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-03 17:35 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-03 23:15 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-03 16:38 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-03 23:56 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-03 17:19 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-04 00:41 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-03 21:29 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-04 06:49 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Nuno Silva <nunojsilva@invalid.invalid> - 2024-09-04 10:16 +0100
Re: Long filenames in DOS/Windows and Unix/Linux Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-04 14:30 +0000
Re: Long filenames in DOS/Windows and Unix/Linux John Ames <commodorejohn@gmail.com> - 2024-09-04 08:41 -0700
Re: Long filenames in DOS/Windows and Unix/Linux Muttley@dastardlyhq.com - 2024-09-04 15:57 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Richard Kettlewell <invalid@invalid.invalid> - 2024-09-04 18:03 +0100
Re: Long filenames in DOS/Windows and Unix/Linux Ralf Fassel <ralfixx@gmx.de> - 2024-09-05 11:29 +0200
Re: Long filenames in DOS/Windows and Unix/Linux Richard Kettlewell <invalid@invalid.invalid> - 2024-09-05 18:21 +0100
Re: Long filenames in DOS/Windows and Unix/Linux candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2024-09-07 18:20 +0000
Word splitting oddities (Was: Long filenames in DOS/Windows and Unix/Linux) gazelle@shell.xmission.com (Kenny McCormack) - 2024-09-07 21:51 +0000
Re: Long filenames in DOS/Windows and Unix/Linux Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-10 07:17 +0200
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-10 06:51 +0200
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to Muttley@dastardlyhq.com - 2024-09-04 07:31 +0000
Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) Marcel Mueller <news.5.maazl@spamgourmet.org> - 2024-09-01 11:44 +0200
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-15 23:24 +0300
Re: Piping to stdin Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-08-15 20:50 +0000
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-16 17:11 +0300
Re: Piping to stdin Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-08-16 15:25 +0000
Re: Piping to stdin Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-16 19:29 +0000
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-17 14:49 +0300
Re: Piping to stdin Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-16 03:20 +0100
Re: Piping to stdin Phil Carmody <pc+usenet@asdf.org> - 2023-08-15 18:33 +0300
Re: Piping to stdin "Nuno Silva" <nunojsilva@invalid.invalid> - 2023-08-14 09:45 +0100
Re: Piping to stdin Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2023-08-13 21:26 -0600
Re: Piping to stdin Spiros Bousbouras <spibou@gmail.com> - 2023-08-14 09:24 +0000
Re: Piping to stdin Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-14 11:29 +0100
Re: Piping to stdin gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-14 11:28 +0000
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-14 15:41 +0000
Re: Piping to stdin Richard Harnden <richard.nospam@gmail.com> - 2023-08-14 22:02 +0100
Re: Piping to stdin scott@slp53.sl.home (Scott Lurndal) - 2023-08-14 21:14 +0000
Page 5 of 8 — ← Prev page 1 2 3 4 [5] 6 7 8 Next page →
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-09-03 21:54 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux |
| Message-ID | <vb80iq$3g6hb$2@dont-email.me> |
| In reply to | #16261 |
On Tue, 3 Sep 2024 13:56:08 -0400, Wayne wrote: > On 9/1/2024 3:03 AM, Lawrence D'Oliveiro wrote: > >> Sorry, no, it looks like the “$'...'” syntax for string literals is not >> from Posix, it’s a Bash-ism. > > Actually, dollar quotes were added to POSIX as of SUS Issue 8: Glad to know. I was looking at the man page for dash(1) as my reference for a vanilla POSIX shell. <https://manpages.debian.org/1/dash.1.en.html>
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2024-09-08 07:24 +0200 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux |
| Message-ID | <vbjcdj$1qrgd$1@dont-email.me> |
| In reply to | #16248 |
On 01.09.2024 09:03, Lawrence D'Oliveiro wrote: > I wrote: > >> If you avoid newlines in filenames, Posix shells can cope with anything >> else if you set “IFS=$'\n'”. > > Sorry, no, it looks like the “$'...'” syntax for string literals is not > from Posix, it’s a Bash-ism. Note that it's not a "Bash-ism" - Bash was rarely the _inventor_ of any shell features, mostly adopted them from other shells, primarily from Kornshell (still, by far, not catching up). Kornshell documented that specific feature with its 1993 version. And we've learned from other replies that it's meanwhile - 30 years later - already in POSIX. (Good news!) Janis
[toc] | [prev] | [next] | [standalone]
| From | Helmut Waitzmann <nn.throttle@xoxy.net> |
|---|---|
| Date | 2024-09-01 20:06 +0200 |
| Subject | Arbitrary characters in filenames (was: Long filenames in DOS/Windows and Unix/Linux) |
| Message-ID | <83jzfv5jvq.fsf_-_@helmutwaitzmann.news.arcor.de> |
| In reply to | #16247 |
Lawrence D'Oliveiro <ldo@nz.invalid>:
> On Sat, 31 Aug 2024 09:27:44 +0100, Richard Kettlewell wrote:
>
>> I think the thing that makes it hard is not the spaces as such,
>> but the tooling that makes it inconvenient to handle them,
>> which primarily means Bourne shell parsing rules. The problem
>> basically ceases to exist once you’re outside the shell
>> ecosystem.
>>
>>
>> The rest of Unix has evolved substantially since the 1970s but
>> shell is still stuck in this particular trap. It’s like we’re
>> still making making arrowheads out of flint but everything else
>> from steel.
>>
>
> If you avoid newlines in filenames, Posix shells can cope with
> anything else if you set “IFS=$'\n'”.
>
>
> If you insist on wanting to accept those as well, then I don’t
> think Posix is enough, but Bash does have facilities that help
> you cope.
>
If one wants to cope with any character (including newline
characters) in the POSIX shell's command line, one could make use
of the apostroph quoting mechanism.
If one wants to process arbitrary (may be generated) lists of
filenames, one could make use of the "xargs" utility with option
"-0".
To generate those lists of filenames, there are
find ... -print0
and
printf '%s\0' ...
available.
Followup-To: comp.unix.shell
[toc] | [prev] | [next] | [standalone]
| From | Muttley@dastardlyhq.com |
|---|---|
| Date | 2024-08-31 08:37 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <vauknd$uvji$1@dont-email.me> |
| In reply to | #16242 |
On Sat, 31 Aug 2024 05:57:12 -0000 (UTC) gazelle@shell.xmission.com (Kenny McCormack) gabbled: > 2) Spaces in filenames are pretty much a necessity from the end-user No they're not. > b) The way VFAT does it (and NTFS emulates) - where, for any > file with a long name, there is an 8.3 filename (usually > with weird characters in the filename) as well, and either > filename is usable by programs. This is one place where I > think Windows really gets it right (and Unix could learn > from it). No, just no. The windows "solution" is a hideous hack only required for backwards compatability.
[toc] | [prev] | [next] | [standalone]
| From | John Ames <commodorejohn@gmail.com> |
|---|---|
| Date | 2024-09-03 08:44 -0700 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <20240903084440.0000663d@gmail.com> |
| In reply to | #16244 |
On Sat, 31 Aug 2024 08:37:01 -0000 (UTC) Muttley@dastardlyhq.com wrote: > On Sat, 31 Aug 2024 05:57:12 -0000 (UTC) > gazelle@shell.xmission.com (Kenny McCormack) gabbled: > > 2) Spaces in filenames are pretty much a necessity from the > > end-user > > No they're not. WhoNeedsSpacesWhenYouCanJustCapitalizeEveryWordAsAVisualSignifierAmIRight or-alternatively-make-liberal-use-of-dashes or_use_underscores_like_some_deranged_freak Very readable and not at *all* weird or clunky!
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2024-09-03 15:47 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <fcGBO.3783$b8hf.2671@fx41.iad> |
| In reply to | #16256 |
John Ames <commodorejohn@gmail.com> writes: >On Sat, 31 Aug 2024 08:37:01 -0000 (UTC) >Muttley@dastardlyhq.com wrote: > >> On Sat, 31 Aug 2024 05:57:12 -0000 (UTC) >> gazelle@shell.xmission.com (Kenny McCormack) gabbled: >> > 2) Spaces in filenames are pretty much a necessity from the >> > end-user >> >> No they're not. > >WhoNeedsSpacesWhenYouCanJustCapitalizeEveryWordAsAVisualSignifierAmIRight >or-alternatively-make-liberal-use-of-dashes >or_use_underscores_like_some_deranged_freak > >Very readable and not at *all* weird or clunky! > Perhaps Dennis had it right with a 14-character maximum filename :-)
[toc] | [prev] | [next] | [standalone]
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Date | 2024-09-03 15:54 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <vb7bgi$3bl1v$1@dont-email.me> |
| In reply to | #16257 |
On Tue, 03 Sep 2024 15:47:23 +0000, Scott Lurndal wrote: > John Ames <commodorejohn@gmail.com> writes: >>On Sat, 31 Aug 2024 08:37:01 -0000 (UTC) >>Muttley@dastardlyhq.com wrote: >> >>> On Sat, 31 Aug 2024 05:57:12 -0000 (UTC) >>> gazelle@shell.xmission.com (Kenny McCormack) gabbled: >>> > 2) Spaces in filenames are pretty much a necessity from the >>> > end-user >>> >>> No they're not. >> >>WhoNeedsSpacesWhenYouCanJustCapitalizeEveryWordAsAVisualSignifierAmIRight >>or-alternatively-make-liberal-use-of-dashes >>or_use_underscores_like_some_deranged_freak >> >>Very readable and not at *all* weird or clunky! >> > > Perhaps Dennis had it right with a 14-character maximum filename :-) Only because space was tight on those early disk drives, and they only allocated 16 bytes for each directory entry (2 bytes inode#, 14 bytes filename). :-) -- Lew Pitcher "In Skills We Trust"
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2024-09-03 16:10 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <vb7ccs$1hcps$1@news.xmission.com> |
| In reply to | #16256 |
In article <20240903084440.0000663d@gmail.com>, John Ames <commodorejohn@gmail.com> wrote: >On Sat, 31 Aug 2024 08:37:01 -0000 (UTC) >Muttley@dastardlyhq.com wrote: > >> On Sat, 31 Aug 2024 05:57:12 -0000 (UTC) >> gazelle@shell.xmission.com (Kenny McCormack) gabbled: >> > 2) Spaces in filenames are pretty much a necessity from the >> > end-user >> >> No they're not. > >WhoNeedsSpacesWhenYouCanJustCapitalizeEveryWordAsAVisualSignifierAmIRight >or-alternatively-make-liberal-use-of-dashes >or_use_underscores_like_some_deranged_freak > >Very readable and not at *all* weird or clunky! > I love this post. Yeah, you got it exactly. Note that users really hate underscores. They hate them as much as (or more than) we, the admins, love them. So, your comment about "deranged freak" is spot on. -- Elect a clown, expect a circus.
[toc] | [prev] | [next] | [standalone]
| From | Muttley@dastardlyhq.com |
|---|---|
| Date | 2024-09-04 07:27 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to |
| Message-ID | <vb925l$3oa4b$1@dont-email.me> |
| In reply to | #16259 |
On Tue, 3 Sep 2024 16:10:04 -0000 (UTC) gazelle@shell.xmission.com (Kenny McCormack) boringly babbled: >In article <20240903084440.0000663d@gmail.com>, >John Ames <commodorejohn@gmail.com> wrote: >>On Sat, 31 Aug 2024 08:37:01 -0000 (UTC) >>Muttley@dastardlyhq.com wrote: >> >>> On Sat, 31 Aug 2024 05:57:12 -0000 (UTC) >>> gazelle@shell.xmission.com (Kenny McCormack) gabbled: >>> > 2) Spaces in filenames are pretty much a necessity from the >>> > end-user >>> >>> No they're not. >> >>WhoNeedsSpacesWhenYouCanJustCapitalizeEveryWordAsAVisualSignifierAmIRight >>or-alternatively-make-liberal-use-of-dashes >>or_use_underscores_like_some_deranged_freak >> >>Very readable and not at *all* weird or clunky! >> > >I love this post. > >Yeah, you got it exactly. Note that users really hate underscores. They Can you link to the survey which shows this.
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2024-09-04 11:27 +0000 |
| Subject | User surveys (Was: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to) |
| Message-ID | <vb9g6i$1if17$1@news.xmission.com> |
| In reply to | #16286 |
In article <vb925l$3oa4b$1@dont-email.me>, <Muttley@dastardlyhq.com> wrote: ... >>Yeah, you got it exactly. Note that users really hate underscores. They > >Can you link to the survey which shows this. I'm not aware of any such surveys. Are you? -- Never, ever, ever forget that "Both sides do it" is strictly a Republican meme. It is always the side that sucks that insists on saying "Well, you suck, too".
[toc] | [prev] | [next] | [standalone]
| From | Muttley@dastardlyhq.com |
|---|---|
| Date | 2024-09-04 13:12 +0000 |
| Subject | Re: User surveys (Was: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to) |
| Message-ID | <vb9mbr$3rlq6$1@dont-email.me> |
| In reply to | #16292 |
On Wed, 4 Sep 2024 11:27:14 -0000 (UTC) gazelle@shell.xmission.com (Kenny McCormack) boringly babbled: >In article <vb925l$3oa4b$1@dont-email.me>, <Muttley@dastardlyhq.com> wrote: >.... >>>Yeah, you got it exactly. Note that users really hate underscores. They >> >>Can you link to the survey which shows this. > >I'm not aware of any such surveys. Are you? Which was my point so you have no way of knowing what users like or don't like wtf to filenames other than whatever small group you've gone around and actually asked.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2024-09-03 17:37 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <20240903103327.395@kylheku.com> |
| In reply to | #16256 |
On 2024-09-03, John Ames <commodorejohn@gmail.com> wrote: > On Sat, 31 Aug 2024 08:37:01 -0000 (UTC) > Muttley@dastardlyhq.com wrote: > >> On Sat, 31 Aug 2024 05:57:12 -0000 (UTC) >> gazelle@shell.xmission.com (Kenny McCormack) gabbled: >> > 2) Spaces in filenames are pretty much a necessity from the >> > end-user >> >> No they're not. > > WhoNeedsSpacesWhenYouCanJustCapitalizeEveryWordAsAVisualSignifierAmIRight > or-alternatively-make-liberal-use-of-dashes > or_use_underscores_like_some_deranged_freak This is a strawman argument; filenamews should not only not have spaces, but should be reasonably short. (No, not 8.3 short; that's not "reasonably" and therefore another strawman.) If we use spaces in your examples, the readability improves, but if you have a directory of just half a dozen such names, you've got a paragraph to read. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | John Ames <commodorejohn@gmail.com> |
|---|---|
| Date | 2024-09-03 11:39 -0700 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <20240903113937.000008a3@gmail.com> |
| In reply to | #16260 |
On Tue, 3 Sep 2024 17:37:21 -0000 (UTC) Kaz Kylheku <643-408-1753@kylheku.com> wrote: > On 2024-09-03, John Ames <commodorejohn@gmail.com> wrote: > > On Sat, 31 Aug 2024 08:37:01 -0000 (UTC) > > Muttley@dastardlyhq.com wrote: > > > >> On Sat, 31 Aug 2024 05:57:12 -0000 (UTC) > >> gazelle@shell.xmission.com (Kenny McCormack) gabbled: > >> > 2) Spaces in filenames are pretty much a necessity from the > >> > end-user > >> > >> No they're not. > > > > WhoNeedsSpacesWhenYouCanJustCapitalizeEveryWordAsAVisualSignifierAmIRight > > or-alternatively-make-liberal-use-of-dashes > > or_use_underscores_like_some_deranged_freak > > This is a strawman argument; filenamews should not only not have > spaces, but should be reasonably short. (No, not 8.3 short; that's not > "reasonably" and therefore another strawman.) > > If we use spaces in your examples, the readability improves, but if > you have a directory of just half a dozen such names, you've got a > paragraph to read. I'm unclear on how that qualifies as a straw-man argument...? Also, who says that filenames should not, as a rule, contain spaces?
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2024-09-03 20:11 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <20240903130000.933@kylheku.com> |
| In reply to | #16262 |
On 2024-09-03, John Ames <commodorejohn@gmail.com> wrote: > On Tue, 3 Sep 2024 17:37:21 -0000 (UTC) > Kaz Kylheku <643-408-1753@kylheku.com> wrote: > >> On 2024-09-03, John Ames <commodorejohn@gmail.com> wrote: >> > On Sat, 31 Aug 2024 08:37:01 -0000 (UTC) >> > Muttley@dastardlyhq.com wrote: >> > >> >> On Sat, 31 Aug 2024 05:57:12 -0000 (UTC) >> >> gazelle@shell.xmission.com (Kenny McCormack) gabbled: >> >> > 2) Spaces in filenames are pretty much a necessity from the >> >> > end-user >> >> >> >> No they're not. >> > >> > WhoNeedsSpacesWhenYouCanJustCapitalizeEveryWordAsAVisualSignifierAmIRight >> > or-alternatively-make-liberal-use-of-dashes >> > or_use_underscores_like_some_deranged_freak >> >> This is a strawman argument; filenamews should not only not have >> spaces, but should be reasonably short. (No, not 8.3 short; that's not >> "reasonably" and therefore another strawman.) >> >> If we use spaces in your examples, the readability improves, but if >> you have a directory of just half a dozen such names, you've got a >> paragraph to read. > > I'm unclear on how that qualifies as a straw-man argument...? Because it is based on a strawman interpretation of the "no spaces" rule. That strawman interpretation is that there are no other rules used in combination with the "no spaces" rule, and thus that any ridiculous name is fine, just as long as it doesn't contain spaces. And so, look how unreadable is this 100 character name in CamelCase! Q.E.D. no spaces is a bad recommendation! -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | John Ames <commodorejohn@gmail.com> |
|---|---|
| Date | 2024-09-03 13:25 -0700 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <20240903132547.00000656@gmail.com> |
| In reply to | #16263 |
On Tue, 3 Sep 2024 20:11:28 -0000 (UTC) Kaz Kylheku <643-408-1753@kylheku.com> wrote: > Because it is based on a strawman interpretation of the "no spaces" > rule. That strawman interpretation is that there are no other rules > used in combination with the "no spaces" rule, and thus that any > ridiculous name is fine, just as long as it doesn't contain spaces. > > And so, look how unreadable is this 100 character name in CamelCase! > Q.E.D. no spaces is a bad recommendation! Well, there were no other factors *presented* alongside the blanket statement that spaces in filenames are unnecessary, so it would appear on the face of it to be an accurate assessment of the claim being made, which wasn't in a post of yours to begin with. And I'd still like to know who died and made whom king where filenames and spaces therein are concrned.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2024-09-03 20:34 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <xpKBO.50308$Hld5.16972@fx15.iad> |
| In reply to | #16264 |
John Ames <commodorejohn@gmail.com> writes: >On Tue, 3 Sep 2024 20:11:28 -0000 (UTC) >Kaz Kylheku <643-408-1753@kylheku.com> wrote: > >> Because it is based on a strawman interpretation of the "no spaces" >> rule. That strawman interpretation is that there are no other rules >> used in combination with the "no spaces" rule, and thus that any >> ridiculous name is fine, just as long as it doesn't contain spaces. >> >> And so, look how unreadable is this 100 character name in CamelCase! >> Q.E.D. no spaces is a bad recommendation! > >Well, there were no other factors *presented* alongside the blanket >statement that spaces in filenames are unnecessary, so it would appear >on the face of it to be an accurate assessment of the claim being made, >which wasn't in a post of yours to begin with. > >And I'd still like to know who died and made whom king where filenames >and spaces therein are concrned. > For people who exclusively use GUIs, spaces in a field are not a problem. For people who work from the command line, spaces suck and are completely unnecessary and even a PITA and moreover, a potential security issue. I've not found a need for whitespace in a filesystem over the last 45 years of interactive computer usage. YMMV.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-09-03 21:52 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux (Was: Piping to stdin) |
| Message-ID | <vb80ek$3g6hb$1@dont-email.me> |
| In reply to | #16265 |
On Tue, 03 Sep 2024 20:34:37 GMT, Scott Lurndal wrote: > For people who work from the command line, spaces suck and are > completely unnecessary and even a PITA and moreover, a potential > security issue. I work heavily from the command line. I like having spaces in file/ directory names, and I regularly use them.
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2024-09-03 15:16 -0700 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux |
| Message-ID | <87seug1iyj.fsf@nosuchdomain.example.com> |
| In reply to | #16264 |
John Ames <commodorejohn@gmail.com> writes:
> On Tue, 3 Sep 2024 20:11:28 -0000 (UTC)
> Kaz Kylheku <643-408-1753@kylheku.com> wrote:
>
>> Because it is based on a strawman interpretation of the "no spaces"
>> rule. That strawman interpretation is that there are no other rules
>> used in combination with the "no spaces" rule, and thus that any
>> ridiculous name is fine, just as long as it doesn't contain spaces.
>>
>> And so, look how unreadable is this 100 character name in CamelCase!
>> Q.E.D. no spaces is a bad recommendation!
>
> Well, there were no other factors *presented* alongside the blanket
> statement that spaces in filenames are unnecessary, so it would appear
> on the face of it to be an accurate assessment of the claim being made,
> which wasn't in a post of yours to begin with.
>
> And I'd still like to know who died and made whom king where filenames
> and spaces therein are concrned.
There is no official "rule" about spaces in filenames, though I can
imagine easily imagine that some organizations and projects have
rules forbidding them. A couple of data points: The gcc git repo
contains 137394 files and none of them have spaces in their names.
The Linux kernel git repo contains 85803 files, and exactly one has
spaces in its name. In either cases, I don't know whether this is
due to some hard rule.
Spaces in file names are likely not to be an issue if you interact
with the filesystem via a GUI like Windows Explorer *or* if you use
a scripting language like Perl or Python that requires strings used
as filenames to be enclosed in quotation marks. In those contexts,
space is just another character.
It can be a real issue if you're interacting via shell commands.
If I happen to know that none of the files I'm working with have
spaces (or other problematic characters) in their names, a lot of
things become easier -- but risky if there's a funny character I'm
not aware of. For example, I might type something like:
for file in * ; do cp -p $file $file.bak ; done
(Yes, this skips files whose names start with '.'; I usually don't
need to worry about that) I never (well, hardly ever) create files
with spaces in their names. I typically use '-' rather than '
' to delimit words in file names. When I have to work with such
files, I can do it, but it requires a bit of extra effort.
And if, for example, I'm writing a shell script that needs to be
generally useful, I'll spend the extra effort to make sure it works
with arbitrary file names (or I'll write it in a scripting language
where it's not an issue). But I don't typically bother if I know
I'm working with files that I created.
It would be ideal, I suppose, if interactive shells dealt better with
spaces in file names, but I'm not sure how that could be achieved.
In current shells, removing two files named "foo" and "bar" is easy, and
removing a single file named "foo bar" requires some extra effort. I
find that to be a good tradeoff.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-09-03 22:18 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux |
| Message-ID | <vb81vo$3g6hb$6@dont-email.me> |
| In reply to | #16269 |
On Tue, 03 Sep 2024 15:16:36 -0700, Keith Thompson wrote: > For example, I might type something like: > > for file in * ; do cp -p $file $file.bak ; done It’s quite easy to fix that to work with spaces in file names. How long have you been working with *nix shells?
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2024-09-03 22:59 +0000 |
| Subject | Re: Long filenames in DOS/Windows and Unix/Linux |
| Message-ID | <yxMBO.22279$5%Yf.10118@fx39.iad> |
| In reply to | #16270 |
Lawrence D'Oliveiro <ldo@nz.invalid> writes: >On Tue, 03 Sep 2024 15:16:36 -0700, Keith Thompson wrote: > >> For example, I might type something like: >> >> for file in * ; do cp -p $file $file.bak ; done > >It’s quite easy to fix that to work with spaces in file names. How long >have you been working with *nix shells? Longer than you.
[toc] | [prev] | [next] | [standalone]
Page 5 of 8 — ← Prev page 1 2 3 4 [5] 6 7 8 Next page →
Back to top | Article view | comp.unix.programmer
csiph-web