Tag Info

New answers tagged


man uses less internally, and less has -j option that is almost like scrolloff feature (see this answer). Negative values keep the searches at the bottom of the screen. So if you do info curl|less -j 4, you'll be able to search while keeping 4 lines above the text, and if you do info curl|less -j -4, you'll be able to search while keeping 4 lines below the ...


If the key does not contain any newlines, you could simply pipe it in. # cryptsetup luksFormat foobar.img originalkey WARNING! ======== This will overwrite data on foobar.img irrevocably. Are you sure? (Type uppercase yes): YES # cryptsetup luksAddKey foobar.img newkey < originalkey Unfortunately cryptsetup has several modes of handling keyfiles, ...


There is no standard; some combination of man command, info command | less, command -h, command --help, command -help (ugh, Java), looking around for a README, altagoobingleduckgoing, etc. must be used, depending on the command, how good the vendor is about writing documentation (OpenBSD is very good in this regard, others well maybe yeah about that). ...


You can use the fmt command, which as far as I know is present in any Linux distribution. man apropos | fmt -w 70 will wrap up lines at 70 characters.


You can use fold man cp | fold -w 20 will fold after each 20 characters(!). Note that this will cut words in two as the only option is "fold every 20 characters" taking care of this, you might use sed as follows (with dynamic line length) man cp | sed 's/.\{20\} /&\n/g' will add a newline after 20 random characters followed by a space (i.e. new ...


Try setting the COLUMNS environment variable. Works for me with man from mandb on Debian with groff 1.22.3. $ COLUMNS=60 man apropos | head APROPOS(1) Manual pager utils APROPOS(1) NAME apropos - search the manual page names and descrip‐ tions SYNOPSIS apropos [-dalv?V] [-e|-w|-r] [-s list] [-m sys‐ ...


May be more appropriate as a comment Another source for understanding the meaning of the command line utility argument syntax would be the Utility Argument Syntax conventions documented in Chapter 12 and Regular Expressions documented in Chapter 9 of the POSIX.1-2008 (2013 Edition) standard.

Top 50 recent answers are included