New answers tagged ls
Most if not all vi implementations prevent you to write the file if you use a regular save command like either ZZ, :w, :wq or :x, eg with vim: :w E45: 'readonly' option is set (add ! to override) On the other hand, if you tell vi to write the file despite its permissions, with using something like :x! or :wq!, the editor is temporarily relaxing the ...
Note: Due to legacy licensing reasons, most GNU/Linux distributions don’t include the original vi program as written by Bill Joy. Instead, the vi command is provided by running Vim in vi-compatibility mode. The following answer is based on running Vim with its vi-compatibility mode. Modifying a read-only file Vim warns the user if they modify the buffer of ...
That's the number of blocks used on the filesystem. The info utility on GNU/Linux machines will explain it in more detail. Run info coreutils ls I can only assume that your UNIX provides something similiar. To get a more human readable output run ls -ltrh Thus I presume that your GNU/Linux and UNIX machine use different blocksizes on their fs.
Try using find. find folder/ -d 1 -name '*abc' folder/: Path to search -d 1: Only search one level down. This prevents it from searching all subdirectories below the folder you're looking for. Remove this if you want that behavior. -name '*abc': The pattern to search for. More information can be gotten with man find.
Top 50 recent answers are included