You can also use the menuing system for your graphical environment. First, you can the graphical version of Vim from the command line by typing GVim.
On a Linux or Unix system, you have a couple of options. Of course you can also search for it using Spotlight. If you're using a Mac, you'll find MacVim in your applications folder.
MACVIM SCREENSHOTS WINDOWS
You can also use the Windows Search feature and look for GVim that way. If there are multiple options, select GVim which is the graphical version of Vim. For example, if you're on a window system you can use the Start menu to navigate to Vim. Start the graphical version of Vim like you would any other graphical application on your OS. These options aren't available to you in the command line only version of Vim. For example, if you want to access your systems clipboard or you want to use the File Explorer to open files, or you want to use the scroll wheel on your mouse to skim through a document. Yet another reason to use the GUI version of Vim is to take advantage of GUI only features. It makes sense to run Vim as a standalone graphical application as opposed to running it in a terminal window. It's just a heavy, graphical, focused environment. For example, I don't know many people who leave a command prompt open all the time on their window system. Another reason you might want to use a graphical version of Vim is that you really don't use the command line as part of your normal workflow. This way you don't have to use one editor in one place and another editor in another place. That graphical environment might be your Linux desktop, a Mac, or even a Window system. For example, if you're a Linux admin and you work with Vim all day on all of your servers, you might want to leverage that knowledge even when you're working in a graphical desktop environment. With that said, there are a couple of good reasons to use a graphical version of Vim.
MACVIM SCREENSHOTS HOW TO
So anything you already know how to do in Vim will also work in the GUI version too. The good news is that all of that knowledge you already have about Vim is transferable to the graphical user interface or GUI version of Vim.
If you use vim and haven’t got in the habit of using :lcd I highly recommend it.All the other lessons in this course have covered topics related to the command line or textual user interface version of Vim. I used it the other day with bundle show to dig through the source of two dependencies of my Rails project to better understand them. The status line displays the path of the current file based on the local current directory, so if I know where the current file is I can quickly figure out where the local current directory is. Another plugin, fugitive, bases its commands on the git repository of the current file so it works smoothly with different local directories as well.īang commands (like :!cp README.md ~/Desktop) also use the local current directory.įinally, after using it for a while it gets easy to tell which directory I’m in. Both Command-T and ack.vim search within the local current directory. Now, what’s really neat, is that a new window (created from commands such as :sp and :tabedit) gets the local directory of the window it’s created from. The current window is the current frame within the current tab. The :lcd command changes the path of the current window. , :lcd ~/Desktop, and :lcd /etc/apache2 all work. The path is relative to the current directory, so :lcd. You type :lcd path/to/directory in command mode. For a long time I didn’t use it, mainly because I didn’t understand how it works.įirst, using it is simple.
I find vim’s :lcd command to be quite useful.
0 kommentar(er)
