Simon said on Thu, 13 Jan 2022 18:38:56 +
>Steve Litt wrote:
>
>> This is one reason why, in shellscripts, you
>> need to quote almost all variables: So they act correctly with the
>> space laden filenames that windows dwoobydogs just love to create.
>
>Not just Windows users. I regularly u
Olaf Meeuwissen said on Fri, 14 Jan 2022 18:40:40 +0900
>Hi,
>
>Steve Litt writes:
>
>> [...] Here at Troubleshooters.Com, spaces and all punctuation except
>> underscore and hyphen are forbidden, but files coming in from the
>> outside have horrible filenames.
>
>Pretty sure you allow periods
Benjamin Riefenstahl said on Fri, 14 Jan 2022 10:33:29 +0100
>Hi Steve,
>
>> Benjamin Riefenstahl said on Thu, 13 Jan 2022 18:19:23 +0100
>>>Different code paths within Bash. [...]
>
>Steve Litt writes:
>> This is true, but not the explanation for this particular behavior,
>> as follows:
>>
>
Hendrik Boom wrote:
>> I recall a lot of resistance when Apple brought out the Mac and suddenly
>> programmers had to learn how to write programs that did what the user wanted
>> - when the user wanted.
>
> Sounds good. But for the first two years the Mac was out, programmers
> couldn't use
Greetings
When I put this system together ( a LONG time ago) nvidia was not
quite the pariah it has become in the open source community. So I'm
stuck with nouveau for drivers (its a long explanation but trust me
I'm STUCK there!).
Nouveau is really not as wonderful as it purports to be and I woul
Hi,
Steve Litt writes:
> [...] Here at Troubleshooters.Com, spaces and all punctuation except
> underscore and hyphen are forbidden, but files coming in from the
> outside have horrible filenames.
Pretty sure you allow periods too ;-P
--
Olaf MeeuwissenFSF Associate Member s
Hi,
Steve Litt writes:
> Benjamin Riefenstahl said on Thu, 13 Jan 2022 18:19:23 +0100
>
>>Hi Steve,
>>
>>Steve Litt writes:
>>> [slitt@mydesk ~]$ "cat -n" /etc/fstab | cut -b 1-20 | head -n5
>>> bash: cat -n: command not found
>>> [slitt@mydesk ~]$ "cat -n /etc/fstab" | cut -b 1-20 | head -n5
Hi Steve,
> Benjamin Riefenstahl said on Thu, 13 Jan 2022 18:19:23 +0100
>>Different code paths within Bash. [...]
Steve Litt writes:
> This is true, but not the explanation for this particular behavior, as
> follows:
>
> [slitt@mydesk ~]$ /usr/bin/cat -n /etc/fstab | cut -b 1-20 | head -n5
>
On Thu 13/Jan/2022 19:38:56 +0100 Simon wrote:
Similarly with file names. Once upon a time the human had to adapt to what the
computer supported - such as fitting your entire file name into 8 characters.
Now the computer (mostly) supports what is natural for a human - and that
includes using
