rw-r-r- 1 taylor staff 64 Feb 4 23:07 another odd name rw-r-r- 1 taylor staff 324 Feb 4 23:07 a confusing name #Neooffice ch03 page protector how to#The third example illustrates how to avoid the shell incorrectly interpreting the filename another odd name by escaping the spaces with backslashes: To remove a file named a confusing name, the first rm command in the following snippet doesn’t work, but the second does. To tell the shell not to break an argument at spaces, you can either put quotation marks around a filename that includes spaces (for example, “my file.txt”), or escape the spaces by prefacing each one with a backslash ( \).įor example, the rm program, covered later in this chapter, removes Unix files. That’s because the shell breaks commands into separate words with spaces as delimiters, just as we do in English. If you have a file with a space in its name, that space confuses the shell if you enter it as part of the filename. As an added bonus, this makes life easier for your less fortunate (Windows-using) friends when you send them files. It’s 99 percent as legible, and considerably easier to work with.įurther, in the interest of having files correctly identified in both the Finder and Unix, you’d be wise to get into the habit of using the appropriate file extensions (i.e. Though it may be tempting to include spaces in filenames as you do in the Finder, if you’re planning on doing any substantial amount of work on the Unix side, get used to using dashes or underscores in place of spaces in your filenames. (The reverse is also true: if you create a file in the Finder whose name contains a slash, it will appear as a colon in the Terminal.) If you display a file called test:me in the Finder, the name is shown as test/me instead. Also be aware that the Finder dislikes colons (which older versions of OS X used as a directory separator, just as Unix uses the forward slash). #Neooffice ch03 page protector mac#That is, rather than naming a file myFile.txt, as a Unix person would, most Mac folks would call it my file.txt. Spaces are a standard part of Macintosh file and folder names, so while I recommend using only letters, numbers, dots, and underscores in filenames, the reality is that you will probably have to work with spaces in file and directory names because Mac people are used to including them. Other characters (including spaces) are legal in a filename, but they can be hard to use because the shell gives them special meanings or otherwise forces you to constantly be changing how you work with these filenames on the command line. Filenames are usually made up of upper- and lowercase letters, numbers, dots (.), and underscores ( _). Unix filenames may contain almost any character except /, which is reserved as the separator between files and directories in a pathname. A directory is really just a special kind of file, so the rules for naming directories are the same as the rules for naming files. Line spacing and ligature changes in NeoOffice 2.2.As Chapter 3 explained, both files and directories are identified by their names.Applications and tools which support OpenDocument.Using NeoOffice with QuarkXPress and InDesign. #Neooffice ch03 page protector pdf#Using PDF to preserve exact layout, fonts and formatting.Setting the default file format for saving your work.Improving Compatibility with Microsoft Office.How to deploy NeoOffice on PPC and Intel Macs using a single image.How to get NeoOffice and QuickTime to play more media formats (starting with NeoOffice 2.2.3).How to use Eudora or Entourage with NeoOffice 2.0. #Neooffice ch03 page protector mac os x#
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |