Mercurial > vim
view runtime/doc/evim.man @ 35769:4f48d5d327ea v9.1.0609
patch 9.1.0609: outdated comments in Makefile
Commit: https://github.com/vim/vim/commit/4c3616d7a2c8c3b828e4d4ebbcd43e4a22154262
Author: Shane Harper <shane@shaneharper.net>
Date: Mon Jul 22 20:09:26 2024 +0200
patch 9.1.0609: outdated comments in Makefile
Problem: outdated comments in Makefile
Solution: update outdated comments, update rule for vimtags
(Shane Harper)
related: commit b81109192f
Here are the changes and the reasons for them:
- Delete the comment preceding the assignment to VIMPROG. Since b81109192f
there's no need for VIMPROG to be set to something else when this is executed
from src/Makefile. (The comment was wrong anyway; VIMPROG was being set to
"$$BUILD_DIR/$(VIMTARGET)".)
```
# Set to $(VIMTARGET) when executed from src/Makefile.
VIMPROG = ../../src/vim
```
- Delete "`and installed`" in the following comment; The vimtags rule doesn't
require that Vim has been installed.
```
# Use Vim to generate the tags file. Can only be used when Vim has been
# compiled and installed. Supports multiple languages.
vimtags: $(DOCS)
```
- With commit b81109192f there is no longer a need to set VIMPROG here:
```
-@BUILD_DIR="`pwd`"; cd $(HELPSOURCE); if test -z "$(CROSS_COMPILING)"; then \
$(MAKE) VIMPROG="$$BUILD_DIR/$(VIMTARGET)" vimtags; fi
```
The new code below will use the same vim executable as the old code:
```
-@cd $(HELPSOURCE); if test -z "$(CROSS_COMPILING)"; then \
$(MAKE) vimtags; fi
```
- Delete the following comment which was related to setting VIMPROG as it no longer has any value:
```
# We can assume Vim was build, but it may not have been installed,
# thus use the executable in the current directory.
```
Note: this comment used to be (unnecessarily) echoed to the terminal (because
it was indented) when making installrtbase.
closes: #15320
Signed-off-by: Shane Harper <shane@shaneharper.net>
Signed-off-by: Christian Brabandt <cb@256bit.org>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Mon, 22 Jul 2024 20:30:07 +0200 |
parents | 4a588e3afd4a |
children | 4a958ef2dc5e |
line wrap: on
line source
EVIM(1) EVIM(1) NAME evim - easy Vim, edit a file with Vim and setup for modeless editing SYNOPSIS evim [options] [file ..] eview DESCRIPTION eVim starts Vim and sets options to make it behave like a modeless edi- tor. This is still Vim but used as a point-and-click editor. This feels a lot like using Notepad on MS-Windows. eVim will always run in the GUI, to enable the use of menus and toolbar. Only to be used for people who really can't work with Vim in the normal way. Editing will be much less efficient. eview is the same, but starts in read-only mode. It works just like evim -R. See vim(1) for details about Vim, options, etc. The 'insertmode' option is set to be able to type text directly. Mappings are setup to make Copy and Paste work with the MS-Windows keys. CTRL-X cuts text, CTRL-C copies text and CTRL-V pastes text. Use CTRL-Q to obtain the original meaning of CTRL-V. OPTIONS See vim(1). FILES /usr/local/lib/vim/evim.vim The script loaded to initialize eVim. AKA Also Known As "Vim for gumbies". When using evim you are expected to take a handkerchief, make a knot in each corner and wear it on your head. SEE ALSO vim(1) AUTHOR Most of Vim was made by Bram Moolenaar, with a lot of help from others. See the Help/Credits menu. 2002 February 16 EVIM(1)