![]() bg colour Specify the background colour to use for normal text. fg colour Specify the foreground colour to use for normal text. sl lines Specify the number of lines of scrollback to save off the top of the X( 7) for more information on the syntax of geometry ![]() geometry geometry Specify the size of the terminal, in rows and columns of text. Unless the BoldAsColour resource is set to 0 or 2. fwb font-name Specify the font to use for bold double-width characters (typicallyĬhinese, Japanese and Korean text). Japanese and Korean text) displayed in the terminal. fw font-name Specify the font to use for double-width characters (typically Chinese, Specify a bold font, pterm will overprint the normal font to make If BoldAsColour is set to 0 or 2 and you do not If theīoldAsColour resource is set to 1 (the default), bold text will beĭisplayed in different colours instead of a different font, so this option fb font-name Specify the font to use for bold text displayed in the terminal. fn font-name Specify the font to use for normal text displayed in the terminal. ThisĪllows you to set up several different sets of defaults and choose between ` -name xyz', it will look them up as xyz.Font instead. It will look them up as (for example) pterm.Font. Sorry.) -name name Specify the name under which pterm looks up X resources. This option is supplied automatically by GTK. (Note this option hasĪ double minus sign, even though none of the others do. "entries" only feels right when talking about the process of looping over them to get filenames, not for the resulting set of filenames that match some filter.Pterm -e sh -c 'mycommand < inputfile' -display display-name Specify the X display on which to open pterm. Or fn (for filename) is also a good local-use variable name. More often, you'd write a shell script using variable names like c_files=( *.c ). When dealing with hardlinks, the term "dir entry" is usefully distinct from file, moreso than "filename".īut "name" also works. reading the contents or inode metadata involves the actual file.īut just matching a glob expression against the name doesn't involve the file at all, just the filename / dir entry.ĭirectory entry is most appropriate when actually looping on a function like readdir(3), or for example "use ln to create a new directory entry referring to this file". directory entry) will probably depend on context and what you're doing. A path or pathname is something you can pass to a system call like POSIX open(2) or chdir(2) or Win32 OpenFile() But you could argue semantics that it's not "a filename". But foo/bar is the name of a file, and also a path. ![]() foo is a simple path and also a filename. dent->d_type isn't showing the type on Stack Overflow.Ī "path" like foo/bar or /a/b/foo/bar is a string that ends with a filename, but can use directories to refer to a filename that's not in the current directory. entry returned by readdir is a directory, link or file. Or to find entries that are directories themselves when recursing. It would be needlessly pedantic to bother always making the distinction between a file (inode + data) and the filename(s) / directory entries that refer to it.Īlso note that directory entries in modern filesystems often also store a "type" field so programs like find don't need to stat(2) each file to check predicates like find -type f (regular file) vs. The actual file data/inode isn't stored in the directory containing a filename for it.īut sane humans have no problem saying things like "read a file that's in some directory". Directory entries (filenames) are references to files / inodes.Ī file can have multiple names in different directories (link count > 1). (Go read them if you don't understand why those words fit, and remember that in POSIX "file" includes all types of inode (including directory), not just regular files). There are good answers that propose files and entries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |