| Age | Commit message (Collapse) | Author |
|
|
|
|
|
* Don't bother prefixing commands with a line of ${_MKCMD}\
and instead rely upon "make -s". This is less intrusive on
all the Makefiles than the former. Idea from David Laight.
* Rename the variables use to print messages. The scheme now is:
_MKMSG_FOO Run _MKMSG 'foo'
_MKTARGET_FOO Run _MKMSG_FOO ${.TARGET}
From discussion with Alistair Crooks.
|
|
|
|
search fails to find a matching tag in any of the tags files, try a full
linear search.
|
|
|
|
Modify options.awk to detect an incorrectly sorted options array.
NB: if GTAGS is undefined theses sources will still generate invalid programs.
|
|
|
|
|
|
in options.c.
Is there any reason why we don't use options.awk so this file would
always be correct? (especially if the awk script checked the sort)
|
|
|
|
|
|
Add a 'matchchars' option to set the character pairs that % looks for.
Traditionally this was []{}() but someone added <> to nvi - probably
for editing html, but it is a pain for C. :set matchars=[]{}() will
restore the traditional behaviour.
If the 'open' and 'close' characters are the same (eg "" or '') then % will
alternate forwards and backwards searches.
Use common code to detect options that must have an even number of characters.
|
|
|
|
Patches provided by Joel Baker in PR 22365, verified by myself.
|
|
program/tool from "FOO" to "TOOL_FOO". The new variables are:
TOOL_ASN1_COMPILE TOOL_CAP_MKDB TOOL_CAT TOOL_CKSUM TOOL_COMPILE_ET
TOOL_CONFIG TOOL_CRUNCHGEN TOOL_CTAGS TOOL_DB TOOL_EQN TOOL_FGEN
TOOL_GENCAT TOOL_GROFF TOOL_HEXDUMP TOOL_INDXBIB TOOL_INSTALLBOOT
TOOL_INSTALL_INFO TOOL_M4 TOOL_MAKEFS TOOL_MAKEINFO TOOL_MAKEWHATIS
TOOL_MDSETIMAGE TOOL_MENUC TOOL_MKCSMAPPER TOOL_MKESDB
TOOL_MKLOCALE TOOL_MKMAGIC TOOL_MKTEMP TOOL_MSGC TOOL_MTREE
TOOL_PAX TOOL_PIC TOOL_PREPMKBOOTIMAGE TOOL_PWD_MKDB TOOL_REFER
TOOL_ROFF_ASCII TOOL_ROFF_DVI TOOL_ROFF_HTML TOOL_ROFF_PS
TOOL_ROFF_RAW TOOL_RPCGEN TOOL_SOELIM TOOL_SUNLABEL TOOL_TBL
TOOL_UUDECODE TOOL_VGRIND TOOL_ZIC
For each, provide default in <bsd.sys.mk> of the form:
TOOL_FOO?= foo
and for the ${USETOOLS}=="yes" case in <bsd.own.mk>, provide override:
TOOL_FOO= ${TOOLDIR}/bin/${_TOOL_PREFIX}foo
Document all of these in bsd.README.
This cleans up a chunk of potential (and actual) namespace collision
within our build infrastructure, as well as improves consistency in
the share/mk documentation and provision of appropriate defaults for
each of these variables.
|
|
"flooding nvi['s insert mode] leads it to dump core"
|
|
Otherwise, (among other things) db_get() thinks it can re-use the TEXT buffers
when it's not true, leading to a crash because that TEXT buffer will be
released just before it is actually used to create a new one.
This fixes PR#21797.
|
|
|
|
stopgap measure to make vi recovery mostly functional on non-binary files.
The problem is that the db holding the recovery file can become corrupted,
in which case the data size of the line becomes huge. We use heuristics to
correct the size when we load a db in recovery mode. We could use a slightly
better heuristic (looking for ascii chars before correcting the length),
but it is not worth it. Another way would have been to trap the SEGV and
access data[len] and see if that worked, but that seemed exceedingly ugly.
|
|
difficult to read and understand. Most manuals of English style
therefore say that you should use "use".
|
|
":cs add" works when using a database file in the current directory, whichever
way we specify its name.
|
|
Fixes memory re-use after free().
. Fake a directory name of "." if given a path without '/'.
This makes ":cs add cscope.out" work, and behave like ":cs add ."
|
|
|
|
|
|
|
|
|
|
|
|
control variable that is checked against against "<= 255".
|
|
from vi.ref, and explain how to set "escapetime" to work-around the problem
described in PR 8277. This should close PR 8277.
|
|
doesn't have adverse side-effects.
|
|
side-effects, like the ones described in bin/15891 and bin/16210.
patch from Sven Verdoolaege (nvi maintainer)
|
|
|
|
Rev 1.6 fixes an obscure core-dump problem, but changes the long time
behaviour of cursor positioning when switching files.
"Fixes" PR bin/15891.
|
|
|
|
a second time. Checking for the plain temp filename was not enough,
as it may be set even though we are calling the function for the
first time.
fixes bin/15474 by Chuck Cranor
|
|
|
|
(vi dumped core when editing a new file after having edited another one)
affects common/exf.c
|
|
(vi dumped core when editing a new file after having edited another one)
|
|
This only affects #ifdef DEBUG code.
|
|
|
|
"underflow of cnt in vs_paint() by O_NUMBER_LENGTH when both leftright and
number options in use"
|
|
Simon Burge which came from the Debian project.
This is still not TRT, but it's correct, and it gets us closer to future
versions of nvi.
I'll do ART (A Right Thing) when I have time... That's why I'm committing
this now. :-/
This fixes FreeBSD PR#23912
|
|
|
|
|
|
|
|
|
|
O_NUMBER both are active. Patch from Debian bug report #79768.
|
|
pointed by Aymeric Vincent.
|
|
|