Gustin Johnson wrote:
> On 10-05-14 11:56 AM, Ralf Mardorf wrote:
> <snip>
>
>> ... wow, it works. Do you know that most information about issues
>> similar to this one don't have good explanations in the web?
>>
>>
> Actually these sorts of things *are* well documented. The beginners and
> the advanced bash guides for example.
Hi Bob :)
Bob did you check the file names for multiple space-signs?
Hi Gustin :)
A NOTE AT FIRST, I'm not speaking against Linux, I'm arguing against
your opinion. Neither Bob, nor I are idiots and Bob did use allowed
signs, perhaps he did read and understand the beginners and the advanced
bash guides.
I wasn't at LAC, but I guess they were talking about a lack of
documentation too. Your opinion seems to be an exceptional opinion.
Yes a good idea, every musician using Linux should read the advanced
bash guides, sounds close to reality for the dash issue and the file
name issue in general:
Frank Smith wrote:
> HI All
> Trying to backup my multi-track files from Ardour and I keep getting
> <F1>Name of file ect
> as invalid file name and cannot back up the whole Dir.
>
> This means I'll have missing audio when I come to replay the session.
>
> Anything I can do?
>
> Cheers
> Bob
'Are Linux users lemmings collectively jumping off of the cliff of reliable,
well-engineered commercial software?'
-- Matt Welsh
Linux is the most worse documented OS (of the OSs that have a "bigger"
user community) regarding to what users do need. A good documentation
needs a good index + enough hits by search engines. Users often, e.g.
musicians often aren't nerds who wish to learn how to use a terminal and
other stuff that is completely irrelevant for a musician and btw. I know
German musicians, able to understand English, they are intelligent, but
no computer freaks, or even tech freaks, so when a friend did read
"host: MIDI, PC1, PC2, Mac" on a switch besides the MIDI IOs of his
Clavinova and the Clavinova's MIDI didn't work with other keyboards, he
didn't think about that "Mac" might be a bad position for this switch,
he thought that his Clavinova was defect. Sounds idiotic? Dolphins could
easily jump over tuna nets instead of dying in those nets, if they would
have the same thinking, cognition as humans do have, but they are
different to us. Users need better documentation, short quick guides on
their native language. A user seldom has knowledge about the tools he is
using. A developer needs to take care about this, that's why e.g. for
electric the two contacts of a main plug are one plug instead of also
having single plugs for each contact and in the professional electronic
world it's more safe, but less, because of isolating transformers. Main
plugs designed by the penguin would tend to be two single plugs, hence
the user would be able to disconnect one plug and to kill herself/
himself. Linux developers would use those two plugs instead of one plug
too and they wouldn't use isolating transformers. I'm doing this at
home, because 'knowledge + no stress = safe', this is the situation for
Linux developers too, but not for users, they do miss knowledge and not
at work, because of the stress.
If your hobby is the computer the Linux documentation is fine. If you're
a typist you would visit a desktop and openoffice class. If you are a
musician? How many on this list do use Linux at home, but Pro Tools &
Co. at work?
Regarding to the problem of the original post, it's possible to get a
lot of links that nearly say the same about the signs that are allowed
for file names, but OTOH there's somebody having an issue seemingly
because he used the < and > signs for track names. The application
allowed him to do this and now he has got trouble. It's not only that
for Linux < and > are allowed signs for file names, but also that even
the poster child of Linux audio apps seems to fail.
Documentations say that < and > are allowed in file names. Paul Davis is
known as a gifted coder and POSIX pedant, Ardour is the poster child of
Linux audio apps, so why should a user think that < and > aren't allowed
signs while Ardour allows him to use this signs?
Regarding to the dash as first sign for file names and easy ways to use
those file names by command line, I didn't get any hit on English or
German when using google.com and google.de. Most hits didn't say
anything about the dash, but one link said that it's impossible to use
the dash as first sign.
Btw. the command rm¹ comes with a quick guide, but I didn't find any
other command's output or documentation, when just searching for issues
because of file names and making some tests. And even if documentations
about signs in file names for Linux do differ, no documentation (I got
hits by using Google) reported issues with the < and > in a file name
and just one documentation referred to the dash as first sign, by giving
no way how to solve the issue for the dash.
Cheers!
Ralf
¹
spinymouse-s...@64studio:~$ cd Desktop
spinymouse-s...@64studio:~/Desktop$ touch -n
touch: invalid option -- n
Try `touch --help' for more information.
spinymouse-s...@64studio:~/Desktop$ touch -- -n
spinymouse-s...@64studio:~/Desktop$ ls
-n
spinymouse-s...@64studio:~/Desktop$ rm -n
rm: invalid option -- n
Try `rm ./-n' to remove the file `-n'.
Try `rm --help' for more information.
spinymouse-s...@64studio:~/Desktop$ cat -n
^C
spinymouse-s...@64studio:~/Desktop$ rm -- -n
spinymouse-s...@64studio:~/Desktop$ ls
spinymouse-s...@64studio:~/Desktop$ touch --help
Usage: touch [OPTION]... FILE...
Update the access and modification times of each FILE to the current time.
A FILE argument that does not exist is created empty.
A FILE argument string of - is handled specially and causes touch to
change the times of the file associated with standard output.
Mandatory arguments to long options are mandatory for short options too.
-a change only the access time
-c, --no-create do not create any files
-d, --date=STRING parse STRING and use it instead of current time
-f (ignored)
-m change only the modification time
-r, --reference=FILE use this file's times instead of current time
-t STAMP use [[CC]YY]MMDDhhmm[.ss] instead of current time
--time=WORD change the specified time:
WORD is access, atime, or use: equivalent to -a
WORD is modify or mtime: equivalent to -m
--help display this help and exit
--version output version information and exit
Note that the -d and -t options accept different time-date formats.
Report bugs to <[email protected]>.
spinymouse-s...@64studio:~/Desktop$
_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users
