2015-05-16 15:10:58 +00:00
|
|
|
|
//! Files, and methods and fields to access their metadata.
|
|
|
|
|
|
2018-12-17 04:48:49 +00:00
|
|
|
|
use std::fs::{self, metadata};
|
2016-10-29 19:27:23 +00:00
|
|
|
|
use std::io::Error as IOError;
|
2015-12-15 21:47:37 +00:00
|
|
|
|
use std::io::Result as IOResult;
|
2017-05-03 16:51:17 +00:00
|
|
|
|
use std::os::unix::fs::{MetadataExt, PermissionsExt, FileTypeExt};
|
Print the parent path for passed-in files
This commit changes all the views to accommodate printing each path's prefix, if it has one.
Previously, each file was stripped of its ancestry, leaving only its file name to be displayed. So running "exa /usr/bin/*" would display only filenames, while running "ls /usr/bin/*" would display each file prefixed with "/usr/bin/". But running "ls /usr/bin/" -- without the glob -- would run ls on just the directory, printing out the file names with no prefix or anything.
This functionality turned out to be useful in quite a few situations: firstly, if the user passes in files from different directories, it would be hard to tell where they came from (especially if they have the same name, such as find | xargs). Secondly, this also applied when following symlinks, making it unclear exactly which file a symlink would be pointing to.
The reason that it did it this way beforehand was that I didn't think of these use-cases, rather than for any technical reason; this new method should not have any drawbacks save making the output slightly wider in a few cases. Compatibility with ls is also a big plus.
Fixes #104, and relates to #88 and #92.
2016-04-11 18:10:55 +00:00
|
|
|
|
use std::path::{Path, PathBuf};
|
2019-07-31 22:43:31 +00:00
|
|
|
|
use std::time::{SystemTime, UNIX_EPOCH, Duration};
|
2014-05-04 20:33:14 +00:00
|
|
|
|
|
2018-12-07 23:43:31 +00:00
|
|
|
|
use log::{debug, error};
|
|
|
|
|
|
|
|
|
|
use crate::fs::dir::Dir;
|
|
|
|
|
use crate::fs::fields as f;
|
|
|
|
|
use crate::options::Misfire;
|
2014-06-16 23:27:05 +00:00
|
|
|
|
|
2017-05-01 21:43:28 +00:00
|
|
|
|
|
2015-01-24 12:38:05 +00:00
|
|
|
|
/// A **File** is a wrapper around one of Rust's Path objects, along with
|
|
|
|
|
/// associated data about the file.
|
|
|
|
|
///
|
|
|
|
|
/// Each file is definitely going to have its filename displayed at least
|
2015-05-16 17:16:35 +00:00
|
|
|
|
/// once, have its file extension extracted at least once, and have its metadata
|
2015-01-24 12:38:05 +00:00
|
|
|
|
/// information queried at least once, so it makes sense to do all this at the
|
|
|
|
|
/// start and hold on to all the information.
|
2015-05-12 14:38:12 +00:00
|
|
|
|
pub struct File<'dir> {
|
2015-05-16 15:10:58 +00:00
|
|
|
|
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// The filename portion of this file’s path, including the extension.
|
Print the parent path for passed-in files
This commit changes all the views to accommodate printing each path's prefix, if it has one.
Previously, each file was stripped of its ancestry, leaving only its file name to be displayed. So running "exa /usr/bin/*" would display only filenames, while running "ls /usr/bin/*" would display each file prefixed with "/usr/bin/". But running "ls /usr/bin/" -- without the glob -- would run ls on just the directory, printing out the file names with no prefix or anything.
This functionality turned out to be useful in quite a few situations: firstly, if the user passes in files from different directories, it would be hard to tell where they came from (especially if they have the same name, such as find | xargs). Secondly, this also applied when following symlinks, making it unclear exactly which file a symlink would be pointing to.
The reason that it did it this way beforehand was that I didn't think of these use-cases, rather than for any technical reason; this new method should not have any drawbacks save making the output slightly wider in a few cases. Compatibility with ls is also a big plus.
Fixes #104, and relates to #88 and #92.
2016-04-11 18:10:55 +00:00
|
|
|
|
///
|
|
|
|
|
/// This is used to compare against certain filenames (such as checking if
|
|
|
|
|
/// it’s “Makefile” or something) and to highlight only the filename in
|
|
|
|
|
/// colour when displaying the path.
|
2015-08-25 14:04:15 +00:00
|
|
|
|
pub name: String,
|
2015-05-16 15:10:58 +00:00
|
|
|
|
|
Print the parent path for passed-in files
This commit changes all the views to accommodate printing each path's prefix, if it has one.
Previously, each file was stripped of its ancestry, leaving only its file name to be displayed. So running "exa /usr/bin/*" would display only filenames, while running "ls /usr/bin/*" would display each file prefixed with "/usr/bin/". But running "ls /usr/bin/" -- without the glob -- would run ls on just the directory, printing out the file names with no prefix or anything.
This functionality turned out to be useful in quite a few situations: firstly, if the user passes in files from different directories, it would be hard to tell where they came from (especially if they have the same name, such as find | xargs). Secondly, this also applied when following symlinks, making it unclear exactly which file a symlink would be pointing to.
The reason that it did it this way beforehand was that I didn't think of these use-cases, rather than for any technical reason; this new method should not have any drawbacks save making the output slightly wider in a few cases. Compatibility with ls is also a big plus.
Fixes #104, and relates to #88 and #92.
2016-04-11 18:10:55 +00:00
|
|
|
|
/// The file’s name’s extension, if present, extracted from the name.
|
|
|
|
|
///
|
|
|
|
|
/// This is queried many times over, so it’s worth caching it.
|
2015-08-25 14:04:15 +00:00
|
|
|
|
pub ext: Option<String>,
|
2015-05-16 15:10:58 +00:00
|
|
|
|
|
Print the parent path for passed-in files
This commit changes all the views to accommodate printing each path's prefix, if it has one.
Previously, each file was stripped of its ancestry, leaving only its file name to be displayed. So running "exa /usr/bin/*" would display only filenames, while running "ls /usr/bin/*" would display each file prefixed with "/usr/bin/". But running "ls /usr/bin/" -- without the glob -- would run ls on just the directory, printing out the file names with no prefix or anything.
This functionality turned out to be useful in quite a few situations: firstly, if the user passes in files from different directories, it would be hard to tell where they came from (especially if they have the same name, such as find | xargs). Secondly, this also applied when following symlinks, making it unclear exactly which file a symlink would be pointing to.
The reason that it did it this way beforehand was that I didn't think of these use-cases, rather than for any technical reason; this new method should not have any drawbacks save making the output slightly wider in a few cases. Compatibility with ls is also a big plus.
Fixes #104, and relates to #88 and #92.
2016-04-11 18:10:55 +00:00
|
|
|
|
/// The path that begat this file.
|
|
|
|
|
///
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// Even though the file’s name is extracted, the path needs to be kept
|
|
|
|
|
/// around, as certain operations involve looking up the file’s absolute
|
|
|
|
|
/// location (such as searching for compiled files) or using its original
|
|
|
|
|
/// path (following a symlink).
|
2015-08-25 14:04:15 +00:00
|
|
|
|
pub path: PathBuf,
|
2015-05-16 15:10:58 +00:00
|
|
|
|
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// A cached `metadata` (`stat`) call for this file.
|
Print the parent path for passed-in files
This commit changes all the views to accommodate printing each path's prefix, if it has one.
Previously, each file was stripped of its ancestry, leaving only its file name to be displayed. So running "exa /usr/bin/*" would display only filenames, while running "ls /usr/bin/*" would display each file prefixed with "/usr/bin/". But running "ls /usr/bin/" -- without the glob -- would run ls on just the directory, printing out the file names with no prefix or anything.
This functionality turned out to be useful in quite a few situations: firstly, if the user passes in files from different directories, it would be hard to tell where they came from (especially if they have the same name, such as find | xargs). Secondly, this also applied when following symlinks, making it unclear exactly which file a symlink would be pointing to.
The reason that it did it this way beforehand was that I didn't think of these use-cases, rather than for any technical reason; this new method should not have any drawbacks save making the output slightly wider in a few cases. Compatibility with ls is also a big plus.
Fixes #104, and relates to #88 and #92.
2016-04-11 18:10:55 +00:00
|
|
|
|
///
|
|
|
|
|
/// This too is queried multiple times, and is *not* cached by the OS, as
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// it could easily change between invocations — but exa is so short-lived
|
Print the parent path for passed-in files
This commit changes all the views to accommodate printing each path's prefix, if it has one.
Previously, each file was stripped of its ancestry, leaving only its file name to be displayed. So running "exa /usr/bin/*" would display only filenames, while running "ls /usr/bin/*" would display each file prefixed with "/usr/bin/". But running "ls /usr/bin/" -- without the glob -- would run ls on just the directory, printing out the file names with no prefix or anything.
This functionality turned out to be useful in quite a few situations: firstly, if the user passes in files from different directories, it would be hard to tell where they came from (especially if they have the same name, such as find | xargs). Secondly, this also applied when following symlinks, making it unclear exactly which file a symlink would be pointing to.
The reason that it did it this way beforehand was that I didn't think of these use-cases, rather than for any technical reason; this new method should not have any drawbacks save making the output slightly wider in a few cases. Compatibility with ls is also a big plus.
Fixes #104, and relates to #88 and #92.
2016-04-11 18:10:55 +00:00
|
|
|
|
/// it's better to just cache it.
|
2015-08-25 14:04:15 +00:00
|
|
|
|
pub metadata: fs::Metadata,
|
2015-05-16 15:10:58 +00:00
|
|
|
|
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// A reference to the directory that contains this file, if any.
|
2015-05-16 15:10:58 +00:00
|
|
|
|
///
|
|
|
|
|
/// Filenames that get passed in on the command-line directly will have no
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// parent directory reference — although they technically have one on the
|
|
|
|
|
/// filesystem, we’ll never need to look at it, so it’ll be `None`.
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// However, *directories* that get passed in will produce files that
|
|
|
|
|
/// contain a reference to it, which is used in certain operations (such
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// as looking up compiled files).
|
2017-06-29 12:07:45 +00:00
|
|
|
|
pub parent_dir: Option<&'dir Dir>,
|
2019-07-13 20:14:42 +00:00
|
|
|
|
|
|
|
|
|
/// Whether this is one of the two `--all all` directories, `.` and `..`.
|
|
|
|
|
///
|
|
|
|
|
/// Unlike all other entries, these are not returned as part of the
|
|
|
|
|
/// directory's children, and are in fact added specifically by exa; this
|
|
|
|
|
/// means that they should be skipped when recursing.
|
|
|
|
|
pub is_all_all: bool,
|
Override the names of . and ..
There was a problem when displaying . and .. in directory listings: their names would normalise to actual names! So instead of literally seeing `.`, you’d see the current directory’s name, inserted in sort order into the list of results. Obviously this is not what we want.
In unrelated news, putting `.` and `..` into the list of paths read from a directory just takes up more heap space for something that’s basically constant.
We can solve both these problems at once by moving the DotFilter to the files iterator in Dir, rather than at the Dir’s creation. Having the iterator know whether it should display `.` and `..` means it can emit those files first, and because it knows what those files really represent, it can override their file names to actually be those sequences of dots.
This is not a perfect solution: the main casualty is that a File can now be constructed with a name, some metadata, both, or neither. This is currently handled with a bunch of Options, and returns IOResult even without doing any IO operations.
But at least all the tests pass!
2017-06-28 17:41:31 +00:00
|
|
|
|
}
|
2014-11-25 20:50:23 +00:00
|
|
|
|
|
Override the names of . and ..
There was a problem when displaying . and .. in directory listings: their names would normalise to actual names! So instead of literally seeing `.`, you’d see the current directory’s name, inserted in sort order into the list of results. Obviously this is not what we want.
In unrelated news, putting `.` and `..` into the list of paths read from a directory just takes up more heap space for something that’s basically constant.
We can solve both these problems at once by moving the DotFilter to the files iterator in Dir, rather than at the Dir’s creation. Having the iterator know whether it should display `.` and `..` means it can emit those files first, and because it knows what those files really represent, it can override their file names to actually be those sequences of dots.
This is not a perfect solution: the main casualty is that a File can now be constructed with a name, some metadata, both, or neither. This is currently handled with a bunch of Options, and returns IOResult even without doing any IO operations.
But at least all the tests pass!
2017-06-28 17:41:31 +00:00
|
|
|
|
impl<'dir> File<'dir> {
|
2018-12-16 07:18:43 +00:00
|
|
|
|
pub fn from_args<PD, FN>(path: PathBuf, parent_dir: PD, filename: FN) -> IOResult<File<'dir>>
|
2017-06-29 12:17:26 +00:00
|
|
|
|
where PD: Into<Option<&'dir Dir>>,
|
|
|
|
|
FN: Into<Option<String>>
|
|
|
|
|
{
|
|
|
|
|
let parent_dir = parent_dir.into();
|
|
|
|
|
let name = filename.into().unwrap_or_else(|| File::filename(&path));
|
|
|
|
|
let ext = File::ext(&path);
|
2017-08-26 22:53:47 +00:00
|
|
|
|
|
2017-08-19 12:53:33 +00:00
|
|
|
|
debug!("Statting file {:?}", &path);
|
|
|
|
|
let metadata = fs::symlink_metadata(&path)?;
|
2019-07-13 20:14:42 +00:00
|
|
|
|
let is_all_all = false;
|
|
|
|
|
|
|
|
|
|
Ok(File { path, parent_dir, metadata, ext, name, is_all_all })
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
pub fn new_aa_current(parent_dir: &'dir Dir) -> IOResult<File<'dir>> {
|
|
|
|
|
let path = parent_dir.path.to_path_buf();
|
|
|
|
|
let ext = File::ext(&path);
|
|
|
|
|
|
|
|
|
|
debug!("Statting file {:?}", &path);
|
|
|
|
|
let metadata = fs::symlink_metadata(&path)?;
|
|
|
|
|
let is_all_all = true;
|
|
|
|
|
|
|
|
|
|
Ok(File { path, parent_dir: Some(parent_dir), metadata, ext, name: ".".to_string(), is_all_all })
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
pub fn new_aa_parent(path: PathBuf, parent_dir: &'dir Dir) -> IOResult<File<'dir>> {
|
|
|
|
|
let ext = File::ext(&path);
|
|
|
|
|
|
|
|
|
|
debug!("Statting file {:?}", &path);
|
|
|
|
|
let metadata = fs::symlink_metadata(&path)?;
|
|
|
|
|
let is_all_all = true;
|
Override the names of . and ..
There was a problem when displaying . and .. in directory listings: their names would normalise to actual names! So instead of literally seeing `.`, you’d see the current directory’s name, inserted in sort order into the list of results. Obviously this is not what we want.
In unrelated news, putting `.` and `..` into the list of paths read from a directory just takes up more heap space for something that’s basically constant.
We can solve both these problems at once by moving the DotFilter to the files iterator in Dir, rather than at the Dir’s creation. Having the iterator know whether it should display `.` and `..` means it can emit those files first, and because it knows what those files really represent, it can override their file names to actually be those sequences of dots.
This is not a perfect solution: the main casualty is that a File can now be constructed with a name, some metadata, both, or neither. This is currently handled with a bunch of Options, and returns IOResult even without doing any IO operations.
But at least all the tests pass!
2017-06-28 17:41:31 +00:00
|
|
|
|
|
2019-07-13 20:14:42 +00:00
|
|
|
|
Ok(File { path, parent_dir: Some(parent_dir), metadata, ext, name: "..".to_string(), is_all_all })
|
2017-06-29 12:07:45 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/// A file’s name is derived from its string. This needs to handle directories
|
|
|
|
|
/// such as `/` or `..`, which have no `file_name` component. So instead, just
|
|
|
|
|
/// use the last component as the name.
|
|
|
|
|
pub fn filename(path: &Path) -> String {
|
2017-08-19 10:15:17 +00:00
|
|
|
|
if let Some(back) = path.components().next_back() {
|
|
|
|
|
back.as_os_str().to_string_lossy().to_string()
|
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
// use the path as fallback
|
|
|
|
|
error!("Path {:?} has no last component", path);
|
|
|
|
|
path.display().to_string()
|
2017-06-29 12:07:45 +00:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/// Extract an extension from a file path, if one is present, in lowercase.
|
|
|
|
|
///
|
|
|
|
|
/// The extension is the series of characters after the last dot. This
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// deliberately counts dotfiles, so the “.git” folder has the extension “git”.
|
2017-06-29 12:07:45 +00:00
|
|
|
|
///
|
|
|
|
|
/// ASCII lowercasing is used because these extensions are only compared
|
|
|
|
|
/// against a pre-compiled list of extensions which are known to only exist
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// within ASCII, so it’s alright.
|
2017-06-29 12:07:45 +00:00
|
|
|
|
fn ext(path: &Path) -> Option<String> {
|
2018-06-19 12:58:03 +00:00
|
|
|
|
let name = path.file_name().map(|f| f.to_string_lossy().to_string())?;
|
2017-06-29 12:07:45 +00:00
|
|
|
|
|
|
|
|
|
name.rfind('.').map(|p| name[p+1..].to_ascii_lowercase())
|
2014-05-04 20:33:14 +00:00
|
|
|
|
}
|
|
|
|
|
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// Whether this file is a directory on the filesystem.
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
pub fn is_directory(&self) -> bool {
|
2015-05-16 17:16:35 +00:00
|
|
|
|
self.metadata.is_dir()
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
}
|
|
|
|
|
|
2018-03-31 08:54:14 +00:00
|
|
|
|
/// Whether this file is a directory, or a symlink pointing to a directory.
|
|
|
|
|
pub fn points_to_directory(&self) -> bool {
|
|
|
|
|
if self.is_directory() {
|
|
|
|
|
return true;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if self.is_link() {
|
|
|
|
|
let target = self.link_target();
|
|
|
|
|
if let FileTarget::Ok(target) = target {
|
|
|
|
|
return target.points_to_directory();
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2018-12-16 07:18:43 +00:00
|
|
|
|
false
|
2018-03-31 08:54:14 +00:00
|
|
|
|
}
|
|
|
|
|
|
2015-09-03 17:48:53 +00:00
|
|
|
|
/// If this file is a directory on the filesystem, then clone its
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// `PathBuf` for use in one of our own `Dir` values, and read a list of
|
2015-09-03 17:48:53 +00:00
|
|
|
|
/// its contents.
|
|
|
|
|
///
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// Returns an IO error upon failure, but this shouldn’t be used to check
|
2015-09-03 17:48:53 +00:00
|
|
|
|
/// if a `File` is a directory or not! For that, just use `is_directory()`.
|
2017-09-01 18:13:47 +00:00
|
|
|
|
pub fn to_dir(&self) -> IOResult<Dir> {
|
|
|
|
|
Dir::read_dir(self.path.clone())
|
2015-08-26 08:35:11 +00:00
|
|
|
|
}
|
|
|
|
|
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// Whether this file is a regular file on the filesystem — that is, not a
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// directory, a link, or anything else treated specially.
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
pub fn is_file(&self) -> bool {
|
2015-05-16 17:16:35 +00:00
|
|
|
|
self.metadata.is_file()
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
}
|
|
|
|
|
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// Whether this file is both a regular file *and* executable for the
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// current user. An executable file has a different purpose from an
|
|
|
|
|
/// executable directory, so they should be highlighted differently.
|
2015-05-07 21:27:33 +00:00
|
|
|
|
pub fn is_executable_file(&self) -> bool {
|
2015-11-04 14:56:37 +00:00
|
|
|
|
let bit = modes::USER_EXECUTE;
|
2015-05-16 17:16:35 +00:00
|
|
|
|
self.is_file() && (self.metadata.permissions().mode() & bit) == bit
|
2015-05-07 21:27:33 +00:00
|
|
|
|
}
|
|
|
|
|
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// Whether this file is a symlink on the filesystem.
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
pub fn is_link(&self) -> bool {
|
2015-05-16 17:16:35 +00:00
|
|
|
|
self.metadata.file_type().is_symlink()
|
2016-10-29 19:27:23 +00:00
|
|
|
|
}
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
|
2017-05-03 16:51:17 +00:00
|
|
|
|
/// Whether this file is a named pipe on the filesystem.
|
|
|
|
|
pub fn is_pipe(&self) -> bool {
|
2017-06-27 00:13:50 +00:00
|
|
|
|
self.metadata.file_type().is_fifo()
|
2014-05-05 09:51:24 +00:00
|
|
|
|
}
|
|
|
|
|
|
2017-06-27 00:13:50 +00:00
|
|
|
|
/// Whether this file is a char device on the filesystem.
|
|
|
|
|
pub fn is_char_device(&self) -> bool {
|
|
|
|
|
self.metadata.file_type().is_char_device()
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/// Whether this file is a block device on the filesystem.
|
|
|
|
|
pub fn is_block_device(&self) -> bool {
|
|
|
|
|
self.metadata.file_type().is_block_device()
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/// Whether this file is a socket on the filesystem.
|
|
|
|
|
pub fn is_socket(&self) -> bool {
|
|
|
|
|
self.metadata.file_type().is_socket()
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// Re-prefixes the path pointed to by this file, if it’s a symlink, to
|
2017-05-15 21:38:23 +00:00
|
|
|
|
/// make it an absolute path that can be accessed from whichever
|
|
|
|
|
/// directory exa is being run from.
|
|
|
|
|
fn reorient_target_path(&self, path: &Path) -> PathBuf {
|
|
|
|
|
if path.is_absolute() {
|
|
|
|
|
path.to_path_buf()
|
|
|
|
|
}
|
2017-06-29 12:07:45 +00:00
|
|
|
|
else if let Some(dir) = self.parent_dir {
|
2017-05-15 21:38:23 +00:00
|
|
|
|
dir.join(&*path)
|
|
|
|
|
}
|
|
|
|
|
else if let Some(parent) = self.path.parent() {
|
|
|
|
|
parent.join(&*path)
|
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
self.path.join(&*path)
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/// Again assuming this file is a symlink, follows that link and returns
|
|
|
|
|
/// the result of following it.
|
|
|
|
|
///
|
|
|
|
|
/// For a working symlink that the user is allowed to follow,
|
|
|
|
|
/// this will be the `File` object at the other end, which can then have
|
|
|
|
|
/// its name, colour, and other details read.
|
2015-01-24 17:26:26 +00:00
|
|
|
|
///
|
2017-05-15 21:38:23 +00:00
|
|
|
|
/// For a broken symlink, returns where the file *would* be, if it
|
|
|
|
|
/// existed. If this file cannot be read at all, returns the error that
|
|
|
|
|
/// we got when we tried to read it.
|
2016-10-29 19:27:23 +00:00
|
|
|
|
pub fn link_target(&self) -> FileTarget<'dir> {
|
2017-05-15 21:38:23 +00:00
|
|
|
|
|
|
|
|
|
// We need to be careful to treat the path actually pointed to by
|
2017-09-01 18:13:47 +00:00
|
|
|
|
// this file — which could be absolute or relative — to the path
|
|
|
|
|
// we actually look up and turn into a `File` — which needs to be
|
2017-05-15 21:38:23 +00:00
|
|
|
|
// absolute to be accessible from any directory.
|
2017-08-19 12:53:33 +00:00
|
|
|
|
debug!("Reading link {:?}", &self.path);
|
2017-06-29 12:07:45 +00:00
|
|
|
|
let path = match fs::read_link(&self.path) {
|
|
|
|
|
Ok(p) => p,
|
|
|
|
|
Err(e) => return FileTarget::Err(e),
|
2015-05-11 22:28:01 +00:00
|
|
|
|
};
|
|
|
|
|
|
2017-06-29 12:07:45 +00:00
|
|
|
|
let absolute_path = self.reorient_target_path(&path);
|
2014-11-25 20:50:23 +00:00
|
|
|
|
|
2017-05-15 21:38:23 +00:00
|
|
|
|
// Use plain `metadata` instead of `symlink_metadata` - we *want* to
|
|
|
|
|
// follow links.
|
2017-08-19 11:22:17 +00:00
|
|
|
|
match fs::metadata(&absolute_path) {
|
|
|
|
|
Ok(metadata) => {
|
|
|
|
|
let ext = File::ext(&path);
|
|
|
|
|
let name = File::filename(&path);
|
2019-07-13 20:14:42 +00:00
|
|
|
|
FileTarget::Ok(Box::new(File { parent_dir: None, path, ext, metadata, name, is_all_all: false }))
|
2017-08-19 11:22:17 +00:00
|
|
|
|
}
|
|
|
|
|
Err(e) => {
|
|
|
|
|
error!("Error following link {:?}: {:#?}", &path, e);
|
|
|
|
|
FileTarget::Broken(path)
|
|
|
|
|
}
|
2014-06-21 18:39:27 +00:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// This file’s number of hard links.
|
2015-01-24 12:38:05 +00:00
|
|
|
|
///
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// It also reports whether this is both a regular file, and a file with
|
|
|
|
|
/// multiple links. This is important, because a file with multiple links
|
2017-09-01 18:13:47 +00:00
|
|
|
|
/// is uncommon, while you come across directories and other types
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// with multiple links much more often. Thus, it should get highlighted
|
|
|
|
|
/// more attentively.
|
2015-05-12 02:33:40 +00:00
|
|
|
|
pub fn links(&self) -> f::Links {
|
2015-06-16 23:49:29 +00:00
|
|
|
|
let count = self.metadata.nlink();
|
2015-05-11 22:28:01 +00:00
|
|
|
|
|
2015-05-12 02:33:40 +00:00
|
|
|
|
f::Links {
|
2018-06-19 12:58:03 +00:00
|
|
|
|
count,
|
2015-05-11 22:28:01 +00:00
|
|
|
|
multiple: self.is_file() && count > 1,
|
|
|
|
|
}
|
2015-01-24 12:38:05 +00:00
|
|
|
|
}
|
|
|
|
|
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// This file's inode.
|
2015-05-12 02:33:40 +00:00
|
|
|
|
pub fn inode(&self) -> f::Inode {
|
2015-06-16 23:49:29 +00:00
|
|
|
|
f::Inode(self.metadata.ino())
|
2015-01-24 12:38:05 +00:00
|
|
|
|
}
|
|
|
|
|
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// This file's number of filesystem blocks.
|
|
|
|
|
///
|
|
|
|
|
/// (Not the size of each block, which we don't actually report on)
|
2015-05-12 02:33:40 +00:00
|
|
|
|
pub fn blocks(&self) -> f::Blocks {
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
if self.is_file() || self.is_link() {
|
2015-06-16 23:49:29 +00:00
|
|
|
|
f::Blocks::Some(self.metadata.blocks())
|
2015-01-24 12:38:05 +00:00
|
|
|
|
}
|
|
|
|
|
else {
|
2015-05-12 02:33:40 +00:00
|
|
|
|
f::Blocks::None
|
2015-01-24 12:38:05 +00:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// The ID of the user that own this file.
|
2015-05-12 02:33:40 +00:00
|
|
|
|
pub fn user(&self) -> f::User {
|
2015-06-16 23:49:29 +00:00
|
|
|
|
f::User(self.metadata.uid())
|
2015-01-24 12:38:05 +00:00
|
|
|
|
}
|
|
|
|
|
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// The ID of the group that owns this file.
|
2015-05-12 02:33:40 +00:00
|
|
|
|
pub fn group(&self) -> f::Group {
|
2015-06-16 23:49:29 +00:00
|
|
|
|
f::Group(self.metadata.gid())
|
2015-01-24 12:38:05 +00:00
|
|
|
|
}
|
|
|
|
|
|
2017-05-19 08:27:38 +00:00
|
|
|
|
/// This file’s size, if it’s a regular file.
|
2015-01-24 12:38:05 +00:00
|
|
|
|
///
|
|
|
|
|
/// For directories, no size is given. Although they do have a size on
|
2017-05-19 08:27:38 +00:00
|
|
|
|
/// some filesystems, I’ve never looked at one of those numbers and gained
|
|
|
|
|
/// any information from it. So it’s going to be hidden instead.
|
|
|
|
|
///
|
|
|
|
|
/// Block and character devices return their device IDs, because they
|
|
|
|
|
/// usually just have a file size of zero.
|
2015-05-12 02:33:40 +00:00
|
|
|
|
pub fn size(&self) -> f::Size {
|
2015-02-26 14:05:26 +00:00
|
|
|
|
if self.is_directory() {
|
2015-05-12 02:33:40 +00:00
|
|
|
|
f::Size::None
|
2014-11-25 20:50:23 +00:00
|
|
|
|
}
|
2017-05-19 08:20:47 +00:00
|
|
|
|
else if self.is_char_device() || self.is_block_device() {
|
|
|
|
|
let dev = self.metadata.rdev();
|
2017-05-20 20:55:18 +00:00
|
|
|
|
f::Size::DeviceIDs(f::DeviceIDs {
|
2017-05-19 08:20:47 +00:00
|
|
|
|
major: (dev / 256) as u8,
|
|
|
|
|
minor: (dev % 256) as u8,
|
2017-05-20 20:55:18 +00:00
|
|
|
|
})
|
2017-05-19 08:20:47 +00:00
|
|
|
|
}
|
2014-11-25 20:50:23 +00:00
|
|
|
|
else {
|
2015-05-16 17:16:35 +00:00
|
|
|
|
f::Size::Some(self.metadata.len())
|
2014-05-25 14:52:36 +00:00
|
|
|
|
}
|
2014-05-04 20:33:14 +00:00
|
|
|
|
}
|
|
|
|
|
|
2017-07-05 22:07:27 +00:00
|
|
|
|
/// This file’s last modified timestamp.
|
2019-07-31 22:43:31 +00:00
|
|
|
|
/// If the file's time is invalid, assume it was modified today
|
2018-12-17 01:51:55 +00:00
|
|
|
|
pub fn modified_time(&self) -> Duration {
|
2019-12-20 04:15:43 +00:00
|
|
|
|
match self.metadata.modified() {
|
|
|
|
|
Ok(system_time) => system_time.duration_since(UNIX_EPOCH).unwrap(),
|
|
|
|
|
Err(_) => Duration::new(0, 0),
|
2019-07-31 22:43:31 +00:00
|
|
|
|
}
|
2015-11-15 16:12:16 +00:00
|
|
|
|
}
|
|
|
|
|
|
2018-12-17 04:46:50 +00:00
|
|
|
|
/// This file’s last changed timestamp.
|
|
|
|
|
pub fn changed_time(&self) -> Duration {
|
|
|
|
|
Duration::new(self.metadata.ctime() as u64, self.metadata.ctime_nsec() as u32)
|
2015-11-15 16:12:16 +00:00
|
|
|
|
}
|
2015-02-09 18:14:05 +00:00
|
|
|
|
|
2017-07-05 22:07:27 +00:00
|
|
|
|
/// This file’s last accessed timestamp.
|
2019-07-31 22:43:31 +00:00
|
|
|
|
/// If the file's time is invalid, assume it was accessed today
|
2018-12-17 01:51:55 +00:00
|
|
|
|
pub fn accessed_time(&self) -> Duration {
|
2019-12-20 04:15:43 +00:00
|
|
|
|
match self.metadata.accessed() {
|
|
|
|
|
Ok(system_time) => system_time.duration_since(UNIX_EPOCH).unwrap(),
|
|
|
|
|
Err(_) => Duration::new(0, 0),
|
2019-07-31 22:43:31 +00:00
|
|
|
|
}
|
2015-11-15 16:12:16 +00:00
|
|
|
|
}
|
2015-02-09 18:14:05 +00:00
|
|
|
|
|
2018-12-17 01:51:55 +00:00
|
|
|
|
/// This file’s created timestamp.
|
2019-07-31 22:43:31 +00:00
|
|
|
|
/// If the file's time is invalid, assume it was created today
|
2018-12-17 01:51:55 +00:00
|
|
|
|
pub fn created_time(&self) -> Duration {
|
2019-12-20 04:15:43 +00:00
|
|
|
|
match self.metadata.created() {
|
|
|
|
|
Ok(system_time) => system_time.duration_since(UNIX_EPOCH).unwrap(),
|
|
|
|
|
Err(_) => Duration::new(0, 0),
|
2019-07-31 22:43:31 +00:00
|
|
|
|
}
|
2015-02-09 16:33:27 +00:00
|
|
|
|
}
|
|
|
|
|
|
2017-07-05 22:07:27 +00:00
|
|
|
|
/// This file’s ‘type’.
|
2015-01-24 12:38:05 +00:00
|
|
|
|
///
|
2017-07-05 22:07:27 +00:00
|
|
|
|
/// This is used a the leftmost character of the permissions column.
|
|
|
|
|
/// The file type can usually be guessed from the colour of the file, but
|
|
|
|
|
/// ls puts this character there.
|
2016-04-16 19:01:45 +00:00
|
|
|
|
pub fn type_char(&self) -> f::Type {
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
if self.is_file() {
|
2015-05-12 02:33:40 +00:00
|
|
|
|
f::Type::File
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
}
|
|
|
|
|
else if self.is_directory() {
|
2015-05-12 02:33:40 +00:00
|
|
|
|
f::Type::Directory
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
}
|
|
|
|
|
else if self.is_pipe() {
|
2015-05-12 02:33:40 +00:00
|
|
|
|
f::Type::Pipe
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
}
|
|
|
|
|
else if self.is_link() {
|
2015-05-12 02:33:40 +00:00
|
|
|
|
f::Type::Link
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
}
|
2016-06-14 03:14:36 +00:00
|
|
|
|
else if self.is_char_device() {
|
|
|
|
|
f::Type::CharDevice
|
|
|
|
|
}
|
|
|
|
|
else if self.is_block_device() {
|
|
|
|
|
f::Type::BlockDevice
|
|
|
|
|
}
|
|
|
|
|
else if self.is_socket() {
|
|
|
|
|
f::Type::Socket
|
|
|
|
|
}
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
|
else {
|
2015-05-12 02:33:40 +00:00
|
|
|
|
f::Type::Special
|
2014-05-04 20:33:14 +00:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2017-05-21 09:48:27 +00:00
|
|
|
|
/// This file’s permissions, with flags for each bit.
|
2015-05-12 02:33:40 +00:00
|
|
|
|
pub fn permissions(&self) -> f::Permissions {
|
2017-05-30 14:29:29 +00:00
|
|
|
|
let bits = self.metadata.mode();
|
2015-05-11 22:28:01 +00:00
|
|
|
|
let has_bit = |bit| { bits & bit == bit };
|
|
|
|
|
|
2015-05-12 02:33:40 +00:00
|
|
|
|
f::Permissions {
|
2015-11-04 14:56:37 +00:00
|
|
|
|
user_read: has_bit(modes::USER_READ),
|
|
|
|
|
user_write: has_bit(modes::USER_WRITE),
|
|
|
|
|
user_execute: has_bit(modes::USER_EXECUTE),
|
2017-05-30 14:29:29 +00:00
|
|
|
|
|
2015-11-04 14:56:37 +00:00
|
|
|
|
group_read: has_bit(modes::GROUP_READ),
|
|
|
|
|
group_write: has_bit(modes::GROUP_WRITE),
|
|
|
|
|
group_execute: has_bit(modes::GROUP_EXECUTE),
|
2017-05-30 14:29:29 +00:00
|
|
|
|
|
2015-11-04 14:56:37 +00:00
|
|
|
|
other_read: has_bit(modes::OTHER_READ),
|
|
|
|
|
other_write: has_bit(modes::OTHER_WRITE),
|
|
|
|
|
other_execute: has_bit(modes::OTHER_EXECUTE),
|
2017-05-30 14:29:29 +00:00
|
|
|
|
|
|
|
|
|
sticky: has_bit(modes::STICKY),
|
|
|
|
|
setgid: has_bit(modes::SETGID),
|
|
|
|
|
setuid: has_bit(modes::SETUID),
|
2014-05-26 10:50:46 +00:00
|
|
|
|
}
|
|
|
|
|
}
|
2015-01-24 12:38:05 +00:00
|
|
|
|
|
2017-07-05 22:07:27 +00:00
|
|
|
|
/// Whether this file’s extension is any of the strings that get passed in.
|
2015-05-16 15:10:58 +00:00
|
|
|
|
///
|
|
|
|
|
/// This will always return `false` if the file has no extension.
|
2015-05-09 15:10:26 +00:00
|
|
|
|
pub fn extension_is_one_of(&self, choices: &[&str]) -> bool {
|
|
|
|
|
match self.ext {
|
|
|
|
|
Some(ref ext) => choices.contains(&&ext[..]),
|
|
|
|
|
None => false,
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2015-05-16 15:10:58 +00:00
|
|
|
|
/// Whether this file's name, including extension, is any of the strings
|
|
|
|
|
/// that get passed in.
|
2015-05-09 15:10:26 +00:00
|
|
|
|
pub fn name_is_one_of(&self, choices: &[&str]) -> bool {
|
|
|
|
|
choices.contains(&&self.name[..])
|
|
|
|
|
}
|
2015-01-24 12:38:05 +00:00
|
|
|
|
}
|
|
|
|
|
|
2016-06-14 03:14:36 +00:00
|
|
|
|
|
2016-03-31 22:13:15 +00:00
|
|
|
|
impl<'a> AsRef<File<'a>> for File<'a> {
|
|
|
|
|
fn as_ref(&self) -> &File<'a> {
|
2017-03-31 16:09:32 +00:00
|
|
|
|
self
|
2016-03-31 22:13:15 +00:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2015-02-23 11:32:35 +00:00
|
|
|
|
|
2016-10-29 19:27:23 +00:00
|
|
|
|
/// The result of following a symlink.
|
|
|
|
|
pub enum FileTarget<'dir> {
|
|
|
|
|
|
|
|
|
|
/// The symlink pointed at a file that exists.
|
2018-06-19 12:58:03 +00:00
|
|
|
|
Ok(Box<File<'dir>>),
|
2016-10-29 19:27:23 +00:00
|
|
|
|
|
|
|
|
|
/// The symlink pointed at a file that does not exist. Holds the path
|
|
|
|
|
/// where the file would be, if it existed.
|
|
|
|
|
Broken(PathBuf),
|
|
|
|
|
|
|
|
|
|
/// There was an IO error when following the link. This can happen if the
|
2017-05-07 14:14:06 +00:00
|
|
|
|
/// file isn’t a link to begin with, but also if, say, we don’t have
|
2016-10-29 19:27:23 +00:00
|
|
|
|
/// permission to follow it.
|
|
|
|
|
Err(IOError),
|
2017-05-15 21:38:23 +00:00
|
|
|
|
|
|
|
|
|
// Err is its own variant, instead of having the whole thing be inside an
|
|
|
|
|
// `IOResult`, because being unable to follow a symlink is not a serious
|
|
|
|
|
// error -- we just display the error message and move on.
|
2016-10-29 19:27:23 +00:00
|
|
|
|
}
|
|
|
|
|
|
2017-05-07 13:45:04 +00:00
|
|
|
|
impl<'dir> FileTarget<'dir> {
|
2017-05-07 14:14:06 +00:00
|
|
|
|
|
|
|
|
|
/// Whether this link doesn’t lead to a file, for whatever reason. This
|
|
|
|
|
/// gets used to determine how to highlight the link in grid views.
|
2017-05-07 13:45:04 +00:00
|
|
|
|
pub fn is_broken(&self) -> bool {
|
2017-05-07 16:15:22 +00:00
|
|
|
|
match *self {
|
2017-05-07 16:39:01 +00:00
|
|
|
|
FileTarget::Ok(_) => false,
|
|
|
|
|
FileTarget::Broken(_) | FileTarget::Err(_) => true,
|
2017-05-07 13:45:04 +00:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2016-10-29 19:27:23 +00:00
|
|
|
|
|
2017-05-21 09:48:27 +00:00
|
|
|
|
/// More readable aliases for the permission bits exposed by libc.
|
|
|
|
|
#[allow(trivial_numeric_casts)]
|
|
|
|
|
mod modes {
|
|
|
|
|
use libc;
|
|
|
|
|
|
|
|
|
|
pub type Mode = u32;
|
|
|
|
|
// The `libc::mode_t` type’s actual type varies, but the value returned
|
|
|
|
|
// from `metadata.permissions().mode()` is always `u32`.
|
|
|
|
|
|
|
|
|
|
pub const USER_READ: Mode = libc::S_IRUSR as Mode;
|
|
|
|
|
pub const USER_WRITE: Mode = libc::S_IWUSR as Mode;
|
|
|
|
|
pub const USER_EXECUTE: Mode = libc::S_IXUSR as Mode;
|
2017-05-30 14:29:29 +00:00
|
|
|
|
|
2017-05-21 09:48:27 +00:00
|
|
|
|
pub const GROUP_READ: Mode = libc::S_IRGRP as Mode;
|
|
|
|
|
pub const GROUP_WRITE: Mode = libc::S_IWGRP as Mode;
|
|
|
|
|
pub const GROUP_EXECUTE: Mode = libc::S_IXGRP as Mode;
|
2017-05-30 14:29:29 +00:00
|
|
|
|
|
2017-05-21 09:48:27 +00:00
|
|
|
|
pub const OTHER_READ: Mode = libc::S_IROTH as Mode;
|
|
|
|
|
pub const OTHER_WRITE: Mode = libc::S_IWOTH as Mode;
|
|
|
|
|
pub const OTHER_EXECUTE: Mode = libc::S_IXOTH as Mode;
|
2017-05-30 14:29:29 +00:00
|
|
|
|
|
|
|
|
|
pub const STICKY: Mode = libc::S_ISVTX as Mode;
|
|
|
|
|
pub const SETGID: Mode = libc::S_ISGID as Mode;
|
|
|
|
|
pub const SETUID: Mode = libc::S_ISUID as Mode;
|
2017-05-21 09:48:27 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2015-05-16 17:33:08 +00:00
|
|
|
|
#[cfg(test)]
|
2017-06-29 12:07:45 +00:00
|
|
|
|
mod ext_test {
|
|
|
|
|
use super::File;
|
2015-11-04 10:07:08 +00:00
|
|
|
|
use std::path::Path;
|
2015-01-25 13:04:15 +00:00
|
|
|
|
|
2015-01-25 13:47:07 +00:00
|
|
|
|
#[test]
|
|
|
|
|
fn extension() {
|
2017-06-29 12:07:45 +00:00
|
|
|
|
assert_eq!(Some("dat".to_string()), File::ext(Path::new("fester.dat")))
|
2015-01-25 13:47:07 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn dotfile() {
|
2017-06-29 12:07:45 +00:00
|
|
|
|
assert_eq!(Some("vimrc".to_string()), File::ext(Path::new(".vimrc")))
|
2015-01-25 13:47:07 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn no_extension() {
|
2017-06-29 12:07:45 +00:00
|
|
|
|
assert_eq!(None, File::ext(Path::new("jarlsberg")))
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#[cfg(test)]
|
|
|
|
|
mod filename_test {
|
|
|
|
|
use super::File;
|
|
|
|
|
use std::path::Path;
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn file() {
|
|
|
|
|
assert_eq!("fester.dat", File::filename(Path::new("fester.dat")))
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn no_path() {
|
|
|
|
|
assert_eq!("foo.wha", File::filename(Path::new("/var/cache/foo.wha")))
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn here() {
|
|
|
|
|
assert_eq!(".", File::filename(Path::new(".")))
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn there() {
|
|
|
|
|
assert_eq!("..", File::filename(Path::new("..")))
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn everywhere() {
|
|
|
|
|
assert_eq!("..", File::filename(Path::new("./..")))
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn topmost() {
|
|
|
|
|
assert_eq!("/", File::filename(Path::new("/")))
|
2015-11-04 10:07:08 +00:00
|
|
|
|
}
|
2015-01-25 13:04:15 +00:00
|
|
|
|
}
|