Difference between revisions of "Quickstart Tutorial"
(Outline) |
(→The Bare Essentials: Better structure, wrote start/quit parts) |
||
Line 7: | Line 7: | ||
== The Bare Essentials == | == The Bare Essentials == | ||
+ | |||
+ | === Launching Vifm === | ||
+ | |||
+ | ==== Run Vifm from a Terminal ==== | ||
+ | |||
+ | ''Without arguments'', like in | ||
+ | |||
+ | <source lang="bash"> | ||
+ | vifm | ||
+ | </source> | ||
+ | |||
+ | Vifm with no configuration starts with both panes in current directory of a | ||
+ | shell. | ||
+ | |||
+ | ''With single argument''', like in | ||
+ | |||
+ | <source lang="bash"> | ||
+ | vifm /bin | ||
+ | </source> | ||
+ | |||
+ | path changes left (or top) pane to specified path. In this case this pane is | ||
+ | also automatically set to be the active one (e.g. it owns cursor). | ||
+ | |||
+ | ''With two arguments'', like in | ||
+ | |||
+ | <source lang="bash"> | ||
+ | vifm /bin /tmp | ||
+ | </source> | ||
+ | |||
+ | the first one specifies path for the left (or top) pane and the second one for | ||
+ | the right (or bottom) pane. | ||
+ | |||
+ | See also [[Starting Vifm]]. | ||
+ | |||
+ | ==== Quitting ==== | ||
+ | |||
+ | Using normal mode (main mode, in which Vifm starts) shortcut <kbd>ZZ</kbd>. | ||
+ | |||
+ | Or with the help of command-line mode (the one entered after <kbd>:</kbd> is | ||
+ | pressed) command <code>:q</code>, which should be followed by the | ||
+ | <kbd>Enter</kdb> key to be executed. | ||
+ | |||
+ | See also [[Quitting Vifm]]. | ||
+ | |||
+ | === Navigation === | ||
'''TODO: cover following topics''' | '''TODO: cover following topics''' | ||
− | + | ||
− | + | * j,k | |
− | + | * [space]/[tab] | |
− | + | * h,l --> on a directory. Explain how to quit vim/vi if they hit 'l' on an file. | |
− | + | ||
− | + | === Opening files === | |
− | + | ||
− | + | '''TODO: cover following topics''' | |
− | + | ||
− | + | * If a launcher is already defined by default and installed [Enter] -- i think | |
− | + | * if run an unknown filetype without [[Defining a Filetype Association]], you must use the commandline. | |
− | + | **if the program runs within the terminal as text only, such as ls, type without the quotes, ':!!ls -al %c' and then press [Enter]. Explain that that is a commandline mode command and what each part of it does. link to a list of available command line commands. | |
− | + | **if you would like to continue using Vifm while the program runs, which is most likely the case if it runs in its own window, run the task in the background using '&'. For example, if you wanted to launch the terminal emulator xterm in the current directory use '!xterm &'. If xterm didn't work try gnome-terminal, urxvt, konsol, [https://en.wikipedia.org/wiki/List_of_terminal_emulators etc]. Did you noticed that you didn't need to specify the current directory? This is because Vifm launches '!' commands in the current directory. | |
+ | ** Press the [Enter] key (carriage return) to edit a file (or open a folder). (Change <code>set norunexec</code> to <code>set runexec</code> in <code>~/.vifm/vifmrc</code> to run executable files rather then open them for editing.) (Not sure if this this bullet should be included in the very basic tutorial???) | ||
+ | |||
*by now you should be able to do anything from with Vifm, if just might not be much fast then just using the command line. | *by now you should be able to do anything from with Vifm, if just might not be much fast then just using the command line. | ||
Revision as of 20:54, 21 September 2014
TODO: This should cover all of the most basic Tasks
TODO: I'll keep updating this with my biggest bumps in the learning curve as well.
This first part should give just enough information to allow the new user to navigate through the tree to any file/dir, open the file, and pass commands to the shell.
The Bare Essentials
Launching Vifm
Run Vifm from a Terminal
Without arguments, like in
vifm
Vifm with no configuration starts with both panes in current directory of a shell.
With single argument', like in
vifm /bin
path changes left (or top) pane to specified path. In this case this pane is also automatically set to be the active one (e.g. it owns cursor).
With two arguments, like in
vifm /bin /tmp
the first one specifies path for the left (or top) pane and the second one for the right (or bottom) pane.
See also Starting Vifm.
Quitting
Using normal mode (main mode, in which Vifm starts) shortcut ZZ.
Or with the help of command-line mode (the one entered after : is
pressed) command :q
, which should be followed by the
Enter</kdb> key to be executed.
See also Quitting Vifm.
TODO: cover following topics
- j,k
- [space]/[tab]
- h,l --> on a directory. Explain how to quit vim/vi if they hit 'l' on an file.
Opening files
TODO: cover following topics
- If a launcher is already defined by default and installed [Enter] -- i think
- if run an unknown filetype without Defining a Filetype Association, you must use the commandline.
- if the program runs within the terminal as text only, such as ls, type without the quotes, ':!!ls -al %c' and then press [Enter]. Explain that that is a commandline mode command and what each part of it does. link to a list of available command line commands.
- if you would like to continue using Vifm while the program runs, which is most likely the case if it runs in its own window, run the task in the background using '&'. For example, if you wanted to launch the terminal emulator xterm in the current directory use '!xterm &'. If xterm didn't work try gnome-terminal, urxvt, konsol, etc. Did you noticed that you didn't need to specify the current directory? This is because Vifm launches '!' commands in the current directory.
- Press the [Enter] key (carriage return) to edit a file (or open a folder). (Change
set norunexec
toset runexec
in~/.vifm/vifmrc
to run executable files rather then open them for editing.) (Not sure if this this bullet should be included in the very basic tutorial???)
- by now you should be able to do anything from with Vifm, if just might not be much fast then just using the command line.
Do Common Tasks Faster
TODO: cover following topics
- cd
- yank
- paste/put
- delete
- ....I really haven't figured out much more than this...yet!!
Basic configuration
TODO: cover following topics
- Setting options
- Making options persistent